Arch Linux

hymn

Member

Registered: 2023-11-18

Posts: 3

[Solved] Stuck on [Ok] Reached target graphical interface

I'm pretty new to this so apologies for any mistakes I made. After updating to the latest kernel and nvidia drivers, my system doesn't start anymore. Removing the quiet kernel param lead me at the "Reached target graphical interface line". I guess something is wrong with sddm following xorg being broken. I already reinstalled both and the nvidia driver but still no luck

● sddm.service - Simple Desktop Display Manager
     Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; preset: disabled)
     Active: active (running) since Wed 2023-11-22 17:00:32 CET; 17min ago
       Docs: man:sddm(1)
             man:sddm.conf(5)
   Main PID: 1573 (sddm)
      Tasks: 2 (limit: 38065)
     Memory: 16.7M
        CPU: 29ms
     CGroup: /system.slice/sddm.service
             └─1573 /usr/bin/sddm

Nov 22 17:00:33 arch sddm[1573]: Display server starting...
Nov 22 17:00:33 arch sddm[1573]: Writing cookie to "/run/sddm/xauth_TaBOok"
Nov 22 17:00:33 arch sddm[1573]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_TaBOok -noreset -displayfd 16
Nov 22 17:00:33 arch sddm[1573]: Failed to start display server process.
Nov 22 17:00:33 arch sddm[1573]: Attempt 1 starting the Display server on vt 2 failed
Nov 22 17:00:35 arch sddm[1573]: Tried to start Xorg before previous instance exited
Nov 22 17:00:35 arch sddm[1573]: Attempt 2 starting the Display server on vt 2 failed
Nov 22 17:00:37 arch sddm[1573]: Tried to start Xorg before previous instance exited
Nov 22 17:00:37 arch sddm[1573]: Attempt 3 starting the Display server on vt 2 failed
Nov 22 17:00:37 arch sddm[1573]: Could not start Display server on vt 2

journalctl -p 3 -xb

http://0x0.st/HwAC.txt

journalctl -b

http://0x0.st/HwmT.txt

lsmod

http://0x0.st/Hwms.txt

My mkinitcpio.conf

http://0x0.st/HwmM.txt

Last edited by hymn (2023-11-25 01:19:52)

shulamy

Member

From: israel

Registered: 2010-09-11

Posts: 468

Re: [Solved] Stuck on [Ok] Reached target graphical interface

for me, nomodeset solved the problem (of monitor frequency)

ezik

hymn

Member

Registered: 2023-11-18

Posts: 3

Re: [Solved] Stuck on [Ok] Reached target graphical interface

for me, nomodeset solved the problem (of monitor frequency)

ezik

Wrong thread? I don't have an issue with monitor frequency, I don't even reach the gui. + According to the wiki, nvidia_drm.modeset only has to be set for Nvidia Driver <545 but im using 545.29.02-3

shulamy

Member

From: israel

Registered: 2010-09-11

Posts: 468

Re: [Solved] Stuck on [Ok] Reached target graphical interface

i don't reach gui without nomodeset as well, but do with it

and it works for other problems too

ezik

loqs

Member

Registered: 2014-03-06

Posts: 18,928

Re: [Solved] Stuck on [Ok] Reached target graphical interface

Disabling modesetting is a useful workaround to reach a console for diagnostic purposes but rarely a solution to an issue.
As a test does booting with the Kernel parameters nvidia_drm.modeset=1 nvidia_drm.fbdev=1 make any difference?

hymn

Member

Registered: 2023-11-18

Posts: 3

Re: [Solved] Stuck on [Ok] Reached target graphical interface

Disabling modesetting is a useful workaround to reach a console for diagnostic purposes but rarely a solution to an issue.
As a test does booting with the Kernel parameters nvidia_drm.modeset=1 nvidia_drm.fbdev=1 make any difference?

nvidia_drm.fbdev=1

leads to a verry laggy experience after entering my luks password, which made it almost impossible to do anything.

nvidia_drm.modeset=1

didn't change anything either.

I finally fixed it after 3 hours of debugging with ChatGPT (lol) and my idea to uninstall xorg in favor of wayland. My last resort would have been to completely reinstall the system.
The commands I used were

sudo pacman -S nvidia-settings opencl-nvidia
sudo nvidia-xconfig
sudo bash -c 'echo "blacklist nouveau" > /etc/modprobe.d/nouveau.conf'

Not sure what exactly fixed it and why nouveau wasn't blocked, although according to the wiki, nvidia-utils blocks nouveau. And now I can boot into either wayland or xorg. Strange behavior... But thank you anyways for helping

Last edited by hymn (2023-11-25 01:22:26)