Please help i cannot normally boot my Garuda installation any more after todays update, and restoring a snapshot creates a grub error. The only way i can get into my installation is through recovery mode.
I am assuming that the latest update had a grub update and hence going back a snapshot renders you unable to boot with a message like “452: out of range pointer” or something similar.
The fix for this is chrooting into your system and reinstalling grub.
Try to follow this tutorial:
And then hold off on updating and provide us with the update logs first.
cat /var/log/pacman.log | tb
This will give you a link post it here. Your system looks a pretty recent install so your logs shouldn’t be particularly big to require filtering.
I had the same problem booting up this morning. I noticed there was an update to SDDM last night, and this thread: Boot hang after update mentions about hanging at the same point. The suggested solution of removing "splash" from the boot options has resolved it for me. Hopefully, an update to SDDM or Plymouth will come soon to properly resolve this.
I'm having the same issue. None of the snapshots allow me to boot. I've managed to do it only recovery in mode. Also my systemctl --user is showing that app-autorandr\[email protected] and [email protected] are failed. It seems that second one is BTRFS Assistant Snapper check.
Also, I'm having systemd: Failed to start Powerdevil. and org_kde_powerdevil: org.kde.powerdevil: KDE Power Management System init failed! journal errors.
When I make garuda-update everything is normal, but if I restart it won't boot again. Only in recovery mode in one of the kernels.
Search for @petsam and chroot in forum search upper right, please.
Please don’t misunderstand, but it has been repeated over and over again so many times in the forum. If you had opened your own thread, you would know that we ask you to start your own search before asking.
Hmm... Since no one here was providing an update log I decided to take matters in my own hand and update my system and see what's happening. Which surprisingly resulted in nothing... The system updates normally and I could reboot my system as always. Which could result in either of the two scenarios:
The package that was causing the issue causing the issue has been fixed upstream, or
I simply don't have the package that's causing this issue installed.
I would request anyone facing this issue to provide us with the update logs when they roll back a snapshot and chroot to fix their grub.
grep '2023-06-25' /var/log/pacman.log | tb
change '2023-06-25' here with whatever date you updated your system on.
Please post this log along with your inxi when you post in this thread.
I had the same issue, I’ve just put sddm in my ignorepkg parameter in pacman.conf in the interim till it is resolved. I also had to go back to a snapshot, I realised it was sddm when I noticed all of my peripherals were being accessed by the linux kernel on boot due to the lights flickering.
Honestly a lot of login user applications don’t run well for me due to me using a 5120x1440 resolution on an NVIDIA card. The open-source drivers REALLY DON’T LIKE this resolution. But that is off topic
Hmm... that's strange because as I said above I updated my system today and could access the system normally. The only thing that's different from stock garuda on my system is that I use plymouth instead of plymouth-git. So, I thought that's the issue since that's for whom the splash kernel parameter is for additionally that's the package that's been updated along side sddm recently.
╰─λ pacman -Qi sddm
Name : sddm
Version : 0.20.0-1
Description : QML based X11 and Wayland display manager
Architecture : x86_64
URL : https://github.com/sddm/sddm
Licenses : GPL
Groups : None
Provides : display-manager
Depends On : qt5-declarative xorg-xauth xorg-server ttf-font
Optional Deps : None
Required By : sddm-kcm
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 4.51 MiB
Packager : Antonio Rojas <[email protected]>
Build Date : Friday 23 June 2023 10:22:10 PM
Install Date : Sunday 25 June 2023 09:13:06 PM
Install Reason : Explicitly installed
Install Script : No
Validated By : Signature
chroot makes it possible to update your system and repair your grub.
Again for you.
Hello Garuda users.
Please read the following template before requesting assistance:
Please post the terminal/konsole input and output as text (no pictures) from the following command:
Refusing to post the output of the required “garuda-inxi” on a help request will likely result in you not receiving any help from the Garuda team. A failure to provide your system specs may also result in your thread being closed without notice, (as without this information providing assistance is often next to impossible).
Before opening a new help request, please search the Arch and Garuda Wiki’s, and read any relevant sections related to your issue. Also, thoroughly search any error messages in the forum’s search engine and on the web. For in depth information on how to search for answers to Linux issues effectively, read the tips on the Garuda Wiki:
Please report in detail everything you have already attempted to solve your problem.
Thanks! Garuda boots now that i removed the splash from my command line. Right at the beginning of the booting process i see an error line flash past but i can't read it.
About the link i updated yesterday when the trouble occurred, but i tried restoring it with the 2023-06-10 snapshot that is why it might think that was the last one. i give you the 2023-06-25's details https://termbin.com/34ag
Did you try and remove splash from your command line that fixed it for me.
Boot Garuda through your recovery option (press CTRL D to complete loading)
Run Garuda Welcome and Choose Garuda boot option. (Enter pass word)
The kernel command line has the word 'splash' right at the beginning of the command line, delete only that word, save and reboot, Garuda should boot fine again.