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 ...

 

 

Some strange thing is that on the C4 the mac adress changes after installing updates after initial deploying image to emmc card:

 

MAC after deploying image - U-Boot.armv8, 00:50:43:84:FB:2F

 

MAC after updates without kernel - 02:0B:18:CC:AF:CB

Am 21.10.2020 um 08:39 schrieb 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 have the same problem with my C4 :-(

I think I'm having the same issue with my Odroid N2 (Buster Server, 5.8, EMMC). I updated yesterday, and now it doesn't boot and there's no HDMI output. I haven't been able to identify the problem yet - perhaps I need to look into the USB-UART module.

 

Upgrade: linux-image-current-meson64:arm64 (20.08.9, 20.08.18),
linux-libc-dev:arm64 (4.19.146-1, 4.19.152-1),
libldap-2.4-2:arm64 (2.4.47+dfsg-3+deb10u2, 2.4.47+dfsg-3+deb10u3),
mariadb-common:arm64 (1:10.3.23-0+deb10u1, 1:10.3.25-0+deb10u1),
linux-dtb-current-meson64:arm64 (20.08.9, 20.08.18),
linux-u-boot-odroidn2-current:arm64 (20.08.1, 20.08.13),
armbian-firmware:arm64 (20.08.9, 20.08.17),
libldap-common:arm64 (2.4.47+dfsg-3+deb10u2, 2.4.47+dfsg-3+deb10u3),
armbian-config:arm64 (20.08.9, 20.08.20),
mariadb-client-10.3:arm64 (1:10.3.23-0+deb10u1, 1:10.3.25-0+deb10u1),
mariadb-client-core-10.3:arm64 (1:10.3.23-0+deb10u1, 1:10.3.25-0+deb10u1),
mariadb-client:arm64 (1:10.3.23-0+deb10u1, 1:10.3.25-0+deb10u1),
linux-buster-root-current-odroidn2:arm64 (20.08.9, 20.08.17),
tzdata:arm64 (2020a-0+deb10u1, 2020d-0+deb10u1)

 

In the meantime I've installed Focal Server on a microSD card and that's working fine. Worst case I can flash that image to the EMMC.

Exactly the same issue just happened to me after reboot N2 - I thought it was due to a power surge, but I used a new SD card with a new installation and right after apt upgrade/reboot (within 20 minutes of installation) everything is back to black screen.

This is definitely a kernel issue of some sort and seems to disable Odroids completely - not even any messages showing.

petit boot still loads, but nothing else does

Hier with C2 too. After kernel upgrade i cannot boot any more.

I started with the uart console and saw this error:

 

"Net: Could not get PHY for ethernet@c9410000: addr -1"

Do any of you guys have a serial cable to help with debugging?  Everyone who play with SBC should own at least one.  Go order one right now on your favorite Chinese e-commerce site, they are only a few dollars.  It will take a month to get to you, but next time you have some problem, you will be in a much better position to diagnose the issue.

 

Have anyone here attempted any of the Recovery steps?  That section of docs was recently updated.

20 hours ago, isndwx said:

I started with the uart console

Only full console bootlog can help. You need to switch console to serial and change verbosirty to 10 in /boot/armbianEnv.txt

Hello Igor, thank you for your reply. I restored a backup and updated today again and now armbian boots as normal, so i think what caused the error is now fixed. Thank you for your support.

It seems I was too late to notice this topic. My C2 “died” as well, as it no longer boots. I didn’t have a backup script in place yet. I’ve ordered an UART cable, which should arrive this week. Hopefully I understand how this work and be able to resurrect Armbian.

 

I’ll just need to make sure not to reboot my N2, since I updated it as well, but didn’t reboot yet.

9 hours ago, w0ndersp00n said:

I’ll just need to make sure not to reboot my N2, since I updated it as well, but didn’t reboot yet.

Upgrades are tested but ... we don't test all variants, upgrading from some old images is certainly not tested at all.

 

BTW. We could use some help to improve our auto testing facility https://github.com/armbian/autotests which primary goal is to minimise unpleasant surprises.

Well, my C2 doesn’t seem to have a console so I guess I need to recover it another way. My N2 thankfully didn’t crash after the update. It had a power outage...

 

I’ll check out the autotests later. Need to deal with some private stuff first, then recover the C2 and then I’ll be able to get tinkering again.

On 12/28/2020 at 2:41 PM, Igor said:

BTW. We could use some help to improve our auto testing facility https://github.com/armbian/autotests which primary goal is to minimise unpleasant surprises.

Wow that's really cool I'll start doing that.