AMD GPU Drivers Installation

probe2k · 2018-04-21 15:15:39

Guys, I don't have much experience with AMD drivers and their compatibility. I recently purchased a laptop with amd gpu. However, I am unable to decide which packages should I install for the it. The lspci generated this output for the graphics card and I am really uncertain which one is needed...
Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] (rev c1)
Please help. Thanks!

Steef435 · 2018-04-21 21:18:47

Welcome!

All you can do is search, really. Take a look in the wiki and here.

It's important to know what specific card is in your computer first. One specific model is preferred over lspci output. Can you find some specifications for your laptop somewhere?

loqs · 2018-04-21 21:52:03

What is the full output of `lspci -nnk`

pb · 2018-04-22 09:09:24

First of all - take a look at: https://support.amd.com/en-us/download and try "Manually select your driver". If the driver for your GPU is: RN-AMDGPU-UNIFIED-LINUX you should to use amdgpu, see: https://wiki.archlinux.org/index.php/AMDGPU. You can use AMDGPU-PRO from AUR, but only when you really had to do this. AMDGPU is good enaugh for common use.
If the driver will be Crimson (Catalyst) you should to use radeonsi, see: https://wiki.archlinux.org/index.php/ATI. Only when your driver is See or Southern Islands you can try to use amdgpu, too (but if I think well, the proper driver for R7 M260 is amdgpu).

thorstenhirsch · 2018-04-22 10:06:10

Yes, R7 M260 works with AMDGPU. This is actually the best case scenario - the driver is included in the kernel, so you don't need to install anything. Don't download anything from AMD's website (that driver has no benefit at all) and don't install the AMDGPU-PRO package from AUR unless you absolutely need FreeSync right now. I think that's the only popular PRO feature that's not yet in the kernel, but it's only a matter of months until we also see it there.

edit: If you want to play a game in steam that's using the vulkan api you need to install vulkan-radeon. Since steam games cannot make use of pacman's dependency resolution you need to think of dependencies like this for yourself.

edit2: And please check if you've installed xf86-video-amdgpu. I thought xorg-server depends on it, but according to the package browser it doesn't.

Last edited by thorstenhirsch (2018-04-22 10:24:58)

probe2k · 2018-04-25 13:25:24

I have installed xf86-video-amdgpu and it does show up in the display driver list. However, the boot log shows some bugs in there.
Output of lspci -nnk

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08)
Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1028:0810]
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)
Subsystem: Dell UHD Graphics 620 [1028:0810]
Kernel driver in use: i915
Kernel modules: i915
00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08)
Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1028:0810]
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
Subsystem: Dell Sunrise Point-LP USB 3.0 xHCI Controller [1028:0810]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
Subsystem: Dell Sunrise Point-LP Thermal subsystem [1028:0810]
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21)
Subsystem: Dell Sunrise Point-LP Serial IO I2C Controller [1028:0810]
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: Dell Sunrise Point-LP CSME HECI [1028:0810]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 RAID bus controller [0104]: Intel Corporation 82801 Mobile SATA Controller [RAID mode] [8086:282a] (rev 21)
Subsystem: Dell 82801 Mobile SATA Controller [RAID mode] [1028:0810]
Kernel driver in use: ahci
Kernel modules: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d4e] (rev 21)
Subsystem: Dell Device [1028:0810]
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21)
Subsystem: Dell Sunrise Point-LP PMC [1028:0810]
Kernel driver in use: intel_pmc_core
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21)
Subsystem: Dell Sunrise Point-LP HD Audio [1028:0810]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21)
Subsystem: Dell Sunrise Point-LP SMBus [1028:0810]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [1002:6900] (rev c1)
Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [1028:0810]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 07)
Subsystem: Dell RTL810xE PCI Express Fast Ethernet controller [1028:0810]
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31)
Subsystem: Dell QCA9377 802.11ac Wireless Network Adapter [1028:1810]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci

Output of dmesg | grep amdgpu

Apr 25 18:21:44 archlinux kernel: [drm] amdgpu kernel modesetting enabled.
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: enabling device (0006 -> 0007)
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: GTT: 256M 0x0000000000000000 - 0x000000000FFFFFFF
Apr 25 18:21:44 archlinux kernel: [drm] amdgpu: 4096M of VRAM memory ready
Apr 25 18:21:44 archlinux kernel: [drm] amdgpu: 4096M of GTT memory ready.
Apr 25 18:21:44 archlinux kernel: [drm] amdgpu: irq initialized.
Apr 25 18:21:44 archlinux kernel: amdgpu: [powerplay] amdgpu: powerplay sw initialized
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000000400080, cpu addr 0xffffb0cac1621080
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000000400100, cpu addr 0xffffb0cac1621100
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000000400180, cpu addr 0xffffb0cac1621180
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000000400200, cpu addr 0xffffb0cac1621200
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000000400280, cpu addr 0xffffb0cac1621280
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000400300, cpu addr 0xffffb0cac1621300
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000000400380, cpu addr 0xffffb0cac1621380
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000000400400, cpu addr 0xffffb0cac1621400
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 8 use gpu addr 0x0000000000400480, cpu addr 0xffffb0cac1621480
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 9 use gpu addr 0x0000000000400520, cpu addr 0xffffb0cac1621520
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 10 use gpu addr 0x00000000004005a0, cpu addr 0xffffb0cac16215a0
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 11 use gpu addr 0x0000000000400620, cpu addr 0xffffb0cac1621620
Apr 25 18:21:44 archlinux kernel: amdgpu: [powerplay] can't get the mac of 5
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: kfd not supported on this ASIC
Apr 25 18:21:44 archlinux kernel: [drm] Initialized amdgpu 3.19.0 20150101 for 0000:01:00.0 on minor 1

This can't get the mac of 5, kfd not supported issue is the reason I am not able to use this thing. The VGA driver still shows intel instead of both intel and amdgpu

V1del · 2018-04-25 13:44:54

Please post output in [ code ] tags. Those "errors" are likely to be harmless. Since this is a dual gpu system, you will want to look at https://wiki.archlinux.org/index.php/PRIME for information on how to make use of your dedicated AMD card.

probe2k · 2018-04-25 18:58:18

@V1del, Hi I tried that, but "xrandr --listproviders" outputs "Providers: number : 0" since gnome switched to wayland. Also, I tried the setoffloadsink to send intensive tasks to discrete gpu, however it doesn't seem to work

V1del · 2018-04-25 19:02:09

You should still be able to use DRI_PRIME=1 I suppose, and afaik GNOME has it's own dedicated graphics support available on a right click. I'm entirely unsure if any of this works properly on wayland though. So you'd likely have to opt for xorg to have this in any workable fashion.

ratcheer · 2018-04-26 21:10:11

I get the exact same errors with my R7 Topaz 340, resulting in a kernel OOPS. I believe it is a bug in the kernel module, which seems to be supplied by AMD developers. I also believe they may be dragging their feet on providing a fix. But it may be that the Linux people are dragging their feet on accepting a fix. When I was researching my problem, I found some finger pointing between the two camps.

Yes, DRI_PRIME=1 works with Wayland.

Tim

Last edited by ratcheer (2018-04-26 21:12:50)

loqs · 2018-04-26 23:24:44

@ratcheer any bug report or mailing list links? Are there any potential fixes in 4.17-rc2 or drm-next-4.18-wip?

Last edited by loqs (2018-04-26 23:24:53)

ratcheer · 2018-04-27 13:59:26

@loqs, I'll see if I can retrack down the stuff I found and report back, but my wife just had surgery and I'm spending a lot of time helping her.

Tim

probe2k · 2018-04-29 22:48:53

Yeah, DRI_PRIME=1 does work, but I am unable to keep it to default when the system switches to graphics intensive tasks

probe2k · 2018-04-30 02:41:30

For DRI_PRIME=1 and DRI_PRIME=3

[probe@archlinux ~]$ DRI_PRIME=1 glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: AMD ICELAND (DRM 3.19.0 / 4.14.35-1-lts, LLVM 6.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.1
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.1
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.0.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:
[probe@archlinux ~]$ glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.1
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.1
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.0.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

V1del · 2018-04-30 15:12:58

What do you mean with unable to keep it to default? You prepend that to any utility's startup command that you want to make use of the AMD card. Which number you set that to is irrelevant it simply has to be present.

probe2k · 2018-04-30 15:19:08

That's the issue, it's not using amdgpu at all. No matter what I do, it runs it on intel drivers

V1del · 2018-04-30 15:37:14

And you are assessing that from where exactly? The output you posted above confirms AMDGPU is the renderer. (Technically yes, the Intel GPU will remain the "controlling card" as that is where the display is connected to, PRIME is used to do the actual rendering task on the dedicated GPU which then copies over the final image for display.)

Last edited by V1del (2018-04-30 15:39:47)

probe2k · 2018-05-02 00:34:17

I have seen many people with primary vga controller being the dedicated chip, however that's not so in my case.
If I play games, would it use the default integrated graphics or the discrete graphics card?

loqs · 2018-05-02 00:49:23

probe2k wrote:

I have seen many people with primary vga controller being the dedicated chip, however that's not so in my case.

In those systems the display is connected to the discrete GPU is that possible for your system?

probe2k wrote:

If I play games, would it use the default integrated graphics or the discrete graphics card?

V1del already covered that

V1del wrote:

Technically yes, the Intel GPU will remain the "controlling card" as that is where the display is connected to, PRIME is used to do the actual rendering task on the dedicated GPU which then copies over the final image for display.

V1del · 2018-05-02 09:44:17

It might help if you posted the exact steps you are taking to show what you see and how that differs from what you expect to see.

probe2k · 2018-05-08 02:09:21

Thanks sir. I guess it's working, I just wanted to it to control the vga, but that doesn't seems to happen. So, it's good eitherways.

V1del · 2018-05-08 07:10:28

Well the closest to that would be to set up offloading, however that will likely not work on Wayland currently: https://wiki.archlinux.org/index.php/PR … rimary_GPU (however as already mentioned, depending on what software you are using to show you which graphics controller is being used, that might still simply query the X display driver which will always be intel, as long as your GL provider is AMD, that's what you want to have)

If you feel this has been sufficiently answered please mark as [SOLVED] by editing the title and adding that information.

Last edited by V1del (2018-05-08 07:19:25)

Arch Linux

#1 2018-04-21 15:15:39

AMD GPU Drivers Installation

#2 2018-04-21 21:18:47

Re: AMD GPU Drivers Installation

#3 2018-04-21 21:52:03

Re: AMD GPU Drivers Installation

#4 2018-04-22 09:09:24

Re: AMD GPU Drivers Installation

#5 2018-04-22 10:06:10

Re: AMD GPU Drivers Installation

#6 2018-04-25 13:25:24

Re: AMD GPU Drivers Installation

#7 2018-04-25 13:44:54

Re: AMD GPU Drivers Installation

#8 2018-04-25 18:58:18

Re: AMD GPU Drivers Installation

#9 2018-04-25 19:02:09

Re: AMD GPU Drivers Installation

#10 2018-04-26 21:10:11

Re: AMD GPU Drivers Installation

#11 2018-04-26 23:24:44

Re: AMD GPU Drivers Installation

#12 2018-04-27 13:59:26

Re: AMD GPU Drivers Installation

#13 2018-04-29 22:48:53

Re: AMD GPU Drivers Installation

#14 2018-04-30 02:41:30

Re: AMD GPU Drivers Installation

#15 2018-04-30 15:12:58

Re: AMD GPU Drivers Installation

#16 2018-04-30 15:19:08

Re: AMD GPU Drivers Installation

#17 2018-04-30 15:37:14

Re: AMD GPU Drivers Installation

#18 2018-05-02 00:34:17

Re: AMD GPU Drivers Installation

#19 2018-05-02 00:49:23

Re: AMD GPU Drivers Installation

#20 2018-05-02 09:44:17

Re: AMD GPU Drivers Installation

#21 2018-05-08 02:09:21

Re: AMD GPU Drivers Installation

#22 2018-05-08 07:10:28

Re: AMD GPU Drivers Installation

Board footer