Re: cubox-i does not boot after upgrade to bullseye

[Rainer Dorsch <ml@bokomoko.de>]

Am Dienstag, 28. Dezember 2021, 01:10:39 CET schrieb Rainer Dorsch:
> In order to exclude that I got something wrong with the UUID:
> Does root=/dev/mmcblk0p2 also work if ext4ls mmc 0:2 shows the rootfs?

At least the result is the same for /dev/mmcblk0p2:

[...]
[    3.743918] zswap: loaded using pool lzo/zbud
[    3.749114] Key type ._fscrypt registered
[    3.753212] Key type .fscrypt registered
[    3.757174] Key type fscrypt-provisioning registered
[    3.762439] AppArmor: AppArmor sha1 policy hashing enabled
[    3.794654] vcc_3v3: supplied by v_5v0
[    3.811521] List of all partitions:
[    3.815075] No filesystem could mount root, tried:
[    3.815079]
[    3.821507] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
[    3.829798] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-10-armmp #1 
Debian 5.10.84-1
[    3.837995] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
[    3.844536] Backtrace:

If a module is missing, would that be different for a new installation and an 
upgrade?

Thanks
Rainer


-- 
Rainer Dorsch
http://bokomoko.de/