cchtml.com - User contributions [en]

Category:NeedsUpdating

2008-02-13T10:38:46Z

200.29.96.75: elttrou

vililiracc
Here is your opportunity to support this site. Any of the linked pages below need updating. Please update and remove the NeedsUpdating flag.

Fedora 8 Installation Guide

2008-02-13T10:38:37Z

200.29.96.75: actrdarsi

eltouricdo
==General Status==
* Supported since [[Catalyst 7.11]], which adds support for kernel 2.6.23.

==Installation Option #1 Freshrpms.net repository==
rpm -ihv http://ftp.freshrpms.net/pub/freshrpms/fedora/linux/8/freshrpms-release/freshrpms-release-1.1-1.fc.noarch.rpm
yum install -y ati-x11-drv
and restart your system.

==Installation Option #2 Livna repository==
rpm -ivh http://rpm.livna.org/livna-release-8.rpm
* [http://www.fedorafaq.org/#radeon These instructions] on the Unoffical Fedora FAQ work. (In order not to duplicate the the instructions, we provide the link rather than the instructions themselves).

==Installation Option #3 via ATI Installer==
You can get the latest ATI-Driver here:

[http://ati.amd.com/support/drivers/linux/linux-radeon.html|ATI Linux Driver]

The above bugzilla contains a patch to the firegl module source code. Here is an annotated walk-through for those not familiar with using the patch utility:
* Install the driver interactively
sh ./ati-driver-installer-8.42.3-x86.x86_64.run
* Backup the existing module, download the patch
cd /lib/modules/fglrx/build_mod/
cp firegl_public.c firegl_public.c.orig
wget -qO- http://ati.cchtml.com/attachment.cgi?id=466 > firegl.patch
* Apply the patch
patch -p0 < firegl.patch
* Now build and install the kernel module
./make.sh
cd .. ; ./make_install.sh
* Create an initial X Server configuration file
aticonfig --initial
* Restart your X Server (by logging out/in or rebooting)

==Issues==
* AMD/ATI Catalist Control Center (amdcccle) fails to start, see [http://ati.cchtml.com/show_bug.cgi?id=672 this bugzilla entry].

FYI: this patch (and others like it) is incomplete. It fails miserably with the drm module loaded. It will not work without drm either, and what would be the point?
As seen by dmesg:

[drm] Initialized drm 1.1.0 20060810
[fglrx] Maximum main memory to use for locked dma buffers: 1898 MBytes.
[fglrx] ASYNCIO init succeed!
[fglrx:KCL_enable_pat] *ERROR* Pat entry 2 is already configured
[fglrx] PAT is disabled!
[fglrx:firegl_init_module] *ERROR* firegl_stub_register failed

The livna rpm incurs the same failure. Stick with F7 and kernel 2.6.22, or use the radeon driver instead.

----
Updated by yangyud: 
You need to remove the loaded "drm" module from kernel before install the fglrx module. 
'''rmmod radeon; rmmod drm''' 

==See Also==
* [[Frequently Asked Questions#Why does fglrx not work for my bleeding-edge kernel?]]

[[Category:Installation Documentation]]
Ok, the problem is gdm. I can `startx`, but gdm fails to load with fglrx, and there is no indication in any log as to why.
This continues with new 7.11 Catalyst driver.
Because of this, the problem is NOT with the driver, rather it is the default GDM time value of 10-seconds. To remedy:

vi /etc/gdm/custom.conf

[daemon]
GdmXserverTimeout=60

This allows enough time for X to startup before gdm considers it dead and aborts the X startup process.

Troubleshooting

2008-02-13T10:38:09Z

200.29.96.75: dronbas

taercn
==Kernel Related Issues==

=== No 3D acceleration ===
If you see output that looks like this:

$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.1)

Make sure you do not have Xinerama enabled in your xorg.conf! 3D-acceleration is not supported by fglrx in Xinerama mode.

Then try these two commands:

sudo mkdir -p /usr/X11R6/lib/modules/dri
sudo ln -s /usr/lib/dri/fglrx_dri.so /usr/X11R6/lib/modules/dri
Source<ref>http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian</ref>

Or you can try deleting all files from the /lib/modules/$(uname -r)/volatile folder and relinking:

<code>
sudo rm /lib/modules/$(uname -r)/volatile/* 
sudo ln -s /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko
</code> 

If that doesn't work confirm fglrx is loaded:

lsmod | grep fglrx

If it returns nothing then try this:

sudo depmod -ae
sudo echo fglrx >> /etc/modules
(If this returns "bash: /etc/modules: Permission denied" then sudo su first.)

If it doesn't still work, open up /etc/modprobe.d/lrm-video with an editor, and uncomment any line(s) that contains fglrx in it.

In case nothing above works, open /etc/modprobe.d/blacklist-restricted with an editor and comment any line that might contain fglrx word in it.

=== nForce 3 AGP Issues ===

For nForce3 based motherboards: if the install seems to go well, but fglrx still fails and $ fglrxinfo tells you you're still running Mesa, there may be a problem with the nVidia AGP-PCI Bridge module's compatibility with your BIOS (or vice versa, I haven't yet investigated). (Confirmed at least for ASUS K8N-E Deluxe.) A solution is to downgrade your BIOS to a previous version (see your motherboard manual/manufacturer's website for instructions). Here is a list of compatible BIOS versions (if your model is not listed here and you find a version that fixes the problem, please add it to the list so others can benefit):

(Update: March 22nd, 2007) It appears that the beta ASUS bios 1012 will also fix the problem. I had the ATI drivers installed but fglrxinfo was still reporting Mesa as the OpenGL provider. I flashed the BIOS to 1012, rebooted into Ubuntu. Problem solved.

''The 1012 bios did not work for my K8N-E deluxe mobo and my x800. Bios 1006 works great though.''

*ASUS
**K8N-E Deluxe: Version 1006
**K8N-E Deluxe: Version 1012 beta
**K8N Bios versions up 1003 to 1011, my Solution -> K8V-X (Asus with Via-Chipset) It is working really good now. (Always Problems: nForce3 Chipset)

*ASROCK
**K8Upgrade-NF3

(A little workaround for K8Upgrade-NF3 is to edit xorg.conf, in section "Devices", adding this line: Option "UseInternalAGPGART" "no")
It doesn't work with Gutsy release yet.

*GIGABYTE
**GA-K8NSC-939: Bios versions: F1, F2

=== AGP Initialization fails with amd_k7_agp module ===
With Kernel 2.6.16.x, there came a new feature called "EDAC" which creates a conflict causing amd_k7_agp not to work. This results in a
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV"
(EE) fglrx(0): cannot init AGP
Message in the error-log.

To resolve the problem, in your kernel config change
CONFIG_EDAC_AMD76X=y
to
#CONFIG_EDAC_AMD76X is not set
(just comment it out)
recompile/reinstall/reboot your kernel. Everything should work now.

=== Using realtime enabled kernels ===

Apparently the official driver doesn't support realtime enabled kernels, as installation fails to build the kernel module (see /usr/share/ati/fglrx-install.log). Correct this if I'm wrong.

==X Server Related Issues==

=== No high-resolution video modes available ===
* Recent versions of the fglrx driver (seen with 7.12) seem to have problems with video resolutions higher than 1280 x 1024. The modes of the xorg.conf are simply ignored, and the server starts up e.g. with a resolution 1280 x 1024 (even if this resolution is not defined in xorg.conf). This is particularly a problem on LCD displays.
* [http://ati.cchtml.com/show_bug.cgi?id=160 This bug] documents the problem.
* No known workaround.
* The bug seems to be fixed with driver version 8.1 (though I cannot fully verify this since my system locks up hard after (correctly) setting the graphics mode, SuSE 10.0 not supported anymore - [[User:Akhuettel|Akhuettel]])

=== No XVideo support on 690G integrated graphic chipset ===
*Upgrade your BIOS if you get random flicker lines and black screen with a 690G chip.
*Motherboard using the 690G IGP chipset don't have XVideo support. When you execute the "xvinfo" command you get "no adaptors present". This is the case by using the 8.39.4 FGLRX driver and whenever the "sudo aticonfig --overlay-type=Xv" command or the "sudo aticonfig --overlay-type=opengl" was used. ATI seem to know this as there list TVtime as an application unable to run on a 690G chip.

=== System lockup on logout or switch to virtual consoles ===

If your system locks up after you logout or when you try to switch to a virtual console, this might be an instance of [http://ati.cchtml.com/show_bug.cgi?id=330 this bug]. It is likely that the problem only occurs for users with an '''Xorg version of at least 7.0'''. Probably it only affects users of '''DVI'''.

There is a workaround: Use a standard D-Sub VGA connector instead of the DVI connector.

This workaround was posted as a comment to another related bug: see [http://ati.cchtml.com/show_bug.cgi?id=239#c48 here].
---------
Unfortunately "D-sub" users (like me) have the same problem.

=== BigDesktop (Dual screen) doesn't work after GDM login screen ===

This can occur on Ubuntu Feisty Fawn & Gutsy.

System > Prefrences > Screen Resolution

Select the resolution that is a combination of both screen resolutions wide and your height.

If X crashes during login, go to a virtual console using Ctrl+Alt+F1, log in, <code>sudo vim /etc/X11/xorg.conf</code>, and comment out the line which looks like the following:
{{Box File|/etc/X11/xorg.conf|
<pre> Option "DesktopSetup" "something"</pre>
}}

=== Computer Freezes while using fglrx (UMA and SIDEPORT) ===
If after choosing fglrx as your driver in either xorg.conf or xfree86.conf files, the computer freezes and becomes unresponsive while trying to start X this may be the solution.

Some ATI cards have the ability to run in three modes: UMA, SIDEPORT, or a combination of both. UMA mode is that one in which the video card does not use its dedicated memory, but rather uses and shares the system memory. On the other hand, SIDEPORT mode is the one in which the card uses its own dedicated memory. And finally, the third mode is a combination of the previous modes in which the card uses both the system memory and its dedicated memory.

If your computer hangs, this settings may be where the solution lies. If your computer hangs, try using either UMA by itself or a combination of both. However, if you choose the combination, make sure that the UMA one is at least 128MB. In my case, I have SIDEPORT 128MB and 128MB UMA. If I choose any less for UMA, it does not work. This is definetly not an attractive solution since it compromises your systems performance. Hopefully, this will be solved very soon.

On some systems, the BIOS screen may not offer a choice of UMA or SIDEPORT. In this case, you can try turning the amount of RAM dedicated to the video card down, from 128Mb to 64Mb for example.

=== Graphical Anomalies ===

This was experienced with an ATI Radeon X1600 Pro 512mb:

After following instructions for both Method 1 and Method 2, whenever the Composite Extension is disabled, the display would be almost unusable, but the fglrxinfo command would display the correct information. If the Composite Extension is re-enabled the display would be usable, but fglrxinfo would report using mesa drivers.

To resolve the problem it maybe needed to lower the AGP Aperture setting in my BIOS to 128mb (or lower worked too). The AGP Aperture was initially set to 256mb. After setting the AGP Aperture to 128mb, everything worked perfectly; the Composite Extension is disabled, fglrxinfo reports the correct drivers, and direct rendering is enabled. Some systems may require setting the AGP Aperture to the highest setting (256mb or 512mb).

There's been a bug report regarding [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/150627 anomalies in Firefox] as well.

=== Blank Screen with Xorg 1.3.0 ===
If you happen to get a blank screen on X startup and you find lines similar to those in your Xorg.log:
{{Box File|/var/log/Xorg.log|
<nowiki>
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(swlDalHelperValidateModeFromDAL 0x549) [...]
3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so [...]
4: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxPreInit 0x8b3) [...]
</nowiki>
}}

Then you're probably using the ati-drivers with Xorg-1.3.0. If that's the case the only solution (known to me) is to use a version < 1.3.0.

Edit: I got the same problem after using the --add-pairmode argument of aticonfig (using Xorg 1.3.0). My ati mobility x300 seemes to try
sending the monitor signal to the vga output (even if no monitor is connected to it). After pressing [Fn]+[F8(CRT/LCD)] the monitor
signal sometimes returnes to the internal laptop monitor.
By switching to a console or shutting down the X-server, the card switches back to vga...

My solution: overwriting the file /etc/ati/amdpcsdb with /etc/ati/amdpcsdb.default (sudo cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb)
and restore the xorg.conf (since Xorg replaces /etc/X11/xorg.conf with a failsafe config file). Then reboot the system: fglrx should now
work fine again with Xorg-1.3.0 .

=== Radeon GPU fan is very loud / constantly works ===
:See [http://ati.cchtml.com/show_bug.cgi?id=499 bug 499] for additional information.
It seems fglrx has a bug with all X800/X850 cards causing them to heat up excessively
even when not in 3D mode. This behaviour will cause the cards' fans to function on full
blast continuously. There is no known fix as of driver 8.31.05 or previous. Open source
"radeon" driver does not exhibit this problem.

My Ati 1650GT has the same problem.It was normal when I enter ubuntu for 1 or 2minutes,and than ,the fan became crazy..No doubt it's because the temp~

It happens too with Radeon X1800 GTO and Radeon X1900 GT.

Possible solution (at least using a Mobility Radeon X1600):
<pre>aticonfig --set-powerstate=1</pre>

To find out which powerstates your Radeon supports try:
<pre>aticonfig --lsp</pre>

=== System freezes after logout with GDM or KDM<ref>http://ati.cchtml.com/show_bug.cgi?id=239 Going back to gdm/kdm hardlocks after running X session</ref> ===

If you use GDM, which is the default Login Manager on Ubuntu, modify
<pre>sudo gedit /etc/gdm/gdm.conf</pre>

{{Box File|/etc/gdm/gdm.conf|
<nowiki>AlwaysRestartServer=true</nowiki>
}}

If you use KDM, which is the default Login Manager on Kubuntu, add to the [X-:*-Core] section the following

<pre>sudo kate /etc/kde3/kdm/kdmrc</pre>

{{Box File|/etc/kde3/kdm/kdmrc|
<nowiki>TerminateServer=true</nowiki>
}}

=== System freezes at startup of Fedora 7 after installing the driver ===

Turn of the Redhat Graphical boot from grub config:

Edit the grub config file located at /boot/grub/grub.conf and remove the 'rhgb' from the kernel line in order to disable the Redhat Graphical boot.

=== System lockup on logout with catalyst 8.01 <ref>http://www.phoronix.com/forums/showthread.php?t=7448&page=5 System lockup on logout with catalyst 8.01</ref>===
To solve this issue you need to disable atieventsd. On ubuntu you can run:
<pre>
sudo /usr/sbin/update-rc.d -f atieventsd remove
</pre>

==References==
<references/>

[[Category:Installation Documentation]]

[[Category:NeedsUpdating]]
{{VCT}}

Gentoo Installation Guide

2008-02-13T10:38:02Z

200.29.96.75: eltbodar

monolopa
Orginally found on the [http://gentoo-wiki.com/HOWTO_ATI_Drivers Gentoo Wiki], the GNU Free Documentation license allows me to copy/paste it here.

== Introduction ==

This guide should help you install and configure the proprietary graphics drivers from ATI. This guide applies for ALL versions of fglrx - it was made before the (rather dramatic) 8.8.25 January 05 release, but it is maintained such that all versions should work.

*Note: If you are using an ATI 7500 Mobility (or such card that isn't supported by the ati-drivers) this HOWTO will not help. Instead use the ATI kernel drivers. See also: http://forums.gentoo.org/viewtopic-p-2137276.html#2137276

== Kernel Configuration ==

Get into menuconfig (cd /usr/src/your-kernel && make menuconfig) and check the following:
{{Box Code|menuconfig|<pre>
Loadable Module Support --->
[*] Enable loadable module support
[*] Module unloading

Processor type and features --->
[*] Enable VM86 support
[*] MTRR (Memory Type Range Register) support

Device Drivers --->
Character Devices --->
<M> /dev/agpgart (AGP Support)
<M> Your_AGP_Chipset_Here
[ ] Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)

Graphics support --->
[ ] Support for framebuffer devices

Kernel Hacking --->
[ ] Kernel debugging
</pre>
}}
Sync your kernel menuconfig with the selected portions posted here. (note: you can compile /dev/agpgart & your agp chipset [most likely ati-agp] into the kernel if you want.)

'''Please be aware that -mm and -rc(1,2,3,4,...) kernels often break fglrx due to unexpected changes in syntax, etc. If you want to use ati-drivers, use the stock gentoo-sources or at the very least, a STABLE 2.4 or 2.6 kernel!'''

Don't forget to compile, install, and reboot into the kernel. Directions for this are beyond the scope of this file; if you need help recompiling the kernel, [http://gentoo-wiki.com/HOWTO_Compile_a_Kernel_Manually click here].

== Grabbing a Driver Set ==

For installation it will be easier to drop out of X to a command prompt. Do this using whatever command your Window Manager uses.
I use fluxbox so it's just rightclick -> fluxbox menu -> exit. For KDE or GNOME it's probably just a matter of logging out. When all else fails, hit CTL+ALT+BACKSPACE to kill the X server ungracefully. If the X server only reboots or for some reason you've disabled this hotkey, log in as root and type '''init 3''' to bring the system run level down.

There is also the possibility to stop the xdm service by entering ''/etc/init.d/xdm stop'' as root.

Thanks to portage, installing the drivers is easy. If you have not already done it recently, start by synchronising your portage tree:

emerge --sync

Getting the latest drivers will probably mean unmasking them.

echo "x11-drivers/ati-drivers ~arch" >> /etc/portage/package.keywords
echo "x11-drivers/ati-drivers-extra ~arch" >> /etc/portage/package.keywords

Replace {{Codeline|<~arch>}} with your system architecture; it's going to be either {{Codeline|~x86}} or {{Codeline|~amd64}}, the only two CPU architectures supported by the ATI driver.

Now let's install the drivers. ati-drivers-extra is a (god-awful) control panel for the driver you probably won't use; you can leave that part out if you want, but for completeness we mention it here.

su -
emerge -av ati-drivers ati-drivers-extra

The next step is switch to the ATi OpenGL subsytem:

(#opengl-update ati)
eselect opengl set ati
(very important!)(opengl-update is deprecated)
Configure X:
First, make a standard config file.

xorgconfig

For a single screen

aticonfig --initial --input=/etc/X11/xorg.conf

For a dual head, second screen is {left|right|above|below}

aticonfig --initial=dual-head --input=/etc/X11/xorg.conf --screen-layout={left|right|above|below}

Adapt input with your path to xorg's conf file

If for some reason this command doesn't work, then try manually executing from its default location:

/opt/ati/bin/aticonfig [...]

Now, let's get back into X.

startx

Open up a command prompt and run:

fglrxinfo

If the OpenGL vendor string says "ATI Technologies," then congrats! You've got the drivers working and hardware acceleration going great. If not...read on...

== Troubleshooting ==

=== Config Files ===
By default, the driver uses the Internal AGPGART. Sometimes the internal one doesn't work, and you will have to use the one provided with the kernel. Search your xorg.conf for the line that has the option "UseInternalAGPGART." Simply change the "yes" to "no."

{{Box File|xorg.conf|
Option "UseInternalAGPGART" "no"
}}

Now simply add the modules to {{Filename|/etc/modules.autoload.d/kernel-2.x}} where x is your kernel version.

Add the following (ORDER IS VERY IMPORTANT);
{{Box File|/etc/modules.autoload.d/kernel-2.x|
agpgart
intel-agp # change intel-agp to your chipset. eg: via-agp, nvidia-agp sis-agp.
fglrx
}}

Finally, run

modules-update

Then you can reboot and everything should work. If you have are having problems, check dmesg and /var/log/Xorg.0.log for more info.

=== Blank screen or monitor turning off after startx ===

Versions of ati-drivers >= 8.16.20 have an issue with this that's easily corrected by inserting:
{{Box File|xorg.conf|
Option "ForceMonitors" "notv"
}}
in the device section of xorg.conf (discussed here: http://bugs.gentoo.org/show_bug.cgi?id=103028)

Check if you have a non-DDC monitor connected via VGA/HD15 connector. If so change your xorg.conf:
{{Box File|xorg.conf|
# Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "NONE, CRT"
Option "IgnoreEDID" "off"
Option "HSync2" "30-85"
Option "VRefresh2" "50-160"
# Option "ScreenOverlap" "0"
}}
where HSync2 and VRefresh2 are your monitor parameters.

Also, try changing the MonitorLayout option. The default is "AUTO, AUTO", which is to say X will attempt to autodetect what kind of monitor you've got on the first and second display heads. This can theoretically fail (though I have never observed it). Try changing it around a bit. For example, if you have an LCD and no secondary monitor, change the line to read:

{{Box File|xorg.conf|
Option "MonitorLayout" "TMDS, NONE"
}}

if you have a CRT, simply replace "TMDS" with "CRT".

=== Crashes on startup ===
'''If you are unable to use any 3d applications and get this error instead:'''

FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!

'''Then you do not have tmpfs mounted on /dev/shm, which the driver requires.''' Make yourself sure you have tmpfs support compiled into kernel. It's under

File systems -->
Pseudo filesystems -->
[*] Virtual memory file system support (former shm fs)

To mount this, add to following line to {{filename|/etc/fstab}} (if it isn't there already):

{{Box File|/etc/fstab|
tmpfs /dev/shm tmpfs defaults 0 0
}}

Then just do a:
mount /dev/shm

If the drivers still crap out on you, or for example you get a black screen on X init, try going into your system BIOS and change graphics-related stuff around. Believe it or not, for me my 9800 gives a black screen on X init if I have the AGP Aperture set at anything other than 128MB. I don't know what causes this, and I don't care; I'm just relating to you how I overcame ''my'' problem ;)

Also, '''whenever you update your compiler''', you '''must''' recompile your kernel otherwise you won't be able to insert the fglrx module. Note that recompiling your kernel means you must also unmerge/emerge ati-drivers!

=== Duplicate symbol errors in X log ===
If you are unable to start X or X fails to load the fglrx driver and you have multiple symbol errors in your Xorg log, chances are that you have compiled X with the ''dlloader'' flag. This flag can not be used with the fglrx driver. To fix this problem, remove the dlloader flag by editing your /etc/portage/package.use file as follows:
{{Box File|/etc/portage/package.use|
x11-base/xorg-x11 -dlloader
}}
Now re-emerge the ''xorg-x11'' package and reinstall the fglrx driver.

=== Crashes on the exit of X.org / X won't shutdown ===
Perform the following if you can get the fglrx drivers working with hardware acceleration, but are suffering from a complete system crash when trying to quit X. You should boot into your system, login, then start on this. You don't need to boot into X, and shouldn't need to edit your xorg.conf file (as fglrx is already setup as the driver and working)

You've emerged the "stable" version of the ati-drivers, these are out of date -- remove them (emerge --unmerge ati-drivers), to add the most recent you should either add them to the keywords file (/etc/portage/package.keywords) or emerge your local ebuild (emerge /usr/portage/x11-drivers/ati-drivers/ati-drivers-8.22.5.ebuild) if you're told it requires a dependency, emerge the local e-build for that, then try again. (usually eselect-opengl is required.)
Once you have the most recent ati-drivers emerged, run (eselect opengl set ati). Now you can (startx) and hopefully quit without any problems.

=== glxinfo says "error: failed to open DRM: Operation not permitted" ===
If a check with the glxinfo fails for ordinary users though works fine for root it might be related to filepermissions of the device-file.
Here is how to solve it:

Make sure that the filepermissions on the card-device allows the video-group to read and write. The common group in gentoo with X is "video". All normal users should be part of this group. Also, the device must have permissions for this group to read and write the card-device.

Check the permissions on the card-device:

root:/#ls -lcF /dev/dri/card0

crw-rw---- 1 root root 226, 0 Oct 5 16:19 /dev/dri/card0

It can be changed with:

root:/dev/dri#chgrp video card0

Check if user is part of video:

paddlaren:~>id paddlaren

uid=1000(paddlaren) gid=1000(paddlaren)

groups=1000(paddlaren),10(wheel),11(floppy),18(audio),19(cdrom),80(cdrw),85(usb),100(users),35(games)

To add a user to the video-group:

root:~#gpasswd -a my_user video

paddlaren:~>id paddlaren

uid=1000(paddlaren) gid=1000(paddlaren)

groups=1000(paddlaren),10(wheel),11(floppy),18(audio),19(cdrom),27(video),80(cdrw),85(usb),100(users),35(games)

Logoff and on to ensure that the membership of the group is known to the system.

== See Also ==

*[http://ati.cchtml.com/ ATi Unofficial Bugzilla (occasionally monitored by ATi personnel)]
*Check out user Wedge_'s excellent ATI Radeon [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html FAQ here]

[[Category:Installation Documentation]]

Ubuntu Installation Guide

2008-02-13T10:37:56Z

200.29.96.75: getliacelor

rollibobo
*[[Ubuntu_Breezy_Installation_Guide|Breezy (5.10) Installation Guide]]
*[[Ubuntu_Dapper_Installation_Guide|Dapper (6.06) Installation Guide]]
*[[Ubuntu_Edgy_Installation_Guide|Edgy (6.10) Installation Guide]]
*[[Ubuntu_Feisty_Installation_Guide|Feisty (7.04) Installation Guide]]
*[[Ubuntu_Gutsy_Installation_Guide|Gutsy (7.10) Installation Guide]]

[[Category:Installation Documentation|Ubuntu]]

Fedora Core 5 Installation Guide

2008-02-13T10:37:45Z

200.29.96.75: ladombob

cozelt
*Note: You must have your "kernel-devel-[version]" RPM package installed prior to fglrx installation.
*Note: The administrator of this wiki uses FC5 on a Radeon 9700 with the latest driver without any issues using the Official ATI Binary Installer.
Red Hat's developers [http://www.redhat.com/archives/rhl-devel-list/2006-February/msg01178.html comments on 3rd party installers].

==livna.org package==
#Enable the livna repository
#Install the drivers and kernel module

<code>rpm -ivh http://rpm.livna.org/livna-release-5.rpm</code>
<code>yum install kmod-fglrx</code>

Notes:
* For ease of installation and updating, the package name of the driver has been changed
* As of today (2006-04-08) livna is still working out install bugs ( [http://bugzilla.livna.org/show_bug.cgi?id=842 Bugtracker] ) in the X86_64 package. It apperas they have fixed the problem, but have not yet finished testing. Some people report mixed success compiling from the source RPMS. YMMV.
* As of today (2006-06-14) tried several times to install the driver for ATI RADEON X700. It installed but not working. Still stuck at vesa. Those who are trying this method, be warned.

==Official ATI Binary installer==
===Pre-installation===
Update your kernel, kernel-devel, and xorg packages to the very latest before installation.
===Installation===
#Download the latest [[:Category:Releases|release]].
#su to root in init level 3 (No X server running)
# sh ati-driver-installer-[version].run
#Follow the prompts and it will install.

===Post-Installation===
#Run the <code>aticonfig --initial</code> command if you have not updated your X.org configuration file (xorg.conf).
#Change back to run level 5. <code> init 5</code>

==RPM installer==
No longer supported as Fedora Core 5 is shipping with X.org version 7.0.

[[Category:Installation Documentation]]

Fedora Core 6 Installation Guide

2008-02-13T10:37:39Z

200.29.96.75: varorrelca

coletodar
==Official ATI Factory Installer==
* To do the following, you must have the following software installed:
#kernel-devel
#qt-devel
#rpmdevtools.noarch
#redhat-rpm-config.noarch
#compat-libstdc++-33

* The ATI installer is theoretically capable of creating FC6 RPMs. To see a compete list of installer options, do
# sh ati-driver-installer-<your_version>.run --help
* To see a list of all distributions you can generate packages for, do
# sh ati-driver-installer-<your_version>.run --list
* To create a set of FC6 RPM's with the (current) ATI factory installer, usually you would do the following:
# sh ati-driver-installer-8.34.8-x86.x86_64.run --buildpkg Fedora/FC6

Normally this would work, but the current version of the ATI Factory installer (8.34.8) is broken and will not complete generation of FC6 rpm's. In fact the ATI Factory installer has been broken since at least 8.29. When RPM generation is invoked, it produces the following error:

"install: cannot stat `fireglcontrolpanel': No such file or directory"

and exits. The problem seems to be related to the qt-devel or the version of qt installed. There is a hack to work around this problem; it involves editing the scripts packaged with the installer. The hack is on Phoronix Forums.<ref>http://www.phoronix.net/forums/showthread.php?t=318</ref>

It's all about deleting fireglcontrolpanel completely out of the rpm generation entirely. Basically you won't have fireglcontrolpanel installed after you generate and install the rpm's, but everything else should work.

* When you do manage to get the drivers installed, remember to put this at the end of your xorg.conf file:

Section "Extensions"
Option "Composite" "Disable"
EndSection

'''If this is not done then Mesa will load instead of ATI DRI.'''

== Livna rpm ==

If your /var/log/Xorg.0.log does not say anything useful and fglrxinfo shows only Mesa and everything else seems OK then add directory /usr/lib/ati-fglrx to library path:
* Create /etc/ld.so.conf.d/fglrx.conf and add /usr/lib/fglrx row there.
* run ldconfig
* restart X

==References==
<references/>

{{VCT}}
[[Category:Installation Documentation]]

Fedora 7 Installation Guide

2008-02-13T10:37:28Z

200.29.96.75: acgetdom

roerletool
Installation on Fedora 7 is easy: Download the latest fglrx driver, apply it an executable permission, and run it.
There are basically 2 options:
1: Install the driver
2: Generate distribution specific package

Choice one installs the driver and second choice generates rpm according to your system and puts them in working directory

--------

After the newest ATI catalyst release (8.39.4), fglrx module can be installed on new Xorg (7.2). Unfortunately, the previous ATI driver (8.37.6), nor the latter one (8.38.6), or even the hotfix (8.38.7) were compatible with the X server in the Fedora 7 distribution.

As pointed out at Phoronix.com, the latest release (8.39.4) has very little changes and completely ignored Fedora 7 users who have waited over a month for a functional driver.

"The AMD 8.38.6 display driver had introduced Red Hat Enterprise Linux 5 packaging support along with fixing a few bugs, but the driver was one of the least interesting releases in recent times."
http://www.phoronix.com/scan.php?page=article&item=764&num=1

Given that this release focuses on packaging support, ATI are still prioritizing cosmetic changes over functional aspects. Whilst packages are a 'nice to have', basic functionality is far more critical.

[[Category:Installation Documentation]]

Ubuntu Edgy Installation Guide

2008-02-13T10:37:23Z

200.29.96.75: drongetolo

dompasva
The [[:Category:Releases|latest]] fglrx driver supports the Radeon 9700 up to the HD series cards.

==Pre-Installation Checks==
=== Enable "restricted" Repository ===
To do this in GNOME, go to your System Menu > Administration > Software Sources. Place a check next to "Proprietary drivers for devices (restricted)," click Close, click Reload, and let the application update the package list.

To do this in XFCE, go to your Applications > System > Software Sources. Place a check next to "Proprietary drivers for devices (restricted)," click Close, click Reload, and let the application update the package list.

If you use KDE, go to K > System > Adept Manager Manage Packages. Enter your password. Go to Adept > Manage Repositories. Right Click everything that starts with deb or deb-src and select enable. Select fetch updates and you are good to go!

=== Disable Composite Extension ===
In Ubuntu Edgy the Composite extension is enabled by default, however, ''fglrx'' does not yet support Composite with DRI. In order to disable Composite you have to edit the ''xorg.conf'' file:
<pre>sudo gedit /etc/X11/xorg.conf</pre>
and add these lines at the end of the file:
{{Box File|/etc/X11/xorg.conf|
<pre>Section "Extensions"
Option "Composite" "Disable"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection</pre>
}}
*Note: Xubuntu does not have gedit. The default text editor in Xubuntu is called mousepad.
*Note: Kubuntu does not have gedit. The default text editor in Kubuntu is called kate.
*Another option is to use nano (or vim).

== Installation ==
===Method 1: Install the 8.34.8 Driver the Ubuntu Way===

<pre>
sudo apt-get update
sudo apt-get install linux-restricted-modules-$(uname -r) #Okay if it is already installed
sudo apt-get install xorg-driver-fglrx
</pre>
Continue to "Configure the Driver" below.

===Method 2: Install the 8.38.6 Driver Manually===
*Note: ''This is just an alternative installation method for the section above. It might help if you still get 'DRI missing' errors.''

Download the ATI driver installer: [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.38.6-x86.x86_64.run ati-driver-installer-8.38.6-x86.x86_64.run](this installer is for 32bit '''and''' 64bit systems), taking care of which version needs for your [[Hardware|device]].

Change to the download directory. Make sure that you have the [http://www.ubuntux.org/node/71 ''universe'' and ''multiverse'' repositories] enabled in ''/etc/apt/sources.list'' before doing these steps.

''Install necessary tools:''
<pre>
sudo apt-get update
sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5 linux-headers-$(uname -r)
</pre>

''Create .deb packages:''
<pre>
bash ati-driver-installer-8.38.6-x86.x86_64.run --buildpkg Ubuntu/edgy
</pre>

''Blacklist old fglrx module from linux-restricted-modules:''

*Note: You only need to do this if you've installed the driver from Method 1 above.

As ubuntu's ''linux-restricted-modules'' package includes the fglrx module from an old driver version (8.28.8), we have to blacklist this module to make sure the new kernel module which is needed by the new driver will be used instead.

<pre>sudo gedit /etc/default/linux-restricted-modules-common</pre>
Add "fglrx" to the line "DISABLED_MODULES"
{{Box File|/etc/default/linux-restricted-modules-common|
<pre>DISABLED_MODULES="fglrx"</pre>
}}

''Install .deb packages:''
<pre>
sudo dpkg -i xorg-driver-fglrx_8.38.6-1*.deb
sudo dpkg -i fglrx-kernel-source_8.38.6-1*.deb
sudo dpkg -i fglrx-amdcccle_8.38.6-1*.deb
</pre>

''Remove any old fglrx debs from /usr/src/:''
<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Fix broken dependencies''
*Note: ''You only need to do this if you have installed previous versions of these drivers using this method before.''
<pre>
sudo apt-get -f install
</pre>

''Compile the kernel module:''
<pre>
sudo module-assistant prepare
sudo module-assistant update
sudo module-assistant build fglrx
sudo module-assistant install fglrx
sudo depmod -ae
</pre>

'''IMPORTANT''': You have to recompile the kernel module after each kernel update!
''NOTE'': the new ATI driver (8.36.5) now support kernel 2.6.20!

===Configure the Driver===
<pre>
sudo aticonfig --initial
</pre>
*Note: An '''alternative''' to the '''aticonfig --initial''' command is to edit ''/etc/X11/xorg.conf'' and replace the string "ati" with "fglrx" in the "Device" section. This way you won't lose your old "Screen" and "Monitor" settings. Afterwards you can use aticonfig for setting overlay etc.
<pre>
sudo aticonfig --overlay-type=Xv
</pre>

===Finish the Installation===
Now save any open document and reboot your system:
<pre>
sudo shutdown -r now
</pre>
*Note: An '''alternative''' to rebooting is to restart the X Server by pressing your CTRL+ALT+BACKSPACE keys. If you do not reboot, you must remove any old kernel modules such as "drm" "radeon" or "fglrx" using the "rmmod" command. Example: <code>rmmod fglrx</code> ''If this sounds difficult, or you don't know which modules are "Modules such as..." then stick to rebooting ;)''

== Post-Installation Checks ==
===Verifying===
Run the following command to check its output to ensure the fglrx driver is installed properly:
<pre>
fglrxinfo

display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700
OpenGL version string: 2.0.6400 (8.35.5)
</pre>
If you do not see ATI as your vendor, then there are ways to [[Troubleshooting|troubleshoot installation]].

=== Additional configure with aticonfig tool ===
You can even more configure the driver with the '''aticonfig''' tool, more information can be found at [[Configuring]].

For example: 
* use powerplay option to switch power state for battery friendly or performance mode
* use dual head or one big desktop mode
* turn second monitor on/off on the fly

==Ubuntu-specific Issues==

=== Revert to Xorg driver ===

If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing
<pre>sudo dpkg-reconfigure xserver-xorg</pre>
and selecting the "ati" driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup.

You also need to remove the xorg-driver-fglrx or your manually installed drivers to get the 3D acceleration back, since it is provided by file /usr/lib/libGL.so.1.2 which belongs to libgl1-mesa package and which is moved to backup and replaced at the installation of xorg-driver-fglrx (or the manually built) package. In case the removal of the fglrx drivers fails to restore the file from libgl1-mesa, you have to reinstall the package by running:

<pre>sudo apt-get install --reinstall libgl1-mesa</pre>

=== If suspend and hibernate not working ===

If after fglrx installation suspend and hibernate stop working. I mean it suspends and hibernates but does not start and just gives black screen. Then put POST_VIDEO to false:
{{Box File|/etc/default/acpi-support|
<pre># Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false</pre>
}}

or try this other (works for X700 and X1100):

{{Box File|/etc/default/acpi-support|
<pre># Should we attempt to warm-boot the video hardware on resume?
SAVE_VBE_STATE=false
POST_VIDEO=true
USE_DPMS=false</pre>
}}

==See Also==
*[[Frequently Asked Questions]]
*[[Performance Issues]]

=== Permalinks to guides for older driver versions ===

* [http://wiki.cchtml.com/index.php?title=Ubuntu_Edgy_Installation_Guide&oldid=3402 Ubuntu Edgy Installation Guide of driver v8.33.6]
* [http://wiki.cchtml.com/index.php?title=Ubuntu_Edgy_Installation_Guide&oldid=3541 Ubuntu Edgy Installation Guide of driver v8.34.8]

{{VCT}}
[[Category:Installation Documentation]]

Ubuntu Breezy Installation Guide

2008-02-13T10:37:17Z

200.29.96.75: cobasnochita

eltactrocmo
== Method 1: Installing Breezy's Included Driver (8.16.20) ==

The fglrx driver supports Radeon 8500+ and the X-series cards (see [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_8.16.20.html#173867 release notes]). When running the dpkg-reconfigure commands you can accept the defaults whenever you aren't sure.

=== Installing the driver ===

''All Platforms:''
<pre>
sudo apt-get install xorg-driver-fglrx
sudo apt-get install linux-restricted-modules-$(uname -r) #Okay if it is already installed
sudo dpkg-reconfigure xserver-xorg #Select the fglrx driver and 64-bit users should deselect int10a
</pre>

''64-bit users:''

You have to downgrade to an older version of libdri.a due to an incompatilbity with the ATI drivers. [http://ati.cchtml.com/attachment.cgi?id=182 Download it here]

Change to download directory:
<pre>
gunzip libdri.a.gz
sudo cp /usr/X11R6/lib/modules/extensions/libdri.a libdri.a.old
sudo cp libdri.a /usr/X11R6/lib/modules/extensions/
</pre>

If you wish to revert to any non-fglrx driver you will need to copy the libdri.a.old file back over the fglrx version.

''All platforms:'' Ctrl-Alt-Backspace to restart your desktop.

=== Confirm that it works ===
<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)
</pre>

=== Troubleshooting ===

If you have a widescreen LCD display that is stuck at 1024x768 then it is probably the bug in the 8.16.20 driver that was fixed in 8.18.X (see the next section).

The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors.

== Method 2: Generating/Installing Ubuntu packages for the newer 8.28.8 drivers in Breezy Badger ==

'''Important Warning:''' Installation of this driver requires removing the restricted-modules package in order to work. That package includes drivers for madwifi (Atheros wireless cards), nvidia cards, and a handful of other devices. I provide a work-around for the madwifi drivers, but you need to perform it before removing the restricted modules (jump to end of this this post).

When running the dpkg-reconfigure command you should answer the questions that you know and take the defaults for the rest. You might want to say ''no'' to the monitor detection--it has caused X-Windows to crash for some people.

=== Remove existing fglrx driver ===

Remove Breezy's included drivers if they are installed:

<pre>
sudo apt-get remove xorg-driver-fglrx
sudo apt-get remove fglrx-control
sudo apt-get remove linux-restricted-modules-$(uname -r)
sudo dpkg-reconfigure xserver-xorg #select the "ati" module
</pre>

Reboot.

*Note 1: If after reboot, your system hangs at a black screen before taking you to a graphical login - reboot to 'recovery mode' and edit /etc/X11/xorg.conf to use 'vesa' instead of 'ati'. Then continue with the steps below.

*Note 2: You can change your xorg.conf file to Option "vesa" BEFORE rebooting, so after rebooting you can have usable X (and skip Note 1). Remember that you HAVE to reboot (just restarting X will leave you with unusable X).

=== Installing the new driver ===

Download the ATI driver installer: [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.28.8.run ati-driver-installer-8.28.8.run] (this installer is for 32bit '''and''' 64bit systems)

This guide refers to the 32bit version of the driver. The installation procedure for 64bit should be the same as for 32bit, except some filenames will differ slightly.

Change to the download directory. Make sure that you have the ''universe'' and ''multiverse'' repositories enabled in ''/etc/apt/sources.list'' before doing these steps. [http://mail3.mpr.org/mlomker/sources.list Sample sources.list].

''Install necessary tools:''

<pre>
sudo apt-get install gcc-3.4 module-assistant build-essential fakeroot dh-make debconf libstdc++5 gcc-3.3-base
</pre>

''Create .deb packages:''

<pre>
bash ati-driver-installer-8.28.8.run --buildpkg Ubuntu/breezy
</pre>

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.28.8-1_i386.deb
sudo dpkg -i fglrx-kernel-source_8.28.8-1_i386.deb
sudo dpkg -i fglrx-control_8.28.8-1_i386.deb
</pre>

''Remove any old fglrx deb's from /usr/src/:''

<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Compile the kernel driver:''

<pre>
sudo module-assistant prepare
sudo module-assistant update
sudo module-assistant a-i fglrx
</pre>

''Update the xorg.conf file:''

<pre>
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv
</pre>

Reboot.

=== Confirm that it worked ===

<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9700 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

(''renderer string'' depends on your hardware and may/will be different)

=== Troubleshooting ===

==== General ====

Look for error messages in /var/log/Xorg.0.log and kern.log.
If you receive the '''(EE) No devices detected''' error message, it is highly possible that you own a Radeon from the 7000-7500 series with the R100 chip, which the proprietary Linux drivers don't support.

==== Madwifi Drivers in Breezy Badger ====
In order to continue using the [http://madwifi.org madwifi] driver you can do the following '''before''' removing the linux-restricted-modules package and rebooting.
<pre>
sudo cp /lib/modules/$(uname -r)/volatile/ath_hal.ko /lib/modules/$(uname -r)/kernel/
sudo depmod -a $(uname -r)
</pre>

[[Category:Installation Documentation]]

Ubuntu Feisty Installation Guide

2008-02-13T10:36:47Z

200.29.96.75: ladelbota

boeltdron
The [[:Category:Releases|latest]] fglrx driver supports Radeon 9500 and the X-series cards up to HD2900. Workstation cards are not supported.

==Pre-Installation Checks==
===Video Card Support===
{| border="1" cellspacing="0" cellpadding="3"
!|Card Class
!|Supported (8.42.3)
!|Supported (7.12)
|-
|Radeon Consumer Cards 9500 to 9800
|Yes
|
|-
|Radeon Consumer Cards X300 to X1950
|Yes
|
|-
|Radeon Consumer Cards HD 2400 to HD 2900
|Yes
|
|-
|FireGL Workstation Cards
|No
|Yes
|}

=== Enable "restricted" Repository ===
Make sure the ''restricted'' repository is enabled in ''/etc/apt/sources.list'' or this guide will not work!

System > Administration > Software Sources. Check "Proprietary Drivers for Devices (Restricted)" box.

=== Disable Composite Extension ===
In Ubuntu Feisty the Composite extension is enabled by default, however, ''fglrx'' does not yet support Composite with DRI. In order to disable Composite you have to edit the ''xorg.conf'' file:
<pre>gksu gedit /etc/X11/xorg.conf</pre>
and add these lines at the end of the file:

{{Box File|/etc/X11/xorg.conf|
<pre>Section "Extensions"
Option "Composite" "Disable"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection</pre>
}}

*Note: Xubuntu does not have gedit. The default text editor in Xubuntu is called mousepad.
<pre>gksu mousepad /etc/X11/xorg.conf</pre>
*Note: Kubuntu does not have gedit. The default text editor in Kubuntu is called Kate.
<pre>kdesu kate /etc/X11/xorg.conf</pre>
Another option is to use nano directly from the terminal.
<pre>sudo nano /etc/X11/xorg.conf</pre>

== Installation ==

===Method 1: Install the Driver the Ubuntu Way===
<pre>
sudo apt-get update
sudo apt-get install linux-restricted-modules-generic restricted-manager
sudo apt-get install xorg-driver-fglrx
sudo depmod -a
</pre>

Note: The second line of the above may not be necessary. If apt says it cannot find the "linux-restricted-modules" package, try line 3. If that fails, check your sources.list (see top of page)

If the system complains about dependencies, use your preferred package manager to download python2.4 and, if necessary, its dependencies.

===Method 2: Install the 8.42.3 Driver Manually===

*Note: ''This is just an alternative installation method for the section above. It might help if you still get 'DRI missing' errors.''

Download the ATI driver installer:
[https://www2.ati.com/drivers/linux/ati-driver-installer-8.42.3-x86.x86_64.run ati-driver-installer-8.42.3-x86.x86_64.run] (this installer is for 32bit '''and''' 64bit systems)

Change to the download directory. Make sure that you have the ''universe'' and ''multiverse'' repositories enabled in ''/etc/apt/sources.list'' before doing these steps.

There is a detailed manual with screenshots at [https://wiki.ubuntu.com/AddingRepositoriesHowto Ubuntu Wiki].

By default, Ubuntu does not enable the Universe and Multiverse repositories. But they include some important programs and codecs, so it is highly recommended to activate them.

''Install necessary tools:''
<pre>
sudo apt-get update
sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper \
debconf libstdc++5 linux-headers-generic
</pre>

''Create .deb packages:''
<pre>
sudo bash ati-driver-installer-8.42.3-x86.x86_64.run --buildpkg Ubuntu/feisty
</pre>

''Blacklist old fglrx module from linux-restricted-modules:''

*Note: You only need to do this if you've installed the driver from Method 2 above.

As ubuntu's ''linux-restricted-modules'' package includes the fglrx module from an old driver version (8.28.8), we have to blacklist this module to make sure the new kernel module which is needed by the new driver will be used instead.

Ubuntu/Gnome users type in:
<pre>gksu gedit /etc/default/linux-restricted-modules-common</pre>

Kubuntu/KDE users type in:
<pre>kdesu kate /etc/default/linux-restricted-modules-common</pre>

Add "fglrx" to the line "DISABLED_MODULES"
{{Box File|/etc/default/linux-restricted-modules-common|
<pre>DISABLED_MODULES="fglrx"</pre>
}}

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.42.3-1*.deb \
fglrx-kernel-source_8.42.3-1*.deb \
fglrx-amdcccle_8.42.3-1*.deb
</pre>

*Note: If you have a 64 bit install, the above dpkg command will likely complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you recieve this error, issue the following command after the above dpkg command, which will force the installation of all of the 32 bit dependencies, and then the amdccle pacakge:

<pre>
sudo apt-get install -f
</pre>

''Remove any old fglrx debs from /usr/src/:''
<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Fix broken dependencies''
*Note: ''You only need to do this if you have installed previous versions of these drivers using this method before.''
<pre>
sudo apt-get -f install
</pre>

''Compile the kernel module:''
*Note: ''Since Catalyst 7.12, this step is not needed anymore, because the fglrx-kernel-source package compiles and installs the module.''
<pre>
sudo module-assistant prepare
sudo module-assistant update
sudo module-assistant build fglrx
sudo module-assistant install fglrx
sudo depmod -a
</pre>

It's necessary, because sometimes this file is written by other packages, and so there's no 3D acceleration.

''Create the following folder''

<pre>
sudo mkdir /lib/modules/$(uname -r)/volatile
</pre>

''Create a symbolic link''

<pre>
sudo ln -s /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko
</pre>

'''IMPORTANT''': You have to recompile the kernel module after each kernel update!

===Configure the Driver===
*Note Method 2 Users: Before you carry out this step you must reboot your machine. Or else the fglrx driver will not be in use on xorg.conf and using the aticonfig options will cause a memory dump and not intialise the Driver properly.
*Note: An '''alternative''' to the '''aticonfig --initial''' command is to edit ''/etc/X11/xorg.conf'' and replace the string "ati" with "fglrx" in the "Device" section. This way you won't lose your old "Screen" and "Monitor" settings. Afterwards you can use aticonfig for setting overlay etc. Another alternative is '''aticonfig --initial --force''' if you encounter issues with the first command.
<pre>
sudo aticonfig --initial
</pre>
Then:
<pre>
sudo aticonfig --overlay-type=Xv
</pre>
*Note: Is there an alternative to the previous step?

===Finish the Installation===
Now save any open document and reboot your system:
<pre>
sudo shutdown -r now
</pre>
*Note: An '''alternative''' to rebooting is to restart the X Server by pressing your CTRL ALT BACKSPACE keys. You must remove any old kernel modules such as "drm" "radeon" or "fglrx" using the "rmmod" command. Example: <code>sudo rmmod fglrx</code>

== Post-Installation Checks ==
===Verifying===
Run the following command to check its output to ensure the fglrx driver is installed properly:
<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY RADEON 9600/9700 Series
OpenGL version string: 2.0.6650 (8.40.4)
</pre>
The <code>OpenGL vendor string</code> should read '''ATI''' and not '''Mesa'''.

If you see a message like 'Xlib: extension "XFree86-DRI" missing on display ":1.0"' then you may have to add the following to /etc/X11/xorg.conf (see [http://ubuntuforums.org/showthread.php?t=292642#post1714920]):
{{Box File|/etc/X11/xorg.conf|
<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>
}}

=== Additional configure with aticonfig tool ===
You can even more configure the driver with the '''aticonfig''' tool, more information can be found at [[Configuring]].

For example: 
* use powerplay option to switch power state for battery friendly or performance mode
* use dual head or one big desktop mode
* turn second monitor on/off on the fly

==Ubuntu-specific Issues==

=== Revert to Xorg driver ===

If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing
<pre>sudo dpkg-reconfigure xserver-xorg</pre>
and selecting the "ati" driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup.

You also need to remove the xorg-driver-fglrx or your manually installed drivers to get the 3D acceleration back, since it is provided by file /usr/lib/libGL.so.1.2 which belongs to libgl1-mesa package and which is moved to backup and replaced at the installation of xorg-driver-fglrx (or the manually built) package. In case the removal of the fglrx drivers fails to restore the file from libgl1-mesa, you have to reinstall the package by running:

<pre>sudo apt-get install --reinstall libgl1-mesa</pre>

=== If suspend is not working ===

If suspend stops working after fglrx installation, meaning display will not initialize after attempting to resume, then changing a few options has been reported to work for some hardware. 

For ATI X700 and ATI X1100 on Acer Aspire 5051:
{{Box File|/etc/default/acpi-support|
<pre>
SAVE_VBE_STATE=false
POST_VIDEO=true
USE_DPMS=false
</pre>
}}

For ATI X1300 and the ATI X1400 on a Dell Inspiron 9400 or Lenovo Thinkpad T60, also for ATI X1600 on Asus Z96J (using install method 2):
{{Box File|/etc/default/acpi-support|
<pre>
POST_VIDEO=false
</pre>
}}

==See Also==
*[[Frequently Asked Questions]]
*[[Performance Issues]]
*[[Troubleshooting]]
*[http://www.petitiononline.com/x200MLin/petition.html Petition for better ATI/AMD Radeon XPRESS 200M Linux Drivers]
* [http://ubuntuforums.org/showpost.php?p=2221323

[[Category:Installation Documentation]]

Category:Installation Documentation

2008-02-13T10:36:41Z

200.29.96.75: catrletocava

riccoalricge
Documentation to install the ATi Linux driver under the different distributions of GNU/Linux.