N2+ failing to boot multiple times

[Pedro Teixeira]

So, I've noticed there were some updates available, so decided to do so, now running 20.08.7 Focal / 5.8.13 kernel.

 

Now, I did run the nand-sata-install when I first installed armbian a month ago to an external SSD and all's working perfectly. The thing is, a couple of weeks ago, even after this latest update and rebooting, the sbc won't boot up, I had to pull the plug and back about 20 times for it to boot. So this is what I found running dmesg.

 

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.8.13-meson64 (root@xeon) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209) #20.08.6 SMP PREEMPT Thu Oct 1 18:51:27 CEST 2020
[    0.000000] Machine model: Hardkernel ODROID-N2Plus
[    0.000000] efi: UEFI not found.
[    0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000b5800000, size 896 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x00000000ed7fffff]
[    0.000000] NUMA: NODE_DATA [mem 0xb5033100-0xb5034fff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000000000-0x000000003fffffff]
[    0.000000]   DMA32    [mem 0x0000000040000000-0x00000000ed7fffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000004ffffff]
[    0.000000]   node   0: [mem 0x0000000005300000-0x00000000ed7fffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x00000000ed7fffff]

 

Specifically [    0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!

 

Is there anything I can do to fix this? I dread whenever I need to reboot due to having to go around doing this.

 

I've also noticed the hwclock isn't working properly?

 

sptz@odroidn2:~$ hwclock --test -D
hwclock: use --verbose, --debug has been deprecated.
hwclock from util-linux 2.34
System Time: 1601811651.679131
Trying to open: /dev/rtc0
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.

 

[Igor]

6 hours ago, Pedro Teixeira said:

Is there anything I can do to fix this?

If you are not a kernel hacker, migrating to stock legacy kernel , wait that its fixed, downgrade kernel to last known to work version -> armbian-config -> system -> alternative kernels + freezing kernel updates at that kernel (also in armbian-config) ...

 

6 hours ago, Pedro Teixeira said:

 

I've also noticed the hwclock isn't working properly?

 

If you want to have modern kernel, this is a very small price to pay. Porting drivers from a kernel where support for hardware was developed (private hardkernel kernel 4.9.y in this case) takes years, costs millions. Which is why support comes this way.