Graphical interface not working after updating the OS, GPU drivers were updated, is it possible to downgrade? I don’t know how to access the terminal from the boot sequence
no need to chroot… you should be able to login from there:
by pressing keycombo: Ctrl + Alt + F4
And updating GPU driver/packages usually should not break the graphical interface.
You talk about Nvidia i bet ?
yep, it’s Nvidia but what confuses me is that sddm.conf was completely empty so I deleted it and reinstalled sddm but it didn’t fix the issue
/etc/sddm.conf.d/ is used with dropins
there should be a kde_settings.conf file
and may recreate the empty file again…
sudo touch /etc/sddm.conf
AMD gpu here. Looks like I have a similar issue. However, the key combo ctrl+alt+F4 (to start a terminal session) does not work. Display is just unresponsive. sddm.conf (in /etc/) is blank, default.conf isn’t, and kde_settings in sddm.conf.d is also populated.
I did find this in my xorg log.
[ 11.434] (EE) Device(s) detected, but none match those in the config file.
[ 11.434] (EE)
Fatal server error:
[ 11.434] (EE) no screens found(EE)
[ 11.434] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 11.434] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 11.434] (EE)
[ 11.434] (EE) Server terminated with error (1). Closing log file.
And running sudo touch /etc/sddm.conf results in:
[root@EndeavourOS /]# sudo touch /etc/sddm.conf
sudo: unable to find terminal name for device 136, 0
Try Ctrl + Alt + F6 or F1
also it would seem yay stopped working.
Btw what do you obtain from journalctl -r
Command unfortunately doesn’t work. (From F1 to F6, no response.) Remains a black screen, that is, the monitors arent receiving any signal.
Checking other bits when I get the liveusb up.
Yep, yay is not working either.
Do you get this error?
yay: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory
And interesting journalctl results.
tried LTS kernel?
no need for you to touch the file as you have not removed it …
Used the 6.6 LTS kernel, no change to the issue.
With the sddm.conf, I generated an example config sddm --example-config and copy pasted it into the blank sddm (to clarify the config file was blank before touch.) Unfortunately still had the same issue.
That being said, journalctl DID change.
Hey I think I found a solution to yay not working, for me, sudo ln -s /usr/lib/libalpm.so.15.0.0 /usr/lib/libalpm.so.14.0 got it working again, according this
since my drivers are from yay, fixing it and upgrading the drivers might fix it, trying it rn
SUCCESS! So the trick was,
sudo ln -s /usr/lib/libalpm.so.15.0.0 /usr/lib/libalpm.so.14
After running that, it will fix yay, after yay is fixed, just run yay -Syuu and update everything.
Thanks for the help 
This may work but is not the recommended way to fix this.
1 Like
well yes but it does work as a temporary solution
The proper way is to reinstall/rebuild yay.
thats not the solution it is a workaround … temp fixing yay for you in this case but never the suggested solution.
If marked as solution, users will blindly use it…
to remove the symlink:
sudo rm /usr/lib/libalpm.so.14.0
1 Like