Garuda boot options bug

inxi -Faz
Kernel: 5.15.11-230-tkg-pds x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: intel_pstate=passive BOOT_IMAGE=/vmlinuz-linux-tkg-pds
root=UUID=eaada518-9789-45a6-96d5-9ea2e9563ec6 rw rootflags=subvol=@
rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
kernel.unprivileged_userns_clone=0 kernel.yama.ptrace_scope=2
lsm=landlock,lockdown,yama,apparmor,bpf net.core.bpf_jit_harden=2
apparmor=1 security=apparmor delayacct
Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Type: Server Mobo: Intel model: S2600CP v: G50768-509
serial: <superuser required> BIOS: Intel
v: SE5C600.86B.02.06.0007.082420181029 date: 08/24/2018
Info: model: Intel Xeon E5-2650 v2 bits: 64 type: MT MCP SMP
arch: Ivy Bridge family: 6 model-id: 0x3E (62) stepping: 4 microcode: 0x42E
Topology: cpus: 2x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 2x 512 KiB (1024 KiB) desc: d-8x32 KiB; i-8x32 KiB L2: 2x 2 MiB (4 MiB)
desc: 8x256 KiB L3: 2x 20 MiB (40 MiB) desc: 1x20 MiB
Speed (MHz): avg: 2592 high: 2594 min/max: 1200/2600 scaling:
driver: intel_cpufreq governor: powersave cores: 1: 2594 2: 2594 3: 2594
4: 2594 5: 2594 6: 2594 7: 2594 8: 2594 9: 2586 10: 2586 11: 2590
12: 2592 13: 2591 14: 2590 15: 2592 16: 2592 17: 2594 18: 2594 19: 2594
20: 2594 21: 2594 22: 2594 23: 2594 24: 2594 25: 2593 26: 2593 27: 2593
28: 2593 29: 2593 30: 2593 31: 2593 32: 2593 bogomips: 166397
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: Micro-Star MSI
driver: nvidia v: 495.46 alternate: nouveau,nvidia_drm bus-ID: 02:00.0
chip-ID: 10de:1b06 class-ID: 0300
Device-2: Matrox Systems MGA G200e [Pilot] ServerEngines vendor: Intel
driver: mgag200 v: kernel bus-ID: 09:00.0 chip-ID: 102b:0522 class-ID: 0300
Display: x11 server: X.Org compositor: kwin_x11 driver:
loaded: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 92 s-size: 707x402mm (27.8x15.8")
s-diag: 813mm (32")
Monitor-1: HDMI-0 res: 2560x1440 hz: 144 dpi: 93
size: 698x393mm (27.5x15.5") diag: 801mm (31.5")
OpenGL: renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
v: 4.6.0 NVIDIA 495.46 direct render: Yes
Device-1: NVIDIA GP102 HDMI Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 02:00.1 chip-ID: 10de:10ef
class-ID: 0403
Device-2: Creative SB X-Fi Surround 5.1 Pro type: USB
driver: snd-usb-audio bus-ID: 2-1.8:6 chip-ID: 041e:3237 class-ID: 0102
serial: <filter>
Sound Server-1: ALSA v: k5.15.11-230-tkg-pds running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.43 running: yes
Device-1: Intel I350 Gigabit Network driver: igb v: kernel port: 1020
bus-ID: 07:00.0 chip-ID: 8086:1521 class-ID: 0200
IF: eno0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel I350 Gigabit Network driver: igb v: kernel port: 1000
bus-ID: 07:00.1 chip-ID: 8086:1521 class-ID: 0200
IF: enp7s0f1 state: down mac: <filter>
IF-ID-1: br-43e377a74c7b state: down mac: <filter>
IF-ID-2: docker0 state: down mac: <filter>
IF-ID-3: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Hardware-1: Adaptec Series 7 6G SAS/PCIe 3 driver: aacraid
v: 1.2.1[50983]-custom port: 4000 bus-ID: 01:00.0 chip-ID: 9005:028c
rev: N/A class-ID: 0104
Local Storage: total: 21.83 TiB used: 6.59 TiB (30.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 model: root size: 21.83 TiB block-size:
physical: 512 B logical: 512 B type: N/A serial: N/A rev: V1.0 scheme: GPT
ID-1: / raw-size: 21.83 TiB size: 21.83 TiB (100.00%)
used: 6.59 TiB (30.2%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-12d783ca-85f9-4344-8e01-a57b4947f1a0
ID-2: /boot raw-size: 1024 MiB size: 1022 MiB (99.80%)
used: 476.9 MiB (46.7%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 21.83 TiB size: 21.83 TiB (100.00%)
used: 6.59 TiB (30.2%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-12d783ca-85f9-4344-8e01-a57b4947f1a0
ID-4: /var/log raw-size: 21.83 TiB size: 21.83 TiB (100.00%)
used: 6.59 TiB (30.2%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-12d783ca-85f9-4344-8e01-a57b4947f1a0
ID-5: /var/tmp raw-size: 21.83 TiB size: 21.83 TiB (100.00%)
used: 6.59 TiB (30.2%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-12d783ca-85f9-4344-8e01-a57b4947f1a0
Kernel: swappiness: 133 (default 60) cache-pressure: 50 (default 100)
ID-1: swap-1 type: zram size: 125.81 GiB used: 10 MiB (0.0%)
priority: 100 dev: /dev/zram0
Permissions: Unable to run ipmi sensors. Root privileges required.
System Temperatures: cpu: 35.0 C mobo: N/A gpu: nvidia temp: 55 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 55%
Processes: 562 Uptime: 1h 58m wakeups: 0 Memory: 125.81 GiB
used: 22.98 GiB (18.3%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 alt: 10 clang: 13.0.0 Packages: 2914 pacman: 2875 lib: 578
flatpak: 39 Shell: fish v: 3.3.1 default: Zsh v: 5.8 running-in: konsole
inxi: 3.3.11

If you choose to start the linux-tkg-pds kernel in garuda boot options, after saving the settings the next startup is from the linux-zen kernel and the settings are reset. I attach 2 screenshots.

  1. This is how settings are reset after restarting
  2. This is how I save the default kernel
    I will provide more information on request

I know that it works as intended in Ext4, but I do believe I read somewhere in this forum that there is a bug in BTRFS that prevents you from doing so.

I may be wrong.


@Bro is correct, this feature is not working correctly with btrfs and Grub. That issue is out of Garuda's hands, as the development of both BTRFS and Grub comes from separate upstream projects.

There are however workarounds that can allow you to set a different kernel to boot into. I would suggest searching the forum for workarounds as this topic has been discussed numerous times in the past.


This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.