A20 not booting: 5.10.105-olimex vs 5.10.0-13-rt-armmp

[aleix]

I installed

Code Select Expand

sudo apt install wireguard wireguard-dkms openresolv

after which I rebooted and never got the board to boot again (just solid red led, no green).

I tried another SD card from another A20 board and the system booted fine, so the problem is within the SD.

I mounted the SD in the laptop and fsck -f does not throw any error.

Since I can explore the logs from the mounted SD, I can see that while in my other working SD I have

Code Select Expand

$ ls /boot/
-rw-r--r-- 1 root root 8.9M Apr 13 10:22 initrd.img-5.10.105-olimex
-rw-r--r-- 1 root root  16M Apr 13 10:14 kernel.itb
-rw-r--r-- 1 root root  27K Apr 13 10:14 kernel.its
-rw-r--r-- 1 root root 2.2K Apr 13 10:12 boot.cmd
-rw-r--r-- 1 root root 2.3K Apr 13 10:12 boot.scr
-rw-r--r-- 1 root root 1.2K Apr 13 10:08 uEnv.txt
-rw-r--r-- 1 root root 3.5M Apr 13 09:06 System.map-5.10.105-olimex
-rw-r--r-- 1 root root 187K Apr 13 09:06 config-5.10.105-olimex
-rwxr-xr-x 1 root root 6.3M Apr 13 09:06 vmlinuz-5.10.105-olimex

on my problematic SD I have

Code Select Expand

$ ls -lh /boot/
-rw-r--r-- 1 root root 2,2K mar 22 00:00 boot.cmd
-rw-r--r-- 1 root root 2,3K mar 22 00:00 boot.scr
-rw-r--r-- 1 root root 245K mar 17 16:40 config-5.10.0-13-rt-armmp
-rw-r--r-- 1 root root 187K mar 21 20:20 config-5.10.105-olimex
-rw-r--r-- 1 root root  24M abr 21 10:35 initrd.img-5.10.0-13-rt-armmp
-rw-r--r-- 1 root root 8,9M abr 21 10:36 initrd.img-5.10.105-olimex
-rw-r--r-- 1 root root  29M abr 21 10:35 kernel.itb
-rw-r--r-- 1 root root  27K abr 21 10:35 kernel.its
-rw-r--r-- 1 root root   83 mar 17 16:40 System.map-5.10.0-13-rt-armmp
-rw-r--r-- 1 root root 3,5M mar 21 20:20 System.map-5.10.105-olimex
-rw-r--r-- 1 root root 1,2K mar 21 23:56 uEnv.txt
-rw-r--r-- 1 root root 4,8M mar 17 16:40 vmlinuz-5.10.0-13-rt-armmp
-rwxr-xr-x 1 root root 6,3M mar 21 20:20 vmlinuz-5.10.105-olimex

Exploring /var/log/apt/history.log I see that

Code Select Expand

Start-Date: 2022-04-21  10:36:30
Commandline: apt install wireguard wireguard-dkms openresolv
Requested-By: olimex (1000)
Install: linux-kbuild-5.10:armhf (5.10.106-1, automatic), linux-compiler-gcc-10-arm:armhf (5.10.106-1, automatic), dctrl-tools:armhf (2.24-3, automatic), linux-headers-armmp:armhf (5.10.106-1, automatic), linux-headers-5.10.0-13-common:armhf (5.10.106-1, automatic), wireguard-dkms:armhf (1.0.20210219-1), linux-headers-5.10.0-13-armmp:armhf (5.10.106-1, automatic), openresolv:armhf (3.12.0-1), dkms:armhf (2.8.4-3, automatic)
Remove: resolvconf:armhf (1.87)
End-Date: 2022-04-21  10:37:52


So this install, I think, messed up my kernel.

Do you have any viable suggestion for rolling back, not being able to boot?

Thanks for reading.

[LubOlimex]

Might be a good idea to also ask the wireguard community about why these three installs might have messed up the Olimage (which is Debian-based).

[aleix]

Thanks for the answer. I have now asked them in their IRC channel.

[aleix]

I have checked this with the very nice people from WireGuard's channel on Libera.Chat.

Using another A20 I have with Olimage, we tested:

Code Select Expand

$ zgrep WIREGUARD /boot/config-$(uname -r)
CONFIG_WIREGUARD=m
# CONFIG_WIREGUARD_DEBUG is not set

So the olimex linux image does include the built-in wireguard module. Then,

Code Select Expand

$ apt show linux-image-5.10.105-olimex
Package: linux-image-5.10.105-olimex
Version: 5.10.105-20220413-090538
Priority: optional
Section: kernel
Source: linux-5.10.105-olimex
Maintainer: root <root@runner-cpbkaozn-project-1-concurrent-0>
Installed-Size: 81.1 MB
Homepage: https://www.kernel.org/
Download-Size: 24.8 MB
APT-Manual-Installed: no
APT-Sources: http://repository.olimex.com bullseye/main armhf Packages
Description: Linux kernel, version 5.10.105-olimex
This package contains the Linux kernel, modules and corresponding other
<fluxion>  files, version: 5.10.105-olimex.

After this, we checked

Code Select Expand

$ apt-cache showpkg wireguard-modules
Package: wireguard-modules
Versions:

Reverse Depends:
  wireguard-tools,wireguard-modules 0.0.20171001
  wireguard,wireguard-modules 0.0.20191219
Dependencies:
Provides:
Reverse Provides:
linux-image-rt-armmp 5.10.106-1 (= 1.0.0)
linux-image-armmp-lpae 5.10.106-1 (= 1.0.0)
linux-image-armmp 5.10.106-1 (= 1.0.0)

Their conclusion after all this is:

The package linux-image-5.10.105-olimex should've had a Provides for wireguard-modules.
That's a packaging bug from the maintainer.
Workaround recommended:

Code Select Expand

$ apt install --no-install-recommends wireguard-tools