SOLVED stuck at Reached target Graphical Interface after enabling dGPU

iwuvkittens · 2025-08-23 19:18:54

moderndaytragedy wrote:

Do i need amdgpu or nvidia nvidia_modeset nvidia_uvm nvidia_drm or both

amdgpu is in tree so its added by the kms in hooks

iwuvkittens · 2025-08-23 19:19:45

moderndaytragedy wrote:

Also do i remove nvidia open since it says conflicting packages

what are you trying to do? you should be editing your initramfs generators config file

moderndaytragedy · 2025-08-23 19:21:10

No such file in the directory
There the xorg.conf.d folder in both usr and etc do i delete that

moderndaytragedy · 2025-08-23 19:23:14

"what are you trying to do? you should be editing your initramfs generators config file" sorry i thought i was supposed to get a package not edit a file

iwuvkittens · 2025-08-23 19:24:40

moderndaytragedy wrote:

No such file in the directory
There the xorg.conf.d folder in both usr and etc do i delete that

sorry i made a typo, your log says it's located in /usr/share/X11 so:

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

moderndaytragedy wrote:

"what are you trying to do? you should be editing your initramfs generators config file" sorry i thought i was supposed to get a package not edit a file

for mkinitcpio, you should be editing /etc/mkinitcpio.conf

as per:

Last edited by iwuvkittens (2025-08-23 19:28:45)

moderndaytragedy · 2025-08-23 19:27:55

.conf or .conf.d? Because there's only conf.d i don't know if that's the same or not

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

iwuvkittens · 2025-08-23 19:30:14

moderndaytragedy wrote:

.conf or .conf.d? Because there's only conf.d i don't know if that's the same or not

.conf, no need to touch .conf.d. execute the command as is and then add the nvidia modules to the mkinitcpio configuration as noted in the wiki, then after you want to regenerate the image(s):

sudo mkinitcpio -P

and reboot

Last edited by iwuvkittens (2025-08-23 19:31:49)

moderndaytragedy · 2025-08-23 19:37:51

Ran the rm: no such files in the directory
Added the modules (didn't add ... I don't know if that's part of the syntax ot example)
regenerated the image
Same thing
startplasma-wayland works

Last edited by moderndaytragedy (2025-08-23 19:40:56)

iwuvkittens · 2025-08-23 19:40:14

moderndaytragedy wrote:

Ran the rm: no such files in the directory
Added the modules (didn't add ... I don't know if that's part of the syntax ot example)
Same thing
startplasma-wayland works

the "... stuff goes here ..."

notes that, there may be stuff inbetween, after, or before, you added it and regenerated the initramfs images? please clarify by attaching the config file

moderndaytragedy · 2025-08-23 19:47:20

https://privatebin.net/?3db4fe7a7bc5518 … 8uPQkdjxiy
I ran sudo mkinicpio -P before reboot

seth · 2025-08-23 20:01:23

You already have the kms hook.
What are we trying to achieve here?
https://lesma.eu/warusefo is now 404 for some reason, but I previously looked at it and it looked like the X11 server was running fine.

After installing an nvidia driver (nvidia-open is btw NOT suggested for Ada chips atm!) do you actually still face the original problem?
Please post an updated journal and xorg log.

moderndaytragedy · 2025-08-23 20:04:06

Well yeah i still have the problem of black screen on boot but i can open tty and run startplasma-wayland and then i can access kde
I'll post the logs in a sec
Also do i change nvidia open back to nvidia

Last edited by moderndaytragedy (2025-08-23 20:04:48)

moderndaytragedy · 2025-08-23 20:11:18

journal http://0x0.st/KinX.txt
Xorg https://privatebin.net/?e4a166580e0865f … zMgpYkqEpn

seth · 2025-08-23 20:31:32

Aug 23 19:39:57 archlinux systemd-logind[1199]: New session 1 of user sddm.
Aug 23 19:39:57 archlinux systemd[1582]: Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini).
Aug 23 19:39:57 archlinux systemd[1582]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/var/lib/sddm/.cache/drkonqi/sentry-envelopes/*).
Aug 23 19:39:57 archlinux systemd[1582]: Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini).
Aug 23 19:39:57 archlinux systemd[1]: Started Session c1 of User sddm.
Aug 23 19:39:57 archlinux sddm-helper[1578]: Writing cookie to "/tmp/xauth_zuITLr"
Aug 23 19:39:57 archlinux sddm-helper[1578]: Starting X11 session: "" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-ohvSLF"
Aug 23 19:39:57 archlinux sddm[1356]: Greeter session started successfully
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: High-DPI autoscaling Enabled
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: Reading from "/usr/local/share/wayland-sessions/plasma.desktop"
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: Loading theme configuration from "qrc:/theme/theme.conf"
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: Connected to the daemon.
Aug 23 19:39:57 archlinux sddm[1356]: Message received from greeter: Connect
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: Loading qrc:/theme/Main.qml...
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: file:///usr/lib/qt6/qml/SddmComponents/LayoutBox.qml:35:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: file:///usr/lib/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib/qt6/qml/SddmComponents/angle-down.png
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: file:///usr/lib/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib/qt6/qml/SddmComponents/angle-down.png
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: qrc:/theme/Main.qml:41:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 23 19:39:57 archlinux sddm-greeter-qt6[1592]: Adding view for ":0.0" QRect(0,0 0x0)

Because

[     9.335] (II) NVIDIA(0): Validated MetaModes:
[     9.335] (II) NVIDIA(0):     "NULL"

the server is running on the nvidia GPU but there're no outputs attached to that.
/etc/X11/xorg.conf.d/20-amdgpu.conf

Section "Device"
    Identifier "MyAMD"
    Driver "amdgpu"
    BusID "197:0:0"
EndSection

test the outcome and in doubt post an udpated X11 log.

moderndaytragedy · 2025-08-23 20:52:45

So i was testing out switching gpus with supergfxctl and i switched to integrated (and kde boots normally again) but now it says logout is required when i try to go back to hybrid. It also only shows 2 available modes of integrated and hybrid which is a little weird but I don't think i set it up correctly since I skipped the 1.1 point of supergfxctl on archwiki since i don't really understand what i need to do

Do i still edit the file or do i find a way to switch back to nvidia first

seth · 2025-08-24 08:57:00

"integrated" likely means "integrated only, you don't get to use the nvidia gpu no matter what", ie. probably not what you want - so configure it the "hybrid" (which is just the regular prime default setup), check the new status quo and then try to force the X11 server to run on the AMD GPU using the configlet in #39

moderndaytragedy · 2025-08-24 10:05:13

So there's no way to switch between integrated and hybrid without a reboot like on windows? I noticed integrated has a significantly better battery life so i would still like to keep it as a primary way of using this laptop when im not running blender

One issues tho when i switch to hybrid it says logout is required and after reboot it shows integrated again

Also sorry if im being a little slow but is editing the 20-andgpu.conf all i need to do or im missing something

seth · 2025-08-24 12:19:30

"Switching between integrated and hybrid" isn't a thing, you're talking about the (default) hybrid mode - your previous problem (and likely cause of battery drain) is that you've been running the server on the nvidia GPU what it neither the normal nor typically desired behavior.
I assume the cause for that is the slightly abnormal PCI enumeration (typically the GPUs are on 0:2:0 and 1:0:0) and/or the <random swearing here> simpledrm device reverting the card order.
Either way, telling the X11 server to please use the AMD GPU (what just explicitly referencing it as in #39 should™ do, we can get more explicit about this if need be) will prevent that and allow your GPU to power down unless you "prime-run blender", if there're further problems my first take w/ an Ada chip would actually be to disable the GSP.

For now re-enable the "hybrid" mode, add the suggested config and post an updated xorg log to illustrate the new situation.

moderndaytragedy · 2025-08-24 13:34:36

I did't know why it wouldn't let me switch back to hybrid so i deleted supergfxctl and reloaded
Running plasma on Wayland again now nvidia smi can actually reach the driver so i assume im back on hybrid
There's no 20-amdgpu.conf but there is 10-amdgpu.conf in share/x11/xorg.conf.d do i edit that
New xorg log: https://privatebin.net/?e3b41e89ecc71bf … rhqZncZt3d

seth · 2025-08-24 13:39:16

Config from #39 doesn't show up in that log and for wayland your xorg log is actually rather irrelevant, see https://wiki.archlinux.org/title/KDE#Me … -specific)

Edit:

There's no 20-amdgpu.conf but there is 10-amdgpu.conf in share/x11/xorg.conf.d do i edit that

No! You'd add the suggested file. But again: limited meaning for wayland sessions.

Last edited by seth (2025-08-24 13:40:12)

moderndaytragedy · 2025-08-24 13:56:06

Sorry im very confused

Isn't that script to force kde to run on nvidia when that's what we don't want
I don't understand if by the end kde should run on wayland or xorg
I also don't understand how to create a script do i just copy stuff from the section or if i need to cd into a directory first or put the code in a file or something like that

moderndaytragedy · 2025-08-24 14:08:20

Also #39 solved the booting issue i no longer have a black screen and don't need tty to open plasma thank you very much

seth · 2025-08-24 14:08:48

It's not a script, the environment variable allows you to force kwin to use a certain card (order) against its default behavior.
You'd export "KWIN_DRM_DEVICES=/dev/dri/card2:/dev/dri/card1" since rn the nvidia GPU is card1, amd is card1

by the end kde should run on wayland or xorg

For plasam on X11 just add the suggested config file, do NOT edit the file in /usr/share, that's under pacman control and will in doubt be overridden with updates.
If you're running on X11, the xorg log will of course become authoritative in illustrating the status quo.

I also don't understand how to create a script

You don't, https://wiki.archlinux.org/title/Environment_variables

moderndaytragedy · 2025-08-24 14:24:25

Since kde loads normally now do i still need to set up the environmental variable

I still have a couple questions about hybrid graphics do i mark this as SOLVED and make another thread or do i just stay here

Thanks again for fixing the issue and having patience for my beginner questions

Last edited by moderndaytragedy (2025-08-24 14:24:58)

seth · 2025-08-24 14:28:05

qdbus6 org.kde.KWin /KWin supportInformation

will tell you what GPU kwin is running on.
For open questions about random stuff unrelated to the problem at hand please open a new thread w/ a meaningful subject, yes (to the benefit of future readers)

Last edited by seth (2025-08-24 14:28:12)

Arch Linux

#26 2025-08-23 19:18:54

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

#27 2025-08-23 19:19:45

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

#28 2025-08-23 19:21:10

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

#29 2025-08-23 19:23:14

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

#30 2025-08-23 19:24:40

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

#31 2025-08-23 19:27:55

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

#32 2025-08-23 19:30:14

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

#33 2025-08-23 19:37:51

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

#34 2025-08-23 19:40:14

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

#35 2025-08-23 19:47:20

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

#36 2025-08-23 20:01:23

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

#37 2025-08-23 20:04:06

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

#38 2025-08-23 20:11:18

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

#39 2025-08-23 20:31:32

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

#40 2025-08-23 20:52:45

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

#41 2025-08-24 08:57:00

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

#42 2025-08-24 10:05:13

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

#43 2025-08-24 12:19:30

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

#44 2025-08-24 13:34:36

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

#45 2025-08-24 13:39:16

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

#46 2025-08-24 13:56:06

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

#47 2025-08-24 14:08:20

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

#48 2025-08-24 14:08:48

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

#49 2025-08-24 14:24:25

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

#50 2025-08-24 14:28:05

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

Board footer