SOLVED stuck at Reached target Graphical Interface after enabling dGPU

moderndaytragedy · 2025-08-23 09:00:43

hi total beginner here first time on this forum please tell me if im doing something wrong when it comes to posting/replying

asus px13 (hybrid graphics: amd igpu + nvidia dgpu)
used archinstall with kde for all installs

For a week i had a working arch setup however nothing (nvidia-smi, supergfxctl, blender, uefi) would see the nvidia gpu. Turns out it was a windows isuue (no dualboot) and i needed to reset the laptop. After doing so i could now see both gpus in uefi however when i tried booting into arch all i got was a black screen. i reinstalled with pretty much every setting the same (except removing home partition) and got the same thing. if i switch to tty and back it shows Reached target Graphical Interface as the last line but doesnt go any further.

So far Ive tried updating, changing, uninstalling, reinstalling all nvidia drivers, different boot loaders (grub/systemd), reinstalling sddm.

i wonder if i need to disable nvidia at boot since i obviously dont need this thing to run the DE on it but i didnt really get how to do that from the nvidia archwiki page.

any help appreciated thanks

Last edited by moderndaytragedy (2025-08-24 15:28:31)

Lone_Wolf · 2025-08-23 11:05:47

Have you tried the nvidia-open drivers ?

Incase you did try them or they fail also :

Append systemd.unit=multi-user.target to the kernel command line in your bootloader config.
That will bring you to a console login .

login as root, run

# journalctl -b | curl -F 'file=@-' 0x0.st

It will upload your journal to a public hosting site and output a link, post that link.

moderndaytragedy · 2025-08-23 11:59:52

Thanks for replying ill post the journal when i get home

No i haven't tried nvidia open since the wiki said use nvidia or nvidia-dkms for 4060

"Append systemd.unit=multi-user.target to the kernel command line in your bootloader config." I remember i could access the journal before do i still need to do this

Lone_Wolf · 2025-08-23 15:46:22

The command needs to be run as root/with root rights, if you can do that from a normal boot there's no need to append that parameter .

That part of the nvidia wiki page seems to confuse many people .

Your card is from the NV190 family which is newer then NV160 / Turing so the top entry is valid.

For the cards in the NV160 / NV170 / NV190 families nvidia recommends nvidia-open but the closed nvidia driver also supports them.

moderndaytragedy · 2025-08-23 16:37:15

Couldn't download nvidia-open, request url returned error 404, i have reflector for mirror managing.
Here's the journal link
https://0x0.st/KiGF.txt

iwuvkittens · 2025-08-23 17:01:41

moderndaytragedy wrote:

Couldn't download nvidia-open, request url returned error 404, i have reflector for mirror managing.
Here's the journal link
https://0x0.st/KiGF.txt

if it returned 404 your sync databases are trying to retrieve and older version, install it with an upgrade:

sudo pacman -Syu nvidia-open

also check if the nvidia module(s) are loaded:

lspci -k | grep -EA3 "VGA|3D"

Last edited by iwuvkittens (2025-08-23 17:06:25)

moderndaytragedy · 2025-08-23 17:24:43

Thanks, Installed nvidia-open same thing

Unable to load libkmod resources error -2
VGA compatible controller NVIDIA corporation AD107M GeForce rtx 4060 max-q mobile (rev a1)

iwuvkittens · 2025-08-23 17:34:03

moderndaytragedy wrote:

Thanks, Installed nvidia-open same thing
Unable to load libkmod resources error -2
VGA compatible controller NVIDIA corporation AD107M GeForce rtx 4060 max-q mobile (rev a1)

that doesn't look like -k was supplied

iwuvkittens · 2025-08-23 17:35:01

moderndaytragedy wrote:

Thanks, Installed nvidia-open same thing
Unable to load libkmod resources error -2
VGA compatible controller NVIDIA corporation AD107M GeForce rtx 4060 max-q mobile (rev a1)

did you reboot after installing nvidia-open? and which kernel are you running?

Last edited by iwuvkittens (2025-08-23 17:36:30)

moderndaytragedy · 2025-08-23 17:44:07

Yes i did reboot twice
6.16.2-arch-1

moderndaytragedy · 2025-08-23 17:50:30

Retyped lspci with and without sudo
Error reading /sys/bus/pci/devices/00000:00:08.3/label: operation not permitted
Same VGA line
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia

iwuvkittens · 2025-08-23 17:58:05

moderndaytragedy wrote:

Yes i did reboot twice
6.16.2-arch-1

is that the installed kernel or the kernel that you booted into or both you can differentiate with:

pacman -Q linux
uname -r

Last edited by iwuvkittens (2025-08-23 17:58:19)

moderndaytragedy · 2025-08-23 18:03:15

Both give the same

iwuvkittens · 2025-08-23 18:05:42

moderndaytragedy wrote:

Both give the same

did you install a faulty sddm theme? if the problem is due to an sddm theme, you can try manually starting the graphical environment from a tty.

moderndaytragedy · 2025-08-23 18:12:10

I installed kde plasma from archinstall like before, it worked fine when it was just amd igpu before i enabled nvidia

How would i manually start it?

iwuvkittens · 2025-08-23 18:15:04

moderndaytragedy wrote:

I installed kde plasma from archinstall like before, it worked fine when it was just amd igpu before i enabled nvidia
How would i manually start it?

you can switch to tty2 with:

ctrl+alt+fn+2
#or
ctrl+alt+f2

and then run:

#if it starts, then it's something to do with xorg
startplasma-wayland

or try restarting sddm and see if it works:

sudo systemctl restart sddm

if it is due to xorg can you post the xorg log?

Last edited by iwuvkittens (2025-08-23 18:16:46)

moderndaytragedy · 2025-08-23 18:18:15

Holy it did start thank you

How do i post the xorg log

iwuvkittens · 2025-08-23 18:20:59

moderndaytragedy wrote:

Holy it did start thank you
How do i post the xorg log

it's located in

~/.local/share/xorg

upload the relevant files to a paste site like 0x0.st

moderndaytragedy · 2025-08-23 18:25:43

When i try to see it with cat it says no such file or directory am i doing this wrong

iwuvkittens · 2025-08-23 18:30:36

see here

and to upload see here

moderndaytragedy · 2025-08-23 18:39:58

Found one in var/log
I used curl -F 'file=@-' 0x0.st < /var/log/Xorg.0.log it got stuck
Is the file too big or i picked a wrong one?

iwuvkittens · 2025-08-23 18:48:43

moderndaytragedy wrote:

Found one in var/log
I used curl -F 'file=@-' 0x0.st < /var/log/Xorg.0.log it got stuck
Is the file too big or i picked a wrong one?

wait it out, or use a different site

moderndaytragedy · 2025-08-23 18:58:57

Xorg logs: https://lesma.eu/warusefo

iwuvkittens · 2025-08-23 19:10:59

try https://wiki.archlinux.org/title/Kernel … _KMS_start

also try removing:

sudo rm /{etc,usr/share}/X11/xorg.conf

Last edited by iwuvkittens (2025-08-23 19:25:14)

moderndaytragedy · 2025-08-23 19:15:36

Do i need amdgpu or nvidia nvidia_modeset nvidia_uvm nvidia_drm or both

Also do i remove nvidia open since it says conflicting packages

Last edited by moderndaytragedy (2025-08-23 19:18:28)

Arch Linux

#1 2025-08-23 09:00:43

SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#2 2025-08-23 11:05:47

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#3 2025-08-23 11:59:52

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#4 2025-08-23 15:46:22

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#5 2025-08-23 16:37:15

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#6 2025-08-23 17:01:41

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#7 2025-08-23 17:24:43

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#8 2025-08-23 17:34:03

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#9 2025-08-23 17:35:01

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#10 2025-08-23 17:44:07

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#11 2025-08-23 17:50:30

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#12 2025-08-23 17:58:05

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#13 2025-08-23 18:03:15

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#14 2025-08-23 18:05:42

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#15 2025-08-23 18:12:10

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#16 2025-08-23 18:15:04

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#17 2025-08-23 18:18:15

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#18 2025-08-23 18:20:59

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#19 2025-08-23 18:25:43

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#20 2025-08-23 18:30:36

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#21 2025-08-23 18:39:58

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#22 2025-08-23 18:48:43

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#23 2025-08-23 18:58:57

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#24 2025-08-23 19:10:59

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

#25 2025-08-23 19:15:36

Re: SOLVED stuck at Reached target Graphical Interface after enabling dGPU

Board footer