NSA320 fails uboot after upgrade debian buster to bullseye (3 replies)

Hi Bodhi,

I first ugraded my kernel to the latest available and rebooted, that worked fine.
I was able to succesfully upgrade my NSA320 from Buster to Bullseye. But after the reboot it is not coming up. I have a serial-console and this is what is happening now:

NSA320> boot
Initializing devices...

Reset IDE: Bus 0: OK Bus 1: OK
  Device 0: Model: ST2000DL003-9VT166 Firm: CC45 Ser#: 5YD6LRQ4
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
  Device 1: Model: ST4000DM005-2DP166 Firm: 0001 Ser#: ZDH0CSKF
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 3815447.8 MB = 3726.0 GB (7814037168 x 512)
Unknown command 'mmc' - try 'help'
Loading envs from usb 0...
** Bad device usb 0 **
Loading envs from usb 1...
** Bad device usb 1 **
Loading envs from usb 2...
** Bad device usb 2 **
Loading envs from usb 3...
** Bad device usb 3 **
Loading envs from ide 0...
260 bytes read in 88 ms (2 KiB/s)
... envs loaded
importing envs ...
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: Bus 0: OK Bus 1: OK
  Device 0: Model: ST2000DL003-9VT166 Firm: CC45 Ser#: 5YD6LRQ4
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
  Device 1: Model: ST4000DM005-2DP166 Firm: 0001 Ser#: ZDH0CSKF
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 3815447.8 MB = 3726.0 GB (7814037168 x 512)
device ide 0:1
ext4fs_devread read outside partition 18446744073262735360
device ide 1:1
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-nsa320.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!

I have been googling for a cause, but the only thing I could find is about the mkfs.conf file with these things (mkfs.ext4 -O ^64bit /dev/sd... and such, there also was one other option), but I have dealt with that in the past. My filesystems were correctly formatted and working before the upgrade to Bullseye.
I did see in the upgrade output the following:

Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.19.2-kirkwood-tld-1
I: The initramfs will attempt to resume from /dev/sdb1
I: (UUID=e410ee0f-8aa3-4af5-af2e-0cbab3fc195e)
I: Set the RESUME variable to override this.

So i did part 4.a again:

cd /boot
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.19.2-kirkwood-tld-1 -d vmlinuz-5.19.2-kirkwood-tld-1 uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.19.2-kirkwood-tld-1 -d initrd.img-5.19.2-kirkwood-tld-1 uInitrd

I did backup uImage and uInitrd, which were the working ones with kernel-5.19.2, to /boot/11.5,

I have seen this somewhere on your site and tried that (using NSA320 values):

NSA320> load ide 0:1 0x800000 /boot/uImage
ext4fs_devread read outside partition 18446744073262735360

NSA320> ext4ls ide 0:1 /boot/11.5
<DIR>       4096 .
<DIR>       4096 ..
         5733288 uImage
        12719243 uInitrd
        13192459 initrd.img-5.19.2-kirkwood-tld-1

NSA320> load ide 0:1 0x800000 /boot/11.5/uImage
ext4fs_devread read outside partition 18446744073262784512


NSA320> load ide 0:1 0x800000 /boot/bck.20221030/uImage
4963680 bytes read in 861 ms (5.5 MiB/s)

This last attempt was the uImage of pre-bullseye and pre-kernel-update, so kernel-5-2-9 (I think).

It appears it does not like uImage files created after the 'apt full-upgrade', but it also does not like the one created for kernel-5.19.2 anymore,

How can I get out of this situation the best way? Do you get what is going on with these images?

Thanks and kind regards