Arch Linux User Repository

Information comment
This comment provides useful information about this package. Make sure to read it through, you won't regret it.

Repository URL
This package is hosted at sos!git. If you want to contribute to the package, you can do it here: https://git.staropensource.de/Packaging/Linux-Tachyon-AUR

Issue handling
Please only submit issues in the package's repository if they aren't bug reports about the package or help requests. Please keep them to the AUR only. This prevents unnecessary signups.

Updates
I usually publish updates 0-3 days after a kernel release, depending on how busy I am.
If I however get wind of security-relevant updates or any vulnerabilities I will try to update the kernel as soon as possible and write a comment about the vulnerability/update. So make sure to subscribe to this package's comment mailing list.

PKGBUILD environment variable customization
The PKGBUILD file supports customization via environment variables. Here's a list of all of them:
- _disable_colorful_logging: Disables fancy colorful logging. Required because we can't read the CI or COLORTERM environment variables
- _additionalpatches: List of additional patches to apply. Must all be prefixed with a plus sign (+) and be separated by spaces. Invalid values are silently ignored
- _makemenuconfig: Invokes make menuconfig (ncurses-based default configuration menu) before compilation starts
- _makenconfig: Invokes make nconfig (ncurses-based nicer configuration menu) before compilation starts
- _makexconfig: Invokes make xconfig (X11-based GUI configuration menu) before compilation starts
- _use_current: Will use the configuration of the running kernel, if the running kernel is compiled with IKCONFIG_PROC
- _optimize_defconfig: Applies package maintainer-picked configuration changes to your defconfig. Only takes effect with _use_current being enabled
- _copyfinalconfig: Copies the final kernel configuration into the repository root as kconfig-new before compilation starts
- _localmodcfg: Only compiles modules found in modprobed-db's database (which decreases compilation time and kernel size)
- _use_llvm_lto: Compiles the kernel with LLVM instead of GCC. Should work, if not open an issue
- _subarch: Specifies the subarchitecture to compile for (see the PKGBUILD file for a list of all subarches). Default is 41/MGENERIC_CPU (Generic x86-64), which is compatible with all amd64 processors. Must be a number or subarch name
- _subarch_microarch: Specifies the microarchitecture to compile for. Only applies to and is required by the MGENERIC_CPU subarch. Must be a number between 1 and 4 (click for more information)
- _debug: Force enables debug options when set to y, force disables debug options when set to n or uses the config defaults when unset

All of these variables just need to be set for them to apply, except for _subarch and _debug. For more information please check their documentation inside the PKGBUILD file

GPG errors
If makepkg complains about invalid PGP keys, try running this command first: gpg --locate-keys torvalds@kernel.org gregkh@kernel.org sashal@kernel.org benh@debian.org. This command only needs to be executed once.

snotabile: Nice to see that it worked and thank you for the nice words! yarost12 (comaintainer) already suggested adding an option for enabling it to me, will likely land in one of the next few releases

@zerou: Thanks to your kind suggestions, I've been using sched_ext since the linux-clear days. Lately, the magic had stopped. Luckily, I found the catch: the config options listed on the documentation page you linked, need to be integrated. Therefore, anyone who wants to enable sched_ext support on linux-tachyon will need to enter the following parameters:

scripts/config -e CONFIG_BPF
scripts/config -e CONFIG_SCHED_CLASS_EXT
scripts/config -e CONFIG_BPF_SYSCALL
scripts/config -e CONFIG_BPF_JIT
scripts/config -e CONFIG_DEBUG_INFO_BTF
scripts/config -e CONFIG_IKHEADERS
scripts/config -e CONFIG_IKCONFIG
scripts/config -e CONFIG_IKCONFIG_PROC
scripts/config -e CONFIG_FTRACE
scripts/config -e CONFIG_TRACING
scripts/config -e CONFIG_FUNCTION_TRACER
scripts/config -e CONFIG_DYNAMIC_FTRACE
scripts/config -e CONFIG_UPROBE_EVENTS
scripts/config -e CONFIG_KPROBE_EVENTS

Thanks again for your support and for the work you do to keep this fantastic kernel alive. Long life to tachyon!

snotabile: First of all, sorry for the late reply. I was in vacation last week and didn't check the package comments afterwards.

According to the related kernel documentation page (which you will have probably already read) you just need to enable a couple of flags (set the environment variable _makemenuconfig when executing makepkg for that) and that should work.

It could however be that some of Tachyon's scheduler patches mess something up. You could try compiling the kernel without some of the patches though.

To do so, do the following:
1. Clone the patches repository (sos!git@StarOpenSource/Linux-Tachyon)
2. Execute ./scripts/linux.sh download to download the kernel source code for the Tachyon version
3. Edit patch_list.txt and comment out the patches you don't want to be applied (most useful would be to try them individually)
4. Execute ./scripts/linux.sh patches-apply
5. Build the kernel (found in ./linux)
6. Go to step 3 and try again until you find the problematic patch(es)

The process is a bit dull unfortunately; I've already created an issue for improving that.

If you have any problems or need assistance, write me an email so we can exchange Fluxer, DeltaChat, Signal or Discord contact info (preference in order).

I am writing to inquire about the feasibility of running sched-ext (scx_lavd) on the current Tachyon kernel. I have been experimenting with it, but I’ve hit a couple of roadblocks related to kernel hardening and configuration: With the default configuration: Attempting to attach an scx scheduler results in an -EBUSY error. Based on my troubleshooting, this appears to be triggered by kernel lockdown mechanisms or CONFIG_DEBUG_KERNEL restrictions. With a custom "slim" configuration: If I disable the debug-related flags, the attachment fails due to missing kernel BTF (failed to find valid kernel BTF / btf__load_vmlinux_btf() returned NULL). Is there a specific configuration path or set of flags that could enable sched-ext compatibility while maintaining Tachyon's performance characteristics? Thanks.

wibucter: yes, soon. i and yarost12 are aiming on releasing an update for 6.17 in a couple of days. some things changed in my personal life meaning that i don't have so much freetime anymore so updates will take a bit longer at times, and we are still fighting a bit with tachyon fork maintenance but that should soon be resolved (hopefully).

Any new update?

AyoltsYas: That's nice to hear!

Been using the kernel for over a week now, these patches made a big difference for my old laptop. I was able to bring down the idle power usage from around 9 watts to 6 watts. Thanks for maintaining the kernel.

AyoItsYas: Hi, StarOpenSource infrastructure was under heavy load yesterday, caused by AI crawlers. To have at least the other StarOpenSource services online I shot sos!git down for a few hours. It is back online since morning (UTC+2) but I cannot give any guarantees that it will stay that way.

I am currently in the process of creating a whole new infrastructure for StarOpenSource which will take advantage of more servers (currently the infrastructure is using only one server, which is bad), so that problem should be remedied in the very near future.

Sorry for that, I hope you can build it now!

PS: I know that package updates are currently lacking. I'm currently a bit overloaded, but will try to update the package in a few days. I'm currently in the process of fixing a few patches that are currently not being applied.

Cheers
- JeremyStarTM

Having issues with cloning from sos!git

fatal: unable to access 'https://git.staropensource.de/StarOpenSource/Linux-Tachyon.git/': The requested URL returned error: 502
==> ERROR: Failure while downloading tachyon git repo
    Aborting...
 -> error downloading sources: /home/yasiru/.cache/yay/linux-tachyon
         context: exit status 1