Raspberry pi 5 status

ebike said:
Ok, my data/time is all good now.

Another quick question: I have kodi started by openbox and openbox by startx, how do I get startx to run on boot from my normal user?
I have managed to autologin my user by changes to tty's, but it alludes me how to run startx when my user has auto logged in ....

EDIT: Ahh, found it: Placed "startx -- -nocursor" in ~/.profile, now Kodi boots from poweron .... yah!

By the way, anyone know how to get rid of the 10sec coundown on boot, and mute the text on bootup? boot_mute="YES" in loader.conf ?
Thanks, I want it to act more as a Kodi Kiosk machine ..
Click to expand...

You can edit /boot/loader.conf and add:

autoboot_delay="3"

Where 3 is seconds to wait until autoboot.
 
Paul Floyd said:
I just gave that a go and was pleasantly surprised how easy it was.
  1. Downloaded the most recent FreeBSD 15 aarch64 RPI image
  2. Put it onto a microSD card (I used the Raspberry Pi Imager on my mac, but I assume that dd would do the same)
  3. Tried booting that, didn't work, as expected
  4. Got out a USB flash drive, download the firmware image from the rpi5-uefi githib repo (the zip file from the link below "2. Download the firmware image")
  5. Extracted the 3 files from the zip file to the USB drive
  6. Plugged in the USB drive and booted.
Presto, FreeBSD.

OK, no ethernet, no wifi, fan at full speed.
Click to expand...
Hi,

I tried this steps and didn't work here. I can see the Raspberry image (red fruits on screen) but it fails saying I have no boot device able to continue (if needs screen, I can take when I get home).

I tried 15-CURRENT and 14.1R, same results. When I tried an old 13.2-RC1 image from an old rpi4, I got it to boot but have no ethernet (I have an extra realtek gigabit nic, and none are listed). USB nic works though.

I got to the EDK2 Setup menu and noticed that when I have the 13.2RC1 sdcard I have it listed as boot option, other versions I do not. Just to make sure, I run:

xzcat image.xz | dd of=(sdcar dev) bs=1M status=progress on Linux Mint.

Is there any missing steps?

Thanks,

none
 
Can you try the Raspberry Pi imager?

I don't know if all SD cards work. I used SanDisk 128 Gb Extreme PRO microSDXC cards (I have 3, one for Ubuntu [64G], one each for FreeBSD 14.1 and 15.0).
 
I sure can, just to be clear, will try using Raspberry Pi Imager and the img.xz from FreeBSD.org. My goal is to have 14.1R on it, so will try it first :)

Thanks,

if needs any testing, can count on me.

none
 
Paul Floyd said:
Can you try the Raspberry Pi imager?

I don't know if all SD cards work. I used SanDisk 128 Gb Extreme PRO microSDXC cards (I have 3, one for Ubuntu [64G], one each for FreeBSD 14.1 and 15.0).
Click to expand...
Hi,

same thing here using 14.1R. I used the RPI img.xz file. Should I change?

Note after some research: The sdcard from 13.2RC1 uses dos partition, when I use dd or RPI imager, all use GPT. I will try to create a card using dos partition and see what I get.

none
 
small update: I had the sdcard where I used the rpi imager and 14.1R for PI on it, placed it on the slot and got the memstick for arm64 on a flash drive, and that boot 0.3 you posted on another. I ran the install normally, it took forever to write files (more on that later) on the USB 3.0 flash drive, and my first reboot the sdcard boot fine. I really can't say why, it came to life. I removed the flash drive, sdcard again boots ok, to the image from PI preinstalled image you pointed out above. I changed and let just the flash drive and my installation I just did is booting, slow as hell. Installation tool more then 1 hour, booting took long time to edit /etc/fstab to correct a path. sdcard boots fine, flash drive, slow. I used the blue USB 3.0 port.

My pcie connected ethernet is there fine:

re0@pci1:1:0:0: class=0x020000 rev=0x15 hdr=0x00 vendor=0x10ec device=0x8168 subvendor=0x10ec subdevice=0x8168
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller'
class = network
subclass = ethernet

the onboard one is not. Can't find it, by my reading here I guess that was expected.

That's my progress so far. Thaks for the help. I still have no clue why the sdcar didn't work before.

none
 
Someone may want to try USB gadget mode ethernet. Not sure how hard this would be to get working, but helpful for people that don't already have a PCIe hat or USB NIC.

Is there any driver in progress for the Pi 5's onboard eth?
 
There was some discussion about this. IIRC the existing derivers should work but there are problems with handling the new pci device tree.

I'm not a kernel dev but if ever I have some free time I might give this a poke. The most annoying thing for me is the noise of the fan (my Pi is on the desk next to the keyboard).
 
I was wondering what the difference was from the Pi 4s ethernet. I'm running a web server on my Pi 5, and I'd like to run FreeBSD on it again. The fan thing wouldn't bother me, I think that would be a pretty easy fix too.
 
Paul Floyd said:
There was some discussion about this. IIRC the existing derivers should work but there are problems with handling the new pci device tree.

I'm not a kernel dev but if ever I have some free time I might give this a poke. The most annoying thing for me is the noise of the fan (my Pi is on the desk next to the keyboard).
Click to expand...
I understand you. Mine is also on my desk, slowing it down would help a lot... :)

Thanks for the work here.

lostgeek said:
I was wondering what the difference was from the Pi 4s ethernet. I'm running a web server on my Pi 5, and I'd like to run FreeBSD on it again. The fan thing wouldn't bother me, I think that would be a pretty easy fix too.
Click to expand...
I am also looking for this eth to work. My plan is to have my rpi5 running opnsense and acting as as router here :)
 
For those running FreeBSD on Raspberry Pi 5, does anyone get shutdown out of nothing?

I am compiling opnsense on it, and from time to time the box shuts down and I see no log on /var/log/messages. There is just:

Sep 15 11:41:13 rpi5 kernel: pid 33599 (conftest), jid 0, uid 0: exited on signal 11 (core dumped)
Sep 15 12:13:24 rpi5 kernel: pid 67321 (conftest), jid 0, uid 0: exited on signal 11 (core dumped)
Sep 15 12:13:30 rpi5 kernel: pid 71632 (conftest), jid 0, uid 0: exited on signal 11 (core dumped)
Sep 15 13:32:40 rpi5 kernel: pid 9596 (conftest), jid 0, uid 0: exited on signal 11 (core dumped)
Sep 15 14:04:48 rpi5 kernel: pid 17577 (conftest), jid 0, uid 0: exited on signal 11 (core dumped)
Sep 15 14:12:59 rpi5 kernel: pid 75714 (conftest), jid 0, uid 0: exited on signal 11 (core dumped)
Sep 15 14:25:52 rpi5 kernel: pid 22313 (conftest), jid 0, uid 0: exited on signal 11 (core dumped)
Sep 15 14:28:49 rpi5 kernel: pid 57777 (conftest), jid 0, uid 0: exited on signal 11 (core dumped)
Sep 15 14:36:14 rpi5 kernel: pid 9370 (conftest), jid 0, uid 0: exited on signal 11 (core dumped)

as last entries, but that says quite to nothing, as there are some before start it again.

I have a 33w power supply, used for another arm64 devices. I get to have the box running idling for days, but just since yesterday it has shutdown for at least 3 times :/

I now disabled the turbo option on config.txt.

just want to know if this is just here (hardware issue) or not.

Thanks,

none
 
Just installed FreeBSD 14.2-RELEASE on my Raspberry Pi 5 and it boots fine (using the EDK2 firmware images from worproject).

Now i wonder how to get WiFi working. The output of pciconf -lv is rather limited...

P_20250125_181724_1_1.jpg
 
It is not apparent (to me at least) how the wireless chip is connected on the Pi5. Here is the lspci output from Linux on my Pi5:

tingo@tipi5-linux:~ $ lspci
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21)
01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

it doesn't look like the Wi-Fi is on the usb bus either

tingo@tipi5-linux:~ $ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 006: ID 258a:2024 Glorious Model O- Wireless
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0461:4e8e Primax Electronics, Ltd HP USB Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
tingo@tipi5-linux:~ $ lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
|__ Port 2: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 6, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
|__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
 
I think you are on to something:
Code: 
tingo@tipi5-linux:~ $ dmesg | grep -i sdio
[    0.779374] mmc1: new ultra high speed DDR50 SDIO card at address 0001
[    4.243889] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
 
Interesting... The onboard GB Ethernet interface is part of the Rasp Pi southbridge iirc, I'd love to know if anyone hears of this working on freebsd so I can switch over on my Pi 5 server.

0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 38
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: 80000000-800fffff [size=1M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Capabilities: [48] Power Management version 3
Capabilities: [ac] Express Root Port (Slot-), MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [160] Virtual Channel
Capabilities: [180] Vendor Specific Information: ID=0000 Rev=0 Len=028 <?>
Capabilities: [240] L1 PM Substates
Capabilities: [300] Secondary PCI Express
Kernel driver in use: pcieport

0000:01:00.0 Non-Volatile memory controller: SK hynix Gold P31/PC711 NVMe Solid State Drive (prog-if 02 [NVM Express])
Subsystem: SK hynix Gold P31/BC711/PC711 NVMe Solid State Drive
Flags: bus master, fast devsel, latency 0, IRQ 38
Memory at 1b80000000 (64-bit, non-prefetchable) [size=16K]
Memory at 1b80004000 (32-bit, non-prefetchable) [size=4K]
Memory at 1b80005000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [80] Power Management version 3
Capabilities: [90] MSI: Enable- Count=1/16 Maskable+ 64bit+
Capabilities: [b0] MSI-X: Enable+ Count=33 Masked-
Capabilities: [c0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [160] Power Budgeting <?>
Capabilities: [1b8] Latency Tolerance Reporting
Capabilities: [300] Secondary PCI Express
Capabilities: [400] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Capabilities: [900] L1 PM Substates
Kernel driver in use: nvme

0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 44
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: 00000000-005fffff [size=6M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Capabilities: [48] Power Management version 3
Capabilities: [ac] Express Root Port (Slot-), MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [160] Virtual Channel
Capabilities: [180] Vendor Specific Information: ID=0000 Rev=0 Len=028 <?>
Capabilities: [240] L1 PM Substates
Capabilities: [300] Secondary PCI Express
Kernel driver in use: pcieport

0001:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at 1f00410000 (32-bit, non-prefetchable) [size=16K]
Memory at 1f00000000 (32-bit, non-prefetchable) [virtual] [size=4M]
Memory at 1f00400000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable+ Count=61 Masked-
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: rp1

In dmesg I grepped "ethernet" and this was all I found relevant:
[ 2.324859] macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 112 (mac:ad:dr:ess)
and
[ 5.287969] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL)

I am using the PCI-E header for PCI-E/NVM-E storage, otherwise I'd simply get an Intel nic and run that /w an adapter. I suppose there are "hats" which allow two PCIE devices to be run, but for the $ I can't really justify throwing more at the Pi when I have old amd64 stuff which'd probably do the job better anyway... Guess I can't say weather or not I'd chuck < $40 - $50 for a Nic and splitter.. definitely wouldn't spend a penny more though, for both needed items. I've heard USB3 nics aren't as good /w the latency / stability.
 
lostgeek said:
Interesting... The onboard GB Ethernet interface is part of the Rasp Pi southbridge iirc, I'd love to know if anyone hears of this working on freebsd so I can switch over on my Pi 5 server.
Click to expand...

There was a discouraging discussion of this a year ago on the mailing lists, linked by jsm in message 23 of this thread:

https://lists.freebsd.org/archives/freebsd-arm/2024-January/003568.html

It starts positively but soon peters out - the Cadence/GEM driver in /usr/src/sys/ is for device tree, not acpi, and they didn't get very far with device tree booting. It's worth reading the whole thread, I think, though it soon went over my head.

lostgeek said:
In dmesg I grepped "ethernet" and this was all I found relevant:
[ 2.324859] macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 112 (mac:ad:dr:ess)
and
[ 5.287969] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL)

I am using the PCI-E header for PCI-E/NVM-E storage, otherwise I'd simply get an Intel nic and run that /w an adapter. I suppose there are "hats" which allow two PCIE devices to be run, but for the $ I can't really justify throwing more at the Pi when I have old amd64 stuff which'd probably do the job better anyway... Guess I can't say weather or not I'd chuck < $40 - $50 for a Nic and splitter.. definitely wouldn't spend a penny more though, for both needed items. I've heard USB3 nics aren't as good /w the latency / stability.
Click to expand...

I have "TP-Link USB 3.0 to Gigabit Ethernet Network Adapter, USB to RJ45 Lan Wired Adapter for Ultrabook, Chromebook, Laptop, Desktop, Plug and Play for Nintendo Switch, Windows 10/8.1, and Linux OS(UE306)" from Amazon. I haven't done serious testing, but it's been fine for limited use downloading the source tree, doing package management and my little bit of FAFO, and inexpensive.
 
My Pi 4 that used to run FreeBSD got pressed into service yesterday, so it was time to get FreeBSD installed on the Pi 5.

On the Pi 4, I had FreeBSD 14.2 installed on a Silicon Power 512GB SD card (SU512GBSTXDU3V20AF) and tried just moving that over to the Pi 5 with a USB thumb drive populated with the v0.3 rpi5-uefi files. It didn't boot and I don't recall how that image was set up. For expediency, I grabbed the latest 14.2 rpi image and used the Raspberry Pi imager to flash it to the SD card. After popping that into the SD card slot, it booted straight to a FreeBSD login prompt.

I ordered my Pi 5 with an extra NIC via part #720-1 from pishop.us and that NIC works with no extra effort. It is recognized as:

Code: 
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet>

As expected, when I boot to Pi OS (Debian Bookworm), I get both wired NICs and WiFi working.

Also, I'm able to boot the Pi 5 into FreeBSD 14.2 with only the SD card by copying the two binary files into the /boot/efi partition and modifying the config.txt file. The Pi3/4 specific stuff needs to be moved from [all] into the [pi4] section and the contents from the config.txt included with rpi5-uefi download need to be added to a [pi5] section. Here's my config.txt:

Code: 
[all]
arm_64bit=1

[pi5]
armstub=RPI_EFI.fd
device_tree_address=0x1f0000
device_tree_end=0x210000

# Force 32 bpp framebuffer allocation.
framebuffer_depth=32

# Disable compensation for displays with overscan.
disable_overscan=1

# Force maximum USB power regardless of the power supply.
usb_max_current_enable=1

# Force maximum CPU speed.
force_turbo=0

[pi4]
hdmi_safe=1
armstub=armstub8-gic.bin

dtparam=audio=on,i2c_arm=on,spi=on
dtoverlay=mmc
dtoverlay=disable-bt
device_tree_address=0x4000
kernel=u-boot.bin

I suspect that with this configuration, this SD card can now boot a Pi 4 and a Pi 5.
 
Hi
I like FreeBSD and looking for something to build small and simple NAS. Thinking about using Pi 5 with PoE and, probably, NVMe HAT.
So could you help me with the following questions, please?

1. does FreeBSD supports RPi 5 onboard ethernet adapter? - I'm going to minimize everything to the very minimum, so I'd like to use PoE to avoid extra PSU and wires (my router has PoE output).

2. does FreeBSD supports RPi 5 PCIe/NVMe HAT for SSD?

3. does FreeBSD on RPi 5 supports USB ext drives and NTFS?

4. will I be able to install Samba on FreeBSD on RPi 5?

Thank you in advance )
 
Selin said:
Hi
I like FreeBSD and looking for something to build small and simple NAS. Thinking about using Pi 5 with PoE and, probably, NVMe HAT.
So could you help me with the following questions, please?

1. does FreeBSD supports RPi 5 onboard ethernet adapter? - I'm going to minimize everything to the very minimum, so I'd like to use PoE to avoid extra PSU and wires (my router has PoE output).
Click to expand...

No ethernet. I don't know if the PoE will work.

Selin said:
2. does FreeBSD supports RPi 5 PCIe/NVMe HAT for SSD?

3. does FreeBSD on RPi 5 supports USB ext drives and NTFS?

4. will I be able to install Samba on FreeBSD on RPi 5?
Click to expand...

I haven't tried any of the above. I don't see why Samba shouldn't work. From what I've read external USB disks that require power are a bit tricky with the Pi. The standard Pi power supply isn't powerful enough to drive a hard disk as well. And connecting a drive that is powered by USB to a Pi that is also connected to the standard power supply is risky. See for instance https://raspberrypi.stackexchange.com/questions/28310/whats-the-problem-with-backfeeding. This is just somethig that I've read about, I haven't experienced it personally.
 
1. does FreeBSD supports RPi 5 onboard ethernet adapter?
Click to expand...
Not at present. The UEFI doesn't have support for it.
3. does FreeBSD on RPi 5 supports USB ext drives and NTFS?
Click to expand...
USB external drives work for me. I have a USB to SATA cable that I plug into any of the stack of 2.5" SSDs and they all work just fine with my Pi4 and 5. I have no knowledge of using NTFS.
4. will I be able to install Samba on FreeBSD on RPi 5?
Click to expand...

Bash: 
pi5:~ % sudo pkg install -y samba419
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 71 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
    avahi-app: 0.8_2
    cyrus-sasl: 2.1.28_5
    dbus: 1.14.10_5,1
<snip>
[70/71] Extracting py311-markdown-3.6: 100%
[71/71] Installing samba419-4.19.9_4...
[71/71] Extracting samba419-4.19.9_4: 100%
<snip>
=====
Message from samba419-4.19.9_4:

--
How to start: http://wiki.samba.org/index.php/Samba4/HOWTO

I predict: yes.
 
Hi, I used raspberry imager to burn the FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img to a SD card but failed at verification step. Any tricks here?
 
Check if the sha512sum of the image is correct. If not, download the image again.

Code: 
SHA512 (FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img.xz) = 5f804bfa54f29247357e7b78bcc35d9dc231091d0fd79dec0443d2d48299826615f21eef2b0cd80360492581536af576dceb0af0f6709e51f16873fdd5ebc845

And you don't need to extract the xz first, the Raspberry imager can directly use the xz file.
 
eternal_noob said:
Check if the sha512sum of the image is correct. If not, download the image again.

Code: 
SHA512 (FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img.xz) = 5f804bfa54f29247357e7b78bcc35d9dc231091d0fd79dec0443d2d48299826615f21eef2b0cd80360492581536af576dceb0af0f6709e51f16873fdd5ebc845

And you don't need to extract the xz first, the Raspberry imager can directly use the xz file.
Click to expand...
SHA512 is correct.
I used dd command and it looks success.
 
You must log in or register to reply here.
Back
Top