Talk:AMDGPU

From ArchWiki
Jump to: navigation, search

Supported Hardware

I just crawled the product names "Radeon xyz" of VI/CI GPUs together and was going to go on for professional products "FirePro xzy", too.

Afaik, there is no such complete listing on the web. There is a lot of confusion about the code and product names, due to AMD repeatedly rebranding their products and even change code names for same GPUs (Tonga = Antigua, Hawaii = Grenada, Carrizo = Bristol Ridge?, ...)

When I started using gnu/linux, the arch wiki was a great help and there are still a lot of people struggling with graphics drivers. Now I know it is not hard to understand, but it is still confusing for beginners, coming from windows and just being used to install one software suite (not a drm driver, libdrm, mesa, gallium, etc.), supporting all the current hardware.

now everyone has to go through all of this every time to determine 1) which hardware is really in their product and 2) which driver suits their hardware


tl;dr I think maintaining such a list would be really useful for beginners, maybe not here but in a separate article? Iuno (talk) 09:27, 16 February 2016 (UTC)

Well, Gentoo wiki has a simple two-line summary. If it's still not sufficiently clear or the list is already much larger, I guess we could have a separate subpage to not clutter the main page... -- Lahwaacz (talk) 10:20, 16 February 2016 (UTC)
yes, in the meantime I also found this table. It looks good but it is not complete. And completing the list would blow up the table cells a lot. I guess we should wait until vulkan and the new OpenCL driver has been released. Until then, there is no real reason for owners of pre-VI hardware to switch over to amdgpu. All vi and post-vi will be covered, so there is no need to list those separately. For the others I could create a subpage when switching to amdgpu gives you the opportunity for opencl 2.1 and vulkan -- Iuno (talk) 10:50, 16 February 2016 (UTC)

Enable amdgpu for Sea Islands Cards

testing my Hawaii card w/ amdgpu last week, sound did not work, even though 6 pcm/hdmi audio devices were listed. Might be added as an issue (as I think this is important deciding between radeon and amdgpu), but needs further investigation/confirmation from other testers. Iuno (talk) 09:53, 16 February 2016 (UTC)

Please remember the AMDGPU is still in beta, and there's still info and knowledge/experience missing (e.g. most users use the Radeon driver).
AMD isn't that great in providing info and so far a lot of users are confused about their hardware support in use with amdgpu.
Remember there are flags like exp_hw_support. More info need to be added, but it will take some time.
Francoism (talk) 13:14, 16 February 2016 (UTC)
It does indeed seem like that was no CI issue. Audio over hdmi is not supported by amdgpu atm, respectively only with the (upcoming) DAL changes[1], although it is listed as 'done' here. Iuno (talk) 15:59, 22 February 2016 (UTC)

Sea Islands cards not working with 4.5.x?

I stumbled across this wiki page in hopes of getting more performance after seeing Michael from Phoronix get his 290 working with this. Following through all the instructions, menuconfiging and compiling new kernels, in the end all I get is a blank screen with my r9 390. No errors on Xorg.0.log. Can anyone confirm that it isn't just me? Katorisenko (talk) 07:46, 24 April 2016 (UTC)

AMDGPU and HDMI Audio

According to this Freedesktop.org bug comment, HDMI audio support in AMDGPU requires DAL which is "not upstream yet", and won't be anytime soon according to this Phoronix article. I'm currently struggling to make my HDMI audio work with my AMD Radeon R9 380; if this happens to be impossible with AMDGPU, should we mention it in the "Troubleshooting" section of this page? --Hellpe (talk) 23:26, 3 January 2017 (UTC)

I am in favor of adding the information notice to the troubleshooting section. I think users who do not keep up with the news will be confused when Pulseaudio seems to add the HDMI audio devices, despite them being non-functional until the DAL code is refactored and accepted upstream then pushed to regular users. I know it was not immediately clear to me when I upgraded from my radeonsi card to an RX series amdgpu card until I did some reading. I "think" currently the only way to get HDMI audio is to use the AMDGPU-PRO driver for the time being. Ase1590 (talk) 15:48, 4 January 2017 (UTC)
I have it working with an R9 380 under Xorg. I did nothing special, simply disabled the built-in audio and enabled the HDMI audio. It does not work under Wayland however. Pavucontrol shows unavailable. Unit73e (talk) 12:22, 2 December 2017 (UTC)

Some experiments with integrated AMD graphics

Some results after playing with "radeon" and "amdgpu" drivers and gnome (for AMD A10 7850K):

- Having both drivers loaded causes systemd to hang at system shutdown (xorg). Using amdgpu and blacklisting radeon or using radeon and blacklisting amdgpu both fix this problem.

- Having amdgpu driver without mkinitcpio.conf entry causes 1. Wayland can't be enabled (always in xorg mode) and XDG_SESSION_TYPE shows "x11" 2. HDMI sound output is shown only in rare cases

- Having amdgpu driver with mkinitcpio.conf entry causes 1. Wayland is enabled by default and XDG_SESSION_TYPE shows "wayland" 2. HDMI sound is always disabled

- Having radeon driver without mkinitcpio.conf entry causes 1. Wayland can't be enabled (always in xorg mode) and XDG_SESSION_TYPE shows "x11" 2. HDMI sound is always correctly detected and working

- Having radeon driver with mkinitcpio.conf entry 1. Wayland is enabled by default and XDG_SESSION_TYPE shows "wayland" 2. HDMI sound is always correctly detected and working

Beoldhin (talk) 19:07, 23 May 2017 (UTC)

Update: with kernel 4.11.2-1: HDMI sound output is now working with "amdgpu" but only in as "Gnome in xorg" login option (still no sound with Wayland). There are still some graphical glitches when running Wayland with the radeon driver: external screen doesn't turn off after timeout, windows can't be maximized with the "wmctrl" command and updating text in terminal causes some text updating problems (these don't exist with xorg, amdgpu and radeon both work fine). So in summary: I can now select either amdgpu or radeon driver but Wayland is still unstable.

Beoldhin (talk) 19:07, 23 May 2017 (UTC)

Vega Changes for Wiki

With Vega releasing around the end of the month, the DC/DAL is still not it the kernel. Should we just put a note for users to use the AMDGPU-PRO drivers if they have VEGA cards? We could possibly add a note saying that in the AUR, there is an alternate kernel built from their repos with the DC/DAL code. Alternate kernel--> https://aur.archlinux.org/packages/linux-amd-staging-git/ Sesese9 (talk) 00:40, 10 July 2017 (UTC)

DC for Pre-Vega Cards

As far as I can tell, the Arch Linux kernel config enables DC by default for all (supported?) cards: https://git.archlinux.org/svntogit/packages.git/tree/trunk/config?h=packages/linux#n5725 Should the section on enabling DC be removed or changed? Aereaux (talk) 23:39, 6 February 2018 (UTC)

Can't check at the moment, but doesn't that require setting the kernel parameter as well? Also, keep in mind the custom kernels. Faalagorn / 02:51, 10 February 2018 (UTC)
I'm not sure how to check, but according to https://cateee.net/lkddb/web-lkddb/DRM_AMD_DC_PRE_VEGA.html , CONFIG_DRM_AMD_DC_PRE_VEGA=y enables it by default. It looks like it was already changed in the wiki, though. Aereaux (talk) 03:06, 10 February 2018 (UTC)

Moving "Enable GPU display scaling" to xrandr

I thought about it to put this under xrandr directly, but for example for my integrated Intel 6th gen GPU I don't have the "scaling mode" option, and I don't know about NVIDIA. And even if the "scaling mode" option exists for other vendors and or cards, I don't know if the possible values for "scaling mode" are the same everywhere, as far as I remember there are not. That was the reason I did put it here. Bertl (talk) 16:01, 18 February 2018 (UTC)

Ok, looks like Intel uses the same settings, but it's only available for internal (LVDS, eDP) ports, but at least according to https://bugs.freedesktop.org/show_bug.cgi?id=90989 it also uses "None, Full, Center, Full aspect".
I know that radeonsi uses the same commands, but still don't know about NVIDIA.
But yea, now I also think that it should be moved and the Intel section should be merged into it. Bertl (talk) 18:37, 18 February 2018 (UTC)

No 120hz with 4.15 kernel and DC enabled

AMDGPU with DC on in kernel 4.15 was not showing all resolutions and frequencies available. This bug is already fixed on staging: https://bugs.freedesktop.org/show_bug.cgi?id=105039 Unit73e (talk) 09:54, 2 March 2018 (UTC) unit73e

Fixed since Linux 4.16 Unit73e (talk) 18:23, 23 April 2018 (UTC)

Update on kernel parameters

this part does not seems to be required on 4.17:

>> Also, since kernel 4.13, adding the amdgpu.si_support=1 radeon.si_support=0 or amdgpu.cik_support=1 radeon.cik_support=0 kernel parameter is required. Otherwise, AMDGPU will not start and you will end up with either radeon being used instead or the display being frozen during the boot.

—This unsigned comment is by Lesto (talk) 12:10, 22 April 2018‎. Please sign your posts with ~~~~!

Renaming AMDGPU-PRO to Radeon Software for Linux?

So AMD basically changed the name of their AMDGPU-PRO driver as simply Radeon™ Software for Linux, see 17.40, 18.10 and 18.20 preview release notes. With that in mind, should the names on wiki be slowly changed, or the alternative name/note being added somewhere? I'm not sure if AMDGPU-PRO is still used by AMD officially and whether AMDGPU (without PRO) term is being used as well, but the name sure definitely stuck among community – any ideas? Faalagorn / 17:33, 11 May 2018 (UTC)

EDIT: Probably worth noticing is the similar situation happened between Fglrx and AMD Catalyst naming back then. Faalagorn / 17:38, 11 May 2018 (UTC)