Package Base Details: linux-clear

Git Clone URL: https://aur.archlinux.org/linux-clear.git (read-only, click to copy)
Keywords: clear clearlinux intel kernel
Submitter: metak
Maintainer: metak
Last Packager: metak
Votes: 37
Popularity: 4.18
First Submitted: 2018-01-18 21:47
Last Updated: 2020-02-14 22:18

Pinned Comments

metak commented on 2018-01-22 01:49

1. Binaries available in my repo: http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/x86_64/
[home_metakcahura_kernel_Arch_Extra_standard]
Server = http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/$arch

Then, import the key:
Key-ID: pacman-key --recv-keys 50AAD02AEB1F61C9
Keyfile: http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/x86_64/home_metakcahura_kernel_Arch_Extra_standard.key
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,f2fs 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 ... 13 14 15 16 17 18 19 20 21 22 23 ... Next › Last »

Enverex commented on 2018-07-30 11:04

Any chance of making CONFIG_MNATIVE the default (rather than CONFIG_MCORE2) or having some way of enabling it without having to manually edit the PKGBUILD? (e.g. so that the package can be updated and keep this setting without manual intervention).

metak commented on 2018-07-19 15:43

@enihcam I don't mind at all, but I hope it won't be flagged out-of-date again if it's not following kernel.org releases. ;-)

enihcam commented on 2018-07-19 14:25

@metak again, this package is great. people using this package should vote for it. :)

this is only a suggestion. Personally i think it might be too frequent for compiling the kernel because the rapidly increasing version. i think it might be good to slow down a little bit.

Rather than watching www.kernel.org, maybe you want to release a version only when this RSS is updated: https://github.com/clearlinux-pkgs/linux/releases.atom

what do you think?

metak commented on 2018-07-08 17:52

@big_bun Sorry for late reply, I've been busy. I really don't want to deviate too much from default upstream. (only when needed to comply with archlinux packaging for example)

big_bum commented on 2018-07-05 20:37

@metak could you also add l2tp/pptp module in the next build? I think this should enable them: https://github.com/scaleway/kernel-tools/pull/143/commits/381264d671060a26fdfcf6245ea417d85bc371b0

metak commented on 2018-06-30 17:58

@A.J If you have SecureBoot disabled then you simply use this boot parameter module.sig_unenforce to allow loading unsigned kernel modules. Otherwise you'll have to build your kernel with CONFIG_MODULE_SIG_FORCE disabled.

A.J commented on 2018-06-30 17:50

@metak could you elaborate , is it boot option or build option ??

metak commented on 2018-06-30 12:04

@A.J Look below in comments for my comment to @Osleg about option to allow unsigned modules.

A.J commented on 2018-06-30 04:17

sorry for the noop question , but i couldn't get nvidia-dkms working and when i modprobe it i get :

modprobe: ERROR: could not insert 'nvidia': Required key not available

metak commented on 2018-06-25 23:11

@ltsdw Thank you for reporting back. I don't use bluetooth at all so I never paid too much attention to it, but it seems that quite a few people do use it so I'll enable the crypto_user module in next update.