Arch Linux User Repository

Stock kernel parameters are saved in /boot/vmlinuz-linux-clear.cmdline. Although you may not need to apply all the parameters, you should copy most of these into your systemd-boot or GRUB configuration.

If you are using out-of-tree kernel modules with dkms you will need to add the module.sig_unenforce parameter to allow loading of unsigned kernel modules.

Please check the Clear Linux kernel releases on GitHub (not kernel.org) before flagging out of date here.

Linux 5.12 is finally in Clear Linux. It seems they skipped 5.11 entirely! Enjoy.

It make sense that kernel should not be in /boot directly, and that we want a simple tool to take care of everything. It is a good design for this part. But I just don't like the name for the tool (mkinitcpio). It should be more like boot-manager or maybe bootctl (if systemd acquire it), it is not only, or maybe not at all for initcpio. It is esp. for clear kernel since it has almost every possible rootfs built in. And this idea should also apply to ucode. They should not be in /boot either. Has it been decided where they should go ?

I must have got a bit confused but, what is the right way to copy the kernel to /boot ? I see no alpm hooks here.

@yw662 in 2019-11 there were changes to Arch's mkinitcpio package. Installation to /boot is automatic when usr/lib/modules/*/vmlinuz is changed.

I updated linux-clear-bin here: https://aur.archlinux.org/cgit/aur.git/commit/?h=linux-clear-bin&id=c3e28f0845d3e78c0cbe3dd527a4ae0a6109fce8

I must have got a bit confused but, what is the right way to copy the kernel to /boot ? I see no alpm hooks here.

@asasione that's a known issue that is harmless. It will be fixed with an update to mkinitcpio eventually. See:

https://bugs.archlinux.org/task/65725

I am getting two errors on this kernel:

cp: cannot stat '(builtin)': No such file or directory


==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-clear-bin-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
Error while configuring 
Error: command failed to execute correctly

Is there some configuration missing for this kernel?

@aorth your latest fix has worked. Thank you! One more thing though, this small warning has always popped up while upgrading:

==> Generating module dependencies ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-clear-bin-fallback.img ==> WARNING: errors were encountered during the build. The image may not be complete. Error while configuring Error: command failed to execute correctly

@mashaal95 the name of the source files never change (Manifest.kernel-native) so you need to remove them after every build. Let me see if I can modify the PKGBUILD to use unique names for these files.

Edit: as of 5.6.6.942-1 the PKGBUILD now uses unique names for these files and should not cause issues with users not clearing their build directory between builds.

@mashaal95 -- I had the same issue before, I basically it wasn't overwriting a file that needed to be overwritten. So I had to complete delete the folder and bring it in as new.

I was using git directly, you might be using yay or not, but if you are, doing it as new build option instead of the default 'no'

I have just received an update to the kernel today but unfortunately, its giving me this error:

==> Validating source files with b2sums... Manifest.kernel-native ... FAILED pack-kernel-native-from-0.tar ... FAILED ==> ERROR: One or more files did not pass the validity check!

Any clue on how to solve it?