Black Screen after switching NVIDIA RTX 4070 with AMD Radeon RX 9070

[polovest (John)]

Today I switched my NVIDIA RTX 4070 with an AMD Radeon RX 9070 and while I can boot until the login screen of KDE, after I enter my password I only end up with a black screen.

Any idea what I can do?

[polovest (John)]

Interesting: This is not an issue if I select Wayland (“Plasma”) instead of X11 in the login screen (left bottom).

[barryascott]

@polovest

This is not an issue if I select Wayland (“Plasma”) instead of X11

Is Wayland a solution for you? If not what issue would need to be fixed?

[polovest (John)]

I love Wayland, but some apps unfortunately still require X11.

[decathorpe (Fabio Valentini)]

Have you completely uninstalled the proprietary nvidia drivers (if you had them installed for your previous GPU)? They might mess up X.org if they’re still installed on a non-nvidia system.

[barryascott]

@polovest

I love Wayland, but some apps unfortunately still require X11.

And they do not work with Xwayland I take it?

I hear there are apps that cannot screen share when running under Wayland (I have no direct experience to go on).

I guess you need to use one of those apps?

[anotheruser (Mark)]

1. have you updated initramfs? sudo dracut -f
2. does a file /etc/X11/xorg.conf exist? delete or rename it
3. reset kde monitor konfig
   use tty (ctrl-alt-f4 ) to login and delete file .config/kwinoutputconfig.json

[barryascott]

@decathorpe

Have you completely uninstalled the proprietary nvidia drivers

Also have a look at the /etc/X11/xorg.conf.d/ and check that any files in there for nvidia references. I only have 00-keyboard.conf.

[polovest (John)]

Hi!

1. I did a sudo dracut -f, but no change.
2. No, there was no /etc/X11/xorg.conf present.
3. [CTRL]+[Alt]+[F4] doesn’t work unfortunately, no display.
4. /etc/X11/xorg.conf.d/ only contains 00-keyboard.conf as well.

[gnwiii (George N. White III)]

@polovest

[CTRL]+[Alt]+[F4] doesn’t work unfortunately, no display.

There should be some error messages available in the journal that would help understand the display problem, but you need to get a terminal to run journalctl.

Have you tried booting to a text console (use grub editor to add <space>3 to the end of the kernel command line).

Do you have a Live USB installer that boots? In the Live USB environment you can mount the system drive and use journalctl with:

       -D DIR, --directory=DIR
           Takes a directory path as argument. If specified, journalctl will operate on the specified 
           journal directory DIR instead of the default runtime and system journal paths.

[polovest (John)]

Booting is fine, the problem is, this happens after I enter the password in the KDE login screen.

[anotheruser (Mark)]

@polovest

I did a sudo dracut -f, but no change.

have you rebooted the system with the new initramfs?
pls post cat /proc/cmdline

@polovest

[CTRL]+[Alt]+[F4] doesn’t work unfortunately, no display.

or any other of the available virtual consoles F2 / F3 / F5 / F6
sometimes you need to press enter key to get the login prompt.
don’t login in sddm, only try to switch to a tty

EDIT:
create a new userid and use this new userid to open a plasma-x11 session.

also check .local/share/xorg/Xorg.0.log for clues
I understand that a wayland session works.

[gnwiii (George N. White III)]

@polovest

Booting is fine, the problem is, this happens after I enter the password in the KDE login screen.

Yes. that means journalctl should have details of the failiure if you can get a console or terminal in a Live USB environment.

[polovest (John)]

@anotheruser

.local/share/xorg/Xorg.0.log

I found that:

[   220.726] (EE) 
Fatal server error:
[   220.726] (EE) Cannot write display number to fd 13
[   220.726] (EE) 
[   220.726] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[   220.726] (EE) Please also check the log file at "/home/office/.local/share/xorg/Xorg.0.log" for additional information.
[   220.726] (EE) 
[   220.726] (II) AIGLX: Suspending AIGLX clients for VT switch
[   220.726] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[   220.726] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[   220.726] (EE) Server terminated with error (1). Closing log file.

And that related topic:

Xorg fatal error with thunderbolt dock and USB input devices

Yesterday I updated my Dell XPS 15 7590 laptop from Fedora 37 KDE spin to 38. I had my laptop with nothing connected on my desk and the upgrade went alright except for some nvidia driver problems, which I fixed by reinstalling the driver. Today I plugged my laptop in my Dell WD22TB4 thunderbolt dock, and booted. It detected all my monitors and USB devices fine (I never had problems with thunderbolt docks) up until logging in. I had the login screen on all monitors, I typed in my password, and h…

Strange.

[rbekken (Roy Bekken)]

do you have “xorg-x11-drv-amdgpu” installed?

[polovest (John)]

It was not

That fixed it, thank you so much!

Seems that this was not installed/loaded automatically after the graphics card change. But why is Wayland working then, is there also a Wayland AMD GPU driver?

[decathorpe (Fabio Valentini)]

Wayland does not require any GPU-specific driver code, it uses the generic modesetting infrastructure provided by the Linux kernel.

X.org supports this too, with the generic xorg-x11-drv-modesetting DDX, I’m not sure why it didn’t work in your case here and you needed to install the amdgpu DDX (unless xorg-x11-drv-modesetting isn’t installed either?)

[polovest (John)]

Not found

[decathorpe (Fabio Valentini)]

Ah, sorry, I misremembered - the modesetting driver is included in the main xorg-x11-server-Xorg package, so you should definitely have it. Not sure why it didn’t work in this case.

[polovest (John)]

At least I have now AMD instead of NVIDIA, since they (as far as I know) are supporters of Linux