Garuda boot options hangs (NOT AFTER GRUB CUSTOMIZER THIS IS A BUG)

Whenever I use Garuda welcome boot tool it hangs and doesn't let me see he log, I'm trying to set TKH kernel as default.. The busy spinning wheel stays, I can close ti though. And when I open it again is back to the default kernel (Zen Kernel)

NOTE: sorry for bad posting before. Answer here says it's bug with BTRFS

Guys, to be clear I did use Grub customizer but... I was having the problem reported before I used Grub Customizer. Grub customizer made the sparse error at boot to appear, halting the boot process until I press any key. Following in the day I reverted to a clean firs hour of the day snapshot and then I decided to reinstall to use BTRFS RAID and add hibernation to the install.

Step by step screenshots:


In the next one I set TKG-BMQ, then I apply



In the next one the busy spinning wheel is there after click OK in the successful prompt.

When I open the app again is back to default Kernel

can you specify your problem

updated with screenshot and little info, sorry for bad post

1 Like

you do not need to apologize
was just a tip to help you better

1 Like

pls use the seach for that and i have found many solutions maybe there is one for you too .....

search change kernel

Explanation here

Is this the workaround? to do manually then, and I'm on UEFI, is it different in this case?

sudo grub-mkconfig -o /boot/grub/grub.cfg

i'm not a pro in changin kernel
i use tkg-bmq by default
but when i wanted to change
and in garuda menü options it don't go
i whould do it per terminal and whould see what failures shown

I did this:
added a line and change default entry to saved

GRUB_SAVEDEFAULT="true"
GRUB_DEFAULT=saved

sudo grub-mkconfig -o /boot/grub/grub.cfg

OUTPUT

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot: initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux-xanmod
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-xanmod.img
Found fallback initrd image(s) in /boot: initramfs-linux-xanmod-fallback.img
Found linux image: /boot/vmlinuz-linux-tkg-bmq
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-tkg-bmq.img
Found fallback initrd image(s) in /boot: initramfs-linux-tkg-bmq-fallback.img
Detecting snapshots ...
Info: Separate boot partition not detected
Found snapshot: 2021-05-18 09:15:01 | timeshift-btrfs/snapshots/2021-05-18_09-15-01/@
Found snapshot: 2021-05-18 07:27:57 | timeshift-btrfs/snapshots/2021-05-18_07-27-57/@
Found snapshot: 2021-05-17 18:17:29 | timeshift-btrfs/snapshots/2021-05-17_18-17-29/@
Found snapshot: 2021-05-17 15:50:49 | timeshift-btrfs/snapshots/2021-05-17_15-50-49/@
Found snapshot: 2021-05-17 12:39:04 | timeshift-btrfs/snapshots/2021-05-17Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot: initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux-xanmod
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-xanmod.img
Found fallback initrd image(s) in /boot: initramfs-linux-xanmod-fallback.img
Found linux image: /boot/vmlinuz-linux-tkg-bmq
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-tkg-bmq.img
Found fallback initrd image(s) in /boot: initramfs-linux-tkg-bmq-fallback.img
Detecting snapshots ...
Info: Separate boot partition not detected
Found snapshot: 2021-05-18 09:15:01 | timeshift-btrfs/snapshots/2021-05-18_09-15-01/@
Found snapshot: 2021-05-18 07:27:57 | timeshift-btrfs/snapshots/2021-05-18_07-27-57/@
Found snapshot: 2021-05-17 18:17:29 | timeshift-btrfs/snapshots/2021-05-17_18-17-29/@
Found snapshot: 2021-05-17 15:50:49 | timeshift-btrfs/snapshots/2021-05-17_15-50-49/@
Found snapshot: 2021-05-17 12:39:04 | timeshift-btrfs/snapshots/2021-05-17_12-39-04/@
Found 5 snapshot(s)
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 263
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached._12-39-04/@
Found 5 snapshot(s)
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 263
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.

Have to test this after two reboot but you can try and report results.

Start from terminal and post log as text!!!

sudo garuda-boot-options

Looks like you used grub-customizer.

1 Like

Yes, but switched back

OUTPUT: I also clicked "show log"

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
garuda-boot-options version: 0.1
Exec #1: "logname"
Exit #1: 0 QProcess::NormalExit
Exec #2: "mountpoint -q /live/aufs"
Exit #2: 1 QProcess::NormalExit
Exec #3: "plymouth-set-default-theme -l"
Exit #3: 0 QProcess::NormalExit
Exec #4: "plymouth-set-default-theme"
Exit #4: 0 QProcess::NormalExit
Exec #5: "pacman -Qq plymouth"
Exit #5: 0 QProcess::NormalExit
Exec #6: "pacman -Qq plymouth"
Exit #6: 0 QProcess::NormalExit
Exec #7: "test -z \"$(lspci -d 80ee:beef)\""
Exit #7: 0 QProcess::NormalExit
Exec #8: "df -T / |tail -n1 |awk '{print $2}'"
Exit #8: 0 QProcess::NormalExit
Exec #9: "df -T / |tail -n1 |awk '{print $2}'"
Exit #9: 0 QProcess::NormalExit
Exec #10: "grub-editenv /boot/grub/grubenv unset next_entry"
Exit #10: 0 QProcess::NormalExit
Exec #11: "grub-set-default \"1>2\""
Exit #11: 0 QProcess::NormalExit
Exec #12: "update-grub"
SErr #12: "Generating grub configuration file ...\nFound linux image: /boot/vmlinuz-linux-zen\nFound initrd im
age: /boot/amd-ucode.img /boot/initramfs-linux-zen.img\nFound fallback initrd image(s) in /boot: initramfs-lin
ux-zen-fallback.img\nFound linux image: /boot/vmlinuz-linux-xanmod\nFound initrd image: /boot/amd-ucode.img /b
oot/initramfs-linux-xanmod.img\nFound fallback initrd image(s) in /boot: initramfs-linux-xanmod-fallback.img\n
Found linux image: /boot/vmlinuz-linux-tkg-bmq\nFound initrd image: /boot/amd-ucode.img /boot/initramfs-linux-
tkg-bmq.img\nFound fallback initrd image(s) in /boot: initramfs-linux-tkg-bmq-fallback.img\nDetecting snapshot
s ...\nInfo: Separate boot partition not detected \nFound snapshot: 2021-05-18 09:15:01 | timeshift-btrfs/snap
shots/2021-05-18_09-15-01/@\nFound snapshot: 2021-05-18 07:27:57 | timeshift-btrfs/snapshots/2021-05-18_07-27-
57/@\nFound snapshot: 2021-05-17 18:17:29 | timeshift-btrfs/snapshots/2021-05-17_18-17-29/@\nFound snapshot: 2
021-05-17 15:50:49 | timeshift-btrfs/snapshots/2021-05-17_15-50-49/@\nFound snapshot: 2021-05-17 12:39:04 | ti
meshift-btrfs/snapshots/2021-05-17_12-39-04/@\nFound 5 snapshot(s)\nFound memtest86+ image: /boot/memtest86+/m
emtest.bin\n/usr/bin/grub-probe: warning: unknown device type nvme0n1.\nerror: syntax error.\nerror: Incorrect
command.\nerror: syntax error.\nSyntax error at line 263\nSyntax errors are detected in generated GRUB config
file.\nEnsure that there are no errors in /etc/default/grub\nand /etc/grub.d/* files or please file a bug rep
ort with\n/boot/grub/grub.cfg.new file attached.\n"
Exit #12: 1 QProcess::NormalExit
Exec #13: "xdg-open /var/log/boot.log"
SOut #13: "Opening \"/var/log/boot.log\" with Micro  (text/x-log)\n"
SErr #13: "Can't exec \"xterm\": No such file or directory at /usr/share/perl5/vendor_perl/File/DesktopEntry.p
m line 247.\n/usr/bin/xdg-open: line 881: x-www-browser: command not found\nRunning Firefox as root in a regul
ar user's session is not supported.  ($XAUTHORITY is /home/pyro/.Xauthority which is owned by pyro.)\n/usr/bin
/xdg-open: line 881: iceweasel: command not found\n/usr/bin/xdg-open: line 881: seamonkey: command not found\n
/usr/bin/xdg-open: line 881: mozilla: command not found\n/usr/bin/xdg-open: line 881: epiphany: command not fo
und\n/usr/bin/xdg-open: line 881: konqueror: command not found\n/usr/bin/xdg-open: line 881: chromium: command
not found\n/usr/bin/xdg-open: line 881: chromium-browser: command not found\n/usr/bin/xdg-open: line 881: goo
gle-chrome: command not found\n/usr/bin/xdg-open: line 881: www-browser: command not found\n/usr/bin/xdg-open:
line 881: links2: command not found\n/usr/bin/xdg-open: line 881: elinks: command not found\n/usr/bin/xdg-ope
n: line 881: links: command not found\n/usr/bin/xdg-open: line 881: lynx: command not found\n/usr/bin/xdg-open
: line 881: w3m: command not found\nxdg-open: no method available for opening '/var/log/boot.log'\n"
Exit #13: 3 QProcess::NormalExit

Seems that even using root it doesn't change the default.

Did this an reboot and it chose the right kernel.

GRUB_SAVEDEFAULT="true"
GRUB_DEFAULT=saved

sudo grub-mkconfig -o /boot/grub/grub.cfg

ANOTHER TOPIC

I have the sparse error, and it have boot partition. Maybe I need the /boot instead.

nvme0n1p1 259:1 0 256M 0 part /boot/efi

if you have timeshift go back before you made changes manually and try to change the kernel in boot menue

can you be more clear? I think going back before I installed grub custumizer is a good idea. Is that what you mean?

yes thats it

3 Likes

But, do I need to rollback or just not use it?

If you have a snapshot of before you installed grub-customizer roll back to before you installed it.

Do not perform any more installs or updates until you do this. Otherwise you may lose your opportunity to reverse the changes grub-customizer made as timeshift only store a limited number of snapshots.

4 Likes

Just in case:

1 Like

Ok. I reverted to this morning.
/etc/default/grub looks clean as before my DEFAULT_GRUB="saved" changes

First time using this, how do I restore the snapshot? So i stay here