Package Base Details: linux-clear

Git Clone URL: (read-only, click to copy)
Keywords: clear clearlinux intel kernel
Submitter: metak
Maintainer: metak
Last Packager: metak
Votes: 34
Popularity: 2.34
First Submitted: 2018-01-18 21:47
Last Updated: 2020-01-23 09:53

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

« First ‹ Previous ... 9 10 11 12 13 14 15 16 17 18 19 ... Next › Last »

xuanruiqi commented on 2019-02-22 20:12

I tried and seems that it doesn't break anything.

metak commented on 2019-02-20 13:56

@xuanruiqi You can try it if you want. If you followed the instructions in my pinned comment and it still for some reason doesn't work you can still just reboot to default kernel. It shouldn't break anything.

xuanruiqi commented on 2019-02-20 07:34

Thinking about installing this, but wanted to confirm that the extra boot parameters won't break other installed kernels.

bruceutut commented on 2019-02-16 05:09

@metak works like a charm on both local and building machine. thanks m8.

metak commented on 2019-02-15 12:40

@bruceutut Edit: Hey brucetut. I rearranged some things in pkgbuild file and now it appears to build fine. ;-) Can you try it and report back. (I won't bump pkrel for this)

bruceutut commented on 2019-02-14 06:13


Here is the full build log on building machine built with extra-x86_64-build

And built package with issue:

And same package built with makepkg on my local machine:

And my friend another aur packager try to modify pkgbuild to solve this issue refering ths

Thanks again.

metak commented on 2019-02-13 22:37

@bruceutut I'll try replicating this issue when I get some free time, but in the meantime, you could upload full build logs and the built 'bad' package somewhere for me to take a look.

bruceutut commented on 2019-02-13 12:42


Actually, I can build correct package using makepkg command. Or yay/pikaur something.

But the bad package using extra-x86_64-build command, on local machine or my building machine.

The bad package does not have crypto_user and xz compression module is not enabled as well.

Thanks for your patience :)

metak commented on 2019-02-03 15:09

@bruceutut crypto_user should be built since this pkgbuild enables it. It's in /usr/lib/modules/4.20.6-1-clear/kernel/crypto/crypto_user.ko.xz, both on my local build and in clean chroot for repo.
Have you checked your build log? You haven't provided any info.

bruceutut commented on 2019-02-03 08:05

crypto_user module not found in package after successful build.
Anything am i doing wrong ?