Package Details: linux-clear-bin 5.18.6.1159-1

Git Clone URL: https://aur.archlinux.org/linux-clear-bin.git (read-only, click to copy)
Package Base: linux-clear-bin
Description: Clear Linux kernel and modules in binary
Upstream URL: https://github.com/clearlinux-pkgs/linux
Licenses: GPL2
Provides: WIREGUARD-MODULE
Submitter: yw662
Maintainer: aorth
Last Packager: aorth
Votes: 10
Popularity: 0.49
First Submitted: 2019-08-04 22:33 (UTC)
Last Updated: 2022-06-28 16:28 (UTC)

Dependencies (7)

Required by (3)

Sources (2)

Pinned Comments

aorth commented on 2020-04-09 07:01 (UTC) (edited on 2020-09-27 12:08 (UTC) by aorth)

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.

Latest Comments

aorth commented on 2022-05-24 07:14 (UTC)

Thanks @metak. I've updated this package and verified that it boots.

metak commented on 2022-05-24 04:55 (UTC)

It's fixed now in latest release.

aorth commented on 2022-05-20 12:58 (UTC)

Thank you, @metak. I had pull requests merged in the clearlinux-pkgs/linux repository before so I didn't realize they weren't looking there now.

metak commented on 2022-05-20 09:28 (UTC)

@aorth Maintainer of linux-clear package here. I've opened up a new issue for compressed firmware on their issue tracker where it should be seen, they don't look at pull requests for individual packages.
https://github.com/clearlinux/distribution/issues/2633

aorth commented on 2022-01-29 05:41 (UTC) (edited on 2022-04-25 19:14 (UTC) by aorth)

5.16.3.1118-1 doesn't boot on my system. Not sure what's up, but don't have time to investigate yet. Make sure you have another backup kernel installed!

Edit (2022-01-31): Ah I see, Arch Linux began using compressed firmware last week and this requires CONFIG_FW_LOADER_COMPRESS=y in the kernel config. The Clear Linux kernel does not have this option set.

Edit 2 (2022-01-31): I have sent a pull request to Clear Linux to enable compressed firmware loading in their kernel.

Edit 3 (2022-04-25): I've basically stopped updating this package since we can no longer use it in Arch without the patch above. I'll probably orphan the package soon.

aorth commented on 2021-08-14 13:10 (UTC) (edited on 2021-11-06 16:20 (UTC) by aorth)

Is this being built against glibc 2.34? Unable to get nvidia dkms driver to build. Seeing scripts/basic/fixdep: /usr/lib/libc.so.6: version 'GLIBC_2.34' not found (required by scripts/basic/fixdep) in the dkms build log

Hi @radiomike. I'm not sure what environment Intel builds it in and I don't use nvidia so I can't help there. We are only re-packaging the binary builds Intel makes available publicly for Clear Linux.

radiomike commented on 2021-08-13 15:05 (UTC) (edited on 2021-08-13 15:06 (UTC) by radiomike)

Is this being built against glibc 2.34? Unable to get nvidia dkms driver to build. Seeing scripts/basic/fixdep: /usr/lib/libc.so.6: version 'GLIBC_2.34' not found (required by scripts/basic/fixdep) in the dkms build log

aorth commented on 2021-05-05 13:19 (UTC)

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

yw662 commented on 2020-12-13 10:10 (UTC)

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 ?

aorth commented on 2020-12-13 09:15 (UTC)

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

yw662 commented on 2020-12-11 17:38 (UTC)

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.

aorth commented on 2020-06-11 10:08 (UTC)

@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

asasione commented on 2020-06-11 09:51 (UTC) (edited on 2020-06-11 09:52 (UTC) by asasione)

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?

mashaal95 commented on 2020-04-24 04:01 (UTC)

@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

aorth commented on 2020-04-23 12:51 (UTC) (edited on 2020-04-23 13:35 (UTC) by aorth)

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

dedguy21 commented on 2020-04-23 02:57 (UTC)

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

mashaal95 commented on 2020-04-23 02:44 (UTC)

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?

lucasrizzini commented on 2020-04-10 22:56 (UTC)

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

aorth commented on 2020-04-09 07:01 (UTC) (edited on 2020-09-27 12:08 (UTC) by aorth)

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.

aorth commented on 2020-04-09 06:58 (UTC) (edited on 2020-04-09 06:59 (UTC) by aorth)

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

MikeDee commented on 2020-04-08 21:09 (UTC)

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?

aorth commented on 2020-03-08 11:53 (UTC)

@metak yes you're right, this has been solved with the updated mkinitcpio. Thanks!

metak commented on 2020-03-08 10:47 (UTC) (edited on 2020-03-08 10:49 (UTC) by metak)

I am not sure why this happens, but the kernel boots and runs fine. If it still happens in the next few kernel releases I will look at it more closely.

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

aorth commented on 2020-02-20 08:19 (UTC)

With 5.5.4.910-0 there is an error during the mkinitcpio stage of installation:

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

I am not sure why this happens, but the kernel boots and runs fine. If it still happens in the next few kernel releases I will look at it more closely.

aorth commented on 2020-02-13 07:12 (UTC)

@dedguy21 You need to copy the cmdline into the config entry. Here's what I use:

title Arch Linux (clear)
linux /vmlinuz-linux-clear-bin
initrd /intel-ucode.img
initrd /initramfs-linux-clear-bin.img
options luks.name=ffe04b78-49d8-356a-8f4a-aca518cdj2n1=vg0 luks.options=discard root=/dev/mapper/vg0-root quiet console=tty0 console=ttyS0,115200n8 cryptomgr.notests intel_iommu=igfx_off no_timer_check noreplace-smp page_alloc.shuffle=1 rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs tsc=reliable rw module.sig_unenforce

Note that you need to specify the intel-ucode before the general system initrd.

dedguy21 commented on 2020-02-13 01:31 (UTC) (edited on 2020-02-13 01:42 (UTC) by dedguy21)

@aorth

should we add vmzluz-linux-clear-bin.cmdline to systemd-boot linux-clear-bin.conf

as such:

  • 1 title Clear Linux

  • 2 linux /vmlinuz-linux-clear-bin

  • 3 linux /vmlinuz-linux-bin.cmdline *** guessing i would add it at this point

  • 4 initrd /intel-ucode.cpio

  • 5 initrd /initramfs-linux-clear-bin.img

aorth commented on 2020-02-12 17:01 (UTC)

@dedguy21 Yeah, you need to remove the old files before building. Unfortunately all Clear Linux's binary files have the same name for every update (pack-kernel-native-from-0.tar), so when you run makepkg it sees you already have it, and doesn't download a new one. Then of course the hash of the file doesn't match the one in the PKGBUILD.

dedguy21 commented on 2020-02-12 16:38 (UTC) (edited on 2020-02-12 16:51 (UTC) by dedguy21)

Update: removing the old folder and doing a fresh clone resolved the issue. Just wondering why a pull request isn't working to update?


Hi sorry for not posting that here what I get:

Making package: linux-clear-bin 5.5.2.903-1... Checking, retrieve, found (no issues) ...

Validating source files with sha256sums... Manifest.kernek-native ... Failed Pack-kernel-native-from-0.tar ... Failed

Error: One or more files did not pass the validity check

What I plan to do next is rm the linux-clear-bin git download and just start fresh instead of just running an update if it works I will update.

aorth commented on 2020-02-12 10:49 (UTC)

@dedguy21 Can please post the actual error you are getting? The package builds and installs fine for me. I'm currently booted to the kernel so it definitely works.

dedguy21 commented on 2020-02-12 09:52 (UTC)

I'm getting a validity check error again, not using aur helper, just a simple git pull && makepkg -si

aorth commented on 2020-02-07 14:00 (UTC)

@dedguy21 what error are you getting? I just installed with no problem.

aorth commented on 2019-11-11 09:57 (UTC) (edited on 2019-11-11 12:45 (UTC) by aorth)

I have updated linux-clear-bin for the recent changes to Arch Linux's mkinitcpio. The kernel image is no longer owned by the linux-clear-bin package, instead it is copied/removed by mkinitcpio. You don't need to do anything.

Also, the package version as seen by pacman will now be formatted like "5.3.9.839-1" instead of "5.3.9-839", where the Clear Linux revision is using a dotted notation following the vanilla kernel version. This follows the example of other official Arch Linux kernels such as linux-zen and linux-hardened, and allows us to use proper Arch Linux package revisions.

mystique commented on 2019-10-31 23:30 (UTC)

Is there any potential for an -lts kernel?

aorth commented on 2019-08-21 12:07 (UTC) (edited on 2019-08-22 20:30 (UTC) by aorth)

I posted a vastly improved PKGBUILD based on yw662's version in the better-pkgbuild branch on my GitHub repository[0]. Fixes include:

  • Move PKGBUILD variables out of prepare() function
  • Prefix non-standard PKGBUILD variables with underscore
  • Add manifest and kernel pack to source files
  • Use SHA256 instead of MD5 for verification of source files
  • Let makepkg download source files instead of using curl directly in package()
  • Let makepkg unpack source files instead of using tar directly in package()
  • Use local variables in package() and build()
  • Add WIREGUARD-MODULE to "provides"
  • Add linux.preset file for generating initramfs
  • Add hooks to update and remove initramfs if package is updated or removed
  • Updated to 5.2.9-825

I still don't like the use of pkgver for the Clear Linux kernel version because it breaks the Arch pkgrel logic. For example, we cannot ship an update to 5.2.8-821 without incrementing 821. We can perhaps use the PKGBUILD 'epoch' for this though...

[0] https://github.com/alanorth/aur-linux-clear-bin/tree/better-pkgbuild

btd1337 commented on 2019-08-17 16:49 (UTC)

@yw662 How to enable modules like Wifi and sound?

aorth commented on 2019-08-08 20:37 (UTC) (edited on 2019-08-08 20:38 (UTC) by aorth)

This is cool, yw662. I didn't know Intel provided binaries of Clear Linux kernel. A few suggestions:

  • I think you should use sha256sums instead of md5sums
  • You should add the Manifest and packagefile to sha256sums to let makepkg download and verify them instead of calling curl in the package/build step
  • You should add WIREGUARD-MODULE to provides

yw662 commented on 2019-08-04 22:55 (UTC)

Do not forget the module.sig_unenforce parameter. Stock parameters are saved in /boot/vmlinuz-linux-clear.cmdline, although you may not need to apply all the parameters.