Difference between revisions of "Talk:ATI"

From ArchWiki
Jump to: navigation, search
(Enabling video acceleration)
 
(49 intermediate revisions by 15 users not shown)
Line 1: Line 1:
== Questionable Statements ==
+
== Move ==
=== Introduction ===
+
"Naming conventions" paired with an introduction ''and'' an overview, feels overly verbose and jumbled flow-wise.  I suggest a consolidation of the three, offloading much of that info to wikipedia or the like.  Any objections?  I'll edit as soon as April.  [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 08:25, 12 March 2013 (UTC)
+
  
== Enabling video acceleration ==
+
So this page now covers {{Pkg|xf86-video-ati}} and {{Pkg|xf86-video-amdgpu}}. As I understand they are closely related and share quite some code, so it makes sense to keep them on the same page.
  
<tt>~/.bashrc</tt> is the wrong place for setting this environment variables. This file is not consulted when starting i.e. firefox from the gnome shell.
+
The name of the page doesn't seem appropriate anymore however. I am thinking something like "[[AMD graphics]]", like [[Intel graphics]], although that might not make clear that this is about the open source driver. On the other hand, [[AMD graphics (open-source)]] or [[AMD open-source graphics]] might be too long.
Setting this variables makes a difference when using flashplayer for youtube videos. When set, flashplayer reports accelerated rendering enabled at home with my ati hd3200 onboard graphics and rendering is faster in full screen mode.
+
  
It works now no more worse than under windows.
+
What do other people think? Should we move the page? What should be the new name? Thanks. [[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 16:15, 24 November 2015 (UTC)
:: So it only remains to replace content to reference /etc/profile.d instead.  I don't know the specifics off the top of my head, so if someone else would be so kind.... [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 08:18, 12 March 2013 (UTC)
+
::: I simply put a <tt>vdpau.sh</tt> and a <tt>vdpau.csh</tt> file under <tt>/etc/profile.d/</tt> which sets the environment variables and it seems to work (Flash video information says hw-acceleration is on). [[User:Kleinph|Kleinph]] ([[User talk:Kleinph|talk]]) 14:50, 4 June 2013 (UTC)
+
  
== Catalyst versus Radeon ==
+
:How much differences are between kernel/module parameters, etc.?
 +
:Don't forget troubleshooting, debugging, tools, etc. may differ.
 +
:I like the name AMD graphics, and I would prefer this for the ('official') AMD driver.
 +
:A separate page would be something I prefer, but if they are '80/90%' the same, it may be more clear to keep using this page.
 +
:[[User:Beta990|Beta990]] ([[User talk:Beta990|talk]]) 20:53, 25 November 2015 (UTC)
  
;Catalyst
+
::I am not really sure about the differences to be honest, it might well be that there is quite a lot of difference. There is a lot of information on [https://www.phoronix.com/scan.php?page=search&q=AMDGPU Phoronix], but a lot is still unclear to me. It would be nice to get some input from someone who has some more experience with it.
The ATI and Catalyst pages state that Catalyst performs better for 3D. As most of you may have experienced, the Catalyst driver is clunky and very badly optimized for Linux. Gaming performance is usually worse than on Windows. Catalyst and Nvidia drivers do not uses Unix interfaces properly (Linux kernel and Xorg), a big part of it is just a bunch of hacks. See what [http://nouveau.freedesktop.org/wiki/FAQ#So_go_to_a_country_where_it.2BIBk-s_not_illegal_and_produce_specs.21 the nouveau folks think]. Maybe it's a matter of syncing development between different platforms, so adapting the driver as less as possible from Windows is probably more profitable. The lack of respect for interfaces has one major issue: the compatibility with Xorg and Kernels is extremely fragile. Besides, a lot of features or simply not reliable (or at least a real pain to setup) with these drivers, such as dual head / external output, custom kernels, hibernation...
+
::"AMD graphics" indeed is too ambiguous to use for the open-source driver. If we decide to split off the AMDGPU stuff, we can just keep this at [[ATI]] and the new page at [[AMDGPU]], I think.
 +
::[[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 21:36, 25 November 2015 (UTC)
  
It would be a great relief for the Unix communities to finally have a free, full-featured and top class 3D graphic driver.
+
:::Although Phoronix daily publish articles about the new driver, it would be better to have a more 'reliable' source.
 +
:::Maybe we need to wait for users upgrading their cards and also give (the) AMD (module) a bit more time to develop.
 +
:::See my other question about the architect/GPU's that need or could upgrade.
 +
:::Is it supposed to replace the xf86-video-ati driver?
 +
:::[[User:Beta990|Beta990]] ([[User talk:Beta990|talk]]) 21:52, 25 November 2015 (UTC)
  
;Radeon
+
There now is a [[AMDGPU]] page. All info related to the amdgpu driver with GNC 1.2 cards should be moved there. [[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 13:22, 16 February 2016 (UTC)
AMD did a very good thing when they decided to release the specs of their cards. FOSS radeon driver is now lightyears beyond nouveau in term of OpenGL implementation. The FOSS radeon driver seems like the ideal future of Unix graphics to me.
+
  
Since version 9.0.* from late 2012 and January 2013, OpenGL implementation has moved several steps forward as you can see on the [http://www.x.org/wiki/RadeonFeature feature matrix]. In fact, I've tested several games (native or Wine) and radeon performs much better than catalyst most of the times.
+
== Adding xf86-video-amdgpu ==
  
For performance and Unix-frendliness, I suggest we should encourage Unix users to choose radeon over catalyst. Too many people are held back in their switching-to-Unix because of the terrible, infamous catalyst, even if all they need is average 3D graphics.
+
I would like to know what cards should use xf86-video-amdgpu instead of xf86-video-ati; if I understand correctly it is possible (some) older cards are also compatible with this driver.
 +
Is there an official status page (like if DPM works, what is supported, etc.)?
  
Since this revolution is brand new, it requires support from the community. We also need concrete data that states the progress, the support and the performance of radeon compared to catalyst.
+
Thanks!
  
I suggest we create a benchmark page for that. Should we create a new page? I'll begin it below for now, but we shall move it in the future.
+
[[User:Beta990|Beta990]] ([[User talk:Beta990|talk]]) 20:44, 25 November 2015 (UTC)
  
--[[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 12:07, 6 February 2013 (UTC)
+
:The [http://www.x.org/wiki/RadeonFeature/ feature matrix] says only "Volcanic Islands" GPUs are supported, I believe that that is the codename for Graphics Core Next (GCN) 1.2. You can find all cards that are based on GCN 1.2 at [[Wikipedia:List of AMD graphics processing units]]. The feature matrix also lists what features are supported.
 +
:I am not sure about older cards, but I think this is as "official" as it's going to get. [[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 21:19, 25 November 2015 (UTC)
  
:: A benchmark page could be informative, especially for newcomers that are having a difficult time making up their minds.  AMD is actually shifting support from Catalyst to radeon drivers.  They had hired two bodies to work on the radeon driver. But then I came across this: http://www.h-online.com/open/news/item/AMD-dismisses-numerous-open-source-developers-1745131.html
+
::Thanks for the reply. :)
:: I just found this: http://www.theregister.co.uk/2013/02/05/amd_open_source_hd_8000_drivers/print.html
+
::I've read a few reports of users that the driver works on older GCN's, but this should need more testing.
:: Regardless, there has been a lot of headway in the last four years.  I recently tested some games on vanilla Wine and performance was considerable.
+
::How much stable and complete is the new driver? I think we need more info before adding a new wiki page.
:: When I came to Arch, I was using Catalyst.  I was a pain to setup and maintain.  I was since persuaded by a Wine developer to switch to the radeon driver, as it is much easier to debug and submit patches upstream for either Wine or Radeon.  Not to mention Catalyst only ever "officially" supported Ubuntu, SUSE, and RedHat.
+
::[[User:Beta990|Beta990]] ([[User talk:Beta990|talk]]) 22:00, 25 November 2015 (UTC)
:: Drop a line to the Catalyst talk page? [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 17:27, 6 February 2013 (UTC)
+
::: I think the message in the introduction is clear: '''If unsure, try the open source driver first, it will suit most needs and is generally less problematic'''. -- 09:37, 7 February 2013 (UTC)
+
::::Sure, but the previous paragraph clearly tells 'if you want 3D performance, go for Catalyst', which is not very true anymore. --[[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 09:43, 7 February 2013 (UTC)
+
:::::I agree.  So we just need a clear statement from a benchmarking website that supports that.  Preferably something recent.  
+
:::::I will not question the removal of dubious statements, so long as that point is made clear in the edit summary. [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 19:00, 7 February 2013 (UTC)
+
::::::At any rate, edits to wiki articles should be free of personal bias.  Older content should be neutralized if appropriate.  I believe the wiki exists to instruct procedures from any angle, not to influence a personal attitude. Cite credible sources when necessary. [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 08:08, 12 March 2013 (UTC)
+
  
=== Benchmark ===
+
:::Looks like the gentoo wiki pages for the [https://wiki.gentoo.org/wiki/Radeon#Feature_support Radeon] and [https://wiki.gentoo.org/wiki/Amdgpu#Feature_support AMDGPU] drivers have tables for which graphics cards are supported by which open-source driver. Presumably this information is valid for Radeon and AMDGPU themselves, rather than just for their respective Gentoo packages (and is accurate)? [[User:ShadowElemental|ShadowElemental]] ([[User talk:ShadowElemental|talk]]) 04:21, 13 January 2016 (UTC)
 
+
The following benchmark table is open for contribution.
+
However the benchmarking process is not trivial, it needs some helper scripts and configurations beforehand.
+
 
+
====Turn vsync off====
+
The radeon driver will enable vsync by default, which is perfectly fine except for benchmarking. To turn it off, create {{ic|~/.drirc}} (or edit it if it already exists) and add the following section:
+
{{hc|~/.drirc|<nowiki>
+
<driconf>
+
    <device screen="0" driver="dri2">
+
        <application name="Default">
+
            <option name="vblank_mode" value="0" />
+
        </application>
+
    </device>
+
    <!-- Other devices ... -->
+
</driconf>
+
</nowiki>}}
+
It is effectively '''dri2''', not your video card code (like r600).
+
 
+
====Driver switching helper====
+
You may find yourself switching the driver a lot for benchmarking. Since there is conflicts between {{pkg|radeon}} and {{pkg|catalyst-utils}} it is quite cumbersome in the long run. So I wrote a little, very simple script. It only works for syslinux and Arch Linux. You ''must'' adapt it if you are using GRUB or another bootloader. This will also remove the {{ic|/etc/X11/xorg.conf}} file, so if you are using it, backup this file. Catalyst will backup it anyway.
+
{{hc|switchdriver.sh|<nowiki>
+
#!/bin/sh
+
 
+
if [ -z "$(lspci|grep "VGA.*Radeon")" ]; then
+
    echo "You must have a Radeon graphic adapter. Exit."
+
    exit
+
fi
+
 
+
if [ $(id -u) -ne 0 ]; then
+
    echo "You must be root to run this script. Exit."
+
    exit
+
fi
+
 
+
if [ $(pacman -Qi catalyst-utils 2>/dev/null|wc -l) -ge 2 ]; then
+
    pacman -Rdd --noconfirm catalyst-utils catalyst-dkms lib32-catalyst-utils
+
    rm -f "/etc/X11/xorg.conf"
+
    pacman -S --noconfirm ati-dri lib32-ati-dri  xf86-video-ati
+
    if [ -f "/boot/syslinux/syslinux.cfg" ]; then
+
        sed -i 's/nomodeset//' "/boot/syslinux/syslinux.cfg"
+
        echo
+
        echo "#### Syslinux entry:"
+
        grep -A4 "^LABEL arch$" "/boot/syslinux/syslinux.cfg"
+
    else
+
        echo "You do not seem to use Syslinux. No configuration done."
+
        echo "You have to remove 'nomodeset' kernel parameter manually."
+
    fi
+
else
+
    pacman -Rs --noconfirm ati-dri lib32-ati-dri  xf86-video-ati
+
    pacman -Rdd --noconfirm mesa-libgl lib32-mesa-libgl
+
    pacman -S  --noconfirm catalyst-utils catalyst-dkms lib32-catalyst-utils
+
    aticonfig --initial
+
    if [ $? -eq 0 ] && [ -f "/boot/syslinux/syslinux.cfg" ]; then
+
        sed -i '/^LABEL arch$/{n;n;n;s/$/ nomodeset/}' "/boot/syslinux/syslinux.cfg"
+
        echo
+
        echo "#### Syslinux entry:"
+
        grep -A4 "^LABEL arch$" "/boot/syslinux/syslinux.cfg"
+
    else
+
        echo "You do not seem to use Syslinux. No configuration done."
+
        echo "You have to add 'nomodeset' kernel parameter manually."
+
    fi
+
fi
+
</nowiki>}}
+
 
+
====OpenGL FPS monitor====
+
For native OpenGL games, there is actually no universal solution. Check if the game has an embedded FPS monitor (check the developper console or something like that). Otherwise we must use an external tool that will hook the double buffering function (glXSwapBuffers) to compute the framerate. I've found two FPS monitors that could do that:
+
* [http://code.fluffytapeworm.com/projects/libglfps libglfps] which I haven't been able to run properly. But with some source code edits I managed to output the FPS to the terminal.
+
* [http://code.google.com/p/frapix/ frapix] is newer and seems to work.
+
 
+
It works for some OpenGL applications like glxgears, but it will not for others, ''e.g.'' Legend of Grimrock. I'm still looking for a solution here.
+
 
+
====Wine====
+
Thankfully Wine features an embedded FPS monitor which works for all graphical applications. You just need to start the application with the {{ic|1=WINEDEBUG=fps}} variable set.
+
You can actually display the FPS on top of the game window thanks to {{ic|osd_cat}} from the {{pkg|xosd}} package. I wrote a helper script for convenience:
+
 
+
{{hc|winefps.sh|<nowiki>
+
if [ $# -lt 1 ]; then
+
    echo "Usage: ${0##*/} WIN32EXE PARAMS"
+
    exit
+
fi
+
 
+
if [ -z "$(command -v osd_cat)" ]; then
+
    echo "You must have osd_cat."
+
    exit
+
fi
+
 
+
if [ -z "$(sed --version | grep "GNU")" ]; then
+
    echo "You must have GNU sed."
+
    exit
+
fi
+
 
+
WINEDEBUG=fps wine "$@" 2>&1 | tee /dev/stderr | \
+
    sed -un '/^trace:fps:/{s/.* \([^ ]*\)fps/\1/;p}' | \
+
    osd_cat -l1 -f  "-*-*-*-*-*-*-32-*-*-*-*-*-*-*" -O1 -c "yellow"
+
</nowiki>}}
+
 
+
It works fullscreen with radeon, but seems quite messy with catalyst: you get a flash everytime osd_cat refreshes the output. A workaround is to play in windowed mode. If you are using a nice enough window manager you can toggle full screen with a shortcut.
+
[[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 22:15, 9 March 2013 (UTC)
+
 
+
==== Benchmark table====
+
 
+
The relevent measures here focus on the comparison between the two drivers. Remember to use the same configuration and measure tools when benchmarking an application.
+
 
+
;avg: average framerate
+
;min-max: minimum and maximum framerate
+
 
+
{| border="1"
+
! rowspan="2" | Game !! rowspan="2" |Version !! width="50pt" rowspan="2" | Native Wine !! rowspan="2" | Hardware !! colspan="3" | Radeon !! colspan="3" | Catalyst !! rowspan="2" | Comments
+
|-
+
! version !! avg !! min-max  !!  version !! avg !! min-max
+
|-
+
| Command and Conquer Generals    ||        First Decade || Wine        || HD5770  ||          9.1 ||  30 ||  26-32 ||            13.1 ||  27 ||  18-30 ||
+
|-
+
| eduke32                        || 20130120_342 HRP 5.2 || Native      || HD5770  ||          9.1 ||  15 ||  12-18 ||            13.1 ||    ||        || Polymer, crash with Catalyst.
+
|-
+
| eduke32                        || 20130120_342 HRP 5.2 || Native      || HD5770  ||          9.1 ||  60 ||  60-60 ||            13.1 || 120 ||  70-200 || Polymost, loads faster on Catalyst, capped with Radeon.
+
|-
+
| Fallout New Vegas              ||                  1.0 || Wine        || HD5770  ||          9.1 ||  14 ||    5-20 ||            13.1 ||  15 ||    8-22 || Average graphics.
+
|-
+
| Far Cry 2                      ||                  1.3 || Wine        || HD5770  ||          9.1 ||  18 ||  15-40 ||            13.1 ||  20 ||  13-25 || Videos are very buggy with Catalyst.
+
|-
+
| Quake 3 Arena                  ||                1.32 || Wine        || HD5770  ||          9.1 ||  76 ||  75-77 ||            13.1 ||  86 ||  85-87 ||
+
|-
+
| Team Fortress 2                ||                      || Native      || HD5770  ||          9.1 ||  20 ||  10-60 ||            13.1 || 200 ||  30-300 || 16 bots cp_gorge, high graphics.
+
|-
+
| The Elder Scrolls III Morrowind ||                GOTYE || Wine        || HD5770  ||          9.1 ||  26 ||  16-60 ||            13.1 ||  26 ||  14-50 ||
+
|-
+
| Unigine Heaven Benchmark        ||                  2.5 || Native      || HD5770  ||          9.1 ||    ||        ||            13.1 ||  20 ||  15-25 || Using normal tesselation. Radeon does not support tesselation as of 9.1.
+
|-
+
| Unreal Tournament              ||                  436 || Wine        || HD5770  ||          9.1 || 120 || 118-160 ||            13.1 ||  95 ||  90-100 || Game stutters while using Catalyst + osd_cat.
+
|}
+
 
+
Note: this table looks properly aligned when edited in monospace (using [[Emacs Mediawiki]] for instance). I'm not sure that's the best way to go for tables in a wiki because the web view looks terrible; but if each column goes on its respective line, that's even harder to read in my opinion. [[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 22:22, 9 March 2013 (UTC)
+
:: Obviously you went through a serious effort to produce these results, thank you.  It appears to me that driver performance might be dependant on the game engine as much as anything else, but the two drivers are neck to neck on most games.  At least for the 5770, there is no clear performance winner except in a few specific cases.  If only we could convince one of the tech sites to do something more comprehensive...I know they always have a nice selection of hardware to pick from... [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 07:56, 12 March 2013 (UTC)
+
 
+
Well, that was some research on the topic, but that's only the beginning! I still need to work on a proper FPS monitor, but I do not have much time right now. If someone knows how to measure FPS for OpenGL games that do not seem to use glXSwapBuffers... Anyway, as you said, we need more results. I have a bunch of games still waiting to be benchmarked, but I do not have much time right now. I can do it in a month or so. However this is not of utmost importance, what we need right now is a benchmark covering the various ATI cards.
+
 
+
This benchmark definitely needs more advertising. On this page it's worth nothing, chances are high nobody ever reads it. It think it deserves a better, more visited place. ArchWiki is great, and in a few years it managed to gathered so much stuff about Unix. Even when I was using FreeBSD I used Arch Wiki a lot (I'm still using it actually). Besides it seems like there is an army of ex-gamers among Arch users. Look at the Wine stats: [http://appdb.winehq.org/objectManager.php?sClass=distribution&sTitle=View%20Distributions AppDB Distributions]. I've skimmed over the pages, and it seems like Arch is in the top 5 with Ubuntu, Debian, Mint and Gentoo.
+
What I'm suggesting here is that we can manage to gather the benchmark results for different hardware using the manpower of the Arch Wiki.
+
 
+
Maybe that's not a good idea and it would fit better at Xorg or some place. Tell me what you think. If you agree, we can create an specific page ''Radeon vs Catalyst'' or something, create links on ATI and Catalyst pages, and invite users on the forum to contribute. -- [[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 15:25, 12 March 2013 (UTC)
+
 
+
:: My personal conclusion on this benchmark: Catalyst has better performances for native games, but is as bad as Radeon for Wine. Radeon is much more comfortable in many ways since it is almost bug-free (I'm speaking of obvious bugs like crashes and glitches). Every new release of Radeon gives a huge performance boost in games, up to 100-150% I'd say, but I have no data for that. (I could benchmark with 9.0, but that's not worth it, let's wait for 9.2.) -- [[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 15:34, 12 March 2013 (UTC)
+
::: This has got to start somewhere...I think posting something on the forums, linking here, will increase traffic.  We might possibly create a dedicated wiki page, but I don't know how the admins will feel about that.  I suppose the forum thread would poll the support on such a move.  The main argument for Radeon that was presented to me by a Wine developer was: a bug in Catalyst ''might'' get fixed in the distant future, a bug in Radeon could get fixed in a few days. That motivated me to switch. [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 05:49, 13 March 2013 (UTC)
+
 
+
::Okay, so I'll start a thread. If it works and gains popularity, this page will get bloated soon (it already is), so moving it to a dedicated page will be more than necessary. -- [[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 11:29, 14 March 2013 (UTC)
+
 
+
::New thread here: https://bbs.archlinux.org/viewtopic.php?pid=1244119#p1244119
+
 
+
::By the way I've found this benchmark on  [http://www.phoronix.com/scan.php?page=article&item=amd_lucidrar_r4830&num=1 phoronix]. -- [[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 12:07, 14 March 2013 (UTC)
+
 
+
== Overheating ==
+
Worth to mention that the powersaving is related to overheating issues. With the default powersaving off my laptop's graphic card, Mobility Radeon HD 4650, overheating causing the system to shutdown. Changing the setting to mid solved this issue.[[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 12:37, 9 March 2013 (UTC)
+
: Laptops are also prone to dust accumulation. You should try taking some pressurized air to the vents, whether from a can or air compressor.  I've seen dust=overheating dozens of times with my own equipment and with friends and family.  Naturally, lowering the voltage via powersaving functions will mitigate such issues. Temporarily. [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 19:55, 9 March 2013 (UTC)
+
:: Thanks T1nk3r3r, but this isn't dust related, I've a habbit of cracking open my laptop once in a while and cleaning it with a blow fan. This is a real issue that I think needed to be addressed in the wiki. Good remark about lowering the voltage, currently I'm satisfied with the manual mid setting.[[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 09:37, 20 March 2013 (UTC)
+
 
+
== Early KMS ==
+
 
+
I think that the Early KMS start in this page is very messy. The explanations on nouveau and intel pages, and the generic in KMS are much simpler.
+
If someone confirm that this is poorly explained, I will modify it.--[[User:Jacobopantoja|Jacobopantoja]] ([[User talk:Jacobopantoja|talk]]) 02:37, 27 March 2013 (UTC)
+

Latest revision as of 13:22, 16 February 2016

Move

So this page now covers xf86-video-ati and xf86-video-amdgpu. As I understand they are closely related and share quite some code, so it makes sense to keep them on the same page.

The name of the page doesn't seem appropriate anymore however. I am thinking something like "AMD graphics", like Intel graphics, although that might not make clear that this is about the open source driver. On the other hand, AMD graphics (open-source) or AMD open-source graphics might be too long.

What do other people think? Should we move the page? What should be the new name? Thanks. Lonaowna (talk) 16:15, 24 November 2015 (UTC)

How much differences are between kernel/module parameters, etc.?
Don't forget troubleshooting, debugging, tools, etc. may differ.
I like the name AMD graphics, and I would prefer this for the ('official') AMD driver.
A separate page would be something I prefer, but if they are '80/90%' the same, it may be more clear to keep using this page.
Beta990 (talk) 20:53, 25 November 2015 (UTC)
I am not really sure about the differences to be honest, it might well be that there is quite a lot of difference. There is a lot of information on Phoronix, but a lot is still unclear to me. It would be nice to get some input from someone who has some more experience with it.
"AMD graphics" indeed is too ambiguous to use for the open-source driver. If we decide to split off the AMDGPU stuff, we can just keep this at ATI and the new page at AMDGPU, I think.
Lonaowna (talk) 21:36, 25 November 2015 (UTC)
Although Phoronix daily publish articles about the new driver, it would be better to have a more 'reliable' source.
Maybe we need to wait for users upgrading their cards and also give (the) AMD (module) a bit more time to develop.
See my other question about the architect/GPU's that need or could upgrade.
Is it supposed to replace the xf86-video-ati driver?
Beta990 (talk) 21:52, 25 November 2015 (UTC)

There now is a AMDGPU page. All info related to the amdgpu driver with GNC 1.2 cards should be moved there. Lonaowna (talk) 13:22, 16 February 2016 (UTC)

Adding xf86-video-amdgpu

I would like to know what cards should use xf86-video-amdgpu instead of xf86-video-ati; if I understand correctly it is possible (some) older cards are also compatible with this driver. Is there an official status page (like if DPM works, what is supported, etc.)?

Thanks!

Beta990 (talk) 20:44, 25 November 2015 (UTC)

The feature matrix says only "Volcanic Islands" GPUs are supported, I believe that that is the codename for Graphics Core Next (GCN) 1.2. You can find all cards that are based on GCN 1.2 at Wikipedia:List of AMD graphics processing units. The feature matrix also lists what features are supported.
I am not sure about older cards, but I think this is as "official" as it's going to get. Lonaowna (talk) 21:19, 25 November 2015 (UTC)
Thanks for the reply. :)
I've read a few reports of users that the driver works on older GCN's, but this should need more testing.
How much stable and complete is the new driver? I think we need more info before adding a new wiki page.
Beta990 (talk) 22:00, 25 November 2015 (UTC)
Looks like the gentoo wiki pages for the Radeon and AMDGPU drivers have tables for which graphics cards are supported by which open-source driver. Presumably this information is valid for Radeon and AMDGPU themselves, rather than just for their respective Gentoo packages (and is accurate)? ShadowElemental (talk) 04:21, 13 January 2016 (UTC)