No, definitely no unofficial kernels installed here. When chrooted into KaOS, I get this:
# pacman -Q linux
linux 5.10.6-1
uname -r
returns 5.4.0-66-generic
also under chroot. But that's the kernel of the host OS and has nothing to do with KaOS, right? Since it won't boot I can't check the kernel that would actually run in KaOS. (Sorry my previous post was confusing.)
March 16 update was done in chroot. But I forgot to mount the boot partition, which might have caused the fallback to 2018 kernel (wild speculation I know).
Nothing owns /lib/modules/4.19.12-1:
# pacman -Qo /lib/modules/4.19.12-1
エラー: /lib/modules/4.19.12-1 を保有しているパッケージはありません
Japanese to English translation of the above:
# pacman -Qo /lib/modules/4.19.12-1
ERROR: /lib/modules/4.19.12-1 is not owned by any packages
Updated pacman.log 4 with entries from a fresh update today:
https://pastebin.com/jx3D01ba
(Looks OK to me)
I realize that none of this information helps solve the problem. As I said at the beginning of the thread, and as you confirmed in your last post, the 2021-02-21 update appears to be OK. But, for whatever reason, I am getting 100% consistent boot failure ever since that update. Back to square one, I think.
A screenshot of the tty output when it hangs:
![https://www.dropbox.com/s/aqfwb20qccd0812/KAOSbootfailure3.jpg?dl=0](https://)