Package Details: linux-xanmod-bore-headers 6.15.9-1

Git Clone URL: https://aur.archlinux.org/linux-xanmod-bore.git (read-only, click to copy)
Package Base: linux-xanmod-bore
Description: Headers and scripts for building modules for the Linux Xanmod (Stable) with BORE CPU scheduler and tickrate customizations kernel
Upstream URL: http://www.xanmod.org/
Keywords: kernel xanmod
Licenses: GPL2
Submitter: micros24
Maintainer: micros24
Last Packager: micros24
Votes: 7
Popularity: 0.30
First Submitted: 2023-07-03 13:46 (UTC)
Last Updated: 2025-08-02 18:23 (UTC)

Latest Comments

micros24 commented on 2025-08-03 19:49 (UTC)

fixed the hunk failure

ninetailedtori commented on 2025-08-03 17:46 (UTC)

0001-bore.patch needs to be updated to 58cc515f9363948b69dba8f0e2c11f69c89fb5b07481308811680a3373ddd8be. Hunk 2 fails at 8558:

--- kernel/sched/core.c
+++ kernel/sched/core.c
@@ -8558,6 +8562,10 @@ void __init sched_init(void)
    BUG_ON(!sched_class_above(&ext_sched_class, &idle_sched_class));
 #endif
 'x86_64'
+#ifdef CONFIG_SCHED_BORE
+   sched_bore_init();
+#endif // CONFIG_SCHED_BORE
+
    wait_bit_init();

 #ifdef CONFIG_FAIR_GROUP_SCHED

Issue opened: https://github.com/micros24/linux-xanmod-bore/issues/102

noitemstoshow commented on 2024-10-13 23:48 (UTC)

have tried that and that one's same, so I guess its problem from upstream

micros24 commented on 2024-10-13 21:28 (UTC)

@noitemstoshow can you try compiling the "linux-xanmod" package then boot into it and see if that can detect your drives? It might be related to the Xanmod kernel itself without the BORE scheduler.

noitemstoshow commented on 2024-10-11 10:12 (UTC)

Tried this with modprobed-db, my previous testing with linux-clear works fine. However some how with this kernel, it seems my seagate internal HDD sda, and my samsung SSD sdb, are both not detected by the OS. Not to be found in /dev/.

Both kernels are compiled with the same modprobed-db. It is something special here that prevent the harddrives been detected.

micros24 commented on 2024-09-10 02:55 (UTC)

Thanks for letting me know. It is now fixed.

SuperSuslik312 commented on 2024-09-09 12:44 (UTC)

choose-gcc-optimization.sh file has a different checksum than the one in PKGBUILD. because of this, there is a validation error all the time unless you manually change it, or skip any validation checks.