Out of Range error | Fedora 40 KDE | AMDGPU pro driver

Ask Fedora
, , ,
1

I’m using Fedora 40, Plasma 6 with amd gpu. I was playing around trying to optimize the amd driver and installed amdgpu-install-6.0.60002-1.el9.noarch.rpm from the amd website. Once installed, I changed the resolution and it crashed.

When I reboot and try to login to a Plasma session after entering the password I get a black screen with the error “Out of Range” and it hangs.

I can reboot and login to a Gnome xorg session and access the system, but cannot start a plasma session.

How can I reset/decrease resolution so that I can login for the Plasma session?

2

Added f40, kde-plasma and removed gnome

3

Fedora ships the latest amdgpu drivers.
They are included in the linux kernel and the MESA user space driver code that is supported by AMD engineering.

Why did you think you needed to install anything extra?

I would suggest you undo what you did and tell us if that fixed your system.

4

I don’t have a good answer as to why but I did.

I have uninstalled the incorrect driver and reinstalled the mesa drivers. This did not fix the problem.

I changed the resolution after installing the incorrect driver and it crashed. Upon reboot, at the plasma login password, I got the error " Out of Range" and it froze. Rebooting I could enter the xorg session but not Plasma. I have since installed plasma-workspace-x11 and I can login to it, but the plasma wayland session still locks up.

Running kscreen-doctor -o in the shell gives the error “No QT plugins could be initialized”.

Still broke. I would prefer to use the wayland rather than x11. Any suggestions?

Thanks.

5

That only works if you are logged in and running Wayland.

Try renaming the ~/.config folder out of the way then login.
You should be back to default config.

Does that work?

6

I assume they were trying to use AMDGPU-PRO (older proprietary libs?) or ROCm (absolute nightmare a while back :stuck_out_tongue: but required for actual OpenCL if not using AMDGPU-PRO; clover was very not up-to-par).

If OpenCL isn’t needed, the default AMDGPU driver in the kernel is fine for 3D.

7

You wouldn’t have a Snapshot you could revert to if needed? Maybe usnig dnf history and rolling back a couple will help?

8

The snapshots refuse to boot also, but only when trying to use Wayland.

9

Doesn’t work. I have access to the Gnome desktops and Plasma x11, they work fine but the Plasma Wayland keeps throwing the Out of Range error before it launches the fedora splash screen.

The system seems to work fine with x11, though I think the Wayland option was a little snappier.

I tried reinstalling plasma-workspace-wayland but it didn’t make a difference.

10

I suspect that the bad monitor config is saved somewhere in your $HOME.
try creating a new user and login as that user does plasma work?

11

Makes sense, I’ll try it. Actually, after living with Plasma x11 I think I might like it better than wayland, things seem crisper on my monitor.

Thanks for the help.

12

In case anyone else has this problem, check ~/.config/kwinoutputconfig.json
A miss stated resolution or hz setting will freeze the system on boot.

13

At boot I would be surprised if user config is read, do mean on login?

14

Correct, after entering password.