Sorry, but which kernel do you run?and what EEPROM version do you have?
pi@Pi5-3D-500:~ $ sudo rpi-eeprom-update -a
BOOTLOADER: up to date
CURRENT: Wed 5 Jun 15:41:49 UTC 2024 (1717602109)
LATEST: Wed 5 Jun 15:41:49 UTC 2024 (1717602109)
RELEASE: default (/lib/firmware/raspberrypi/bootloader-2712/default)
Use raspi-config to change the release.
I DON'T UNDERSTAND why people mess around with the boot order! Leave it at default until you have a valid reason for changing it. Having uSD in first place will always allow for booting from uSD in case the OS on the NVMe got messed-up. If one wants to boot from NVMe simply remove a bootable uSD from the slot!
Once you've made sure you're running the latest bootloader change your EEPROM config to belowRevert any changes you've made to config.txt!
Reboot and report back.
Code:
pi@Pi5-3D-500:~ $ uname -aLinux Pi5-3D-500 6.6.31+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linuxpi@Pi5-3D-500:~ $ sudo rpi-eeprom-update -a
BOOTLOADER: up to date
CURRENT: Wed 5 Jun 15:41:49 UTC 2024 (1717602109)
LATEST: Wed 5 Jun 15:41:49 UTC 2024 (1717602109)
RELEASE: default (/lib/firmware/raspberrypi/bootloader-2712/default)
Use raspi-config to change the release.
I DON'T UNDERSTAND why people mess around with the boot order! Leave it at default until you have a valid reason for changing it. Having uSD in first place will always allow for booting from uSD in case the OS on the NVMe got messed-up. If one wants to boot from NVMe simply remove a bootable uSD from the slot!
Once you've made sure you're running the latest bootloader change your EEPROM config to below
Code:
sudo -E rpi-eeprom-config --editCode:
[all]BOOT_UART=1PCIE_PROBE=1POWER_OFF_ON_HALT=1BOOT_ORDER=0xf461Reboot and report back.
Statistics: Posted by aBUGSworstnightmare — Wed Jun 26, 2024 4:56 am