It's stuck on 4.19.2 and its update is a relatively simple version bump: I've been using custom ck-sources ebuilds for a while now which are included here: 4.19.2 is problematic because it contains the ext4 corruption bug: --------------- 4.20.0 ebuild: --------------- # Copyright 2018 kuzetsa℠ and others # Distributed under the terms of the GNU General Public License v2 EAPI="6" ETYPE="sources" KEYWORDS="~amd64 ~x86" HOMEPAGE="https://dev.gentoo.org/~mpagano/genpatches/ http://kernel.kolivas.org/" IUSE="experimental" K_WANT_GENPATCHES="base extras experimental" K_GENPATCHES_VER="1" K_SECURITY_UNSUPPORTED="1" K_DEBLOB_AVAILABLE="1" PYTHON_COMPAT=( python2_7 ) inherit python-any-r1 kernel-2 detect_version detect_arch DEPEND="deblob? ( ${PYTHON_DEPS} )" K_BRANCH_ID="${KV_MAJOR}.${KV_MINOR}" DESCRIPTION="Gentoo's genpatches for Linux ${K_BRANCH_ID}, with Con Kolivas' MuQSS process scheduler." MUQSS_VERSION="185" MUQSS_FILE="0001-MultiQueue-Skiplist-Scheduler-version-v0.${MUQSS_VERSION}.patch" MUQSS_BASE_URL="http://ck.kolivas.org/patches/muqss/4.0" # clearly identify package name in distdir MUQSS_DISTNAME="${PN}-${K_BRANCH_ID}-muqss.patch" CK_LVER_URL="${MUQSS_BASE_URL}/${K_BRANCH_ID}" CK_URI="${CK_LVER_URL}/${MUQSS_FILE} -> ${MUQSS_DISTNAME}" SRC_URI="${KERNEL_URI} ${GENPATCHES_URI} ${ARCH_URI} ${CK_URI}" UNIPATCH_LIST="${DISTDIR}/${MUQSS_DISTNAME}" UNIPATCH_STRICTORDER="yes" pkg_setup() { use deblob && python-any-r1_pkg_setup kernel-2_pkg_setup } -------------------- 5.0.0 ebuild: -------------------- # Copyright 2018 kuzetsa℠ and others # Distributed under the terms of the GNU General Public License v2 EAPI="6" ETYPE="sources" KEYWORDS="~amd64 ~x86" HOMEPAGE="https://dev.gentoo.org/~mpagano/genpatches/ http://kernel.kolivas.org/" IUSE="experimental" K_WANT_GENPATCHES="base extras experimental" K_GENPATCHES_VER="1" K_SECURITY_UNSUPPORTED="1" K_DEBLOB_AVAILABLE="1" PYTHON_COMPAT=( python2_7 ) inherit python-any-r1 kernel-2 detect_version detect_arch DEPEND="deblob? ( ${PYTHON_DEPS} )" K_BRANCH_ID="${KV_MAJOR}.${KV_MINOR}" DESCRIPTION="Gentoo's genpatches for Linux ${K_BRANCH_ID}, with Con Kolivas' MuQSS process scheduler." MUQSS_VERSION="190" MUQSS_FILE="0001-MultiQueue-Skiplist-Scheduler-version-v0.${MUQSS_VERSION}.patch" MUQSS_BASE_URL="http://ck.kolivas.org/patches/muqss/${KV_MAJOR}.0" # clearly identify package name in distdir MUQSS_DISTNAME="${PN}-${K_BRANCH_ID}-muqss.patch" CK_LVER_URL="${MUQSS_BASE_URL}/${K_BRANCH_ID}" CK_URI="${CK_LVER_URL}/${MUQSS_FILE} -> ${MUQSS_DISTNAME}" SRC_URI="${KERNEL_URI} ${GENPATCHES_URI} ${ARCH_URI} ${CK_URI}" UNIPATCH_LIST="${DISTDIR}/${MUQSS_DISTNAME}" UNIPATCH_STRICTORDER="yes" pkg_setup() { use deblob && python-any-r1_pkg_setup kernel-2_pkg_setup }
ETA? Seems unmaintained in gentoo.
I'm trying to reach out to the last proxied maintainer, who did a wonderful job maintaining ck-sources, to have them back on board. In the meantime, I'll see what I can do in terms of version bumps. My apologies for the state of the package.
*** Bug 675558 has been marked as a duplicate of this bug. ***
Here is the muqss updated for 5.1 http://ck-hack.blogspot.com/2019/05/linux-51-ck1-muqss-version-0192-for.html?m=1
Running 5.1.3 right now. Bumped from 4.19.2 ebuild. Notice "v" was dropped from the MUQSS_FILE http file name. --------------------- # Copyright 2018 kuzetsa℠ and others # Distributed under the terms of the GNU General Public License v2 EAPI="6" ETYPE="sources" KEYWORDS="~amd64 ~x86" HOMEPAGE="https://dev.gentoo.org/~mpagano/genpatches/ http://kernel.kolivas.org/" IUSE="experimental" K_WANT_GENPATCHES="base extras experimental" K_GENPATCHES_VER="4" K_SECURITY_UNSUPPORTED="1" K_DEBLOB_AVAILABLE="1" PYTHON_COMPAT=( python2_7 ) inherit python-any-r1 kernel-2 detect_version detect_arch DEPEND="deblob? ( ${PYTHON_DEPS} )" K_BRANCH_ID="${KV_MAJOR}.${KV_MINOR}" DESCRIPTION="Gentoo's genpatches for Linux ${K_BRANCH_ID}, with Con Kolivas' MuQSS process scheduler." MUQSS_VERSION="192" MUQSS_FILE="0001-MultiQueue-Skiplist-Scheduler-version-0.${MUQSS_VERSION}.patch" MUQSS_BASE_URL="http://ck.kolivas.org/patches/muqss/5.0" # clearly identify package name in distdir MUQSS_DISTNAME="${PN}-${K_BRANCH_ID}-muqss.patch" CK_LVER_URL="${MUQSS_BASE_URL}/${K_BRANCH_ID}" CK_URI="${CK_LVER_URL}/${MUQSS_FILE} -> ${MUQSS_DISTNAME}" SRC_URI="${KERNEL_URI} ${GENPATCHES_URI} ${ARCH_URI} ${CK_URI}" UNIPATCH_LIST="${DISTDIR}/${MUQSS_DISTNAME}" UNIPATCH_STRICTORDER="yes" pkg_setup() { use deblob && python-any-r1_pkg_setup kernel-2_pkg_setup }
Also had to drop CONFIG_HZ=1000 to CONFIG_HZ=300 in order to get past kernel boot.
Created attachment 577776 [details] ck-sources 5.0.18 Here is the latest gentoo-source of 5.0 track using Muqss by https://github.com/SveSop/kernel_cybmod/tree/MuQSS-5.0 It build and boots fine in amd64 with my config.
Is it possible to take this program (sys-kernel/ck-sources) out of testing? It would be great to have more stable kernels in Gentoo!
(In reply to Eduardo Coutinho Scalabrin from comment #8) > Is it possible to take this program (sys-kernel/ck-sources) out of testing? > It would be great to have more stable kernels in Gentoo! This is unlikely because ck-sources is not officially maintained by the kernel and kernel security teams. As such, they can't sign off on the stability and security of ck kernels.
I've released 5.1.7 recently. Seeing 5.0.x is EOL, I don't think we will be doing any more updates to that. MuQSS patches don't apply cleanly over 4.19.x and 4.14.x LTS kernels. Contacted upstream about their rebase policy.
Ok. The next question: Is it possible to apply full Con Kolliva's patchset (not oly Muqss) with especial use flag?
Made a diff for 5.1.7 to 5.1.11: --- ck-sources-5.1.7.ebuild 2019-06-19 09:50:06.942532228 +0200 +++ ck-sources-5.1.11.ebuild 2019-06-18 14:15:15.992322574 +0200 @@ -11,7 +11,7 @@ IUSE="experimental" K_WANT_GENPATCHES="base extras experimental" -K_GENPATCHES_VER="8" +K_GENPATCHES_VER="12" K_SECURITY_UNSUPPORTED="1" K_DEBLOB_AVAILABLE="1"
(In reply to Reva Denis from comment #11) > Ok. > The next question: Is it possible to apply full Con Kolliva's patchset (not > oly Muqss) with especial use flag? I saw that just now but made a bug report some days ago. I think it would be a good idea for you to follow it: https://bugs.gentoo.org/688092
Created attachment 581218 [details] Suggested ck-sources-5.1.15 Ok, there is an full-featured ck-sources ebuild. This is my variant for ck-sources, that rely on one single-patch with all missing parts instad of only muqss patch. Booting and working at me
I forgot to change description :)
Created attachment 583144 [details] ck-sources 5.1.18 This is my latest ebuild, it includes all ck-patches apart the renaming one because it breaks external module building and swapiness patch because you can change it via sysctl.
Created attachment 583164 [details] ck-sources-5.1.18 singlepatch Ok, I also update my singlepatch ebuild becouse it's simpler to update it. All seems working stable, no errors during compilation.
(In reply to Reva Denis from comment #17) > Created attachment 583164 [details] > ck-sources-5.1.18 singlepatch > > Ok, I also update my singlepatch ebuild becouse it's simpler to update it. > All seems working stable, no errors during compilation. can you please confirm that external modules (like nvidia-drivers) work? they compile fine but their dependencies fail due to kernel renaming that caused by last part of patch.
No, I can't. I don't have any kernel external modules such as nvidia drivers. That's need researches. If breaks firmware compatibility it's possible to skeep kernel renaming.
Created attachment 583996 [details] ck-sources-5.2.2 singlepatch edition Simple update.
Created attachment 583998 [details] ck-sources 5.2.2 Ebuild for the full patchset. I changed it to download the whole patchset as a whole and apply it all. I suggest to test it. For now works correctly for me (no out of tree special drivers).
Arthur, I don't want to upset you, but does my ebuild do the same, doesn't it?
Reva, you are right, but it downloads it as one file, so without polluting the Manifest file. Also it should be easier for future major releases. On another note, maybe we should merge the full patchset and single patch into one ebuild with a USE flag to toggle. If you agree, I think the default behaviour should be the single patch (even though I prefer the patchset) as in the gentoo repository.
Created attachment 587072 [details] ck-sources 5.2.8 Hello, Added 5.2.8 ck individual patches as an attachment. Builds and runs fine on amd64. All ck patches are applied except swappiness and kernel rename. Kernel rename patch breaks external gentoo modules, such as nvidia. So if we want the full ck patchset we should apply the single patch and remove kernel renaming via another patch, or apply individual patches.
Ok, why don't use swapiness?
Created attachment 587808 [details] ck-sources 5.2.9 Sync to 5.2.9. Builds and boots fine for amd64. I removed swappiness because you can already change it via sysctl and because of: https://chrisdown.name/2018/01/02/in-defence-of-swap.html
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8d5db4b98fa0a1052be8ea7b891aca36f5abcc61 commit 8d5db4b98fa0a1052be8ea7b891aca36f5abcc61 Author: Jory Pratt <anarchy@gentoo.org> AuthorDate: 2019-12-09 23:21:13 +0000 Commit: Jory Pratt <anarchy@gentoo.org> CommitDate: 2019-12-09 23:21:39 +0000 sys-kernel/ck-sources: Version bump This moves use to a full patch from Con instead of a single pick. All 4.x versions have been removed and will be unsupported by myself. Sorry for the trouble look forward to working with you all. Closes: https://bugs.gentoo.org/679978 Closes: https://bugs.gentoo.org/688092 Package-Manager: Portage-2.3.81, Repoman-2.3.20 Signed-off-by: Jory Pratt <anarchy@gentoo.org> sys-kernel/ck-sources/Manifest | 118 ++------------------- sys-kernel/ck-sources/ck-sources-4.14.63.ebuild | 64 ----------- sys-kernel/ck-sources/ck-sources-4.14.66.ebuild | 64 ----------- sys-kernel/ck-sources/ck-sources-4.14.67.ebuild | 64 ----------- sys-kernel/ck-sources/ck-sources-4.14.69.ebuild | 64 ----------- sys-kernel/ck-sources/ck-sources-4.14.71.ebuild | 64 ----------- sys-kernel/ck-sources/ck-sources-4.14.73.ebuild | 64 ----------- sys-kernel/ck-sources/ck-sources-4.14.75.ebuild | 57 ---------- sys-kernel/ck-sources/ck-sources-4.14.78.ebuild | 57 ---------- sys-kernel/ck-sources/ck-sources-4.14.81.ebuild | 57 ---------- sys-kernel/ck-sources/ck-sources-4.18.11.ebuild | 54 ---------- sys-kernel/ck-sources/ck-sources-4.18.13.ebuild | 47 -------- sys-kernel/ck-sources/ck-sources-4.18.16.ebuild | 47 -------- sys-kernel/ck-sources/ck-sources-4.18.19.ebuild | 47 -------- sys-kernel/ck-sources/ck-sources-4.18.5.ebuild | 54 ---------- sys-kernel/ck-sources/ck-sources-4.18.7.ebuild | 54 ---------- sys-kernel/ck-sources/ck-sources-4.18.9.ebuild | 54 ---------- sys-kernel/ck-sources/ck-sources-4.19.2.ebuild | 47 -------- sys-kernel/ck-sources/ck-sources-4.9.120.ebuild | 59 ----------- sys-kernel/ck-sources/ck-sources-4.9.123.ebuild | 59 ----------- sys-kernel/ck-sources/ck-sources-4.9.124.ebuild | 59 ----------- sys-kernel/ck-sources/ck-sources-4.9.126.ebuild | 59 ----------- sys-kernel/ck-sources/ck-sources-4.9.128.ebuild | 59 ----------- sys-kernel/ck-sources/ck-sources-4.9.130.ebuild | 59 ----------- sys-kernel/ck-sources/ck-sources-4.9.132.ebuild | 52 --------- sys-kernel/ck-sources/ck-sources-4.9.135.ebuild | 52 --------- sys-kernel/ck-sources/ck-sources-4.9.137.ebuild | 52 --------- sys-kernel/ck-sources/ck-sources-5.2.3.ebuild | 47 -------- ...ources-5.1.7.ebuild => ck-sources-5.4.2.ebuild} | 16 +-- 29 files changed, 12 insertions(+), 1638 deletions(-)
I'm sorry, but >>> Downloading 'http://ck.kolivas.org/patches/5.0/5.4/5.4-/patch-5.4-ck1.xz' --2019-12-10 11:27:25-- http://ck.kolivas.org/patches/5.0/5.4/5.4-/patch-5.4-ck1.xz Resolving ck.kolivas.org... 84.20.148.218 Connecting to ck.kolivas.org|84.20.148.218|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-12-10 11:27:25 ERROR 404: Not Found.
(In reply to Reva Denis from comment #28) > I'm sorry, but > >>> Downloading 'http://ck.kolivas.org/patches/5.0/5.4/5.4-/patch-5.4-ck1.xz' > --2019-12-10 11:27:25-- > http://ck.kolivas.org/patches/5.0/5.4/5.4-/patch-5.4-ck1.xz > Resolving ck.kolivas.org... 84.20.148.218 > Connecting to ck.kolivas.org|84.20.148.218|:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2019-12-10 11:27:25 ERROR 404: Not Found. Tue Dec 10 06:58 anarchy@bull distfiles $ emerge -f ck-sources Calculating dependencies... done! >>> Fetching (1 of 1) sys-kernel/ck-sources-5.4.2::gentoo * linux-5.4.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] * genpatches-5.4-3.base.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] * genpatches-5.4-3.extras.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] >>> Downloading 'http://distfiles.gentoo.org/distfiles/cf/patch-5.4-ck1.xz' --2019-12-10 06:58:56-- http://distfiles.gentoo.org/distfiles/cf/patch-5.4-ck1.xz Resolving distfiles.gentoo.org... 2600:3402:200:227::2, 2600:3404:200:237::2, 2605:bc80:3010::134, ... Connecting to distfiles.gentoo.org|2600:3402:200:227::2|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-12-10 06:58:56 ERROR 404: Not Found. >>> Downloading 'http://ck.kolivas.org/patches/5.0/5.4/5.4-ck1/patch-5.4-ck1.xz' --2019-12-10 06:58:56-- http://ck.kolivas.org/patches/5.0/5.4/5.4-ck1/patch-5.4-ck1.xz Resolving ck.kolivas.org... 84.20.148.218 Connecting to ck.kolivas.org|84.20.148.218|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 104668 (102K) [text/plain] Saving to: '/var/cache/distfiles/patch-5.4-ck1.xz.__download__' /var/cache/distfile 100%[===================>] 102.21K 118KB/s in 0.9s 2019-12-10 06:58:58 (118 KB/s) - '/var/cache/distfiles/patch-5.4-ck1.xz.__download__' saved [104668/104668] * patch-5.4-ck1.xz BLAKE2B SHA512 size ;-) ... [ ok ] Thanks for letting me know.
