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: 33
Popularity: 3.66
First Submitted: 2018-01-18 21:47
Last Updated: 2019-12-13 13:53

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 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 1 2 3 4 5 6 7 ... Next › Last »

metak commented on 2019-11-08 16:48

@danhyal I'm afraid that's not possible and it kinda defeats the purpose of this package IMO. I already added two patches (cpu optimizations and acs overrides) because they're small and don't change the kernel in radical way. On the other hand -ck patches are much bigger, touch many more files, change a bunch of existing config options, etc. There could also be clashes between -ck and -clear patches... Besides, this kernel is already optimized for desktop/laptop users so I don't really see a point?

danhyal commented on 2019-11-08 15:40

Could you make a seperate package with the ck patchset applied? Since most people using this kernel are desktop/laptop users, it would be useful.

metak commented on 2019-11-05 12:12

@danhyal 5.3.8-4 (clr 5.3.7-853) enable CONFIG_NETFILTER_INGRESS

danhyal commented on 2019-11-05 09:01

Could you add the config option CONFIG_NETFILTER_INGRESS

dedguy21 commented on 2019-11-04 21:14

Ah I am running mkinicpio 26 not 27 I will update. Thanks.

_----------- Yes everything is working now.

Thanks again for your time.

metak commented on 2019-11-04 19:10

@dedguy21 I'm a bit confused as to what you want to achieve? You don't need to do 1) and 2). New version of mkinitcpio=27-1 includes hook and preset files so that not every kernel package has to provide them. Just build this package as any other or use the binaries provided in my repo.

dedguy21 commented on 2019-11-04 18:51

@ metak Apologies for the possible noobie questions....

I have the linux-clear kernel in the /usr/lib/module folder.

1) How can I write the proper compressed image to the /boot folder 2) and the .preset files to the mkinitcpio.d folder

I used yay for installation, should I just git files and run make install?

metak commented on 2019-11-04 11:48

@dedguy21 Hello. linux-clear package is the "main" kernel, it's the default kernel in clearlinux and clear team focuses the most on it. With that said, linux-clear-current is used mostly for testing purposes when kernel nears towards the latest release candidates (and first .0 release and .1 sometimes) then clear team rebase their patches and test this new kernel. These patches are then moved to linux-clear when everything seems ok. After that they don't update the linux-clear-current much, it's stuck on 5.3.1 and I expect it will get updated with 5.4rc7? I don't know. The kernel .config file is pretty much the same as they try to sync changes between their kernels, the exception being patch for exfat patch and some crypto modules that were introduced in linux-clear.

Yes, I'm maintaining both of them and as you can see they're two separate packages and neither is being abandoned. Use linux-clear and later in kernel development cycle if you want to test the latest rc then try linux-clear-current.

I follow stock arch's kernel way of packaging and those changes were brought by 5.3.8.1-1: Changes for new kmod and mkinitcpio hooks.

dedguy21 commented on 2019-11-04 00:00

First of all I wanted to say thanks for the Clear Linux packages. I always thought if you could marry their kernel with Arch you would have the perfect distro.

So wondering why does linux-clear package has a kernel number higher than linux-clear-current package?

And are you maintaining both packages separately? Or is one being abandoned for the other?

Also, when I install this package, I notice that there isn't an image for this created to the /boot or any .preset in mkinitcpio.d

I located the file in /usr/lib/module

...just wondering if this was done on purpose on your end.

Thanks again

tam1m commented on 2019-10-30 14:09

@metak Ok I didn't know that /usr/lib/modules/<kernel>/build/.config existed. Copying it to another location seems unnecessary, especially since /usr/lib/kernel/.config would nowhere be mentioned in the "Arch World". CONFIG_IKCONFIG is at least enabled by default in arch's linux package. That's why I thought it would be nice to have it in linux-clear, too.