http://wiki.cchtml.com/api.php?action=feedcontributions&feedformat=atom&user=80.128.161.173cchtml.com - User contributions [en]2026-05-13T18:59:10ZUser contributionsMediaWiki 1.43.1http://wiki.cchtml.com/index.php?title=Talk:Frequently_Asked_Questions&diff=4023Talk:Frequently Asked Questions2007-05-28T22:55:45Z<p>80.128.161.173: New page: Changed "vi" to "less", besides there being no need to use an "editor" for read-only purposes, there are "userfriendly" distributions out there which come with nano instead of vi.</p>
<hr />
<div>Changed "vi" to "less", besides there being no need to use an "editor" for read-only purposes, there are "userfriendly" distributions out there which come with nano instead of vi.</div>80.128.161.173http://wiki.cchtml.com/index.php?title=Frequently_Asked_Questions&diff=806Frequently Asked Questions2007-05-28T22:44:11Z<p>80.128.161.173: /* How do I know fglrx is installed correctly? */</p>
<hr />
<div>==Installation==<br />
===How do I know fglrx is installed correctly?===<br />
There are several ways to check if fglrx is loaded and running.<br />
<br>1. Check your X.org or XFree86 log. You should see "DRI Initialization Successful."<br />
# less /var/log/Xorg.0.log<br />
or<br />
# less /var/log/XFree86.0.log<br />
2. Check glxinfo. You should see "direct" and not "indirect."<br />
# glxinfo | grep direct<br />
3. Check your kernel log. You should see fglrx messages near the bottom.<br />
# dmesg<br />
4. Check your modules. You should see fglrx loaded.<br />
# lsmod | grep fglrx<br />
*NOTE: [[Glxgears is not a Benchmark|glxgears]] is not a definite way of checking the installation of fglrx.<br />
<br />
=== Is the rebooting really necessary? ===<br />
<br />
No.<br />
<br />
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.<br />
<br />
==Kernel==<br />
===Why does fglrx not work for my bleeding-edge kernel?===<br />
The development process of the fglrx driver and the GNU/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. <br />
<br />
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)<br />
<br />
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].<br />
<br />
==X Configuration==<br />
===Composite Extension===<br />
If you've enabled transparency, and you've added the Composite extension to the xorg.conf file, the ATI driver will disable DRI.<br />
<br />
The only way to use 3D and the ATI OpenGL drivers is commenting the Option "Composite" "Enable" line.<br />
<br />
It may be necessary to put the following lines into xorg.conf:<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
==Troubleshooting==<br />
* See [[Troubleshooting]] page.<br />
<br />
==See Also==<br />
*[http://ati.amd.com/products/catalyst/linux.html Official ATI Linux Driver FAQ]</div>80.128.161.173