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.

@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?

Is there any wait to apply the futex-wait-multiple patch here?

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.

@MikeDee the instruction about copying parameters into linux-clear-bin.conf only applies if you're using systemd-boot, not GRUB. I haven't used GRUB in years, but the Arch wiki might help you figure out how to add kernel parameters to GRUB. Sorry I can't be more help.

I'm confused with the vmlinuz-linux-clear-bin.cmdline file. It installs to the /boot folder. That's a problem because Grub treats it as a kernel. Then, I read below that the contents of it should be copied into linux-clear-bin.conf. Where should this file go, since it doesn't exist on my system? Will vmlinuz-linux-clear-bin.cmdline execute if it's left in my /boot folder? Is this file even necessary, since it seems to boot fine without it anyways?