My otherwise up-to-date Raspberry Pi 4 Model B used to boot just fine when booting from USB with uBoot but now becomes unresponsive (doesn’t reach gdm and doesn’t allow connection via ssh).
Curiously, num. lock key does respond, but I’m unable to switch consoles…
It boots just fine with UEFI v1.42
I remember updating the eeprom bootloader via the Raspberry Pi OS to the latest version though.
so that bootloader is something Fedora doesn’t provide… if there’s a bug in the bootloader that is preventing USB from booting..regardless of what OS is on that USB.. thats a something the bootloader provider needs to be told about.
My undersanding is that bootloader lives in a dedicated eeprom and raspi is providing it.
Fresh install of Fedora 43 Workstation Beta solved the issue.
However, instruction to prevent automatic suspend do not work anymore:
GNOME suspends after 15 minutes of user inactivity, even on AC power
Will probably submit a bug report, since we’re talking of a beta (another fine one)…
for other reasons I have a workstation 42 on a rpi4b right now. I need to confirm the suspend inhibit works for me as a baseline just to groundtruth before moving to 43 on this.
I have to say the pi’s .. unique… concept of suspend..is the thing that keeps me from using it a a little daily desktop. Maybe the pi5 gets me there.
I’m trying with this config:
sudo -u gdm dbus-run-session gsettings list-recursively org.gnome.settings-daemon.plugins.power | grep sleep
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type ‘nothing’
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 900
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type ‘suspend’
venerable leader, setting both
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type ‘nothing’
seem to have done the trick. No more pi going to sleep.
Happy Beta release day!