so it’s been 14 days and about half a dozen updates requiring rebuilding the kernels since https://forum.manjaro.org/t/kernel-5-4-panic-error-after-latest-update/143914
I respectfully suggest that this ought to be enough time for the maintainer of such a critical issue to fix it himself, even in summertime.
It’s not an issue isolated to the op of the previous post, but also happens on the two machines I have running manjaro.
Interestingly, according to the .conf itself, this error shouldn’t happen, although I witnessed it being compressed via zstd multiple times now, but the comment reads:
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
Also I don’t see a selector for the compression, just the multiple methods listed in my file, but as stated before, the issue shouldn’t even occur, so would the team kindly fix it themselves and provide a corresponding update?! @Yochanan
Those comments should be updated, because apparently, it now uses zstd compression by default. And the 5.4 kernel does not support an initcpio compressed with zstd, so there are only two options…:
Update the comments in /etc/mkinitcpio.conf to make it clear that the default is now zstd, and officially drop support for 5.4 LTS; or…
Return to using gzip as the default compression type for initcpios and keep on supporting 5.4 LTS — as we should, because it’s an official long-term support kernel from upstream.
@Rollingthunder, if you have another kernel installed — later than 5.4 — or you can boot up from the live USB and chroot, edit your /etc/mkinitcio.conf, uncomment the compression entry for gzip, and rebuild your initcpio(s) with…
mkinitcpio -P && update-grub
You’ll need to do this as root or with sudo, of course, but if you’re doing it from within the chroot, then you would normally already have escalated your privileges and thus be root.