cchtml.com - User contributions [en]

Frequently Asked Questions

2007-10-16T11:21:49Z

74.231.24.2:

acelouervid
==Installation==
===How do I know fglrx is installed correctly?===
There are several ways to check if fglrx is loaded and running.
 1. Check your X.org or XFree86 log. You should see "DRI Initialization Successful."
# less /var/log/Xorg.0.log
or
# less /var/log/XFree86.0.log
2. Check glxinfo. You should see "direct" and not "indirect."
# glxinfo | grep direct
3. Check your kernel log. You should see fglrx messages near the bottom.
# dmesg
4. Check your modules. You should see fglrx loaded.
# lsmod | grep fglrx
*NOTE: [[Glxgears is not a Benchmark|glxgears]] is not a definite way of checking the installation of fglrx.

=== Is the rebooting really necessary? ===

No.

However, rebooting is the easiest method to ensure that the kernel module(s) from the old driver are unloaded and the fglrx module is loaded instead. If you don't want to reboot for some reason, you may manually shut down Xorg, unload any old "drm", "radeon" or "fglrx" modules and then start Xorg again.

==Kernel==
===Why does fglrx not work for my bleeding-edge kernel?===
The development process of the fglrx driver and the Linux kernel are not on the same level. The fglrx driver requires some special interactions with the kernel memory API and these tend to change between kernel versions.

There is also an 11-12 week cycle required to develop, validate and test each release of an ATI driver <ref>http://www.phoronix.com/scan.php?page=article&item=735&num=1</ref>. ATI will only look to support the latest kernel that is officially out (no -rc or -git releases are supported) at the time they release a driver. Example: fglrx version A comes out Monday, but kernel version B comes out Tuesday. Kernel version B is not supported by fglrx version A. (but might be able to work anyway by doing a 'modprobe -f fglrx' in a shell)

The binary part of ATI's kernel module has no explicit dependency on the Linux kernel. There are a set of source files that provide the glue to the kernel. This is where the dependency to different kernels exist. As a result, user contributed patches for newer kernels can often be found by searching [http://ati.cchtml.com Bugzilla].

==X Configuration==
===Composite Extension===
If you've enabled transparency, and you've added the Composite extension to the xorg.conf file, the ATI driver will disable DRI.

The only way to use 3D and the ATI OpenGL drivers is commenting the Option "Composite" "Enable" line.

It may be necessary to put the following lines into xorg.conf:

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

==Troubleshooting==
* See [[Troubleshooting]] page.

==See Also==
*[http://ati.amd.com/products/catalyst/linux.html Official ATI Linux Driver FAQ]

==References==
<references/>

Category:OEMs

2007-10-14T11:28:51Z

74.231.24.2:

olochieltca
Beige box manufacturers will typically use stock cards purchased through retail channels only.

This list should contain branded boards (motherboards, AIB cards and systems).

Branded systems will typically invest a lot more effort into ensuring components are compatible and stable. As a result, listing branded systems allows users to understand the breadth of support provided by ATI's drivers.

Please select a hardware manufacturer from the list below.

[[Category:NeedsUpdating]]
[[Link title]]

TurboLinux

2007-10-05T07:22:00Z

74.231.24.2:

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

LFS

2007-10-01T21:42:10Z

74.231.24.2:

erlisiterou
For all of you that like to do things the hard way:
== Getting 3D for your ATI Radeon card in LFS [http://www.linuxfromscratch.org/] ==

Used here
* Kernel 2.6.15 (with agp and DRM configured)
* Fresh LFS install
* Xorg 6.8.2 (By BLFS)
* Driver (proprietary fglrx 8.20.8)

Probably not needed (and might even interfere!) Please verify and edit if possible.
* Mesa-6.4.1 (leftovers after failed attempt at installing r300_dri)

----

After browsing ATI's homepage for drivers I decided to use the installer-package, as I didn't have any easy way to convert rpms into tarballs.

If you decide to use the installer provided by ATI, make sure you don't have any libGL.so.* lying around in /usr/X11R6/lib before running the installer binary. It appears to rename installed files rather than overwriting old. Move any existing just to be safe:

<code>
mkdir /root/old_libGL 
mv /usr/X11R6/lib/libGL.so* /root/old_libGL
</code>

Run the installer, it does some checks and then opens a graphical point-and-clickety install window. Follow instructions and install the correct driver. Maybe it works now already? Never has for me, so I'll continue..

After the installer exits you should have a directory /lib/modules/fglrx/build_mod
with a script "make.sh" to re-build the fglrx driver. Now for kernel 2.6.15 with fglrx 8.20.8 you'll need to apply a patch for avoiding errors of:

Bad page state at free_hot_cold_page
I pathched manually, since all you need to do is change line 2624 in firegl_public.c to
#if LINUX_VERSION_CODE >= 0x02060f

If the script complains about not being run from a real console, you could try to hack it a bit to go on anyway.

<code>
cd /lib/modules/fglrx/build_mod 
vi make.sh
</code>

search for:

if [ $? -ne 0 ];
then
echo "You arent running in a 'login shell'."
echo "Please login directly from a console"
echo "or use 'su -l' to get the same result."
exit 1
fi

and delete the line with 'exit 1' to get past that annoyance. Run it to build the modules. Then change to the parent directory and run "make_install.sh", hack as needed. This installs the kernel module and it's conterpart in /lib/X11R6/modules/

Finally, when all of this is done, you might need an old version of libstdc++
check it by typing:

[shell]$ ldd /usr/X11R6/lib/modules/dri/fglrx_dri.so
libm.so.6 => /lib/libm.so.6 (0x408a5000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x408c7000)

Since I had only version 6 on my system I also installed version 5 to make fglrx happy.

Alternatively, setting LIBGL_DEBUG might also reveal old libstdc++ dependencies.

run fglrxconfig, answer a lot of questions, start X and pray.

Good luck!
/Jeol

(...think I forgot somthing, hm.)

== Troubleshooting tips ==
Read the log, look for errors (EE) 
<code>
cat /var/log/Xorg.0.log | grep EE 
LIBGL_DEBUG=verbose glxinfo
</code>

{{VCT}}
[[Category:Distributions]]