I pretty much am stuck with this. No idea what else to bring the Pi Zero up and running
Not helping directly, but another example of an RPiZeroW booting and running 32-bit RasPiOS Bookworm Lite -
Code:
System Information------------------Raspberry Pi Zero W Rev 1.1PRETTY_NAME="Raspbian GNU/Linux 12 (bookworm)"NAME="Raspbian GNU/Linux"VERSION_ID="12"VERSION="12 (bookworm)"Raspberry Pi reference 2024-07-04Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 0b115f302a8f1e5bd3523614d7f45b9d447434c7, stage2Linux bw32l 6.6.51+rpt-rpi-v6 #1 Raspbian 1:6.6.51-1+rpt3 (2024-10-08) armv6l GNU/LinuxRevision: 9000c1Serial: 0000000086907c33Model: Raspberry Pi Zero W Rev 1.1Throttled flag : throttled=0x0Camera : supported=0 detected=0, libcamera interfaces=0david@bw32l:~ $ There are no mentions of kernel in the dmseg log as late as the ones you experience -
Code:
david@bw32l:~ $ dmesg | grep Kernel[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=B8:27:EB:90:7C:33 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 console=tty1 root=PARTUUID=ee6d9033-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=GB[ 5.913667] Kernel memory protection not selected by kernel config.[ 15.710819] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.[ 15.787009] systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System...[ 15.832475] systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System...[ 15.854632] systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).[ 16.077621] systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs...[ 16.184865] systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...[ 16.264134] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...[ 16.332929] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...[ 16.464274] systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse...[ 16.597246] systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...[ 17.002911] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...[ 17.115113] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...[ 17.598020] systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System.[ 17.668875] systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System.[ 18.013572] systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs.[ 18.113621] systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.[ 18.213194] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.[ 18.291904] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.[ 18.383580] systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse.[ 18.463107] systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.[ 18.505667] systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules.[ 18.551705] systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems.[ 18.891969] systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System...[ 19.244930] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...david@bw32l:~ $ The OS had been subject to an update + full_upgrade process immediately before this reboot.
Provided the microSD card was written correctly I find it difficult to believe that an RPiZeroW would either know or care what hardware/OS platform the card was prepared on.
That seems to leave two possibilities -
1. Your 3rd-party Power Supply is failing to keep up with demand at some key point in the boot process
2. Your RPiZeroW board is faulty.
Statistics: Posted by B.Goode — Wed Oct 23, 2024 10:30 am