Raspberry Pi 5 Rev 1.1 16GB (D0 stepping): there is always a delay of one minute before booting selected OS
Machine: Raspberry Pi 5 Rev 1.1 16GB (D0 stepping) PINN version: 3.9.7 with kernel from previous 3.9.4.1 version (Linux recovery 6.1.54-v8 #1 SMP PREEMPT Mon Nov 25 01:14:45 GMT 2024 aarch64 GNU/Linux)
Problem summary: There is always a delay of one minute before booting selected OS. The curious thing is that it always take a minute no matter what you did into PINN. E.g.:
- Booting PINN and leaving the default OS auto boot makes PINN seems to be hanged during one minute until it suddenly start the OS.
- Booting PINN and enter in it, doing anything inside for (i.e.) about 40 seconds and then select an OS to boot makes PINN seems to be hanged during about 20 seconds until it suddenly start the OS. So you where really into PINN for 1 minute.
- If you stay in PINN more than one minute and select an OS to boot it's started immediately.
So it just take about a minute... I think there is some kind of timeout involved but I don't know how to check what is it.
To reproduce: No special steps to reproduce the bug. The delay of one minute always happens without interaction.
Expected behaviour: No delay at all once OS to boot is selected.
Important: Swapping only the "Raspberry Pi 5 Rev 1.1 16GB" with a "Raspberry Pi 4 Rev 1.4 8GB" makes PINN works as expected: the selected OS is always started without any delay at all.
So, IMO, problem should be located either in:
- Raspberry Pi 5.
- Raspberry Pi 5 16GB.
- Raspberry Pi 5 D0 stepping.
Additional info: Here is a dmesg, a /tmp/debug file and a /tmp/message file generated in the Raspberry Pi 5 after more than one minute from boot. Unfortunatley I didn't find anything that may help in these docs:
My config.txt file is the PINN shipped one and the cmdline.txt file is the same but "quiet" was removed and "loglevel" was changed from 2 to 8 to get more info at boot:
ramdisk_size=65536 root=/dev/ram0 init=/init vt.cur_default=1 elevator=deadline repo_list=http://raw.githubusercontent.com/procount/pinn-os/master/os/repo_list.json loglevel=8 sdhci.debug_quirks2=4
I can confirm this on my Raspberry Pi 500+. Since I set a default option - I don't see the boot menu at all. The default system just boots after 1 minute of showing the background image and a frozen mouse cursor. I'd suggest to change this to "bug" since when choosing a default option, the boot menu doesn't appear at all.
If you set a "sticky default" option, then that is what it is supposed to do - bypass the boot menu and boot your selected OS immediately. If you don't want that, please deselect the sticky default. If you have multiple OSes installed, you will then get the boot menu displayed for a few seconds. If you don't press anything it will boot the last OS booted, or you can choose another one.
Regarding the extra 1 minute delay, this is under investigation, but I think it only happens on the Pi5 family.