KaOS-next 6.15.2-1 fails to boot

johnjark

I have just upgraded to KaOs 6.14.8-1 and KaOS-next 6.15.2-1.
Booting into the 6.14 kernel works.

Booting into 6.15 gives a blank grey systemd blank rectangle and the machine hangs.
I cannot get any details from systemctl -b -1 when I reboot into 6.14.

I am at a loss to explore this further.

Many thanks,
JJ

demm

Start with giving full SysInfo, since hardware specs & update log are the minimum needed:
https://kaosx.us/docs/#sysinfo-tool-in-octopi

johnjark

Many thanks for this - I have pasted the output as below -
https://pastebin.com/7EC5mBcs

This is for the KaOS kernel - not possible to do this for the KaOS-next kernel as this still hangs.
JJ

demm

So the issue started with linux-next 6.15.2? Seems you have been on 6.15 ever since 6.15.0, not clear if neither of the previous versions booted.
Hardware should not be an issue (I asked for hardware info to check for older nvidia cards, or if ZFS was used for filesystem).
So, if the issue started with 6.15.2 then it most probably is an upstream change, since no major config change was done, but I will revert one change, if it did just start.

And of no importance for this issue, but it seems this is an install from 2020, you need to run pacman -Qm regularly on any rolling distro (pacman based), since packages do leave the repo, either no longer maintained upstream, no longer needed by the distro, or plain broken. You have over 130 packages on this system, not in the KaOS database, very few are self-build (like ocenaudio), but most are old/obsolete/removed KaOS packages. See for example https://forum.kaosx.us/d/3153-phasing-out-kf5.

demm

Scratch the above, you are using zfs, at least have it installed, zfs is not ready for Linux 6.15, not clear yet from your log how you were able to install 6.15, with zfs, it should have blocked that update. Why did you install Calamares on an already installed system? That pulled in zfs (without any of the modules), thus dracut now adds zfs to the kernel image creation, but without the right modules, that fails.

Since you are not using zfs as filesystem, make sure to remove all installed zfs packages and re-generate the kernel image, easiest just run sudo pacman -S linux-next, and make sure to check the dracut output that it no longer shows FAIL on zfs module (should no longer mention using the zfs module).

johnjark

This has done the trick. Removing zfs allowed the KaOS-next kernel to boot.
KaOS-next is running once again - Thank you so much for your help.

....but more than this, you have taught me much more about my linux system. I have tidied up the junk that was left from experimental work, dumb mistakes, and lack of attention.

I have been using KaOS for many years now and I continue to be amazed at the quality of the distribution and, more importantly, of the support that is so unstintingly given.

Just a SUPERB job, guys,
JJ