Switching the default kernel via garuda settings gui failed

Hello,
I've just installed Garuda Linux some days ago and I tried to switch the default booted kernel from -zen to -tkg-bmq.
While the gui says that the changes which entry to boot from have been applied, the preselected kernel while boot remains the -zen
I can manually select the other one, but that's beside the point of useability.

here is my inxi output:

System:    Kernel: 5.14.13-208-tkg-bmq x86_64 bits: 64 compiler: gcc v: 11.1.0
           parameters: intel_pstate=passive BOOT_IMAGE=/@/boot/vmlinuz-linux-tkg-bmq
           root=UUID=a6b11b9e-5939-45d2-87fb-c163c2e2b7fc rw [email protected] quiet splash
           rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1
           resume=UUID=8f8880d3-3d8a-480f-a148-80b3821c329b loglevel=3
           Console: pty pts/1 wm: kwin_x11 DM: SDDM Distro: Garuda Linux base: Arch Linux
Machine:   Type: Desktop Mobo: ASRock model: X399 Phantom Gaming 6 serial: <filter>
           UEFI: American Megatrends v: P1.30 date: 08/27/2019
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3 serial: <filter>
           charge: 10% (should be ignored) rechargeable: yes status: Discharging
           Device-2: hidpp_battery_1 model: Logitech MX Keys Wireless Keyboard serial: <filter>
           charge: 55% (should be ignored) rechargeable: yes status: Discharging
CPU:       Info: 16-Core (2-Die) model: AMD Ryzen Threadripper 2950X socket: SP3r2 bits: 64
           type: MT MCP MCM arch: Zen+ family: 17 (23) model-id: 8 stepping: 2
           microcode: 800820D cache: L1: 1.5 MiB L2: 8 MiB L3: 32 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
           bogomips: 223746
           Speed: 2404 MHz min/max: 2200/3500 MHz base/boost: 3500/4400 boost: enabled
           volts: 1.1 V ext-clock: 100 MHz Core speeds (MHz): 1: 2404 2: 2398 3: 2404 4: 2401
           5: 2410 6: 2405 7: 2813 8: 2958 9: 2408 10: 2404 11: 2407 12: 2407 13: 2601 14: 2683
           15: 4163 16: 3713 17: 2384 18: 2405 19: 2405 20: 2387 21: 2406 22: 2407 23: 2899
           24: 2661 25: 2408 26: 2409 27: 2398 28: 2406 29: 3197 30: 2392 31: 2401 32: 2711
           Vulnerabilities: Type: itlb_multihit status: Not affected
           Type: l1tf status: Not affected
           Type: mds status: Not affected
           Type: meltdown status: Not affected
           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 AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
           Type: srbds status: Not affected
           Type: tsx_async_abort status: Not affected
Graphics:  Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: eVga.com. driver: N/A
           alternate: nouveau bus-ID: 41:00.0 chip-ID: 10de:1b80 class-ID: 0300
           Device-2: AMD Vega 10 XL/XT [Radeon RX Vega 56/64] vendor: Sapphire Limited
           driver: amdgpu v: kernel bus-ID: 44:00.0 chip-ID: 1002:687f class-ID: 0300
           Device-3: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo
           bus-ID: 5-4.1:5 chip-ID: 046d:082d class-ID: 0102 serial: <filter>
           Display: server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: amdgpu,ati
           unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1
           Screen-1: 0 s-res: 3440x1440 s-dpi: 96 s-size: 910x381mm (35.8x15.0")
           s-diag: 987mm (38.8")
           Monitor-1: DisplayPort-1 res: 3440x1440 hz: 60 dpi: 109 size: 800x335mm (31.5x13.2")
           diag: 867mm (34.1")
           OpenGL: renderer: Radeon RX Vega (VEGA10 DRM 3.42.0 5.14.13-208-tkg-bmq LLVM 12.0.1)
           v: 4.6 Mesa 21.2.4 direct render: Yes
Audio:     Device-1: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel
           bus-ID: 0b:00.3 chip-ID: 1022:1457 class-ID: 0403
           Device-2: NVIDIA GP104 High Definition Audio vendor: eVga.com. driver: snd_hda_intel
           v: kernel bus-ID: 41:00.1 chip-ID: 10de:10f0 class-ID: 0403
           Device-3: AMD Vega 10 HDMI Audio [Radeon Vega 56/64] driver: snd_hda_intel v: kernel
           bus-ID: 44:00.1 chip-ID: 1002:aaf8 class-ID: 0403
           Device-4: Yamaha Steinberg UR22mkII type: USB driver: snd-usb-audio bus-ID: 5-3.1:4
           chip-ID: 0499:170f class-ID: 0103
           Device-5: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo
           bus-ID: 5-4.1:5 chip-ID: 046d:082d class-ID: 0102 serial: <filter>
           Sound Server-1: ALSA v: k5.14.13-208-tkg-bmq running: yes
           Sound Server-2: sndio v: N/A running: no
           Sound Server-3: JACK v: 1.9.19 running: no
           Sound Server-4: PulseAudio v: 15.0 running: no
           Sound Server-5: PipeWire v: 0.3.39 running: yes
Network:   Device-1: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel port: 2000
           bus-ID: 04:00.0 chip-ID: 8086:1539 class-ID: 0200
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
           Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 05:00.0
           chip-ID: 8086:2723 class-ID: 0280
           IF: wlp5s0 state: down mac: <filter>
           Device-3: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel port: 1000
           bus-ID: 06:00.0 chip-ID: 10ec:8125 class-ID: 0200
           IF: enp6s0 state: down mac: <filter>
           IF-ID-1: anbox0 state: down mac: <filter>
           IF-ID-2: br-4a4fa6ca1d6a state: up speed: 10000 Mbps duplex: unknown mac: <filter>
           IF-ID-3: docker0 state: down mac: <filter>
           IF-ID-4: veth25d2dca state: up speed: 10000 Mbps duplex: full mac: <filter>
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-9:3
           chip-ID: 8087:0029 class-ID: e001
           Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:    Local Storage: total: 7.09 TiB used: 31.75 GiB (0.4%)
           ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung model: SSD 970 PRO 1TB
           size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
           type: SSD serial: <filter> rev: 1B2QEXP7 temp: 50.9 C scheme: GPT
           SMART: yes health: PASSED on: 18d 20h cycles: 210 read-units: 2,837,576 [1.45 TB]
           written-units: 4,878,492 [2.49 TB]
           ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Intel model: SSDPEKNW010T8 size: 953.87 GiB
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
           serial: <filter> rev: 002C temp: 44.9 C scheme: GPT
           SMART: yes health: PASSED on: 1y 297d 14h cycles: 1,095
           read-units: 39,736,574 [20.3 TB] written-units: 116,839,120 [59.8 TB]
           ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: HD103UJ family: SpinPoint F1 DT
           size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A
           serial: <filter> rev: 1118 temp: 29 C scheme: GPT
           SMART: yes state: enabled health: PASSED on: 1y 229d 5h cycles: 1339
           ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD5000AAVS-00ZTB0
           family: Caviar Green size: 465.76 GiB block-size: physical: 512 B logical: 512 B
           sata: 2.5 speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1B01 temp: 33 C scheme: GPT
           SMART: yes state: enabled health: PASSED on: 6y 69d 12h cycles: 1700
           ID-5: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST2000DL003-9VT166
           family: Barracuda Green (AF) size: 1.82 TiB block-size: physical: 512 B
           logical: 512 B sata: 3.0 speed: 6.0 Gb/s type: HDD rpm: 5900 serial: <filter>
           rev: CC32 temp: 39 C scheme: GPT
           SMART: yes state: enabled health: PASSED on: 7y 20d 21h cycles: 2244 read: 1.25 TiB
           written: 1.37 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100
           threshold: 97
           ID-6: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST2000VN000-1HJ164
           family: NAS HDD size: 1.82 TiB block-size: physical: 4096 B logical: 512 B sata: 3.1
           speed: 6.0 Gb/s type: HDD rpm: 5900 serial: <filter> rev: SC60 temp: 35 C scheme: GPT
           SMART: yes state: enabled health: PASSED on: 3y 111d 15h cycles: 1732 Pre-Fail:
           attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
           ID-7: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 850 EVO M.2 250GB
           family: based SSDs size: 232.89 GiB block-size: physical: 512 B logical: 512 B
           sata: 3.1 speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q temp: 48 C scheme: GPT
           SMART: yes state: enabled health: PASSED on: 3y 134d 8h cycles: 1730
           written: 22.27 TiB
Partition: ID-1: / raw-size: 919.28 GiB size: 919.28 GiB (100.00%) used: 31.75 GiB (3.5%)
           fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:3
           ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 562 KiB (0.2%)
           fs: vfat block-size: 512 B dev: /dev/nvme0n1p1 maj-min: 259:2
           ID-3: /home raw-size: 919.28 GiB size: 919.28 GiB (100.00%) used: 31.75 GiB (3.5%)
           fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:3
           ID-4: /var/log raw-size: 919.28 GiB size: 919.28 GiB (100.00%) used: 31.75 GiB (3.5%)
           fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:3
           ID-5: /var/tmp raw-size: 919.28 GiB size: 919.28 GiB (100.00%) used: 31.75 GiB (3.5%)
           fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:3
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 50 (default 100)
           ID-1: swap-1 type: partition size: 34.33 GiB used: 0 KiB (0.0%) priority: -2
           dev: /dev/nvme0n1p3 maj-min: 259:4
           ID-2: swap-2 type: zram size: 31.21 GiB used: 512 KiB (0.0%) priority: 100
           dev: /dev/zram0
Sensors:   System Temperatures: cpu: 47.1 C mobo: N/A gpu: amdgpu temp: 53.0 C mem: 53.0 C
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 1252
Info:      Processes: 561 Uptime: 1h 4m wakeups: 39 Memory: 31.21 GiB used: 6.28 GiB (20.1%)
           Init: systemd v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages:
           pacman: 2061 lib: 568 Shell: fish (sudo) v: 3.3.1 default: Bash v: 5.1.8
           running-in: alacritty inxi: 3.3.08

I am thankful for any advise.

Use the 'Garuda Welcome' app and select the 'Garuda Boot Options' and you should be able to select which kernel to use as default during boot.

Those are the steps I took and it returned: applied successfully. But it still boots into the -zen kernel.

Sounds like an issue with the Garuda Boot Options GUI. Maybe one of the Garuda devs can weight in.

1 Like

I think that kernel orders or defining new defaults have some known bugs (if you search in the forum you'll find several topics about it).
You should edit /etc/default/grub and change GRUB_DEFAULT=0 (which is the first line you see in the GRUB) to e.g. GRUB_DEFAULT=1 (second line) or whatever else, also in sub-menu, I think you can use e.g. GRUB_DEFAULT="1>2" (third line in second line submenu).
You should also comment out GRUB_SAVEDEFAULT, e.g.

#GRUB_SAVEDEFAULT=true

Pay attention, sometimes some parameters (e.g. GRUB_DEFAULT) might appear more than once in the grub file).
Then update-grub of course.

PS: welcome!

3 Likes

From what I had read previously, it sounded like enabling GRUB_SAVEDEFAULT had some sort of issue with btrfs. and since I didn't want to wreck my system I left this setting untouched.

I had disabled submenues to ease in debugging why it won't set properly.
Thanks for the hint with the "1>2". I'll give this a try.

1 Like

Yes, I'm not a developer nor a technical experet, but I remember this should be all something related to grub with btrfs, nothing specific to the Garuda Assistant...
Anyway the editing above should work, I've been using it for a long time, pointing to both main menu and sub-menu.

1 Like

Thank you filo, for the quick reply. I successfully set the right default now. It works, but in my humble opinion doing it that way defeats the purpose of having a GUI for the same task.

I mean the graphical way should yield the same result in the end.

1 Like

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