Package Details: linux-ck-headers 6.11.10-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: Headers and scripts for building modules for Linux-ck kernel
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.137884
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Latest Comments

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 .. 308 Next › Last »

graysky commented on 2020-07-23 13:22 (UTC)

@vltr - You sure?

% sha256sum unfuck-ck1-fix-suspend-to-ram.patch
961ed94b8d905f1e901cacb08d253c4170af0a25828111b7558d9c874e923558  unfuck-ck1-fix-suspend-to-ram.patch

vltr commented on 2020-07-23 12:53 (UTC)

hi there, @graysky! just one problem with 5.7.10: the unfuck-ck1-fix-suspend-to-ram.patch has a sha256sum of value 961ed94b8d905f1e901cacb08d253c4170af0a25828111b7558d9c874e923558 in the PKGBUILD, which would not pass the validity check since the correct sha256sum should be 9ad11f720d4dd83ddb8876b453f4526ad35f1ff72465213764fb1d206fea0379. apart from that, everything works fine. thanks!

nTia89 commented on 2020-06-12 16:05 (UTC)

Above all, thanks @graysky for the change! Anyway, /tmp defaults to tmpfs with size=50% but not everybody has so much RAM. By my own, this is the biggest mistake behind that choice...

dimosd commented on 2020-06-12 15:23 (UTC)

I suggest that you disable CONFIG_DEBUG_INFO, as it was before 5.7.2. That's what I am doing in my own builds anyway to build with a 4GB /tmp.

artafinde commented on 2020-06-12 12:23 (UTC)

graysky: Got my answer: https://bugs.archlinux.org/task/66260

artafinde commented on 2020-06-12 10:14 (UTC)

Kr1ss: I think devs would probably reply don't build in tmpfs (and require ~15G of space instead of ~3.5G) but that's a discussion for forums possibly :D - Thanks graysky.

Kr1ss commented on 2020-06-12 09:54 (UTC)

Thx @graysky ! I was only able to build 5.7.2-1 after blowing up /tmp to 20GiB, that's kind of ridiculous. If a user needs debug symbols they can enable them; I think most users wouldn't need'em anyways.

Cheers !

graysky commented on 2020-06-12 09:21 (UTC)

@artafinde - Fuck it, 5.7.2-2-ck1. Change my mind.

artafinde commented on 2020-06-12 09:13 (UTC)

@graysky - Agree, especially since later we strip it from the bug symbols. I raised the question in IRC but no answer. I guess forums or a bug might have better luck.

graysky commented on 2020-06-12 07:53 (UTC) (edited on 2020-06-12 08:16 (UTC) by graysky)

@artafinde - Yes, the debug stuff causes a failure on one of my machines with 16G of memory building in tmpfs (allocating 14.5G to the tmpfs partition on which the build root resides!)

This change was introduced with 5.7.2-1-arch1 here: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=663b08666b269eeeeaafbafaee07fd03389ac8d7

First question is why do we need the debug options?

"If you say Y here the resulting kernel image will include debugging info resulting in a larger kernel image. This adds debug symbols to the kernel and modules (gcc -g), and is needed if you intend to use kernel crashdump or binary object tools like crash, kgdb, LKCD, gdb, etc on the kernel. Say Y here only if you plan to debug the kernel. If unsure, say N."