http://wiki.cchtml.com/api.php?action=feedcontributions&user=63.138.193.130&feedformat=atomcchtml.com - User contributions [en]2024-03-28T14:56:34ZUser contributionsMediaWiki 1.39.4http://wiki.cchtml.com/index.php?title=Troubleshooting&diff=9830Troubleshooting2013-03-16T18:48:25Z<p>63.138.193.130: /* References */</p>
<hr />
<div>==Installer Issues==<br />
When the installer fails to produce results, check the directory where the ati catalyst installer has been placed. If it contains international characters or spaces, weird errors will arise. (The issue has been reported to ATI some time ago, but even in the newest releases they seem to like to prefer to conserve the bug)<br />
<br />
===== February 15, 2013 - Catalyst 13.1 Install on Ubuntu 10.04 (lucid) =====<br />
<br />
Had much the same problems as the poster below, but found another fix:<br />
<br />
Error:<br />
<br />
dh_install: fglrx missing files (arch/#SRCOTHERARCH#/etc/OpenCL/vendors/*.icd), aborting<br />
<br />
Solution found at [http://parallelplusplus.blogspot.ca/2013/01/problems-with-amd-catalyst-131-on-ubuntu.html http://parallelplusplus.blogspot.ca/2013/01/problems-with-amd-catalyst-131-on-ubuntu.html].<br />
<br />
1. Extract files from the installer:<br />
<br />
sh amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --extract amd<br />
<br />
2. Edit the packages/Ubuntu/dists/lucid/rules file as follows:<br />
<br />
The following line had to be appended after line 69:<br />
SRC_other_arch := x86_64<br />
and the following line had to be appended after line 151:<br />
-e "s|#SRCOTHERARCH#|$(SRC_other_arch)|g" \<br />
<br />
3. Create package:<br />
<br />
sudo ./ati-installer.sh 9.012 --buildpkg Ubuntu/lucid<br />
<br />
===== January 22, 2013 - Catalyst 13.1 Install on Ubuntu 11.04 (natty) =====<br />
<br />
Just wanted to document my problems with this install and the workaround I came up with.<br />
<br />
1. I got the installer from AMD (amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run) and attempted this:<br />
<br />
sh amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --buildpkg Ubuntu/natty<br />
<br />
This failed with:<br />
<br />
dh_install: fglrx missing files (arch/#SRCOTHERARCH#/etc/OpenCL/vendors/*.icd), aborting<br />
make: *** [binary-arch] Error 2<br />
dpkg-buildpackage: error: debian/rules binary gave error exit status 2<br />
<br />
That '#SRCOTHERARCH#' looked a bit suspicious. I found a directory arch/x86_64/etc/OpenCL/vendors with an "icd" file in it. I guessed that was what the installer was looking for.<br />
<br />
2. I then extracted the files from the installer:<br />
<br />
sh amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --extract amd<br />
<br />
3. Create sym link for the "#SRCOTHERARCH#" directory that the installer is expecting to find:<br />
cd amd/arch<br />
ln -sf x86_64 '#SRCOTHERARCH#'<br />
<br />
4. Back up to the installer directory and retried the "buildpkg" step - this time it worked and created the three deb package files. I was then able to continue with the install as normal.<br />
<br />
==X Server Related Issues==<br />
<br />
This "free sharing" of information seems too good to be true. Like comnmusim.<br />
<br />
=== No XVideo support on 690G integrated graphic chipset ===<br />
*Upgrade your BIOS if you get random flicker lines and black screen with a 690G chip.<br />
*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.<br />
* XVideo works with 8-1 release (version 8.45.4). You need to change the defaults in /etc/ati/amdpcsdb (created by amdcccle, loaded by X on start, and saved on exit). With X shutdown, set VideoOverlay=Son, OpenGLOverlay=Soff, and Textured2D=STrue. (Don't use aticonfig or xorg.conf to set these. At this time, aticonfig and amdccle don't change these settings, and /etc/ati/amdpcsdb seems to override xorg.conf) (Verified on Asus M2A-VM with BIOS 1501)<br />
* With 8-3 release (8.47.1), to get XVideo working I added ''Option "TexturedVideo" "true"'' to the xorg.conf file. It wasn't necessary to edit the /etc/ati/amdpcsdb file as described in the paragraph above; the open GL overlay can be active and it will still work.<br />
<br />
=== System lockup on logout or switch to virtual consoles ===<br />
<br />
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'''.<br />
<br />
There is a workaround: Use a standard D-Sub VGA connector instead of the DVI connector.<br />
<br />
This workaround was posted as a comment to another related bug: see [http://ati.cchtml.com/show_bug.cgi?id=239#c48 here].<br />
---------<br />
Unfortunately "D-sub" users (like me) have the same problem.<br />
<br />
=== BigDesktop (Dual screen) doesn't work after GDM login screen ===<br />
<br />
This can occur on Ubuntu Feisty Fawn & Gutsy.<br />
<br />
System > Prefrences > Screen Resolution<br />
<br />
Select the resolution that is a combination of both screen resolutions wide and your height.<br />
<br />
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:<br />
{{Box File|/etc/X11/xorg.conf|<br />
<pre> Option "DesktopSetup" "something"</pre><br />
}}<br />
<br />
=== Computer Freezes while using fglrx (UMA and SIDEPORT) ===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
On some ACER laptops (at least the TimelineX), this means that you need to set display adapter mode to DISCRETE in BIOS.<br />
<br />
=== Graphical Anomalies ===<br />
<br />
This was experienced with an ATI Radeon X1600 Pro 512mb:<br />
<br />
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.<br />
<br />
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).<br />
<br />
There's been a bug report regarding [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/150627 anomalies in Firefox] as well.<br />
<br />
=== OpenGL framebuffer Corruption ===<br />
<br />
This problem has been experienced on Thinkpads (T60p) with an ATI MOBILITY FireGL V5250 running driver versions 7.12, 8.01 and 8.02. Whenever any OpenGL application is rendered, the rendered output appears "scrambled" and unreadable. This problem is not very well documented and both glxgears and fgl_glxgears display this anomaly when testing.<br />
<br />
When Anti-Aliasing is forced, the problem resides.<br />
<br />
A solution (tested with 8.02 on Ubuntu Gutsy) to this problem is to open the ATI/AMD Catalyst Control Center and expand the item labeled '3D' in the options tree on the left-hand side of the window. From there, select "Anti-Aliasing" and check the box which reads: "Override application setting". Apply the settings and close the control center.<br />
<br />
For an example of this anomaly, please see [http://i31.tinypic.com/244z9z8.png this image]<br />
<br />
<br />
This solution not work on acer laptop with ATI Mobility Radeon HD 2400 XT.<br />
kepfeltoltes.hu/view/080302/atisux_www.kepfeltoltes.hu_.jpg<br />
<br />
=== Blank Screen with Xorg 1.3.0 ===<br />
If you happen to get a blank screen on X startup and you find lines similar to those in your Xorg.log:<br />
{{Box File|/var/log/Xorg.log|<br />
<nowiki><br />
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(swlDalHelperValidateModeFromDAL 0x549) [...]<br />
3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so [...]<br />
4: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxPreInit 0x8b3) [...]<br />
</nowiki><br />
}}<br />
<br />
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.<br />
<br />
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<br />
sending the monitor signal to the vga output (even if no monitor is connected to it). After pressing [Fn]+[F8(CRT/LCD)] the monitor<br />
signal sometimes returnes to the internal laptop monitor.<br />
By switching to a console or shutting down the X-server, the card switches back to vga...<br />
<br />
My solution: overwriting the file /etc/ati/amdpcsdb with /etc/ati/amdpcsdb.default (sudo cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb)<br />
and restore the xorg.conf (since Xorg replaces /etc/X11/xorg.conf with a failsafe config file). Then reboot the system: fglrx should now<br />
work fine again with Xorg-1.3.0 .<br />
<br />
=== Radeon GPU fan is very loud / constantly works ===<br />
:See [http://ati.cchtml.com/show_bug.cgi?id=499 bug 499] for additional information.<br />
It seems fglrx has a bug with all X800/X850 cards causing them to heat up excessively<br />
even when not in 3D mode. This behaviour will cause the cards' fans to function on full<br />
blast continuously. There is no known fix as of driver 8.31.05 or previous. Open source<br />
"radeon" driver does not exhibit this problem.<br />
<br />
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~<br />
<br />
It happens too with Radeon X1800 GTO and Radeon X1900 GT.<br />
<br />
Possible solution (at least using a Mobility Radeon X1600): <br />
<pre>aticonfig --set-powerstate=1</pre><br />
<br />
To find out which powerstates your Radeon supports try:<br />
<pre>aticonfig --lsp</pre><br />
<br />
=== System freezes after logout with GDM, KDM or XDM<ref>http://ati.cchtml.com/show_bug.cgi?id=239 Going back to gdm/kdm/xdm hardlocks after running X session</ref> ===<br />
<br />
If you use GDM, which is the default Login Manager on Ubuntu, modify<br />
<pre>sudo gedit /etc/gdm/gdm.conf</pre><br />
<br />
{{Box File|/etc/gdm/gdm.conf|<br />
<nowiki>AlwaysRestartServer=true</nowiki><br />
}}<br />
<br />
If you use KDM, which is the default Login Manager on Kubuntu, add to the [X-:*-Core] section the following<br />
<br />
<pre>sudo kate /etc/kde3/kdm/kdmrc</pre><br />
<br />
{{Box File|/etc/kde3/kdm/kdmrc|<br />
<nowiki>TerminateServer=true</nowiki><br />
}}<br />
<br />
if you use xdm, add the following to<br />
<pre>sudo gedit /etc/X11/xdm/xdm-config</pre><br />
<br />
{{Box File|/etc/X11/xdm/xdm-config|<br />
<nowiki>DisplayManager*terminateServer: true</nowiki><br />
}}<br />
<br />
=== System freezes at startup of Fedora 7 or RHEL 5.3 after installing the driver ===<br />
<br />
Turn off the Redhat Graphical boot from grub config:<br />
<br />
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.<br />
<br />
This also works for Red Hat Enterprise Linux 5.3.<br />
<br />
=== 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>===<br />
To solve this issue you need to disable atieventsd. On ubuntu you can run:<br />
<pre><br />
sudo /usr/sbin/update-rc.d -f atieventsd remove<br />
</pre><br />
<br />
=== Intermittent Freezes/Lockups due to AGPv3 running at 8x ===<br />
Try forcing X to set AGP Speed to 4x<br />
{{Box File|/etc/X11/xorg.conf|<br />
<pre> Option "AGPv3Mask" "0x00000002"</pre><br />
}}<br />
((Would be nice to put down WHERE to change this, not just to change this. The same applies to just about every hint shown above.))<br />
<br />
+ You add it to the "Device" section for your graphics card in /etc/X11/xorg.conf.<br />
<br />
Great hammer of Thor, that is powerfully helpufl!<br />
<br />
=== _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 ===<br />
<br />
<b>UPDATE</b>: The problem I have reported here is no more reproducible with the fglrx revision 11.03 (ati-driver-installer-11-3-x86.x86_64.run) within two months of testing. Many thanks to the guys that fixed this !<br />
<br />
Strange name for a bug but this is what your kernel might say if your screen freeze completely while using two sessions and switching between them. The bug is more likely to occur while doing the session switch, but can also occur in a later moment. I have observed it while starting a new application, or while doing a simple page scrolling. Anyway, in case of this bug the graphic is completely unusable as well as the console switching, but the OS and non graphic application continue to work. A reboot it the only way I know to bring back the screen to normal operations. Then your /var/log/kernel.log might contain something like this:<br />
<pre><br />
<br />
Dec 16 07:22:13 cube kernel: [1178220.704151] BUG: unable to handle kernel NULL pointer dereference at 00000000000001c0<br />
Dec 16 07:22:13 cube kernel: [1178220.704168] IP: [<ffffffffa030ef0f>] _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 [fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704319] PGD 171a1b067 PUD 1b5376067 PMD 0 <br />
Dec 16 07:22:13 cube kernel: [1178220.704330] Oops: 0000 [#1] SMP <br />
Dec 16 07:22:13 cube kernel: [1178220.704337] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq<br />
Dec 16 07:22:13 cube kernel: [1178220.704346] CPU 1 <br />
Dec 16 07:22:13 cube kernel: [1178220.704351] Modules linked in: cramfs ext2 iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables fglrx(P) ftdi_sio usbserial ext3 jbd mbcache btrfs nls_utf8 zlib_deflate nls_cp437 crc32c vfat <br />
fat libcrc32c radeon ttm drm_kms_helper drm i2c_algo_bit ppdev lp sco bridge stp bnep rfcomm l2cap crc16 powernow_k8 cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_userspace binfmt_misc fuse loop snd_hda_codec_atihdmi snd_hda_codec_realtek snd_usb_audio snd<br />
_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_usb_lib snd_hwdep snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device sd_mod btusb crc_t10dif usblp asus_atk0110 bluetooth snd parport_pc i2c_piix4 parport psmouse rfkill button k8tem<br />
p i2c_core shpchp serio_raw processor pcspkr evdev soundcore pci_hotplug edac_core snd_page_alloc edac_mce_amd usbhid hid nfs lockd fscache nfs_acl auth_rpcgss sunrpc usb_storage ata_generic ahci firewire_ohci fi<br />
Dec 16 07:22:13 cube kernel: rewire_core crc_itu_t sky2 thermal thermal_sys pata_atiixp libata ohci_hcd ehci_hcd scsi_mod usbcore nls_base [last unloaded: fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] Pid: 7344, comm: Xorg Tainted: P W 2.6.32-5-amd64 #1 System Product Name<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] RIP: 0010:[<ffffffffa030ef0f>] [<ffffffffa030ef0f>] _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 [fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] RSP: 0018:ffff88003e91bc38 EFLAGS: 00010292<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] RAX: 0000000000000000 RBX: ffffc9001236f620 RCX: 00000000000006b0<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] RDX: 0000000000000000 RSI: ffffc90012398e00 RDI: 0000000000000140<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] RBP: ffffc90012398e00 R08: ffff88020b560008 R09: ffffc9001237b620<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] R10: 00000000000006bc R11: 0000000000000001 R12: ffff88003e91bc58<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] R13: 00000000000001c0 R14: ffffc90012398e00 R15: 0000000000000140<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] FS: 00007f52b107d700(0000) GS:ffff880008480000(0000) knlGS:00000000f75858d0<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] CR2: 00000000000001c0 CR3: 00000001712a7000 CR4: 00000000000006e0<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] Process Xorg (pid: 7344, threadinfo ffff88003e91a000, task ffff88020bf5a350)<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] Stack:<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] 000000001238c660 ffffffffa0389489 0000000000000100 0000000000000148<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] <0> 0000000000000000 0000000000000000 000002af00000068 ffffffffa038c6e7<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] <0> 00000000000001c0 000000000019330c 00007f52ab7a2000 ffffc9001236f620<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] Call Trace:<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa0311680>] ? _ZN3MSF9free_surfEP9CMMDriverP10CMMSurface+0x50/0xe0 [fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa030d391>] ? CMMFreeSurface+0x131/0x1b0 [fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa031d24c>] ? _Z8uCWDDEQCmjjPvjS_+0x68c/0xf00 [fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02d2114>] ? firegl_cmmqs_CWDDE_32+0x334/0x440 [fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02d0ba0>] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02d0b30>] ? firegl_cmmqs_CWDDE32+0x0/0x100 [fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02b0b5a>] ? firegl_ioctl+0x1ea/0x250 [fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff810fa4c7>] ? vfs_ioctl+0x56/0x6c<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff810fa9e0>] ? do_vfs_ioctl+0x48d/0x4cb<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff812fd946>] ? do_page_fault+0x2e0/0x2fc<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff810faa6f>] ? sys_ioctl+0x51/0x70<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] Code: 4c 8d 64 24 20 c7 44 24 04 00 00 00 00 4c 8d af 80 00 00 00 48 c7 44 24 20 00 00 00 00 48 c7 44 24 28 00 00 00 00 4c 89 6c 24 40 <49> 8b 5d 00 31 c0 48 85 db 48 89 5c 24 30 74 04 48 8b 43 30 49 <br />
Dec 16 07:22:13 cube kernel: [1178220.704516] RIP [<ffffffffa030ef0f>] _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 [fglrx]<br />
Dec 16 07:22:13 cube kernel: [1178220.704516] RSP <ffff88003e91bc38><br />
Dec 16 07:22:13 cube kernel: [1178220.704516] CR2: 00000000000001c0<br />
Dec 16 07:22:13 cube kernel: [1178220.705883] ---[ end trace c9192c1a2722dc89 ]---<br />
</pre><br />
As fglrx source is closed, it will b difficult to catch this bug without AMD internal resource. If someone from AMD read this: please catch this bug. It is there from a least the last couple of monthly driver and really make my machine unable to do the work it was intended to do. I first see this bug using a Debian Lenny AMD64 with a old kernel. I recently upgraded to Debian Squeeze AMD64 with his last kernel, but the bug is exactly the same.<br />
<br />
=== [SOLVED] System freeze / Catalyst 11-9 / "unable to handle kernel NULL pointer dereference at ..." ===<br />
<br />
Similar to previous section, mouse and keyboard unresponsive afer a ramdomly amount of time.<br />
<br />
-----------------------------------------------------------------------------------------------<br />
Computer<br />
-----------------------------------------------------------------------------------------------<br />
<pre><br />
Linux Debian Squeeze + sid fglrx packages<br />
Desktop<br />
Motherboaord ASUS P5KPL - 4GB RAM<br />
Intel E8500 3.16GHz <br />
ACPI DISABLED<br />
</pre><br />
-----------------------------------------------------------------------------------------------<br />
xorg server<br />
-----------------------------------------------------------------------------------------------<br />
<pre><br />
X.Org X Server 1.7.7<br />
Release Date: 2010-05-04<br />
X Protocol Version 11, Revision 0<br />
Build Operating System: Linux 2.6.37-trunk-amd64 x86_64 Debian<br />
Current Operating System: Linux Joelle 2.6.32-[01] #1 SMP Sat Oct 8 21:03:45 CEST 2011 x86_64<br />
xorg-server 2:1.7.7-13<br />
Current version of pixman: 0.16.4Section "Device"<br />
</pre><br />
-----------------------------------------------------------------------------------------------<br />
xorg.conf<br />
-----------------------------------------------------------------------------------------------<br />
<pre><br />
Section "Device"<br />
Identifier "RADEON HD2600 - fglrx"<br />
Driver "fglrx"<br />
BusID "PCI:2:0:0"<br />
#Option "SWCursor" "true"<br />
Option "TexturedVideo" "on"<br />
Option "TexturedVideoSync" "true"<br />
Option "VideoOverlay" "on"<br />
Option "OpenGLOverlay" "off"<br />
# ATI<br />
#Option "AccelMethod" "EXA"<br />
#Option "AGPMode" "4"<br />
#Option "EnablePageFlip" "true"<br />
#Option "DDCMode"<br />
# NOTUSED Option "RenderAccel" "true" <br />
#Option "SubPixelOrder" "NONE"<br />
#Option "ColorTiling" "false"<br />
#Option "backingstore" "true"<br />
#----<br />
# NOTUSED Option "XAANoOffscreenPixmaps" "true"<br />
# NOTUSED Option "AddARGBGLXVisuals" "true"<br />
# NOTUSEDOption "AllowGLXWithComposite" "true"<br />
EndSection<br />
</pre><br />
------------------------------------------------------------------------------------------------<br />
lspci<br />
------------------------------------------------------------------------------------------------<br />
<pre><br />
Vendor: ATI Technologies Inc<br />
Device: RV630 [Radeon HD 2600 Series]<br />
SVendor: PC Partner Limited<br />
SDevice: Device e410<br />
</pre><br />
------------------------------------------------------------------------------------------------<br />
/proc/ati/0/...<br />
------------------------------------------------------------------------------------------------<br />
<pre><br />
BIOS_CREATION_DATE="09/05/07 21:52"<br />
BIOS_MSG="11X-1E410ASA-001 RV630 GDDR2 128BIT 256MB 600E/500M"<br />
BIOS_KIT_VERSION="BK-ATI VER010.059.000.003.000000"<br />
BIOS_PN="113-B1E41QIM-X01"<br />
</pre><br />
------------------------------------------------------------------------------------------------<br />
amdcccle info<br />
------------------------------------------------------------------------------------------------<br />
BIOS<br />
Date 09/05/07 21:52<br />
Version 010.059.000.003.000000<br />
Part Number 113-B1E41QIM-X01<br />
Memory<br />
Type DDR2<br />
Clock 500 MHz<br />
Size 256 MB<br />
Bandwidth 16.0 GBytes/s<br />
BUS<br />
Graphics Capability PCI Express<br />
Maximum Setting x16<br />
Core Clock 600 MHz<br />
Software<br />
Catalyst version 10.9<br />
Driver Packaging Version 8.771-100825a-104565C-ATI<br />
2D Driver Version 8.89.4<br />
Catalyst Control Center Version 2.13<br />
RandR Version 1.3<br />
OpenGL<br />
OpenGL Provider Advanced Micro Devices, Inc.<br />
OpenGL Renderer ATI Radeon HD 2600 Pro<br />
OpenGL Version 3.3.11079 Compatibilty Profile COntext<br />
------------------------------------------------------------------------------------------------<br />
BUG trace in syslog<br />
------------------------------------------------------------------------------------------------<br />
<pre><br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443571] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443576] IP: [<ffffffffa024b8d1>] _ZN20CMMHeap_SystemMemory8pushPoolEP7CMMPool+0x11/0x40 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443623] PGD 37736067 PUD 5cfd6067 PMD 0 <br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443626] Oops: 0002 [#1] SMP <br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443628] last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda/uevent<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443631] CPU 1 <br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443632] Modules linked in: binfmt_misc fuse coretemp w83627ehf hwmon_vid drm loop snd_hda_codec_atihdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd i2c_i801 soundcore snd_page_alloc i2c_core pcspkr fglrx(P) rng_core evdev psmouse serio_raw ext3 jbd mbcache dm_mod sd_mod crc_t10dif ata_generic uhci_hcd ata_piix libata ehci_hcd scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443656] Pid: 1521, comm: Xorg Tainted: P 2.6.32-[01] #1 System Product Name<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443657] RIP: 0010:[<ffffffffa024b8d1>] [<ffffffffa024b8d1>] _ZN20CMMHeap_SystemMemory8pushPoolEP7CMMPool+0x11/0x40 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443686] RSP: 0018:ffff8800370bb970 EFLAGS: 00010297<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443687] RAX: ffff880037638008 RBX: ffffc9000144a150 RCX: 0000000000000000<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443689] RDX: 0000000000000000 RSI: ffffc9000144a018 RDI: ffff880037638de8<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443690] RBP: 0000000000000002 R08: ffffffffa0278bb0 R09: ffff880037638008<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443692] R10: ffffc9000144a090 R11: ffff880037638008 R12: ffff880037638de8<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443693] R13: 0000000000000040 R14: 0000000000000000 R15: 0000000000000000<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443695] FS: 00007fb0e561d700(0000) GS:ffff880001700000(0000) knlGS:0000000000000000<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443697] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443698] CR2: 0000000000000008 CR3: 000000003776b000 CR4: 00000000000006e0<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443700] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443702] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443704] Process Xorg (pid: 1521, threadinfo ffff8800370ba000, task ffff8800377d3100)<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443705] Stack:<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443706] ffffffffa024b2f6 0000000000000000 ffff880037638de8 ffff880037638e78<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443709] <0> 0000000000000200 0000000000000000 ffffffffa01e45d5 0000000000080000<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443711] <0> ffff880037638de8 ffffffffa0278bb0 ffffffffa01e4938 0000000000000000<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443714] Call Trace:<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443743] [<ffffffffa024b2f6>] ? _ZN7CMMHeap15createPoolSpaceI21CMMPoolAsicAccessibleEEbj+0xb6/0xc0 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443788] [<ffffffffa01e45d5>] ? _ZN20CMMHeap_SystemMemory10obtainPoolEv+0x85/0xc0 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443831] [<ffffffffa01e4938>] ? _ZN16CMMHeap_PAGEABLE10expandHeapEm+0x18/0xb0 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443860] [<ffffffffa024b0ea>] ? _ZN7CMMHeap10expandHeapEmRmPv+0xa/0x10 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443904] [<ffffffffa01e32ed>] ? _ZN7CMMHeap21allocateMorePoolSpaceEmPv+0x8d/0x1b0 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443947] [<ffffffffa01e1cbe>] ? _ZN14CMMHeapManager13allocPageableEjR14CMM_ALLOCATION+0xbe/0x100 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.443992] [<ffffffffa020a1f1>] ? AddrComputeSurfaceInfo+0x31/0x50 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444036] [<ffffffffa01ebc57>] ? _ZN9CMMObjectnwEmP8CMM_CORE+0x37/0x70 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444080] [<ffffffffa01ef7a2>] ? _ZN8MSF_CORE21get_surface_structureEv+0xc2/0xe0 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444122] [<ffffffffa01da40f>] ? _ZN3MSF11create_surfEP9CMMClientP9CMMDriverPvRA4_K14CMM_ALLOCATIONP16MSF_SURF_ATTRIBS+0x1f/0x1c0 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444164] [<ffffffffa01dbaf3>] ? _ZN3MSF21handle_shared_surfaceEP9CMMClientP9CMMDriverP10CMMSurfaceP16MSF_SURF_ATTRIBSP15_CMM_RETURNCODE+0x113/0x280 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444206] [<ffffffffa01d61aa>] ? CMMAllocSurface_WA+0x62a/0xab0 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444235] [<ffffffffa018a522>] ? firegl_trace+0x72/0x1e0 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444278] [<ffffffffa01e7219>] ? _Z8uCWDDEQCmjjPvjS_+0xb59/0x10c0 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444307] [<ffffffffa018ca32>] ? firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444336] [<ffffffffa018b360>] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444365] [<ffffffffa018b2f0>] ? firegl_cmmqs_CWDDE32+0x0/0x100 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444389] [<ffffffffa0169fd8>] ? firegl_ioctl+0x1e8/0x250 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444412] [<ffffffffa0160c75>] ? ip_firegl_unlocked_ioctl+0x9/0xd [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444417] [<ffffffff810e34d8>] ? vfs_ioctl+0x19/0x83<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444419] [<ffffffff810e3a22>] ? do_vfs_ioctl+0x46e/0x4b2<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444422] [<ffffffff810d8216>] ? vfs_read+0xc7/0xfc<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444424] [<ffffffff810e3aa2>] ? sys_ioctl+0x3c/0x5c<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444428] [<ffffffff8100ba6b>] ? system_call_fastpath+0x16/0x1b<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444429] Code: 00 00 00 00 00 00 00 00 00 00 48 8d 47 60 c3 00 00 00 00 00 00 00 00 00 00 00 31 c9 48 8b 97 90 00 00 00 83 7e 18 02 48 0f 44 ce <48> 89 51 08 ff 87 98 00 00 00 48 89 8f 90 00 00 00 c3 00 00 00 <br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444449] RIP [<ffffffffa024b8d1>] _ZN20CMMHeap_SystemMemory8pushPoolEP7CMMPool+0x11/0x40 [fglrx]<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444477] RSP <ffff8800370bb970><br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444478] CR2: 0000000000000008<br />
Oct 8 23:17:33 Joelle kernel: [ 3922.444480] ---[ end trace dbbddd5ad13ce08c ]---<br />
</pre><br />
<br />
<hr><br />
<hr><br />
Edit 29.10.2011<br />
<hr><br />
<hr><br />
Tried : Installed a more recent kernel ( 2.6.32.38 ) , Removed sid fglrx package, and installed a previous version "ati-driver-installer-11-6-x86.x86_64.run" downloaded from ADM site -> bug still present<br />
<br />
Trying now "ati-driver-installer-10-9-x86.x86_64.run"<br />
<br />
<hr><br />
<hr><br />
Edit 06.03.2012<br />
<hr><br />
<hr><br />
Solved ! New ATI drivers conflict with kms. So you have to disable kms ( for example append "nomodeset" on your kernel boot line )<br />
<br />
=== An Example of a working Xorg.conf ===<br />
Lots of trial and error changing Options to get Compiz-Fusion running under Mandriva 2008-2010. X Server 1.6.5<br />
(Sadly, the 'drak' tools that come with Mandriva to configure are worthless.)<br />
<br />
In this instance it was chosen to remove packaged drivers and install from .bin file from AMD/ATI.<br />
<br />
Most Options were added per 'aticonfig -f --initial ... ...'. <br />
And the rest were added as needed. Constantly checking '/var/log/Xorg.0.log' for errors and warnings.<br />
<br />
<pre> Section "ServerLayout" <br />
Identifier "aticonfig Layout" <br />
Screen 0 "aticonfig-Screen[0]-0" 0 0 # The extra zeros are necessary for some reason<br />
Option "AIGLX" <br />
EndSection <br />
<br />
Section "Files"<br />
EndSection <br />
<br />
Section "Module"<br />
Load "dbe"<br />
Load "v4l"<br />
Load "extmod"<br />
Load "type1" <br />
Load "freetype"<br />
Load "glx" <br />
Load "dri" <br />
EndSection <br />
<br />
Section "Monitor"<br />
Identifier "aticonfig-Monitor[0]-0"<br />
Option "VendorName" "Hewlett-Packard"<br />
Option "ModelName" "HP D2845 Ergo 1600 21-inch Display"<br />
HorizSync 31.5-95.0 <br />
VertRefresh 50.0-160.0 <br />
Option "DPMS" "true" <br />
EndSection <br />
<br />
Section "Device"<br />
Identifier "aticonfig-Device[0]-0"<br />
Driver "fglrx"<br />
BusID "PCI:1:0:0"<br />
Option "UseFastTLS" "2"<br />
Option "Textured2D" "on"<br />
Option "TexturedXrender" "off"<br />
Option "BackingStore" "on"<br />
Option "VideoOverlay" "off"<br />
Option "OpenGLOverlay" "off"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "aticonfig-Screen[0]-0"<br />
Device "aticonfig-Device[0]-0"<br />
Monitor "aticonfig-Monitor[0]-0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "on"<br />
Option "RENDER" "on" # essential for proper window border rendering<br />
Option "DAMAGE" "on" # compiz-fusion calls for explicitly<br />
EndSection<br />
</pre><br />
<br />
Open for scrutiny and testing.<br />
<br />
<br />
=== Sticky mouse cursor ===<br />
<br />
Some users reported that the mouse cursor gets stuck when the mouse is moved to the lower right corner. At least in several versions of Ubuntu using Gnome desktop and starting with Catalyst 11.4.<br />
<br />
That seems to be solved when adding ""load "dri"" to "Section Module" of xorg.conf.<br />
<br />
==aticonfig Issues==<br />
If you get the message ‘‘aticonfig: No supported adapters detected’’, you might have a card not officially supported by the fglrx driver but that might still work when forcing the driver to load. See [[Ubuntu#Unsupported_adapter]].<br />
<br />
<br />
=== X server dies at start, possibly with error segmentation fault at address 0x8 ===<br />
* aticonfig can mess up the fglrx config in /etc/ati/amdpcsdb, try overwriting with /etc/ati/amdpcsdb.default<br />
"VideoOverlay" "on"<br />
"OpenGLOverlay" "off"<br />
"UseInternalAGPGART" "yes" <br />
(10/2011, on cat-11.9, ATI 6300 aka 9803)<br />
<br />
<br />
==AMD installer script completes, fglrx X driver loads, fglrxinfo reports error==<br />
<br />
Xorg.log reports 2d/3d acceleration disabled, DRI disabled and uki errors related to /proc/ati files. AMD control panel works.<br />
<br />
This can happen if there is a problem w/ the AMD installer compiling the fglrx.ko kernel module. The installation completes anyway with the fglrx Xorg driver in place. As per 2.6.42.9 and the 12.1 AMD driver there was a compile error in/usr/src/fglrx-8.93/firegl_public.c, due to TS_USEDFPU macro not being defined. Other compile-time errors will produce a similar problem. Check the contents of /usr/share/ati/fglrx-install.log, note if there was a compile error. If so, re-running the AMD installer will not fix the problem since the compile error will just recur. Likewise, patching the bug ie<br />
<br />
http://phoronix.com/forums/showthread.php?68922-Patch-to-compile-fgrlx-module-on-Linux-3-3-rc4-with-x86-32-bit-arch<br />
<br />
and then reinstalling won't help either since the installer re-extracts the source from the archive. To fix, apply whatever fix is required to the sourcecode that the installer leaves in /usr/src/fglrx-xxx and use dkms to compile and install the driver.<br />
<br />
dkms add fglrx/8.93 /usr/src/fglrx-8.93<BR><br />
dkms build fglrx/8.93<BR><br />
dkms install fglrx/8.93<BR><br />
<br />
Apply fixes to the fglrx source and repeat the dkms build step until the build completes, then install & reboot. Check lsmod output to see if fglrx.ko is loaded, confirm DRI and proc stuff in Xorg.log is working.<br />
<br />
In the 2.6.42.9 w/ 12.1 bug case, the fix is to add the TS_USEDFPU ifdef in firegl_public.c as below;<br />
<br />
void ATI_API_CALL KCL_fpu_begin(void)<BR><br />
{<BR><br />
<nowiki>#ifdef CONFIG_X86_64</nowiki><br />
kernel_fpu_begin();<br />
<nowiki>#else</nowiki><BR><br />
<nowiki>#ifndef TS_USEDFPU</nowiki><br />
preempt_disable();<br />
if (__thread_has_fpu(current))<br />
__save_init_fpu(current);<br />
<nowiki>#else</nowiki><br />
struct thread_info *cur_task = current_thread_info();<br />
preempt_disable();<br />
if (cur_task->status & TS_USEDFPU)<br />
__save_init_fpu(cur_task->task);<br />
<nowiki>#endif</nowiki><br />
else<br />
clts();<br />
<nowiki>#endif</nowiki><br />
}<br />
<br />
JL, Yes I'm thinking of ruinnng the title vertically but I also like your idea of changing the color of the text to white. Now I have to figure out how.Thank you for pointing out the ad size. I didn't really test that one out before I put it there.I'm using the Abigail theme from VintageKin.com they have some great family history related themes. I totally recommend them if you are looking for a family history theme. There was another one that I also liked so if this one doesn't work out, I'll switch and see if that helps.I guess the theme doesn't have built-in navigation coding because the built in navigation isn't there.</div>63.138.193.130http://wiki.cchtml.com/index.php?title=Talk:Catalyst_12.10&diff=9386Talk:Catalyst 12.102012-12-10T15:54:58Z<p>63.138.193.130: MCdmDsDxIRnifiJY</p>
<hr />
<div>Xrumer is a program which will post in fomurs and also post blog comments. It has many great features and can go around difficulties such as account creation, client diagnosis, and captchas. This makes it a very hassle-free program to use. You can also retain an where somebody will operate the link building software for you. Using an Xrumer Service really makes obtaining excellent SEO results easy. Xrumer can be very costly to own as it costs $500, but it highly recommended you have a dedicated server as well. This can usually cost $150-$200 monthly. Using an Xrumer service is really a less expensive route to take. Make sure you are getting top quality work when you choose to use an Xrumer service. You want to be able to verify your inbound links, so make sure you get a report. The Xrumer service you utilize should be able to provide you with this. If they will not provide you with this, then you definitely should get someone else for your Xrumer needs. You also want to make sure that there aren't any broken links. If the forum doesn't not allow HTML or certain types of anchor-text, then you'll have many broken links. This certainly does nothing for your SEO rankings, and it is only a waste of time. While Xrumer is very good, there are many individuals who do not make any promises about the amount of posts you will receive. If you find someone who will guarantee their work with Xrumer for a reasonable price, then you should really make the most of that Xrumer service. You'll then know that you are getting the links you deserve. There are many companies who offer a Xrumer service who offer a couple of hundred thousand forum posts or blog comments. This is great, however the the fact is many of these will not even get accepted. The rate of success for this type of Xrumer blast is usually around 4%. Then out of those many of them are not even live on the web. If you want to find a trustworthy Xrumer service, make sure they guarantee the quantity of posts you will have, and make sure you can verify it. When utilizing Xrumer the right way you can observe big increases in your search engine rankings. However, this will not be enough alone in most cases. You will have to include other backlinking strategies and on page SEO as well. However if you are serious regarding obtaining high rankings in the SERP's, then you need to consider using an Xrumer service.</div>63.138.193.130http://wiki.cchtml.com/index.php?title=Ubuntu_Gutsy_Installation_Guide&diff=9065Ubuntu Gutsy Installation Guide2012-10-06T03:56:11Z<p>63.138.193.130: /* Additional configure with aticonfig tool */</p>
<hr />
<div>== Installation ==<br />
<br />
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 7.10 (Gutsy) provides a notification saying that there are restricted drivers available. You just have to go there (Restricted Drivers Manager) and enable the "ATI accelerated graphics driver". Ubuntu will then install and configure the driver for you. If this does not provide the optimal solution you were looking for, please read ahead.<br />
<br />
===Method 1: Install the Driver the Ubuntu Way===<br />
This will install the driver that is currently in the repositories. It may be older than the current version from AMD.<br />
<pre><br />
sudo apt-get update <br />
sudo apt-get install linux-restricted-modules-generic restricted-manager<br />
sudo apt-get install xorg-driver-fglrx<br />
sudo depmod -a<br />
</pre><br />
<br />
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)<br />
<br />
If the system complains about dependencies, use your preferred package manager to download python2.4 and, if necessary, its dependencies.<br />
<br />
===Method 2: Install the Catalyst Driver Manually===<br />
<br />
:''This is just an alternative installation method for the section above. It might help if you still get 'DRI missing' errors.''<br />
<br />
Download page: Catalyst {{catalystversion}} -- File: {{catalystfilename}}. This package contains both the 32-bit and 64-bit driver.<br />
<br />
Change to the directory you downloaded the file. Make sure that you have the ''universe'' and ''multiverse'' repositories enabled in ''/etc/apt/sources.list'' before doing these steps. <br />
<br />
There is a detailed manual with screenshots at [https://wiki.ubuntu.com/AddingRepositoriesHowto Ubuntu Wiki].<br />
<br />
By default, Ubuntu did not enable the Universe and Multiverse repositories, but now in Gutsy, both Universe and Multiverse are activated by default.<br />
<br />
''Install necessary tools:''<br />
{{Box Terminal|<br />
sudo apt-get update<br />
<br />
sudo apt-get install build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)<br />
}}<br />
<br />
''Uninstall previous fglrx:'' <br />
Using Synaptic, completely remove any packages containing "fglrx" in their name.<br />
<br />
If using 64bit make sure to collect package "ia32-libs" before you continue!<br />
<br />
''Create .deb packages:'' <br />
{{Box Terminal|<br />
sudo sh {{catalystfilename}} --buildpkg Ubuntu/gutsy<br />
}}<br />
note: if this step fails with a signal being caught, and you are running the script on an NFS-mounted directory, copy it to a local partition, and it will work. The same error may result from insufficient disk space.<br />
<br />
As an alternative, you can just use<br />
{{Box Terminal|<br />
sudo sh ./{{catalystfilename}} --buildpkg Ubuntu --autopkg<br />
}}<br />
which will download all the needed packages by itself and also automatically detects the Ubuntu version used.<br />
<br />
If this step fails on amd64/x86_64 with a <tt>No such file or directory</tt> message about missing files in <tt>X11R6/lib</tt>, [http://emmetcaulfield.net/Tech/Ubuntu64+ATI follow these instructions] and come back here. Also check that your download path does not contain spaces.<br />
<br />
''Blacklist old fglrx module from linux-restricted-modules:''<br />
<br />
As Ubuntu Gutsy's ''linux-restricted-modules'' package includes the fglrx module from an old driver version (8.37.6), we have to blacklist this module to make sure the new kernel module which is needed by the new driver will be used instead.<br />
<br />
Ubuntu/Gnome users type in:<br />
<pre>gksu gedit /etc/default/linux-restricted-modules-common</pre><br />
<br />
Kubuntu/KDE users type in:<br />
<pre>kdesu kate /etc/default/linux-restricted-modules-common</pre><br />
<br />
Add "fglrx" to the line "DISABLED_MODULES"<br />
{{Box File|/etc/default/linux-restricted-modules-common|<br />
<pre>DISABLED_MODULES="fglrx"</pre><br />
}}<br />
Please note that after the modification above, the "Restricted Driver Manager" will signal "ATI accelerated graphics driver" not enabled (unticked). This is perfectly correct. At the end of the installation procedure it will signal in Status: "in use" (green light), but NOT enabled. It simply means that the fglrx module contained in the linux-restricted-modules package is not enabled, but another fglrx module (8.4) is in use.<br />
<br />
You may also need to edit the file (if it exists):<br />
<pre>gksu gedit /etc/modprobe.d/blacklist-restricted</pre><br />
Put a # in front of the line "blacklist fglrx", if it is present. Otherwise, the kernel module will not load automatically, and you will not get 3D acceleration.<br />
<br />
''Remove any old fglrx debs from /usr/src/:''<br />
<pre><br />
sudo rm /usr/src/fglrx-kernel*.deb<br />
</pre><br />
<br />
''Install .deb packages:''<br />
<br />
<pre><br />
sudo dpkg -i xorg-driver-fglrx_8.476-0*.deb fglrx-kernel-source_8.476-0*.deb fglrx-amdcccle_8.476-0*.deb<br />
</pre><br />
<br />
''Additional 64-bit instructions''<br />
<br />
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 receive 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 package:<br />
<br />
<pre><br />
sudo apt-get install -f<br />
</pre><br />
<br />
Catalyst 8.3 on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:<br />
<pre><br />
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.476-0*.deb fglrx-kernel-source_8.476-0*.deb fglrx-amdcccle_8.476-0*.deb<br />
</pre><br />
<br />
Im not wrhoty to be in the same forum. ROTFL<br />
<br />
===Configure the Driver===<br />
*NOTE THIS WILL ERASE SETTINGS IN /etc/X11/xorg.conf you should be sure there is a backup.<br />
*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.<br />
*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.<br />
<pre><br />
sudo aticonfig --initial<br />
</pre><br />
Then:<br />
<pre><br />
sudo aticonfig --overlay-type=Xv<br />
</pre><br />
*Note: Alternative in the overlay-type to "Xv" can be "opengl" or "disable" if the TV-out makes problems in videos.<br />
<br />
====Alternative: Configure the Driver, The Manual Way:====<br />
An alternative to the "''sudo aticonfig''" commands is to edit "''/etc/X11/xorg.conf''" and change the "Device" section for the video card as shown below. This way you won't lose your old settings.<br />
<pre><br />
gksu gedit /etc/X11/xorg.conf<br />
</pre><br />
<pre><br />
Section "Device"<br />
[...]<br />
# Driver "vesa"<br />
Driver "fglrx"<br />
Option "VideoOverlay" "on"<br />
Option "OpenGLOverlay" "off"<br />
[...]<br />
EndSection<br />
</pre><br />
<br />
<br />
==== TV - Out ====<br />
The composite TV-Out is not working simultaneously with the VGA on my System. To use it I have turned the VGA off and only the TV on. Attention! This command turns off your Monitor!!<br />
<pre><br />
sudo aticonfig --enable-monitor=tv<br />
</pre><br />
To change back to VGA:<br />
<pre><br />
sudo aticonfig --enable-monitor=crt1<br />
</pre><br />
Some have had luck with both mirrored.<br />
<pre><br />
sudo aticonfig --force-monitor=crt1<br />
sudo aticonfig --enable-monitor=crt1,tv<br />
</pre><br />
reboot after that and it should mirror the CRT1 onto the TV.<br />
<br />
===Finish the Installation===<br />
Now save any open document and reboot your system:<br />
<pre><br />
sudo shutdown -hr now<br />
</pre><br />
*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><br />
*Note: Another way to reboot:<br />
<pre><br />
sudo reboot<br />
</pre><br />
<br />
== Post-Installation Checks and Tweaks ==<br />
===Verifying===<br />
Run the following command to check its output to ensure the fglrx driver is installed properly:<br />
<br />
<pre><br />
$fglrxinfo <br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI MOBILITY RADEON X300<br />
OpenGL version string: 2.1.7415 Release<br />
</pre><br />
<br />
64bit Users only ( 32bit users can continue to the fglrxinfo test ), after rebooting you may have noticed that you cant open aticonfig, and the fglrxinfo test below may not show ati in the info from the test, to fix this in terminal do the following command<br />
<pre><br />
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1<br />
</pre><br />
<br />
<br />
The <code>OpenGL vendor string</code> should read '''ATI''' and not '''Mesa'''.<br />
<br />
'''If it still says ''Mesa'' and not ''ATI'', even after re-enabling the driver from the Restricted-manager:'''<br />
You can try the following:<br />
:*<pre>$ less /var/log/Xorg.0.log |grep EE</pre> if this command returns <code>(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work</code> then remove the kernel module and reinstall it.<br />
:: <pre>$ sudo dkms remove -m fglrx -v 8.471 --all</pre><br />
<br />
:*Remove all the packages provided by the <code>xserver-xorg-video-all</code> meta-package (search for it using Synaptic or Adept), then restart the machine. The X Server should now use the new fglrx driver by force (provided the driver is being used in ''xorg.conf'').<br />
::If you can't log in after this, you'll have to log in to a terminal in the login screen, and reinstall the <code>xserver-xorg-video-all</code> package. Your problem is probably somewhere else. (taken from [http://ubuntuforums.org/showpost.php?p=3655658&postcount=139]).<br />
<br />
:*Remove the package xserver-xgl. <br />
::'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running<br />
::<pre>DISPLAY=:0 glxinfo | grep render</pre><br />
::If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])<br />
::'''Warning:''' This might make your compiz stop working as it is configured to use XGl. A solution might be to run the Envy script in order to configure compiz.<br />
<br />
Note: Here is the [[glxinfo]] of a good install (for those interested).<br />
<br />
=== Enable laptop mode on battery power ===<br />
<br />
Enabling laptop mode on battery power gives you much better battery life, however be aware that sometimes it causes odd hangs.<br />
<br />
Switch ENABLE_LAPTOP_MODE to true <br />
{{Box File|/etc/default/acpi-support|<br />
<pre><br />
# Switch to laptop-mode on battery power - off by default as it causes odd<br />
# hangs on some machines<br />
ENABLE_LAPTOP_MODE=true<br />
</pre><br />
}}<br />
<br />
Switch FGLRX_ACPI_SWITCH_POWERSTATES to true<br />
{{Box File|/etc/default/fglrx|<br />
<pre><br />
# Uncomment the next line to enable powerstate switching on ACPI<br />
# events for lid open/close and AC adapter on/off<br />
FGLRX_ACPI_SWITCH_POWERSTATES=true<br />
</pre><br />
}}<br />
<br />
I like to develop my sites first on my lloschoat and then upload to my server but the same procedure should apply both ways:1. Open your phpMyAdmin of your lloschoat;2. Click on your database name on the left sidebar;3. click on "export" tab;4. Check the "Add drop table" and the "save as file".5. Click "go" on the far right and save to your computer.6. open the file in a text editor and replace all occurrences of your site URL with your Localhost dir path.9. Import the edited file to your database on your local host with phpMyAdmin. Was this answer helpful?<br />
<br />
==Specific Issues==<br />
<br />
Your awnser was just what I needed. Its made my day!<br />
<br />
=== Suspend/Hibernation work with 7.12===<br />
<br />
With Gutsy release, there was a big problem using the ATI proprietary drivers. The Suspend/Hibernate function stopped working. The problem was due to the new SLUB allocator incorporated in 2.6.22 / 2.6.23 Kernel. <br />
<br />
'''The problem has been solved in the AMD Catalyst 7.12 driver release.'''<br />
'''UPDATE: The problem has NOT been solved in the AMD Catalyst 7.12 driver release.'''<br />
<br />
Suspend/hibernate is not working for FireGL 5250.<br />
For FireGL 5200, suspend works with the 7.12 fglrx kernel module loaded (which did not work before this release) , but does not work if X is running.<br />
<br />
For Thinkpad T60 with ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:<br />
<br />
SAVE_VBE_STATE=false<br />
<br />
POST_VIDEO=false<br />
<br />
Even with the above settings (like POST_VIDEO=false, etc.) my ASUS Z96J with an X1600 does not suspend. <br />
<br />
This bug has been a serious issue for several months now. There is a lot of frustration over this, because Ubuntu/Canonical has not been helpful. They've said things like suggesting not using fglrx (thanks a lot, that really helps).<br />
<br />
Current status on this bug can be found here: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/121653/<br />
<br />
===If you get /usr/X11R6/lib/modules/dri/fglrx_dri.so not found===<br />
<br />
sudo ln -s /usr/lib/ /usr/X11R6/lib/modules<br />
<br />
It may be necessary to create the /usr/X11R6/lib directory first:<br />
<br />
sudo mkdir /usr/X11R6/lib<br />
<br />
===If you get /usr/X11R6/lib64/modules/dri/fglrx_dri.so not found===<br />
<br />
sudo ln -s /usr/lib/ /usr/X11R6/lib64/modules<br />
<br />
===Segmentation Fault with glxinfo/fglrxinfo===<br />
If <code>fglrxinfo</code> or <code>glxinfo</code> returns a Segmentation fault like this:<br />
<pre><br />
$ fglrxinfo<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon Xpress Series<br />
OpenGL version string: 1.4 (2.1.7170 Release)<br />
<br />
Segmentation fault<br />
</pre><br />
<br />
Set output of libGL to verbose with<br />
<pre>$ export LIBGL_DEBUG=verbose</pre><br />
<br />
Run <code>fglrxinfo</code> or <code>glxinfo</code> again<br />
<pre>libGL: XF86DRIGetClientDriverName: 8.44.3 fglrx (screen 0)<br />
libGL: OpenDriver: trying /usr/lib/dri/fglrx_dri.so<br />
libGL error: dlopen /usr/lib/dri/fglrx_dri.so failed (/usr/lib/dri/fglrx_dri.so: cannot open shared object file: Permission denied)<br />
libGL error: unable to load driver: fglrx_dri.so<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon Xpress Series<br />
OpenGL version string: 1.4 (2.1.7170 Release)<br />
<br />
Segmentation fault</pre><br />
<br />
Don't know if its always fglrx_dri.so, but the fix is to add read permissions to the file.<br />
<br />
Check if read permission is not there<br />
<pre>ls -l /usr/lib/dri/ |grep fglrx_dri<br />
-rw-rw---- 1 root root 17462688 2008-01-13 17:42 fglrx_dri.so<br />
</pre><br />
<br />
Add read permission<br />
<pre>$ sudo chmod +r /usr/lib/dri/fglrx_dri.so</pre><br />
<br />
Check read permission<br />
<pre>ls -l /usr/lib/dri/ |grep fglrx_dri<br />
-rw-rw-r-- 1 root root 17462688 2008-01-13 17:42 fglrx_dri.so<br />
</pre><br />
<br />
Now I know who the brainy one is, Ill keep lokinog for your posts.<br />
<br />
=== Monitor detection (1680x1050 Resolution Issue)--- SOLVED ===<br />
<br />
As specified in the release notes, "Connecting a display device that supports 1680x1050 to a system running Linux may result in a<br />
maximum display resolution of 1280x1024 only being available". (from [http://ubuntuforums.org/showthread.php?t=645974 thread])<br />
<br />
['''It works with the latest driver''']<br />
<br />
Fglrx driver does not detect some monitors correctly, so you have to do it manually (google about your monitor spec with keyword: xorg.conf).<br />
<br />
'''For example:''' Samsung 205BW 1680x1050 monitor needs manually set: <br />
{{Box File|/etc/X11/xorg.conf|<br />
<pre><br />
Section "Monitor"<br />
Option "DPMS"<br />
Identifier "samsung-monitor"<br />
VendorName "Samsung"<br />
ModelName "SyncMaster 205BW"<br />
HorizSync 31.4 - 80.0<br />
VertRefresh 56.000 - 75.000<br />
Modeline "1680x1050" 146.25 1680 1784 1960 2240 1050 1053 1059 1089<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "samsung-screen"<br />
Device "samsung-device"<br />
Monitor "samsung-monitor"<br />
Defaultdepth 24<br />
SubSection "Display"<br />
Depth 24<br />
Modes "1680x1050"<br />
EndSubSection<br />
EndSection<br />
</pre><br />
}}<br />
<br />
<br />
This has made my day. I wish all positngs were this good.<br />
<br />
=== Hang at logout ===<br />
<br />
If you experience hangs when logging out (of X) try disabling atieventsd with this command:<br />
<br />
<pre>sudo /usr/sbin/update-rc.d -f atieventsd remove</pre><br />
<br />
== Revert to Xorg driver ==<br />
<br />
If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing<br />
<pre>sudo dpkg-reconfigure xserver-xorg</pre><br />
and selecting the "ati" driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup. <br />
<br />
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:<br />
<br />
<pre>sudo apt-get install --reinstall libgl1-mesa-glx</pre><br />
<br />
==See Also==<br />
*[[Frequently Asked Questions]]<br />
*[[Performance Issues]]<br />
*[[Troubleshooting]]<br />
<br />
[[Category:Installation Documentation]]</div>63.138.193.130