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
 
You must log in or register to reply here.
Back
Top