Hello! Ever since the chaotic-aur update, it started doing this. It doesn’t boot. It gets stuck where the picture shows. What could be the problem?
Welcome
Use live ISO, in the Welcome App use chroot, use garuda-update to fix the problem.
You can also try to restore a working snapshot from grub and look what changed in the update prozess, use only garuda-update in terminal
Hey guys! I’ve had a similar issue. Last night, I reinstalled Garuda from a live ISO after my previous install would not boot after updating, however the same thing happened with my fresh install. I’ve tried everything SGS suggested with the pinned tutorial.
Ihave tried updating the OS, updating the drivers, switching kernels. I havent been able to spot any errors while dojng all this. I just cannot get Garuda to load the login screen on startup. It just cuts signal even though the pc still runs. I suspect DKMS is involved somehow.
I had a similar issue on my System76 lemur pro. I found that the graphics drivers were not being loaded soon enough causing my system to never finish booting. What I had to do was get my system loaded (loading a working snapshot or re-installing the OS) and force the graphics driver to startup early. I had to write a script to create a config file for my specific graphics config early boot. My fish script is below. You would need to change the i915 part to what your graphics driver is. Hope this helps because this was a pain for me.
if not test -e /etc/dracut.conf.d/earlykms.conf
echo 'Warning, early graphics configuration file does not exist'
set vc_startup /etc/dracut.conf.d/earlykms.conf
mkdir -p (dirname $vc_startup)
echo 'force_drivers+=" i915 "' > $vc_startup
dracut-rebuild
echo 'Rebooting in 5 seconds'
sleep 5
reboot
else
echo 'Early graphics configuration file already exists.'
end
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.