Hi,

I upgraded armbian on N2+ today... Apparently kernel was updated, I dont know how to fix this.

Someone to help me ?

Thanks

Hook up USB UART adapter to debug. If you dont have one there is very little chance to track things down since nobody has a crystal ball to know whats going on inside.

13 minutes ago, Werner said:

nobody has a crystal ball to know whats going on inside.

Yes I know.... But my english is very minimalist

 

13 minutes ago, Werner said:

Hook up USB UART adapter to debug

Already do.

I tried to copy backup of /boot instead of the new one but no effect.

My N2 sometimes hang on u-boot but power cycle solves the problem. Also this is latest test result show that N2 survived stressing, upgrade, reboot. Are you upgrading from some very old image?

5 minutes ago, Igor said:

but power cycle solves the problem

not for me.

6 minutes ago, Igor said:

Are you upgrading from some very old image?

no, armbian was up to date

1 minute ago, Jul said:

no, armbian was up to date

Can you provide exact version of the image or at least approximately when you download, which kernel ... everything you have & can remember. Otherwise we can't say much. It works for us.

4 minutes ago, Igor said:

Can you provide exact version of the image or at least approximately when you download, which kernel ... everything you have & can remember. Otherwise we can't say much. It works for us.

Quote

Start-Date: 2021-02-15  19:59:33
Commandline: apt upgrade
Requested-By: jul (1000)
Upgrade: linux-image-current-meson64:arm64 (21.02.1, 21.02.2), linux-dtb-current-meson64:arm64 (21.02.1, 21.02.2), armbian-firmware:arm64 (21.02.1, 21.02.2), linux-buster-root-current-odroidn2:arm64 (21.02.1, 21.02.2)
End-Date: 2021-02-15  20:00:12

 

Quote

Log started: 2021-02-15  19:59:33
(Lecture de la base de données... 43847 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../armbian-firmware_21.02.2_all.deb ...
Dépaquetage de armbian-firmware (21.02.2) sur (21.02.1) ...
Préparation du dépaquetage de .../linux-buster-root-current-odroidn2_21.02.2_arm64.deb ...
Dépaquetage de linux-buster-root-current-odroidn2 (21.02.2) sur (21.02.1) ...
Préparation du dépaquetage de .../linux-dtb-current-meson64_21.02.2_arm64.deb ...
Dépaquetage de linux-dtb-current-meson64 (21.02.2) sur (21.02.1) ...
Préparation du dépaquetage de .../linux-image-current-meson64_21.02.2_arm64.deb ...
update-initramfs: Deleting /boot/initrd.img-5.10.12-meson64
Removing obsolete file uInitrd-5.10.12-meson64
Dépaquetage de linux-image-current-meson64 (21.02.2) sur (21.02.1) ...
Paramétrage de linux-buster-root-current-odroidn2 (21.02.2) ...
NOTE: You can find previous bootscript versions in /usr/share/armbian !
Recreating boot script
sed: -e expression n°1, caractère 37: option inconnue pour « s »
Paramétrage de linux-image-current-meson64 (21.02.2) ...
update-initramfs: Generating /boot/initrd.img-5.10.16-meson64
update-initramfs: Converting to u-boot format
Paramétrage de linux-dtb-current-meson64 (21.02.2) ...
Paramétrage de armbian-firmware (21.02.2) ...
Traitement des actions différées (« triggers ») pour initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.10.16-meson64
update-initramfs: Converting to u-boot format
Log ended: 2021-02-15  20:00:12

 

1 hour ago, Jul said:

Upgrade: linux-image-current-meson64:arm64 (21.02.1, 21.02.2), linux-dtb-current-meson64:arm64 (21.02.1, 21.02.2), armbian-firmware:arm64 (21.02.1, 21.02.2), linux-buster-root-current-odroidn2:arm64 (21.02.1, 21.02.2)

 

It is working perfectly fine for me:

1. Downloaded https://imola.armbian.com/dl/odroidn2/archive/Armbian_21.02.1_Odroidn2_buster_current_5.10.12.img.xz

2. Burn to SD card, boot, configure, update

3. Reboot, board came back normally http://ix.io/2PyW

 

But I used N2, not N2+ since its deep in the rack and according to automated testings, it also performs fine and its even overclocked. I have no idea - perhaps your SD / eMMC card has issues?

Do you have blue led blinking or not?

I got it too. Focal Legacy on N2+. Yesterday it was still working. I think I've done an update/upgrade. Today it didn't boot anymore.
No display, flashing led. I didn't investigate further. 
Might it be something with the OC fix you had @Igor? I had OC working while it wasn't enabled anymore in boot.ini. I did enable it when I installed the image.

2 minutes ago, NicoD said:

Might it be something with the OC fix you had

I suspected that too, but my N2+ is running the exact kernel / u-boot and its even overclocked by default. The only difference is, that I didn't re-image it. Its some old build which is upgrading and upgrading until it fails. Then I check why it failed.

 

We certainly need more info since I can't reproduce.

1 minute ago, Igor said:

We certainly need more info since I can't reproduce.

I'll check tomorrow if I can find something. I only checked if spi boot gave something to be sure my N2+ wasn't broken. After that I just thought to deal with it later. 

It's ok tonight...

After several power cycle, I played once with the mmc/sd swich -> n2+ boots normally. I don't understand what happened. Perhaps my usb HDD is tired.

I don't dare to stop it anymore, I dread the next upgrade

 

Thanks for your time

2 minutes ago, Jul said:

After several power cycle

Then you just hit this known bug in the boot loader - sometimes it just hangs and power cycle is the only help. Sometimes not just one I guess.

 

Sadly N2/N2+ is still running outdated vendor boot loader, where we will not fix anything and there is some work needed to be done to boot with its modern community supported version. We have already lost several afternoons but since vendor doesn't pay our bills, nor do  you, we can't really spent much on R&D for this hardware. I tried twice and + version come in the meantime. Which adds some complexity.

Weird. Power cycle doesn't seem to help here.
I made another focal legacy image on sd card and that works fine. Updated and all. The image on eMMC still doesn't boot. I've copied the boot.ini from the working image. No difference. 
Doesn't matter much for me. Easy enough to write a new image for it. 

1 time it didn't fully boot with the new image. But I did have hdmi working.

With the non working image no hdmi...

Is it the new u-boot hdmi bug (conflict) u-boot hdmi - kernel hdmi https://github.com/armbian/build/pull/2016/files ?

2 hours ago, denni_isl said:

Is it the new u-boot hdmi bug (conflict) u-boot hdmi - kernel hdmi https://github.com/armbian/build/pull/2016/files ?

That's Rockchip specific.