Closed framps closed 1 year ago
For some reason you don't have the latest firmware.
I executed rpi-update which updated the firmware. Unfortunately I didn't check the UART messages and verified it happened before I updated and upgraded to the latest OS version. Looks like update and upgrade replaced the firmware with an older version. I will execute steps 1 and 2 now again and check the UART boot messages for the firmware update.
Firmware: 23aa699d0e70ed543c1ddcd17bed6446bfb6866e Oct 18 2022 17:40:43
shows up after step 2 and step 3.
Looks like update and upgrade replaced the firmware with an older version
qed :smiley:
ah yes - of course, sorry that catches me out as well.
NP, so there is no way I can test the fix until the next RaspbianOS > 09-22 is published?
You'd have to run rpi-update again, or alternatively copy start4.elf to your boot folder from here https://github.com/raspberrypi/firmware/tree/master/boot This is where rpi-boot gets it from.
That's what I did now:
1) Installed 04-04 lite OS 2) Upgraded the 04-04 OS to the current version with apt and didn't reboot 3) Executed rpi-update (has to be executed last because the OS update installs an old version of start4.elf)
Congratulations :+1: Now the OS boots successfully :smile:
I'll close this issue when the next OS Release is available and I verified an upgrade from 04-04 to this next release will boot. :wink:
Thanks.
@peterharperuk Is there already a target date for next OS Release or can you tell me where I can subscribe to get notified when the next OS Release is available? It's boring to check https://www.raspberrypi.com/software/operating-systems/ from time to time.
I just upgraded the 09-06-2022 image to new 01-21-2023. The system boots now again :+1:
I close this issue now as verified.
I just upgraded my RaspberyOS Bullseye on my CM4 with
sudo update && sudo upgrade
and finally wasn't able to boot the system any more :-(.Then I dd'd the actual image on the eMMc of the CM4 and everything works fine. When I dd'd the image on NMVe the system doesn't boot.
The image I used and does not boot on NVMe is
2022-09-06-raspios-bullseye-armhf-lite.img
.When I restore a backup I have created some time ago the system boots from NVMe. The system also boots when I restore
2022-04-04-raspios-bullseye-armhf-lite.img
which is the base of my restored backup.Looks like there is some issue with NVMe on latest image?