From ArchWiki
Revision as of 12:41, 3 December 2011 by Paullik (talk | contribs) (added troubleshooting guide for RV530 when all 3D apps are showing a black screen)
Jump to: navigation, search

Forking this article for proprietary

Cleaned up some info today and noticed this article is really getting unruly. I propose that we fork the proprietary portion to its own article, such as "ATI Catalyst". Considering that the fglrx is now absolutely unsupported by Arch Linux, it would help make this article much less daunting to newcomers.

-- Thayer Mon Jan 4 10:53:18 PST 2010

I wholly agree.
-- pointone 23:53, 13 February 2010 (EST)
-- piezoelectric 20:58, 10 April 2010 (EDT)

EXA and Adobe Flash performance

I noticed that enabling

Option "AccelMethod" "EXA"

as mentioned under "Performance tuning" lead to significantly worse Flash performance. This was using extra/flashplugin, aur/firefox-beta 3.5rc2-1 and extra/xf86-video-ati 6.12.2-2. My card (ATI Radeon 9550) uses the RV350 chipset, hence it is a bit dated.

If this isn't just a local phenomena, perhaps it should be mentioned?

I don't know. I disabled EXA, and got even worse Flash performance, according to a flash benchmark test I found at Snails Animation [1]. (flashplugin, firefox 3.5.3-1, xf86-video-ati 6.12.2-2.) Same card and chipset, though. --Rataxes 16:38, 15 September 2009 (EDT)

KMS notes

KMS on r5xx not works with linux only if libdrm, libgl, mesa, xf86-video-ati - all installed from git.

KMS seems to be enabled by default on r5xx with latest packages from arch. Should all those messages about it being unsupported be removed? TheCycoONE

If KMS is enabled, dri-driver ( does not load. X switch to software rasterization ( if available. Using 2.6.34-zen1, xorg, mesa and xf86-video-ati from git master. approve plz. --ReMiND 05:47, 27 June 2010 (EDT)

Problem is gone after reading and including new radeon_ucode firmware R600_rlc.bin (provides with linux-firmware package) ReMiND 14:21, 10 July 2010 (EDT)

KMS -- do we have to do anything at all to enable it?

The KMS sections says it's on by default, should we even have to put radeon in MODULES any longer? If not, the intro to that section should probably mention that "you can skip the rest of this section if 'dmesg|grep modesetting' shows 'radeon kernel modesetting enabled'.

KMS Early

I don't know how others feel about this, but my preferred setup is to put options radeon modeset=1 in modprobe.conf and then to include modprobe.con along with the radeon module in mkinitcpio.conf. This way KMS is enabled once for both early and late start. Also, in the event of problems, radeon.modeset=1 can still be added as a kernel option to the bootloader. --piezoelectric

Driver ati or radeon

I just did the tutorial installing:

pacman -S xf86-video-ati libgl ati-dri

I could only get it working by changing in xorg.conf:

Driver "vesa"


Driver "ati"

and not:

Driver "radeon"

as the tutorial stated. I have no idea why/how, but maybe it'll help people reading it here.

--Overwave 16:02, 7 November 2010 (EST) The same happened for me, thanks for your tip.

radeon-initrd does not exist in AUR

Re: I think the radeon-initrd package has been removed since it's no longer needed, should the "tip" just say "add radeon to HOOKS" and not install radeon-initrd? --Unhammer 03:14, 23 August 2010 (EDT)

actually, I think the tip should probably just be removed... I tried adding radeon to HOOKS without having radeon-initrd, and got an error on making the image (I used to need radeon-initrd for 3d to work, now it seems to be enough to have the newest linux-firmware, no special HOOKS needed). --Unhammer 07:29, 23 August 2010 (EDT)
Yes, it should be removed. Please do so. Rransom 19:01, 24 August 2010 (EDT)

required virtual size does not fit available size ...

I was getting this error when trying to setup two screens with different resolutions using 'gnome-display-properties' (which in turn uses xrandr) : required virtual size does not fit available size: requested=(3200, 1080), minimum=(320, 200), maximum=(1920, 1920)

Removing 'nomodeset' from my kernel parameters fixed it. Removing the 'nomodeset' paramter should be discussed somewhere. I don't know enough about what it actually does to do so intelligently. --Gdw2 13:52, 21 March 2011 (EDT)

nomodeset disables KMS, and you shouldn't be using it anymore. It's not there by default, so you probably read about adding it somewhere on the wiki (you could add a warning to there). thestinger 00:18, 22 March 2011 (EDT)

On ATI X1600 (RV530 series) glxgears or any other 3D application or game show black windows

There are three possible solutions:

Try editing /boot/grub/menu.lst and add pci=nomsi at the end of your kernel line.

Also if this doesn't work, you can try adding noapic instead of pci=nomsi.

If none of the above work, then you can try running vblank_mode=0 glxgears or vblank_mode=1 glxgears to see which one works for you, then install driconf via pacman and set that option in ~/.drirc.