On Mon, 15 Sept 2025 at 15:17, Benjamin M via arm <[email protected]> wrote: > > Yes, EDK2 v1.42, indeed. > > Can you provide more details? > > Fedora 42 Workstation > linux-firmware.noarch 20250808-1.fc42 updates > uboot-images-armv8.noarch 1:2025.04-2.fc42 updates > (and rpi-uboot-update has been run) > > Raspi's vcgencmd bootloader_version: > 2025/08/27 19:57:12 > version 000d3ca289ae790a2e46225eb11b319c67642b1a (release) > timestamp 1756321032 > update-time 1757416592 > capabilities 0x0000007f > > > Linux 6.14.0-63.fc42.aarch64 boots from USB and I'm able to ssh into the > > box, but it doesn't reach graphical.target > > When you say 'unresponse' how far does it get, what's on the screen? > It seems to vary when trying to boot Linux 6.16.7-200.fc42.aarch64: > Starting systemd-vconsole-setup.service - Virtual Console Setup... > [OK] Reached target usb-gadget.target - Hardware activated USB gadget. > [OK] Stopped systemd-vconsole-setup.service - Virtual Console Setup. > Starting systemd-vconsole-setup.service - Virtual Console Setup... > Listening on systemd-rfkill.socket - Load/Save RF K1ll Switch Status > /dev/rfkill Watch. > > Would some journalctl -x -p err exports of a failed and boots would help? > (working on my CLI-fu, Linux enthusiast not coming from an engineering > background) > > When did the problem start to occur? > After updating the eeprom bootloader via Rapsberry Pi OS around the end of > August IIRC and after upgrading Fedora's kernel version to 6.15 I think
What does the output of "dmesg | grep 'DMI:'" provide? -- _______________________________________________ arm mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
