cchtml.com - User contributions [en]

Verifying

2007-10-04T10:18:22Z

88.198.25.14:

monletoelt
lieltzell
{{VCT-on-top}}

It is assumed that you have completed the [[Installation|installation process]].

==Verify with ATI tools==
If the installation has worked, then any 3D application should work without issue. A simple way to verify without any possibility of failure is to verify the following occurs. Please note that you may have needed to go through [[:Category:Distributions|distribution specific]] process to enable the 3D support.
===fglrxinfo===
<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 2.0.5804 (8.25.0)
</pre>
===fgl_glxgears===
You can also run the ATI provided application called fgl_glxgears which should show a spinning cube with the venerable glxgears running on each face.

<b>If when you run fgl_glxgears, the cube spins, but is lacking any cogs on the faces, the faces being instead, various shades of blue, and/or you get an error message like:</b>

<pre>
Using GLX_SGIX_pbuffer
913 frames in 5.0 seconds = 182.600 FPS
783 frames in 5.0 seconds = 156.600 FPS
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 14 (X_GetGeometry)
Resource id in failed request: 0x0
Serial number of failed request: 51
Current serial number in output stream: 51
</pre>
===Links===
http://linux.coconia.net/general/ati.htm<br>
http://m.domaindlx.com/LinuxHelp/ati/ati.htm (mirror)
==Verify with Linux tools==
===glxinfo===
This command line option should report "direct" rendering.
$ glxinfo | grep direct

(For Debian 4.0, install the mesa-utils package to get glxinfo.)

===Xorg.0.log===
The X.org X server log file also contains useful information to verify installation was successful. It is located on most Linux distributions at <code>/var/log/Xorg.0.log</code> and can be opened by any text editor.

'''You can now move on to [[Configuring|configuring the driver]].'''

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

Frequently Asked Questions

2007-10-04T10:17:37Z

88.198.25.14:

rolrelorc
==Installation==
===How do I know fglrx is installed correctly?===
There are several ways to check if fglrx is loaded and running.
<br>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/>

Configuring

2007-10-04T10:17:30Z

88.198.25.14:

elclaletol
{{VCT-on-top}}
== aticonfig ==

Since version 8.18.6 the fglrx driver includes the '''aticonfig''' tool which simplifies ''xorg.conf'' editing. Here are some useful commands this tool offers (for a complete list see [http://wiki.cchtml.com/index.php/aticonfighelp ''aticonfig --help'']).

=== Changes taking effect on startup ===
''Changes will change the config file!''

;Initial setup (creates device section using fglrx):
:<pre>sudo aticonfig --initial</pre>

;Enable Video acceleration (Xv Overlay):
:<pre>sudo aticonfig --overlay-type=Xv</pre>

;Force fglrx to use kernel's AGP driver instead of own implementation (only use when internal agpgart doesn't work):
:<pre>sudo aticonfig --internal-agp=off</pre>
*Note: Newer fglrx driver versions do not include an internal AGPGART so the kernel agpgart is used no matter what.

=== Changes taking effect immediately ===
''Changes will not change the config file.''

;Print information about power states.
:<pre>aticonfig --list-powerstates</pre>
Or, for us lazy folk, the shorter version is ''aticonfig --lsp''

;Set a power state to the lowest (battery friendly):
:<pre>aticonfig --set-powerstate=1</pre>
*Note: check out available power states using ''aticonfig --list-powerstates''
*Note: this option does not work when an external monitor is connected

;Print information about connected and enabled monitors:
:<pre>aticonfig --query-monitor</pre>

;Examples how to enable two monitors on the fly:
* Assume you have two monitors already setup correctly ([http://ubuntuforums.org/showthread.php?t=301941 Dual monitor support] at Ubuntuforums)
* This example enable laptop internal monitor (lvds) and external monitor (crt1)
:<pre>aticonfig --enable-monitor=lvds,crt1 --effective=now</pre>
*Note: ''aticonfig --enable-monitor=STRING,STRING'' where STRING can be one of the following set, separated by commas: none,crt1,crt2,lvds,tv,tmds1,tmds2,auto. Only 2 displays can be enabled at the same time. Any displays that are not on the list will be disabled.
*Note: check out connected and enabled monitors using ''aticonfig --query-monitor''

;Turn off the second monitor on the fly and start to use only laptop internal monitor (lvds)
:<pre>aticonfig --enable-monitor=lvds --effective=now</pre>

;Swap monitors on the fly when using big desktop mode
* Assume you have two monitors already setup correctly ([http://ubuntuforums.org/showthread.php?t=301941 Dual monitor support] at Ubuntuforums)
:<pre>aticonfig --swap-monitor --effective=now</pre>
* Note: This only works for big desktop setup. This will swap the contents on the two monitors.

=== Troubleshooting ===

Still not working? Go to the [[Troubleshooting]] page.

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

TurboLinux

2007-10-04T10:17:10Z

88.198.25.14:

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