Package Base Details: linux-clear

Git Clone URL: (read-only)
Keywords: clear clearlinux intel kernel
Submitter: metak
Maintainer: metak
Last Packager: metak
Votes: 19
Popularity: 1.496312
First Submitted: 2018-01-18 21:47
Last Updated: 2019-05-22 13:10

Pinned Comments

metak commented on 2018-01-22 01:49

1. Binaries available in my repo:
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 initcall_debug tsc=reliable no_timer_check noreplace-smp kvm-intel.nested=1 rootfstype=ext4,btrfs,xfs intel_iommu=igfx_off cryptomgr.notests rcupdate.rcu_expedited=1 rcu_nocbs=0-64 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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

bruceutut commented on 2019-02-03 08:05

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

enihcam commented on 2018-11-24 01:29

@metak Yes, after turbo3 patch is removed the package can be built again. :) I have also left this comment in the github.

metak commented on 2018-11-23 15:23

@enihcam That's probably due to the patch turbo3-scheduler.patch in latest commit. No problems on my machine or in repo build. You can try building with that patch disabled to check?

enihcam commented on 2018-11-23 00:27

ld: kernel/sched/fair.o: in function select_task_rq_fair': fair.c:(.text+0x61a): undefined reference tobest_core' ld: fair.c:(.text+0x628): undefined reference to `second_best_core' make[1]: [Makefile:1032: vmlinux] Error 1 make: [Makefile:1001: autoksyms_recursive] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build linux-clear. ==> Restart building linux-clear ? [y/N] ==> ------------------------------------

4.19.3-1 has no such problem.

ltsdw commented on 2018-11-21 18:25

this is not related with the package, but I like to update my problem with module that was resolved after recompile the kernel habilitating preemption. Again, thanks.

ltsdw commented on 2018-11-21 02:28

@metak Yeah, I have module.sig_unenforce as boot parameter... anyway much obliged.

metak commented on 2018-11-21 01:41

@ltsdw What you described sounds more like an issue with yay than this package. The package is properly built and you can manually install the binary.

Edit: as for your edit, have you checked the third point in the sticky comment for dkms modules?

ltsdw commented on 2018-11-20 21:16

@metak so, everything seems be 'ok', nothing appears when I was compiling, none error, the only thing that differs the linux-headers builded from aur (my cached headers from build 19917744) is the size from that one on your repo (19404108). The log build says that installing headers, but when I tried install something for example, whit dkms, says "Your kernel headers for kernel 4.19.2-2-clear cannot be found" so I have to install manually or from my cache or from your binary. (I don't know if it matters but I'm using yay)

Edit: I think this is not related to the package itself, but look what @iwfinger said on this issue that I opened on github:

"Your kernel headers and the compiler version MUST match exactly. "SMP mod_unload" is not the same as "SMP preempt mod_unload". I have never seen this problem as most of my kernels are self-generated, which sidesteps this problem. I'm not sure how to fix it."

You can check on this link:

Do you have idea what can I do?

metak commented on 2018-11-20 19:28

@ltsdw Sorry for late reply. I couldn't reproduce your issue. The package builds fine on my machine and in clean chroot. You'll have to provide more details. Build logs etc.
Have you compared the headers package from my repo with your built binary for differences to make sure your built package is okay?

ltsdw commented on 2018-11-20 19:06

And every module that I tried install I get something like this for example:

[ 2725.823458] 8188eu: version magic '4.19.2-2-clear SMP mod_unload ' should be '4.19.2-2-clear SMP preempt mod_unload '