Re: cubox-i does not boot after upgrade to bullseye
Am Montag, 27. Dezember 2021, 15:26:33 CET schrieb Rainer Dorsch:
> Hi,
>
> I upgraded a cubox-i from buster to bullseye. The upgrade went through
> without any issues. But after the upgrade the system does not boot anymore.
> The output of the serial console is below. The boot process hangs at
>
> [ 3.816424] Waiting for root device /dev/mmcblk1p2...
>
> Did the device enumeration change?
>
> How would I find out the new device name and how would I change the boot
> parameters (which apparently specifies /dev/mmcblk1p2 according to the
> output below)?
>
I tried to get an initramfs shell to better debug, but failed:
I understood from
https://wiki.debian.org/InitramfsDebug
that I should add
break=mountroot
as kernel parameter.
Then from
https://wiki.debian.org/U-boot
I understand that I can add the kernel parameters by
=> setenv bootargs ${bootargs} break=mountroot
=> boot
u-boot passes the parameter
[ 0.000000] Kernel command line: break=mountroot console=ttymxc0,115200
enable_wait_mode=off root=/dev/mmcblk1p2 rootfstype=ext4 ro rootwait
console=ttymxc0,115200 console=tty1
but the kernel seems to ignore the parameter and ends up again in
[ 3.818950] Waiting for root device /dev/mmcblk1p2...
Even if I copy the example literally,
=> setenv bootargs ${bootargs} init=/bin/bash
=> boot
u-boot passes the parameters
init=/bin/bash console=ttymxc0,115200 enable_wait_mode=off root=/dev/mmcblk1p2
rootfstype=ext4 ro rootwait console=ttymxc0,115200 console=tty1
but the kernel seems to ignore the parameter and ends up again in
[ 3.818950] Waiting for root device /dev/mmcblk1p2...
Any hint or advise how I get a debug shell is welcome.
Thanks
Rainer
--
Rainer Dorsch
http://bokomoko.de/
Reply to: