EOL of linux-tkg kernel builds on Chaotic-AUR

Announcements
,
1

Forwarding from the Chaotic-AUR announcements:

What’s up, everyone? A lot of time passed since our last announcement. As usual, we hope everyone is feeling fine :smiling_face:

The reason for this announcement is the EOL of linux-tkg kernel builds in our repository. Since we used to provide these since the early beginning, we felt that an announcement explaining the reasoning behind this decision was necessary. The main reasons are:

  • Introduced maintenance burden due to missing options in the kernel config. Since these were missing from time to time, user input was necessary to continue the build process. No other kernel showed this kind of behavior and confirming the use of the default option for all kernel variants is a quite time-consuming and annoying task. Opening issues every time this happens is also unsustainable long-term.
  • Maintainers making use of it moved to linux-cachyos variants and therefore don’t need linux-tkg anymore.
  • Not having a dedicated builder for these packages anymore. During the last months, they were built on demand to not introduce too much load to the main builder. This means builds were sometimes happening too late (or stalled due to the previously mentioned kernel config issues because we can’t babysit the process for multiple hours)

As an alternative, we can recommend the linux-cachyos kernel variants of @ptr1337. They have proven to be great kernels. In case of popular demand, we also might add additional variants of this kernel :blush:

21 Likes
2

Hi,

Since there was some requests, I will add some informations about the current changes and features on the linux-cachyos patchset and kernel.
We are generally widely testing the patches with several users and systems, before pushing them completely out to avoid any issues.
But as always - there can be all time issues, but we work directly with the upstream developers and creator of these patches.

Here you can find a list and information about the changes:

Scheduler

  • linux-cachyos uses as default the BORE Scheduler together paired with the sched-ext framework
  • The sched-ext framework makes it possible to launch customized schedulers at runtime
  • sched-ext example schedulers are available in the scx-scheds package, which can be found in the AUR
    There are 3 interesting example schedulers:
  1. scx_rusty - a general rust written scheduler, which takes care a lot configuration, topology and should provide a equal performance to EEVDF. Its still in development though.
  2. scx_lavd - Latency Sensitive Scheduler, which is mainly thought for Gaming workloads. This one is funded by Valve, which is probably aimed to be used in the SteamOS in the future
  3. scx_rustland - Scheduler written in rust, which uses userspace Scheduling
  • To start a example scheduler, simply run sudo scx_$schedulername and the scheduler will be attached. To stop it simply use CTRL + C
  • There is also a systemd service available, called “scx.service” configuration can be done via /etc/default/scx
  • ECHO Scheduler - new Scheduler from Hamad, which was the developer of the cacULE and TT Scheduler

Base Patchset

  1. aes-xts: Faster aes-xts on modern cpu’s, which utilizes dynamically avx2, avx512, avx10 [PATCH 0/6] Faster AES-XTS on modern x86_64 CPUs - Eric Biggers
  2. amd-pstate: Preffered Core handling from the 6.9 Kernel, amd-cpb boost (disable boost on ZEN CPUs) from lkml
  3. BBR3: Uses as default network algorithm in linux-cachyos, succesor of bbr and bbrv2
  4. Cachy Sauce: Contains tweaks to the default scheduler settings and other cherry picked changes from Zen and Clearlinux, Steam Deck Patches, HDR Enabling, v4l2 loopback module, lenovolegion patchset
  5. Userspace KSM: Patchset from the PF Kernel, which provides a functionality merging identical pages into one. This does reduce the memory usage. Requires the “uksmd” package from the AUR and enabling the service
  6. ZSTD 1.5.6 API: Improves the btrfs and zram compression, currently the kernel uses the 1.5.0 API

Thats so far the current changes, if you have questions, feedback or anything else, let me know.

11 Likes
3

Hi! I am interested in installing cachyos kernel on my garuda. Currently running zen. Since cachyos uses lots of optimization how can I check my computer if I can run cachyos kernel and if there will be any performance improvements?

Here is my garuda-inxi output:
System:
  Kernel: 6.8.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=b8c044ba-3855-4296-80c1-38218b0791fd rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    ibt=off
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm4 v: 4.18.0
    with: xfce4-panel tools: xfce4-screensaver avail: xautolock vt: 7
    dm: LightDM v: 1.32.0 Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: Compulab model: fitlet2 v: 1.31
    serial: <superuser required> uuid: <superuser required>
    UEFI: American Megatrends v: FLT2.TPM.0.46.02.01 date: 05/24/2021
CPU:
  Info: model: Intel Atom E3950 bits: 64 type: MCP arch: Goldmont level: v2
    built: 2016 process: Intel 14nm family: 6 model-id: 0x5C (92) stepping: 9
    microcode: 0x48
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 224 KiB
    desc: d-4x24 KiB; i-4x32 KiB L2: 2 MiB desc: 2x1024 KiB
  Speed (MHz): avg: 1960 high: 2000 min/max: 800/2000 scaling:
    driver: intel_cpufreq governor: performance cores: 1: 2000 2: 2000 3: 2000
    4: 1842 bogomips: 12748
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Apollo Lake [HD Graphics 505] driver: i915 v: kernel
    arch: Gen-9 process: Intel 14n built: 2015-16 ports:
    active: HDMI-A-1,HDMI-A-2 empty: DP-1 bus-ID: 00:02.0 chip-ID: 8086:5a84
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.12 compositor: xfwm4 v: 4.18.0 driver:
    X: loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x1092 s-dpi: 96 s-size: 1016x289mm (40.00x11.38")
    s-diag: 1056mm (41.59")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: top-right model: HP 25es
    serial: <filter> built: 2018 res: 1920x1080 hz: 60 dpi: 88 gamma: 1.2
    size: 553x309mm (21.77x12.17") diag: 633mm (24.9") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: primary,bottom-l model: HP 25es
    serial: <filter> built: 2017 res: 1920x1080 hz: 60 dpi: 88 gamma: 1.2
    size: 553x309mm (21.77x12.17") diag: 633mm (24.9") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.0.4-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 505 (APL 3)
    device-ID: 8086:5a84 memory: 7.23 GiB unified: yes
  API: Vulkan v: 1.3.279 layers: 4 device: 0 type: integrated-gpu name: Intel
    HD Graphics 505 (APL 3) driver: mesa intel v: 24.0.4-arch1.2
    device-ID: 8086:5a84 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
    (LLVM 17.0.6 128 bits) driver: mesa llvmpipe v: 24.0.4-arch1.2 (LLVM
    17.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
  Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl, snd_soc_avs,
    snd_sof_pci_intel_apl bus-ID: 00:0e.0 chip-ID: 8086:5a98 class-ID: 0403
  API: ALSA v: k6.8.4-zen1-1-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel I211 Gigabit Network driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 8086:1539
    class-ID: 0200
  IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel I211 Gigabit Network driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 02:00.0 chip-ID: 8086:1539
    class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-3: Intel I211 Gigabit Network driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: c000 bus-ID: 03:00.0 chip-ID: 8086:1539
    class-ID: 0200
  IF-ID-1: eno1 state: down mac: <filter>
  Info: services: NetworkManager,smbd,sshd
Drives:
  Local Storage: total: 119.24 GiB used: 30.36 GiB (25.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: BIWIN model: SSD size: 119.24 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
    serial: <filter> fw-rev: 2A scheme: GPT
Partition:
  ID-1: / raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 30.36 GiB (25.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 30.36 GiB (25.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 30.36 GiB (25.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 30.36 GiB (25.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 7.4 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 45.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB note: est. available: 7.4 GiB used: 2.06 GiB (27.8%)
  Processes: 239 Power: uptime: 12h 39m states: freeze,mem,disk
    suspend: s2idle wakeups: 0 hibernate: shutdown
    avail: reboot,suspend,test_resume image: 2.94 GiB
    services: upowerd,xfce4-power-manager Init: systemd v: 255
    default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1545 libs: 453 tools: pacseek,pamac,paru
    Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi default: Bash
    v: 5.2.26 running-in: xfce4-terminal inxi: 3.3.33
Garuda (2.6.24-1):
head: cannot open '/var/log/pacman.log' for reading: No such file or directory
  System install date:     
  Last full system update: 2024-04-06
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:
1 Like
4

To be honest I would simply try it out. Some hardware behaves differently than others and people’s workload does as well.

2 Likes
5

Ok. Sounds good. I will give a try to see how it goes.

It’s been over 12 hours since upgrade to cachyos kernel. System is running stable. Overall impression system’s response seems to be faster even not on very recent hardware. I followed Performance optimized repositories - cachyos-aur skipping mkinitcpio part as system uses dracut.

garuda-inxi:
System:
  Kernel: 6.8.4-1-cachyos arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-cachyos
    root=UUID=b8c044ba-3855-4296-80c1-38218b0791fd rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    ibt=off
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm4 v: 4.18.0
    with: xfce4-panel tools: xfce4-screensaver avail: xautolock vt: 7
    dm: LightDM v: 1.32.0 Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: Compulab model: fitlet2 v: 1.31
    serial: <superuser required> uuid: <superuser required>
    UEFI: American Megatrends v: FLT2.TPM.0.46.02.01 date: 05/24/2021
CPU:
  Info: model: Intel Atom E3950 bits: 64 type: MCP arch: Goldmont level: v2
    built: 2016 process: Intel 14nm family: 6 model-id: 0x5C (92) stepping: 9
    microcode: 0x48
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 224 KiB
    desc: d-4x24 KiB; i-4x32 KiB L2: 2 MiB desc: 2x1024 KiB
  Speed (MHz): avg: 1890 high: 1992 min/max: 800/2000 scaling:
    driver: intel_cpufreq governor: performance cores: 1: 1586 2: 1992 3: 1992
    4: 1992 bogomips: 12748
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Apollo Lake [HD Graphics 505] driver: i915 v: kernel
    arch: Gen-9 process: Intel 14n built: 2015-16 ports:
    active: HDMI-A-1,HDMI-A-2 empty: DP-1 bus-ID: 00:02.0 chip-ID: 8086:5a84
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.12 compositor: xfwm4 v: 4.18.0 driver:
    gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x1092 s-dpi: 96 s-size: 1016x289mm (40.00x11.38")
    s-diag: 1056mm (41.59")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: top-right model: HP 25es
    serial: <filter> built: 2018 res: 1920x1080 hz: 60 dpi: 88 gamma: 1.2
    size: 553x309mm (21.77x12.17") diag: 633mm (24.9") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: primary,bottom-l model: HP 25es
    serial: <filter> built: 2017 res: 1920x1080 hz: 60 dpi: 88 gamma: 1.2
    size: 553x309mm (21.77x12.17") diag: 633mm (24.9") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
    inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.0.4-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 505 (APL 3)
    device-ID: 8086:5a84 memory: 7.23 GiB unified: yes
  API: Vulkan v: 1.3.279 layers: 4 device: 0 type: integrated-gpu name: Intel
    HD Graphics 505 (APL 3) driver: mesa intel v: 24.0.4-arch1.2
    device-ID: 8086:5a84 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
    (LLVM 17.0.6 128 bits) driver: mesa llvmpipe v: 24.0.4-arch1.2 (LLVM
    17.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
  Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl, snd_soc_avs,
    snd_sof_pci_intel_apl bus-ID: 00:0e.0 chip-ID: 8086:5a98 class-ID: 0403
  API: ALSA v: k6.8.4-1-cachyos status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel I211 Gigabit Network driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 8086:1539
    class-ID: 0200
  IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel I211 Gigabit Network driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 02:00.0 chip-ID: 8086:1539
    class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-3: Intel I211 Gigabit Network driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: c000 bus-ID: 03:00.0 chip-ID: 8086:1539
    class-ID: 0200
  IF-ID-1: eno1 state: down mac: <filter>
  Info: services: NetworkManager,smbd,sshd
Drives:
  Local Storage: total: 119.24 GiB used: 30.31 GiB (25.4%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: BIWIN model: SSD size: 119.24 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
    serial: <filter> fw-rev: 2A scheme: GPT
Partition:
  ID-1: / raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 30.31 GiB (25.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 30.31 GiB (25.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 30.31 GiB (25.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 30.31 GiB (25.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 7.4 GiB used: 381.5 MiB (5.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 45.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB note: est. available: 7.4 GiB used: 2.78 GiB (37.5%)
  Processes: 266 Power: uptime: 13h 22m states: freeze,mem,disk
    suspend: s2idle wakeups: 0 hibernate: shutdown
    avail: reboot,suspend,test_resume image: 2.94 GiB
    services: upowerd,xfce4-power-manager Init: systemd v: 255
    default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1545 libs: 453 tools: pacseek,pamac,paru
    Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi default: Bash
    v: 5.2.26 running-in: xfce4-terminal inxi: 3.3.33
Garuda (2.6.24-1):
  System install date:     2024-04-07
  Last full system update: 2024-04-07
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:            logrotate.service
3 Likes