How do I change the default AMD "driver"?

Ask Fedora
1

Long story short:

The Kaveri graphics are having issues again with Mesa drivers, and here I got told this:

Oh it looks like you are using the radeon kernel driver so you aren’t even using radv, only llvmpipe software rendering for vulkan. GCN 1.x and 2.x gpus can use either the radeon or amdgpu driver, radeon is what is used by default though that limits you to opengl only. It is what is used by default by the kernel and most distros due to the amdgpu driver lacking support for some output/video decoding features (not sure what exactly.)

I tested using amdgpu as that is what you normally want to use on these gpus so you get vulkan support and I believe it also tends to perform better.

You need to add some kernel parameters if you want to switch:

Switching from radeon to amdgpu - #13 by jakfrost

That said, there shouldn’t be graphical issues happening in any case but it’s probably useful info to see if the same issue occurs if using amdgpu

I want to avoid waiting a long time (maybe the dude there got busy), so I have to ask here:

I have NO IDEA what the dude is talking about, I only got “there are two GPU Drivers available, you should try swap the one you are using”. AS YOU CAN SEE in the post the instructions given to me didn’t work, so I need appropiate ones.

2

Are you on silver blue or workstation? Thanks.

1 Like
3

What?

It’s just Fedora KDE.

4

Please see Kaveri i/GPUs seem to have problems, again - #6 by josevillani

I have provided instructions

1 Like
5

Changing the kernel arguments is different on non-immutable :fedora:
sudo grubby --info=all
should show you all your kernels and the kernel arguments.

sudo grubby --args="radeon.cik_support=0 amdgpu.cik_support=1" --update-kernel=ALL
would add the arguments for your video card to the kernel

sudo grubby --remove-args="radeon.cik_support=0 amdgpu.cik_support=1" --update-kernel=ALL
would remove them

You can used the instructions @josevillani provided as well.

3 Likes
6

Ok, thanks.

I’ll have that other PC at hand in a couple of days.

7

@josevillani provided unclear instructions in the post linked there, so I can not follow them.

Yors insteas @grumpey lack context, so I’d prefer avoid using them before you have the occasion to explain what some of what you said means, like

.

I just don’t want to use spells which I don’t know the function of.

8

The original instructions provided were to modify the kernel arguments for :fedora: immutable variants/atomic desktops

What I provided was how to modify the kernel arguments for grub2 with grubby on a non-atomic installation. ref: Working with the GRUB 2 Boot Loader :: Fedora Docs

If you wanted to limit the change to only one kernel you could change the --update-kernel argument to be the path of the kernel you’d like to update.
i.e.
--update-kernel=/boot/vmlinuz-6.14.8-300.fc42.x86_64

you can also take a look at man grubby for additional information on the command.

The kernel arguments are from the original post and are also documented here

9

Ok, so I have to look into this one.

Now I am tired and don’t have the computer at hand. No matter. It’s not of immediate importance to solve the issue, I just want to have “the steps” defined and detailed before I get a chance to work on that PC.