Package Base Details: linux-ck

Git Clone URL: (read-only)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 394
Popularity: 3.001011
First Submitted: 2011-07-22 14:51
Last Updated: 2018-12-17 10:13

Packages (2)

Latest Comments

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

graysky commented on 2018-10-05 16:25

@ELMastro - Do not build with an AUR helper. Use makepkg.

ElMastro commented on 2018-10-05 02:49

After [code] INSTALL sound/usb/line6/snd-usb-line6.ko INSTALL sound/usb/line6/snd-usb-pod.ko INSTALL sound/usb/line6/snd-usb-podhd.ko INSTALL sound/usb/line6/snd-usb-toneport.ko INSTALL sound/usb/line6/snd-usb-variax.ko INSTALL sound/usb/misc/snd-ua101.ko INSTALL sound/usb/snd-usb-audio.ko INSTALL sound/usb/snd-usbmidi-lib.ko INSTALL sound/usb/usx2y/snd-usb-us122l.ko INSTALL sound/usb/usx2y/snd-usb-usx2y.ko INSTALL virt/lib/irqbypass.ko DEPMOD 4.18.12-1-ck-ck rm: [/code] mine complains it can't remove '/tmp/packerbuild-1001/linux-ck/linux-ck/pkg/linux-ck/usr/lib/modules/4.18.12-1-ck/source' Can someone please confirm I'm the only one with this problem?

graysky commented on 2018-10-04 21:40

@fran - I mirror the Arch official config just allowing CK1 to set the options it wants to. Does your setup work with the official Arch kernel?

francoism90 commented on 2018-10-01 09:16

@graysky Something goes wrong after the latest kernel update. I use something like this cryptkey=/dev/disk/by-uuid/..:ext4:/keys/mykey as kernel parameter, but it seems the USB is no longer init at boot. When using linux 4.10 it works correctly and the USB contents will be read.

Seems changes have been made in the config ( - don't know why this happens, do you have an idea? :)

air-g4p commented on 2018-09-25 09:44

@graysky - Thank you for sending me down the issues/29 path. I learned quite a bit, and now realize this 'problem' is upstream in nature. I'm sure this will not come as a surprise to you, but I'm running gcc version 8.2.1 20180831 (GCC) and the output of: gcc -c -Q -march=native --help=target | grep march is: -march= skylake Now I understand why, which I do appreciate.

graysky commented on 2018-09-23 17:56

@air-g4p - Your question is really for the gcc patchset I maintain. Issue 29 linked below applies but to my knowledge, there hasn't been any gcc changes to support your CPU. If I am wrong, plz post to the issue against the patch:

air-g4p commented on 2018-09-23 08:03

o/ graysky:

I'm running an i7-8550U which Intel describes as belonging to the Kaby Lake R family. This family was launched in Q3 2017.

That family of CPUs lives here:

Are you planning to add Kaby Lake support within your PKGBUILD or do you suggest I use another one of the other PKGBUILD 'Lakes'?


graysky commented on 2018-09-16 13:01

@ntia89 -

nTia89 commented on 2018-09-16 12:56

oh, thanks... I was missing the change upstream (kernel dev) :-(

graysky commented on 2018-09-16 12:47

This change mirrors that of the upstream Arch kernel and is due to the change of upstream (kernel source) not signing patches any more. You can modify the PKGBUILD to be like the old behavior if you want, but I will maintain as closely as I can how Arch upstream does it.