sys-kernel/bentoo-kernel-bin
Pre-built Linux kernel from CachyOS sources with Gentoo and bentoo patches
Screenshots
View
Download
BrowseChangeLog
commit b5a6aff99c643fe3904e00195ad2d4afc1b4cb5c
Author: lucascouts <lucascs@protonmail.com>
Date: Wed Nov 4 10:50:47 2026 -0300
add(metadata/md5-cache/sys-kernel/bentoo-kernel-bin-7.3.1-r1), del(metadata/md5-cache/sys-kernel/bentoo-kernel-bin-7.3.1), up(sys-kernel/bentoo-kernel-bin-7.3.1 -> 7.3.1-r1)
Rebuilt from sys-kernel/bentoo-kernel-7.3.1-r1: BORE f3770b16 (CachyOS
"7.3: Rebase BORE") now covers update_protect_slice(), so the local
7.3.1-bore-update_protect_slice.patch is dropped. The gpkg is
bentoo-kernel-7.3.1-r1-1 on distfiles.obentoo.org.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit a69a0d62dca6963bbaaef599725218e471840d1d
Author: lucascouts <lucascs@protonmail.com>
Date: Tue Nov 3 10:17:43 2026 -0300
del(sys-kernel/{bentoo-kernel-7.3.0-r1, bentoo-kernel-bin-7.3.0-r1}, virtual/dist-kernel-7.3.0, metadata/md5-cache/{sys-kernel/bentoo-kernel-7.3.0-r1, sys-kernel/bentoo-kernel-bin-7.3.0-r1, virtual/dist-kernel-7.3.0}), mod(sys-kernel/{bentoo-kernel, bentoo-kernel-bin}/Manifest): drop the 7.3.0 series
7.3.1 is booted and is the only version the registry keeps; the DIST
entries removed are the ones no 7.3.1 SRC_URI names.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit 4b8a192a404eb7eb8e24884b824cc368e3670017
Author: lucascouts <lucascs@protonmail.com>
Date: Sun Nov 1 04:21:59 2026 -0300
add(sys-kernel/bentoo-kernel-bin-7.3.1)
Binary of sys-kernel/bentoo-kernel-7.3.1, built by
scripts/build-bentoo-kernel-bin.sh (GCC, bore sched-ext, modules signed
with a throwaway key, MODULE_SIG_FORCE off); every check in the script
passed. The gpkg bentoo-kernel-7.3.1-1.amd64.gpkg.tar (197 MB) is on
distfiles.obentoo.org; a public GET returns 200 and matches the Manifest.
The modules_prepare tree takes the same sources as the binary, including
files/7.3.1-bore-update_protect_slice.patch. Tested unprivileged through
src_configure: every patch applies, modules_prepare succeeds, and its
.config is byte-identical to the one inside the gpkg.
bentoo-kernel-bin-7.3.0-r1 and its R2 object stay as a fallback until
7.3.1 has booted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit 4652f5cdf2a2049e4d4ae061a74663534f547d43
Author: lucascouts <lucascs@protonmail.com>
Date: Sun Oct 25 00:38:51 2026 -0300
del(sys-kernel/{bentoo-kernel-7.2.11, bentoo-kernel-bin-7.2.11}, virtual/dist-kernel-, metadata/md5-cache/{sys-kernel/bentoo-kernel-7.2.11, sys-kernel/bentoo-kernel-bin-7.2.11, virtual/dist-kernel-7.2.9, virtual/dist-kernel-7.2.10, virtual/dist-kernel-7.2.11}), mod(sys-kernel/{bentoo-kernel, bentoo-kernel-bin}/Manifest): drop the 7.2 series
CachyOS moved on to 7.3 without a 7.2.12, and with the 7.3.0 mask lifted
bentoo-kernel{,-bin}-7.3.0-r1 is installable by everyone. The 7.2
virtual/dist-kernel copies existed only to list bentoo-kernel; ::gentoo
carries 7.2.11 and 7.2.12. virtual/dist-kernel-7.3.0 stays.
The Manifests lose the DIST entries only 7.2.11 named (CachyOS 7.2.11-1,
BORE c9ed808e, big-kernel 992fa6e5, the 7.2.11 gpkg); every entry the
7.3.0-r1 ebuilds fetch is kept.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit f04597e51890a793a7844ee2a1f08bb3433b6017
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Oct 23 18:38:26 2026 -0300
up(sys-kernel/bentoo-kernel-bin-7.3.0 -> 7.3.0-r1), mod(profiles/package.mask, metadata/md5-cache)
Rebuilt from sys-kernel/bentoo-kernel-7.3.0-r1 (cachyos-7.3.0-4,
BORE 7.0.0); gpkg bentoo-kernel-7.3.0-r1-1 is on distfiles.obentoo.org.
BINPKG names the source revision literally, so a -bin-only revbump does
not rename it. The mask atom becomes ~, like the source kernel's.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit 24f68f9b4dd30f83df2c9fbe0848598338d52146
Author: lucascouts <lucascs@protonmail.com>
Date: Wed Oct 21 10:31:02 2026 -0300
add(sys-kernel/bentoo-kernel{,-bin}-7.3.0, metadata/md5-cache), mod(.autoupdate/packages.toml, profiles/package.mask)
CachyOS 7.3.0-2, BORE 2b4e3ce8, big-kernel Intel patches at 4c1de6a9
(adds 0104). 0002 no longer applies on 7.3 (drm_WARN_ON_ONCE became
xe_gt_WARN_ON_ONCE in its context), so it ships rebased in files/ via the
new INTEL_PATCHES_REBASED list, applied at the same position.
Gentoo patchset/config are still the 7.2 ones the gentoo-kernel-7.3.0
mirror uses; ::gentoo has published none for 7.3 yet. Both packages join
the existing 7.3.0 package.mask entry, since virtual/dist-kernel-7.3.0 stays
masked until a gentoo-kernel-bin-7.3 exists.
Verified: test build (clang + ThinLTO) compiles; the -bin gpkg built by
scripts/build-bentoo-kernel-bin.sh passed its checks and is on
distfiles.obentoo.org (SHA512 matches the Manifest). Not booted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit 9c1c9bcc6ccc67f29f3e71a54e79c9c1d3f6f71f
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Oct 16 00:02:30 2026 -0300
add(sys-kernel/bentoo-kernel-bin-7.2.11, scripts/build-bentoo-kernel-bin.sh), mod(.autoupdate/packages.toml, metadata/md5-cache)
bentoo-kernel-bin installs a pre-built sys-kernel/bentoo-kernel-7.2.11:
bore + sched-ext, GCC without ThinLTO (provisional: a clang build would
make every out-of-tree module need the exact clang major), x86-64-v3, no
generic-uki (its initramfs would carry the build host's binaries).
Modules are signed with a throwaway key and CONFIG_MODULE_SIG_FORCE is
off, overriding kernel-build's modules-sign default: without Secure Boot,
nvidia-drivers and friends load tainted; under Secure Boot only a
MOK-enrolled key works, and pkg_postinst says so.
The gpkg (bentoo-kernel-7.2.11-1.amd64.gpkg.tar) is ours, on
distfiles.obentoo.org. scripts/build-bentoo-kernel-bin.sh produces it
from the source ebuild with a configuration root and /etc/kernel/config.d
of its own, so nothing of the build host leaks in (config.d, -march,
package.env signing key), checks the CachyOS signature with gpgv, and
refuses the result unless LOCALVERSION, GCC, MODULE_SIG on/FORCE off,
the autogenerated module cert and the absence of any private key hold.
It never uploads; --from-gpkg re-runs only the checks.
Verified: build + every script check, exit 0; ebuild clean install of
the -bin as non-root, exit 0 (5032 modules, signature marker on a
200-module sample); a test out-of-tree module built against the
installed tree has the same vermagic as the in-tree ones; the public
download matches the Manifest (size, BLAKE2B). Not merged, not booted;
verify-sig on the consumer side not exercised (key not installed here).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Author: lucascouts <lucascs@protonmail.com>
Date: Wed Nov 4 10:50:47 2026 -0300
add(metadata/md5-cache/sys-kernel/bentoo-kernel-bin-7.3.1-r1), del(metadata/md5-cache/sys-kernel/bentoo-kernel-bin-7.3.1), up(sys-kernel/bentoo-kernel-bin-7.3.1 -> 7.3.1-r1)
Rebuilt from sys-kernel/bentoo-kernel-7.3.1-r1: BORE f3770b16 (CachyOS
"7.3: Rebase BORE") now covers update_protect_slice(), so the local
7.3.1-bore-update_protect_slice.patch is dropped. The gpkg is
bentoo-kernel-7.3.1-r1-1 on distfiles.obentoo.org.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit a69a0d62dca6963bbaaef599725218e471840d1d
Author: lucascouts <lucascs@protonmail.com>
Date: Tue Nov 3 10:17:43 2026 -0300
del(sys-kernel/{bentoo-kernel-7.3.0-r1, bentoo-kernel-bin-7.3.0-r1}, virtual/dist-kernel-7.3.0, metadata/md5-cache/{sys-kernel/bentoo-kernel-7.3.0-r1, sys-kernel/bentoo-kernel-bin-7.3.0-r1, virtual/dist-kernel-7.3.0}), mod(sys-kernel/{bentoo-kernel, bentoo-kernel-bin}/Manifest): drop the 7.3.0 series
7.3.1 is booted and is the only version the registry keeps; the DIST
entries removed are the ones no 7.3.1 SRC_URI names.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit 4b8a192a404eb7eb8e24884b824cc368e3670017
Author: lucascouts <lucascs@protonmail.com>
Date: Sun Nov 1 04:21:59 2026 -0300
add(sys-kernel/bentoo-kernel-bin-7.3.1)
Binary of sys-kernel/bentoo-kernel-7.3.1, built by
scripts/build-bentoo-kernel-bin.sh (GCC, bore sched-ext, modules signed
with a throwaway key, MODULE_SIG_FORCE off); every check in the script
passed. The gpkg bentoo-kernel-7.3.1-1.amd64.gpkg.tar (197 MB) is on
distfiles.obentoo.org; a public GET returns 200 and matches the Manifest.
The modules_prepare tree takes the same sources as the binary, including
files/7.3.1-bore-update_protect_slice.patch. Tested unprivileged through
src_configure: every patch applies, modules_prepare succeeds, and its
.config is byte-identical to the one inside the gpkg.
bentoo-kernel-bin-7.3.0-r1 and its R2 object stay as a fallback until
7.3.1 has booted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit 4652f5cdf2a2049e4d4ae061a74663534f547d43
Author: lucascouts <lucascs@protonmail.com>
Date: Sun Oct 25 00:38:51 2026 -0300
del(sys-kernel/{bentoo-kernel-7.2.11, bentoo-kernel-bin-7.2.11}, virtual/dist-kernel-, metadata/md5-cache/{sys-kernel/bentoo-kernel-7.2.11, sys-kernel/bentoo-kernel-bin-7.2.11, virtual/dist-kernel-7.2.9, virtual/dist-kernel-7.2.10, virtual/dist-kernel-7.2.11}), mod(sys-kernel/{bentoo-kernel, bentoo-kernel-bin}/Manifest): drop the 7.2 series
CachyOS moved on to 7.3 without a 7.2.12, and with the 7.3.0 mask lifted
bentoo-kernel{,-bin}-7.3.0-r1 is installable by everyone. The 7.2
virtual/dist-kernel copies existed only to list bentoo-kernel; ::gentoo
carries 7.2.11 and 7.2.12. virtual/dist-kernel-7.3.0 stays.
The Manifests lose the DIST entries only 7.2.11 named (CachyOS 7.2.11-1,
BORE c9ed808e, big-kernel 992fa6e5, the 7.2.11 gpkg); every entry the
7.3.0-r1 ebuilds fetch is kept.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit f04597e51890a793a7844ee2a1f08bb3433b6017
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Oct 23 18:38:26 2026 -0300
up(sys-kernel/bentoo-kernel-bin-7.3.0 -> 7.3.0-r1), mod(profiles/package.mask, metadata/md5-cache)
Rebuilt from sys-kernel/bentoo-kernel-7.3.0-r1 (cachyos-7.3.0-4,
BORE 7.0.0); gpkg bentoo-kernel-7.3.0-r1-1 is on distfiles.obentoo.org.
BINPKG names the source revision literally, so a -bin-only revbump does
not rename it. The mask atom becomes ~, like the source kernel's.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit 24f68f9b4dd30f83df2c9fbe0848598338d52146
Author: lucascouts <lucascs@protonmail.com>
Date: Wed Oct 21 10:31:02 2026 -0300
add(sys-kernel/bentoo-kernel{,-bin}-7.3.0, metadata/md5-cache), mod(.autoupdate/packages.toml, profiles/package.mask)
CachyOS 7.3.0-2, BORE 2b4e3ce8, big-kernel Intel patches at 4c1de6a9
(adds 0104). 0002 no longer applies on 7.3 (drm_WARN_ON_ONCE became
xe_gt_WARN_ON_ONCE in its context), so it ships rebased in files/ via the
new INTEL_PATCHES_REBASED list, applied at the same position.
Gentoo patchset/config are still the 7.2 ones the gentoo-kernel-7.3.0
mirror uses; ::gentoo has published none for 7.3 yet. Both packages join
the existing 7.3.0 package.mask entry, since virtual/dist-kernel-7.3.0 stays
masked until a gentoo-kernel-bin-7.3 exists.
Verified: test build (clang + ThinLTO) compiles; the -bin gpkg built by
scripts/build-bentoo-kernel-bin.sh passed its checks and is on
distfiles.obentoo.org (SHA512 matches the Manifest). Not booted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit 9c1c9bcc6ccc67f29f3e71a54e79c9c1d3f6f71f
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Oct 16 00:02:30 2026 -0300
add(sys-kernel/bentoo-kernel-bin-7.2.11, scripts/build-bentoo-kernel-bin.sh), mod(.autoupdate/packages.toml, metadata/md5-cache)
bentoo-kernel-bin installs a pre-built sys-kernel/bentoo-kernel-7.2.11:
bore + sched-ext, GCC without ThinLTO (provisional: a clang build would
make every out-of-tree module need the exact clang major), x86-64-v3, no
generic-uki (its initramfs would carry the build host's binaries).
Modules are signed with a throwaway key and CONFIG_MODULE_SIG_FORCE is
off, overriding kernel-build's modules-sign default: without Secure Boot,
nvidia-drivers and friends load tainted; under Secure Boot only a
MOK-enrolled key works, and pkg_postinst says so.
The gpkg (bentoo-kernel-7.2.11-1.amd64.gpkg.tar) is ours, on
distfiles.obentoo.org. scripts/build-bentoo-kernel-bin.sh produces it
from the source ebuild with a configuration root and /etc/kernel/config.d
of its own, so nothing of the build host leaks in (config.d, -march,
package.env signing key), checks the CachyOS signature with gpgv, and
refuses the result unless LOCALVERSION, GCC, MODULE_SIG on/FORCE off,
the autogenerated module cert and the absence of any private key hold.
It never uploads; --from-gpkg re-runs only the checks.
Verified: build + every script check, exit 0; ebuild clean install of
the -bin as non-root, exit 0 (5032 modules, signature marker on a
200-module sample); a test out-of-tree module built against the
installed tree has the same vermagic as the in-tree ones; the public
download matches the Manifest (size, BLAKE2B). Not merged, not booted;
verify-sig on the consumer side not exercised (key not installed here).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>