Tumbleweed and AMD graphics driver

Ecky · August 16, 2017, 7:39pm

Just installed Tumbleweed and discovered AMD have stopped releasing drivers for their cards (been a while since I upgraded my OS so hadn’t heard about this)

Are we stuck with the radeon opensource driver for the moment or is there something else available?

My card is an R9 280x so the amdgpu-pro driver does support it but opensuse SDB says that driver doesn’t work with Tumbleweed, don’t know how up to date that article is tho so I’m wondering if maybe it will work on Tumbleweed now?

VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798]

Hope I’m not duplicating a thread here but I couldn’t find anything recent where someone had already asked this

gogalthorp · August 16, 2017, 9:25pm

The AMDGPU driver (not pro) is built into the kernel and I believe it should work with that card

Ecky · August 16, 2017, 9:41pm

Didn’t know that mate, thanks for the info

deano_ferrari · August 16, 2017, 10:36pm

You can examine the drivers that were loaded/unloaded when X starts…

egrep "LoadModule|UnloadModule" /var/log/Xorg.0.log

*or perhaps ~/.local/share/xorg/Xorg.0.log if running Gnome

malcolmlewis · August 17, 2017, 12:23am

On Wed 16 Aug 2017 08:46:01 PM CDT, deano ferrari wrote:

Ecky;2834412 Wrote:
> Didn’t know that mate, thanks for the info

You can examine the drivers that were loaded/unloaded when X starts…

Code:

egrep “LoadModule|UnloadModule” /var/log/Xorg.0.log

*or perhaps ~/.local/share/xorg/Xorg.0.log if running Gnome

Hi
Easier with lspci to see if both load…


/sbin/lspci -nnk |grep -A3 VGA

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851]
Subsystem: Hewlett-Packard Company Device [103c:80cb]
Kernel driver in use: amdgpu
Kernel modules: radeon, amdgpu

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

deano_ferrari · August 17, 2017, 12:47am

From experience, that doesn’t always tell the truth with respect to graphics drivers unfortunately.

malcolmlewis · August 17, 2017, 1:22am

Hi
It’s not the loading in this case (since xf86-video-amdgpu may not be installed), it’s whether the kernel amdgpu driver will be recognized, I’m not sure if Southern Island support is there yet since it’s a GCN 1.0 card?

For mine I have to build my own kmp for Leap 42.2 and 42.3 to enable support (Mullins GCN 1.1), but works OTB for Tumbleweed.

deano_ferrari · August 17, 2017, 1:34am

Well that’s what needs to be determined. For TW kernel, I’d be surprised if the support wasn’t there though. AFAIU experimental support for Southern Island chipsets has been implemented since kernel 4.9, but the radeon driver needs to be blacklisted as well.

http://www.phoronix.com/scan.php?page=article&item=amdgpu-rad-49&num=1

malcolmlewis · August 17, 2017, 2:10am

Hi
Ahh, I see Tahiti in the amdgpu kernel driver… so should be good to go, you need to install xf86-video-amdgpu (not installed by default AFAIK) as this will add a blacklist for radeon.

Ecky · August 17, 2017, 5:47pm

Thanks for the replies guys

The system is using the radeon driver so I’ll try installing amdgpu, system’s in the middle of updates at the minute so I’ll give it a shot when that’s finished

Cheers

Ecky · August 17, 2017, 7:33pm

I have amdgpu installed but it’s still using radeon

ecky@localhost:~> egrep "LoadModule|UnloadModule" /var/log/Xorg.0.log
  42.567] (II) **LoadModule**: "glx"
    42.579] (II) **LoadModule**: "radeon"
    42.583] (II) **LoadModule**: "ati"
    42.702] (II) **LoadModule**: "modesetting"
    42.704] (II) **LoadModule**: "fbdev"
    42.705] (II) **LoadModule**: "vesa"
    42.713] (II) **LoadModule**: "fbdevhw"
    42.714] (II) **LoadModule**: "fb"
    42.715] (II) **LoadModule**: "dri2"
    42.715] (II) **LoadModule**: "glamoregl"
    43.316] (II) **LoadModule**: "ramdac"
    43.316] (II) **UnloadModule**: "modesetting"
    43.316] (II) **UnloadModule**: "fbdev"
    43.316] (II) **UnloadModule**: "vesa"
    43.464] (II) **LoadModule**: "libinput"

I tried adding to /etc/modprobe.d/50-blacklist.conf the following line:

blacklist radeon

Still loaded the radeon driver, kwrite had been suggesting ‘radeonfb’ when I added that so just in case I also tried:

blacklist radeonfb

Also had no effect, radeon driver still gets loaded

So, installing the amdgpu package didn’t automatically blacklist the radeon driver and ‘manually’ blacklisting it also didn’t seem to work

I also tried adding the following in /etc/X11/xorg.conf.d/50-device.conf:

Section "Device"
Identifier "Default Device"
driver "amdgpu"
EndSection

When I tried that the system booted to runlevel 3, if I then tried running sddm screen filled up with messages saying something like:

bad “remove” command line
bad “add” command line
bad “remove” command line
bad “add” command line
over and over until it finally stopped at a blank screen

I don’t really know what else I can try here

Incidentally, doubt it’s connected but since the update I did earlier today I"m also now seeing messages relating to what I suspect are usb 3 ports


dmesg | grep xhci
    3.552791] **xhci**_hcd 0000:02:00.0: xHCI Host Controller
    3.552801] **xhci**_hcd 0000:02:00.0: new USB bus registered, assigned bus number 1
   21.235627] **xhci**_hcd 0000:02:00.0: can't setup: -110
   21.235649] **xhci**_hcd 0000:02:00.0: USB bus 1 deregistered
   21.235734] **xhci**_hcd 0000:02:00.0: init 0000:02:00.0 fail, -110
   21.235756] **xhci**_hcd: probe of 0000:02:00.0 failed with error -110

Probably a seperate issue but I thought it worth mentioning

malcolmlewis · August 17, 2017, 7:53pm

On Thu 17 Aug 2017 05:36:01 PM CDT, Ecky wrote:

I have amdgpu installed but it’s still using radeon

Code:

ecky@localhost:~> egrep
“LoadModule|UnloadModule” /var/log/Xorg.0.log 42.567] (II)
LoadModule: “glx” 42.579] (II) LoadModule: “radeon”
42.583] (II) LoadModule: “ati”
42.702] (II) LoadModule: “modesetting”
42.704] (II) LoadModule: “fbdev”
42.705] (II) LoadModule: “vesa”
42.713] (II) LoadModule: “fbdevhw”
42.714] (II) LoadModule: “fb”
42.715] (II) LoadModule: “dri2”
42.715] (II) LoadModule: “glamoregl”
43.316] (II) LoadModule: “ramdac”
43.316] (II) UnloadModule: “modesetting”
43.316] (II) UnloadModule: “fbdev”
43.316] (II) UnloadModule: “vesa”
43.464] (II) LoadModule: “libinput”

I tried adding to /etc/modprobe.d/50-blacklist.conf the following line:

blacklist radeon

Still loaded the radeon driver, kwrite had been suggesting ‘radeonfb’
when I added that so just in case I also tried:

blacklist radeonfb

Also had no effect, radeon driver still gets loaded

So, installing the amdgpu package didn’t automatically blacklist the
radeon driver and ‘manually’ blacklisting it also didn’t seem to work

I also tried adding the following in
/etc/X11/xorg.conf.d/50-device.conf:

Code:

Section “Device”
Identifier “Default Device”
driver “amdgpu”
EndSection

When I tried that the system booted to runlevel 3, if I then tried
running sddm screen filled up with messages saying something like:

bad “remove” command line
bad “add” command line
bad “remove” command line
bad “add” command line
over and over until it finally stopped at a blank screen

I don’t really know what else I can try here

Incidentally, doubt it’s connected but since the update I did earlier
today I"m also now seeing messages relating to what I suspect are usb 3
ports

Code:

dmesg | grep xhci
3.552791] xhci_hcd 0000:02:00.0: xHCI Host Controller
3.552801] xhci_hcd 0000:02:00.0: new USB bus registered,
assigned bus number 1 21.235627] xhci_hcd 0000:02:00.0: can’t
setup: -110 21.235649] xhci_hcd 0000:02:00.0: USB bus 1
deregistered 21.235734] xhci_hcd 0000:02:00.0: init 0000:02:00.0
fail, -110 21.235756] xhci_hcd: probe of 0000:02:00.0 failed with
error -110

Probably a seperate issue but I thought it worth mentioning

Hi
So you installed xf86-video-amdgpu, and see it present in the lspci
output along with the radeon driver?

There should aslo be a file: /X11/xorg.conf.d/10-amdgpu.conf no need to
modify anything in the other files…

Did you also rebuild intird with the command mkinitrd (for the
blacklisting)?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

Ecky · August 18, 2017, 10:38am

Sorry Malcolm, thought I"d included the lspci output in my last post, that’ll teach me not to post as I’m about to go to sleep …

/sbin/lspci -nnk |grep -A3 VGA
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798]
        Subsystem: Tul Corporation / PowerColor Device [148c:3001]
        Kernel driver in use: radeon
        Kernel modules: radeon, amdgpu

Indicates amdgpu is present but not in use doesn’t it?

Been quite a while since I did this kind of thing and never considered myself an expert to begin with, executing mkinitrd just didn’t occur to me

My kernel version is: 4.11.8-2-default

So just to check, should my mkinitrd comand be: mkinitrd -o /boot/initrd.4.11.8-2-default 4.11.8-2-default

Obviously I’d make a backup copy of the existing initrd.4.11.8-2-default first

malcolmlewis · August 18, 2017, 1:28pm

Hi
If you have check the radeon is blacklisted, installed xf86-video-amdgpu, then just run the mkinitrd command by itself…the system will take care of things for the running kernel.

Ecky · August 18, 2017, 1:59pm

there is an entry in 50-blacklist.conf for : blacklist radeonfb

10-amdgpu.conf is present in /etc/X11/xorg.conf.d/

So that all looks good, now I just run mkinitrd right?

I’m assuming that by:

then just run the mkinitrd command by itself

You mean just run the mkinitrd command with no parameters/arguments?

mkinitrd <— like that?

Just want to be sure before I run it

malcolmlewis · August 18, 2017, 3:06pm

Ecky:

there is an entry in 50-blacklist.conf for : blacklist radeonfb

10-amdgpu.conf is present in /etc/X11/xorg.conf.d/

So that all looks good, now I just run mkinitrd right?

I’m assuming that by:
then just run the mkinitrd command by itself
You mean just run the mkinitrd command with no parameters/arguments?

mkinitrd <— like that?

Just want to be sure before I run it

Hi
Yes, just mkinitrd

However it should be radeon that’s blacklisted AFAIK… if you get to just a VT (No GUI), then change to just radeon and run mkinitrd and reboot.

If it’s still not working and back to a VT, then remove the blacklisted items and run mkinitrd again to restore…

Ecky · August 18, 2017, 3:13pm

the blacklist radeonfb entry was added by the system not me so if I get no luck I’ll try ‘manually’ adding an entry for radeon

Will let you know how it goes when I give it a shot a little later today

Many thanks

Tyler_K · August 18, 2017, 3:24pm

No, radeonfb is an old console framebuffer driver … you want the drm gpu driver “radeon”

Ecky · August 19, 2017, 12:33pm

Thanks for the info there Tyler, I had already added blacklist radeon to 50-blacklist.conf myself, it was still getting loaded though, don’t really understand why

I have got the amdgpu driver loading now after running mkinitrd, although it didn’t work on the first attempt (which almost had me screaming obscenities at it)

Ran it a second time and that time it worked

Thanks to all who replied but especially malcom for his patience

Ecky · August 19, 2017, 1:17pm

SIgh

Since doing that I’ve lost all sound, both the internal sound card and hdmi sound

Pulse Audio volume control doesn’t show the sound cards at all

Losing hdmi sound I can understand, why it’s affected the internal soundcard, not so much