I am facing problems while booting Garuda. When I use grub for booting and select the Garuda option, it shows two error but when I try to boot by snapshots it successfully gets booted. This happened after the update. Please help. Thanks
Boot and restore the working snapshot, then fully update your system taking note of any output or errors that occur during the process.
2 Likes
Please post text output as text.
Remove the lock file and try again,
sudo rm /var/lib/pacman/db.lck
sudo pacman -Syu
1 Like
ok sorry
it's my mistake
Fully updated the system...same problem
Please provide more specific information, e.g.what changed, what output you saw, any messages or errors, etc. etc. etc.
"It doesn't work" doesn't help.
2 Likes
It told system is up to date..
OK, so the system is up-to-date. What's the problem?
1 Like
The problem is what I mentioned above...I can't boot directly through grub..it's shows the same error output as in the shared img ...I always have to boot through snapshot
Do you have that kernel installed?
Is the file present on the disk?
Have you made any changes to your GRUB menu recently?
2 Likes
Yes
I saw in the kernel settings that it was installed
No
Please verify it is present on the disk,
ls -l /boot
Sorry it's 1.30am here and I am not on my system...Can I verify and tell tomorrow?
How on Earth were you updating your system etc. if you're not on it? 
Just come back to this tomorrow. It's impossible to troubleshoot a PC you don't have access to.
5 Likes
Are.. I just turned off that and got to sleep
ls -l /boot
drwx------ - root 1 Jan 1970 efi
drwxr-xr-x - root 28 Feb 1:15 grub
drwxr-xr-x - root 5 Dec 2020 memtest86+
.rw-r--r-- 55M root 28 Feb 1:14 initramfs-linux-tkg-bmq-fallback.img
.rw-r--r-- 33M root 28 Feb 1:13 initramfs-linux-tkg-bmq.img
.rw-r--r-- 3.6M root 17 Feb 13:45 intel-ucode.img
.rw-r--r-- 633 root 4 Jan 15:40 refind_linux.conf
.rw-r--r-- 9.4M root 28 Feb 1:13 vmlinuz-linux-tkg-bmq
It's there.
now updated again
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
loadkeys: Unable to open file: in: No such file or directory
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-tkg-bmq.preset: 'default'
-> -k /boot/vmlinuz-linux-tkg-bmq -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-tkg-bmq.img
==> Starting build: 5.11.1-127-tkg-bmq
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
loadkeys: Unable to open file: in: No such file or directory
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-tkg-bmq.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-tkg-bmq.preset: 'fallback'
-> -k /boot/vmlinuz-linux-tkg-bmq -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-tkg-bmq-fallback.img -S autodetect
==> Starting build: 5.11.1-127-tkg-bmq
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
loadkeys: Unable to open file: in: No such file or directory
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
got '3 warnings' and 'loadkeys: Unable to open file: in: No such file or directory'
1 Like
That output from mkinitcpio there says you have two kernels installed: linux-tkg-bmq and linux-lts, but only one of the two has files present under /boot.
This means something is broken. 
Firstly, try removing then reinstalling linux-lts and see if the kernel files appear under /boot.
Then, run sudo grub-mkconfig -o /boot/grub/grub.cfg and check that the /boot/grub/grub.cfg file contains the correct entries for the kernels you have installed.
1 Like
I had only downloaded the Lts one...librewish told it's better if you install Lts kernel
Two files are present under /boot
Show us.
1 Like