Franky66

I am using two Odroid N2 and a new Odroid C4. The N2 installation with OMV5 is using Kernel 4.9.236 actually and the C4 is using the kernel 5.8 used in the latest download image for debian buster. When I try to install newer kernels after the following linux kernel packages the installation gets broken and the odroids are not booting anymore.
 
There is also no output on hdmi to see what problem could be exist. On Odroid N2 I hear the USB drives starting, stopping, starting and then nothing happens.
 
All other updates are installing without problems in rebooting. The N2 are using on my test N2 a micro sd card and on my prod n2 a emmc card. The C4 is also using a emmc card.
 
Can someone help to fix this or are there other persons using these odroids with same problems?
 
Here are the actually installed packages without problems:
 
ii  linux-dtb-legacy-meson64          20.08.6                             arm64        Linux DTB, version 4.9.236-meson64
ii  linux-image-legacy-meson64        20.08.6                             arm64        Linux kernel, version 4.9.236-meson64
 
And here is the output from installing the newer kernel which is actually available
 
Reading package lists...
Building dependency tree...
Reading state information...
Suggested packages:
  linux-firmware-image-legacy-meson64
The following packages will be upgraded:
  linux-dtb-legacy-meson64 linux-image-legacy-meson64
apt-listchanges: Reading changelogs...
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/21.9 MB of archives.
After this operation, 2632 kB of additional disk space will be used.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 62535 files and directories currently installed.)
Preparing to unpack .../linux-dtb-legacy-meson64_20.08.13_arm64.deb ...
Unpacking linux-dtb-legacy-meson64 (20.08.13) over (20.08.10) ...
dpkg: warning: unable to delete old directory '/boot/dtb-4.9.236-meson64': Directory not empty
Preparing to unpack .../linux-image-legacy-meson64_20.08.13_arm64.deb ...
update-initramfs: Deleting /boot/initrd.img-4.9.236-meson64
Removing obsolete file uInitrd-4.9.236-meson64
Unpacking linux-image-legacy-meson64 (20.08.13) over (20.08.10) ...
Setting up linux-dtb-legacy-meson64 (20.08.13) ...
Setting up linux-image-legacy-meson64 (20.08.13) ...
update-initramfs: Generating /boot/initrd.img-4.9.238-meson64
update-initramfs: Converting to u-boot format
Fertig ...
 
 

I saw on github that the problem should be fixed but I didn't see any update in the last 14 days which installed new version of the necessary files. Will there be an update available which fixes this or do I have to manually change files and if yes what files where to change?

@Igor
My big thank to you for your work. I will check the images and will give feedback for errors etc.