Package Base Details: linux-ck

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 410
Popularity: 3.889222
First Submitted: 2011-07-22 14:51
Last Updated: 2019-07-21 10:13

Packages (2)

Latest Comments

« First ‹ Previous ... 3 4 5 6 7 8 9 10 11 12 13 ... Next › Last »

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: https://github.com/graysky2/kernel_gcc_patch/issues/29

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: https://ark.intel.com/products/codename/126287/Kaby-Lake-R

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

Thanks

graysky commented on 2018-09-16 13:01

@ntia89 - https://www.kernel.org/minor-changes-to-tarball-release-format.html

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.

nTia89 commented on 2018-09-16 12:15

some releases ago, I used to download 4.X tar (90MB) and a patch-4.X.Y tar (~KB), while now I download 4.X.Y tar, for every new kernel sub-version. Is there a way to revert to a patch-system in order to build the kernel? I have an very very slow internet connection but I bet it will be appreciate for metered-connection users.

graysky commented on 2018-09-16 11:54

What?

nTia89 commented on 2018-09-16 11:49

Is there an easy way to get back with the kernel patch system?

francoism90 commented on 2018-09-06 07:56

@graysky Sorry for the noise, the commit has been reverted. :|