Search Criteria
Package Base Details: linux-ck
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-ck.git (read-only, click to copy) |
---|---|
Submitter: | graysky |
Maintainer: | graysky |
Last Packager: | graysky |
Votes: | 461 |
Popularity: | 1.01 |
First Submitted: | 2011-07-22 14:51 (UTC) |
Last Updated: | 2024-03-16 18:02 (UTC) |
Latest Comments
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 305 Next › Last »
vp1981 commented on 2021-05-19 05:45 (UTC)
graysky> GCC 11 reorders things and since GCC 11 is in [core], I updated the PKGBUILD.
That was a culprit! I updated PKGBUILD, rebuild the package (linux-ck-sandybridge) and was able to boot with linux-ck-sandybridge kernel.
elektorronikci commented on 2021-05-18 18:47 (UTC) (edited on 2021-05-18 18:47 (UTC) by elektorronikci)
@graysky, thanks for your suggestion. There is not any problem for me, I had already corrected it when I saw it on nconfig. I mentioned about it just to inform.
graysky commented on 2021-05-18 17:43 (UTC)
Right, define an updated mirror and update your system :D
elektorronikci commented on 2021-05-18 17:02 (UTC)
@graysky, no it is GCC 10.2
thaewrapt commented on 2021-05-18 16:05 (UTC)
It could also happen on automation level, where the build system is still using old IDs. I'm building for Skylake right now so I can check if it's actually built for Skylake in the end.
thaewrapt commented on 2021-05-18 16:00 (UTC) (edited on 2021-05-18 16:02 (UTC) by thaewrapt)
Yeah, as I hadn't any issues myself I wanted to suggest "a wrong architecture" source of the problem since I've noticed a change of architecture IDs in the package. For example, I've used 25 for Skylake for quite a long time but in the very last release I see it numbered as 26.
graysky commented on 2021-05-18 15:53 (UTC)
@elektorronikci - Is your system up-to-date? GCC 11 reorders things and since GCC 11 is in [core], I updated the PKGBUILD.
elektorronikci commented on 2021-05-18 15:48 (UTC) (edited on 2021-05-18 15:51 (UTC) by elektorronikci)
There is a problem in the PKGBUILD subarch configuration. When I select Haswell, it was actually Broadwell in the .config file. That may cause boot problem because of some unimplemented machine codes.
vp1981 commented on 2021-05-17 08:46 (UTC)
Ok, I posted message on ck's blog.
I suspect an issue with ck patch and GCC11 but I don't understand why newer processors (haswell and skylake specifically) work.
vp1981 commented on 2021-05-17 03:01 (UTC)
@graysky, thanks I'll do that when I finish testing. I compiled linux-ck-sandybridge 5.12.2, 5.12.3 with the same configuration as 5.12.4 (but without 0002-drm* patch applied) but both kernels didn't boot.
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 305 Next › Last »