this 9 seconds containsOn the CM5 (with eMMC), boot seems to be really slow.
The red light flashes, then after half a second, the green light comes on; then it spends about 9 seconds doing "nothing", then the Linux boot process starts, and it's in Linux 2-7 seconds later.
* Using Raspberry Pi OS Lite, and auto-logging into the CLI, it goes from "power switch" to "bash prompt" in 16 seconds. Looking at dmesg, we see that it's been running for ~7 seconds at that point.
* Using TinyCore, it takes 11.5 seconds to boot, of which dmesg indicates 2.27 seconds in Linux.
So... what's happening that takes 9 seconds between the ACT light going green, and the kernel starting to show the 4x raspberries?
It feels like the bootloader must be probing for something, but I can't figure out what. I have the CM 5 (with embedded eMMC) on the IO board, and nothing else plugged in except a keyboard and monitor.
I already set the eeprom boot mode to 0xf1 (SD card, i.e. eMMC only, no probing).
I also tried disconnecting the HDMI entirely, and using a GPIO + @reboot cron job to indicate booted, and it still has this delay.
Thanks very much for your time and help.
1)the broadcom bcm2712 CPU and GPU Files
2)The Config Files
3)The main initrd and vmlinuz which contain the buildin modules of drivers like macb for network ethernet card
4)The Systemd
What i want to see:
1)A cleaner way to initialize the board by allowing use to use the linux 8k pages
which i still wonder why they exists and what they do
2)I dont want the rcX.d i am still wonder why it is needs its an old respectful by me services
so i need a way to choose between systemd and init rc.d model of service
3)A more cleaner way of the GUI environment initialize
so for now are have lxde kanshi openbox xfce-panels labwc all in a mix xD
Thats for me
Statistics: Posted by acheron_oscura — Tue Dec 02, 2025 8:52 am