Package Details: linux-clear-headers 5.3.7-1

Git Clone URL: (read-only)
Package Base: linux-clear
Description: Header files and scripts for building modules for linux-clear
Upstream URL:
Keywords: clear clearlinux intel kernel
Licenses: GPL2
Submitter: metak
Maintainer: metak
Last Packager: metak
Votes: 28
Popularity: 3.080656
First Submitted: 2018-01-18 21:47
Last Updated: 2019-10-17 22:46

Pinned Comments

metak commented on 2018-01-22 01:49

1. Binaries available in my repo:
Server =$arch

Then, import the key:
Key-ID: pacman-key --recv-keys 50AAD02AEB1F61C9
Donwload and import the key: pacman-key --add /path/to/downloaded/keyfile

Last, sign the key. pacman-key --lsign-key 50AAD02AEB1F61C9

2. After install adjust your boot cmd line. ClearLinux uses clr-boot-manager which takes care of that. This is upstream default:
quiet console=tty0 console=ttyS0,115200n8 cryptomgr.notests initcall_debug intel_iommu=igfx_off kvm-intel.nested=1 no_timer_check noreplace-smp page_alloc.shuffle=1 rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs tsc=reliable rw 
3. For loading unsigned modules. (nvidia, virtualbox, etc.)

If secure boot is disabled just add module.sig_unenforce boot parameter. Otherwise, you'll have to build your kernel with CONFIG_MODULE_SIG_FORCE disabled.

4. Once again (as requested) the _subarch is set to native so for anyone who is building the binaries for redistribution should set it to number corresponding to Generic-x86-64.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

rvlobato commented on 2019-10-15 22:58

@calin @metak I was having the same issue, seems that the conflict was between nvidiafb and nvidia, after blacklisting the nvidiafb (the nvidia-dkms blacklist nouveau) the nvidia modules were loaded.

metak commented on 2019-10-11 18:29

@calin I've already disabled CONFIG_MODULE_SIG_FORCE by default to make it easier and you should not need module.sig_unenforce. Check logs for more clues?

calin commented on 2019-10-10 08:54

The nvidia drivers fail to load even when using module.sig_unenforce, they used to work, not anymore unfortunately, is anyone else having this issue?

metak commented on 2019-10-01 20:03

@Elanzer Sorry about that. The pkgbuild file in obs wasn't synced fully and dell smbios should've been enabled long ago (as it is here in aur). The repo binary is already building.

Elanzer commented on 2019-10-01 19:31

@metak can you compile lts-2018 with CONFIG_DELL_SMBIOS_SMM=y or CONFIG_DELL_SMBIOS_WMI=y?? I dont know which one works for mine. My touchpad is weird with 5.3 so I rolledback to LTS. And with the older kernel i'm getting SMBIOS messages again. My laptop is old and it takes forever to compile a kernel, your binaries are a life-saver. Thanks.

metak commented on 2019-09-20 18:45

@toki1990 I believe it should work on amd cpus, but I don't have amd cpus to try. If you can post some logs maybe someone can help.

toki1990 commented on 2019-09-19 16:57

kernel build complete without error. but kernel not work over amd ryzen processor. is there a way run over amd ?

xuanruiqi commented on 2019-09-08 04:30

It seems that I need the cpio package to correctly build linux-clear. Maybe this is due to some kernel options I enabled, but not sure which ones.

metak commented on 2019-08-26 18:12

@btd1337 That's for archlinux Trusted Users and Developers, not some random aur maintainers. ;-)

btd1337 commented on 2019-08-25 21:24

@metak Why you don't use the Arch Servers? Like here: