AUR (en) - linux-ck

Git Clone URL:	https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base:	linux-ck
Description:	The Linux kernel and modules with ck's hrtimer patches
Upstream URL:	https://wiki.archlinux.org/index.php/Linux-ck
Licenses:	GPL-2.0-only
Provides:	KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces:	virtualbox-guest-modules-arch, wireguard-arch
Submitter:	graysky
Maintainer:	graysky
Last Packager:	graysky
Votes:	459
Popularity:	0.92
First Submitted:	2011-07-22 14:51 (UTC)
Last Updated:	2024-09-19 13:04 (UTC)

Latest Comments

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 34 35 .. 307 Next › Last »

graysky commented on 2019-08-03 19:22 (UTC) (edited on 2019-08-03 19:23 (UTC) by graysky)

Yeah, I think you shouldn't use native in non-interactive mode. See the comments:

Note - the march=native option is unavailable by this method, use the and manually select it.

kwe commented on 2019-08-03 15:01 (UTC) (edited on 2019-08-03 15:03 (UTC) by kwe)

Since switching from _subarch=20 (MIVYBRIDGE) to _subarch=28 (MNATIVE) in the PKGBUILD, it won't build:

  24. Intel Skylake X (MSKYLAKEX) (NEW)  
  25. Intel Cannon Lake (MCANNONLAKE) (NEW)  
  26. Intel Ice Lake (MICELAKE) (NEW)  
> 27. Generic-x86-64 (GENERIC_CPU)  
  28. Native optimizations autodetected by GCC (MNATIVE) (NEW)  
choice[1-28?]: 28  
Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW) 28  
Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW) 28  
Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW) 28  
Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW) 28  
Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW) 28  
Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW) 28

The last message keeps looping forever.

When I switch back to the default _subarch= with no value, the process/interaction seems suboptimal:
- it asks me choice[1-28?]:
- I choose 28
- it asks me Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW)
- I choose y
- it does the modprobed-db recall (as configured)
- it asks me BT8XX GPIO abuser (GPIO_BT8XX) [N/m/y/?] (NEW)
- I choose n (why does this ask me every time?)
- it asks me Studio Evolution SE6X (SND_SE6X) [N/m/?] (NEW)
- I choose n (again, why does this ask me every time?)
- ==> Sources are ready.

air-g4p commented on 2019-07-30 06:28 (UTC)

@graysky - Thanks, and understood.

@zerophase - Thanks, what you said made sense, and got me thinking about my chroot. As I had been using makechrootpkg of late to build linux-ck, I completely forgot that command neither cleans, nor updates a chroot.

As soon as I built linux-ck with my typical extra-x86_64-build my chroot got cleaned and updated, which resolved all the DKMS incompatible gcc versions installation issues.

zerophase commented on 2019-07-29 19:11 (UTC)

@air-g4p if you can rollback to the last good kernel you should be able to install. The last time I had dkms issues was from updating the kernel multiple times without rebooting. On the second kernel update I usually receive a bunch of errors about the version of the kernel dkms is looking for does not exist. Pretty sure that's what is happening to you too.

graysky commented on 2019-07-29 19:06 (UTC)

I do not use dkms so I wouldn't know where to start with it.

air-g4p commented on 2019-07-29 13:34 (UTC) (edited on 2019-07-29 13:35 (UTC) by air-g4p)

@graysky - Saw these DKMS installation errors today after building -ck on my fully updated system:

(2/6) Install DKMS modules ==> dkms install bbswitch/0.8 -k 5.2.4-1-ck Error! Bad return status for module build on kernel: 5.2.4-1-ck (x86_64) Consult /var/lib/dkms/bbswitch/0.8/build/make.log for more information. ==> dkms install vboxhost/6.0.10_OSE -k 5.2.4-1-ck Error! Bad return status for module build on kernel: 5.2.4-1-ck (x86_64) Consult /var/lib/dkms/vboxhost/6.0.10_OSE/build/make.log for more information. ==> dkms install nvidia/430.34 -k 5.2.4-1-ck Error! Bad return status for module build on kernel: 5.2.4-1-ck (x86_64) Consult /var/lib/dkms/nvidia/430.34/build/make.log for more information. ==> dkms install wireguard/0.0.20190702 -k 5.2.4-1-ck Error! Bad return status for module build on kernel: 5.2.4-1-ck (x86_64) Consult /var/lib/dkms/wireguard/0.0.20190702/build/make.log for more information.

My /build/make.logs show multiple instances of:

cc1: error: incompatible gcc/plugin versions cc1: error: fail to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so

Is there a workaround, or a solution?

graysky commented on 2019-07-27 22:15 (UTC)

@SuperIce - Right you are thanks, fixed.

SuperIce97 commented on 2019-07-27 22:13 (UTC) (edited on 2019-07-27 22:13 (UTC) by SuperIce97)

@graysky The 26 should be changed to 27 in this comment in the PKGBUILD: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-ck#n15

nTia89 commented on 2019-07-27 09:25 (UTC)

great!

graysky commented on 2019-07-26 20:22 (UTC)

@nTia89 - Yes, but was waiting for 5.2.3 to incorporate that and the other 2 patches. See: https://aur.archlinux.org/cgit/aur.git/commit/?h=linux-ck&id=c4e43c48637e

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 34 35 .. 307 Next › Last »

Arch Linux User Repository

Search Criteria

Package Details: linux-ck 6.11-1

Package Actions

Dependencies (14)

Required by (6)

Sources (6)