cchtml.com - User contributions [en]

Troubleshooting

2007-10-25T05:41:11Z

207.248.164.198:

liracbot
varsitorbas
==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.

*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")

=== 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.

==X Server Related Issues==

=== 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].

=== BigDesktop doesn't work after GDM login screen ===

This can occur on Ubuntu Feisty Fawn sometimes.

System > Prefrences > Screen Resolution

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

=== 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).

=== 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.

=== X800/X850 fan is very loud / constantly works ===

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~

=== 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>
}}

==References==
<references/>

[[Category:Installation Documentation]]

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

Verifying

2007-10-25T05:38:58Z

207.248.164.198:

videlor
racc4tp
{{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.

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:

<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 
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-25T03:15:30Z

207.248.164.198:

czelzele
viacelrelac
dronda
==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/>

8.32.5

2007-10-25T03:15:14Z

207.248.164.198:

domvartrocr
ATI Linux fglrx driver version 8.32.5

==Release Notes==
* Xorg 7.2 support (partial)
* Radeon X1950 and X1650 support
* Lots of bug fixing

==Links==
* Full release notes: [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_8.32.5.html linux_8.32.5.html]
[[Category:Releases]]

Slackware

2007-10-25T02:32:07Z

207.248.164.198:

ordronbocm
Welcome. This bare-bones little faq details how to get fglrx working on slackware.

==Installation==
*[[Slackware Installation Guide|Installation Guide]]

==Tips and Tricks==
'''Slamd64''' - You need to install GCC 3.3 libraries for fglrx. Download and install [http://www.tfd.chalmers.se/~berend/slamd64/ cxxlibs5]. You will also need to install the 32 bit compatibility libraries in /c.

==Related Resources==

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