http://wiki.cchtml.com/api.php?action=feedcontributions&user=178.168.82.88&feedformat=atomcchtml.com - User contributions [en]2024-03-29T15:14:05ZUser contributionsMediaWiki 1.39.4http://wiki.cchtml.com/index.php?title=Troubleshooting&diff=10446Troubleshooting2014-04-06T13:23:30Z<p>178.168.82.88: wDtYKy Really enjoyed this post.Really thank you! Really Cool.</p>
<hr />
<div>wDtYKy Really enjoyed this post.Really thank you! Really Cool.<br />
<br />
==X Server Related Issues==<br />
<br />
This "free sharing" of information seems too good to be true. Like communism.<br />
<br />
===X Server freeze upon lockscreen/lid-close when Intel iGPU selected===<br />
<br />
On a Haswell system with an Intel HD 4400 as the integrated card in<br />
a hybrid system X freezes (moveable mouse cursor but either black screen <br />
or frozen image of desktop at time of freeze) often when the user locks the screen<br />
(inactivity or otherwise) or closes the lid. The desktop (in 13.10 at least)<br />
can be recovered by switching to a tty and back( e.g. ctrl+alt+fn1, followed<br />
by ctl+alt+fn7). In 12.04 I needed to restart completely from tty.<br />
<br />
This bug occurs because pxpress loads the intel driver with the <br />
"AccelMethod" "UXA" option. You can verify this is the cause<br />
by using a minimal (Intel only) `xorg.conf`<br />
(even before fglrx drivers are installed) with just<br />
<br />
<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "AccelMethod" "UXA" # (mode fglrx uses) I can see the bug<br />
# Option "AccelMethod" "SNA" #(default) no bug!<br />
EndSection<br />
<br />
<br />
<br />
and you should reproduce the bug with a few attempts at closing lid/locking screen.<br />
Whereas with the change to ` Option "AccelMethod" "SNA"` there is no bug <br />
anymore ("SNA" is the default anyway).<br />
<br />
'''How to fix'''<br />
<br />
Create (or edit) the DRI config file `~/.drirc` containing<br />
<br />
<br />
<br />
<device screen="0" driver="dri2"><br />
<application name="Default"><br />
<option name="vblank_mode" value="0"/><br />
</application><br />
</device><br />
<br />
<br />
This turns off "vsync" for the Intel card (the mode that attempts to make your gfx card sync its framerate<br />
with that of the display to avoid tearing, rather than racing ahead at its intrinsic higher framerate).<br />
<br />
Now even when pxpress loads the intel driver in "UXA" mode, the bug should not be reproducible.<br />
<br />
It would be a better solution if it were possible to tell pxpress to load intel<br />
driver with SNA mode directly.<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 />
=== [SOLVED] RadeonHD6670 & Catalyst 13.4 : X server crash ( segmentation fault after __driCreateNewScreen in fglrx_dri.so ) / KMS working ===<br />
<br />
-----------------------------------------------------------------------------------------------<br />
Computer<br />
-----------------------------------------------------------------------------------------------<br />
<pre><br />
Linux <br />
Debian Wheezy + AMD installer<br />
Kernel <br />
3.2.46 #1 SMP Wed Aug 21 11:01:42 CEST 2013 x86_64 GNU/Linux<br />
ACPI disabled<br />
AMD TURKS firmwares included<br />
Desktop<br />
Motherboaord ASUS P5KPL - 4GB RAM<br />
Intel E8500 3.16GHz <br />
</pre><br />
------------------------------------------------------------------------------------------------<br />
BUG trace in syslog<br />
------------------------------------------------------------------------------------------------<br />
<pre><br />
(...)<br />
ukiDynamicMajor: found major device number 252<br />
[ 304.303] ukiDynamicMajor: found major device number 252<br />
[ 304.303] ukiOpenByBusid: Searching for BusID PCI:2:0:0<br />
[ 304.303] ukiOpenDevice: node name is /dev/ati/card0<br />
[ 304.303] ukiOpenDevice: open result is 12, (OK)<br />
[ 304.303] ukiOpenByBusid: ukiOpenMinor returns 12<br />
[ 304.303] ukiOpenByBusid: ukiGetBusid reports PCI:2:0:0<br />
[ 304.346] <br />
[ 304.346] Backtrace:<br />
[ 304.346] 0: /usr/bin/Xorg (xorg_backtrace+0x36) [0x7faadd5d1d06]<br />
[ 304.346] 1: /usr/bin/Xorg (0x7faadd453000+0x182859) [0x7faadd5d5859]<br />
[ 304.346] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7faadc77b000+0xf030) [0x7faadc78a030]<br />
[ 304.346] 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7faadb484000+0x11fc45) [0x7faadb5a3c45]<br />
[ 304.346] 4: /usr/lib/dri/fglrx_dri.so (__driCreateNewScreen_20050727+0x56) [0x7faad542e0c6]<br />
[ 304.346] 5: /usr/lib/xorg/modules/extensions/libglx.so (0x7faad9d4c000+0x1e0ea) [0x7faad9d6a0ea]<br />
[ 304.346] 6: /usr/lib/xorg/modules/extensions/libglx.so (0x7faad9d4c000+0x1fb05) [0x7faad9d6bb05]<br />
[ 304.346] 7: /usr/bin/Xorg (InitExtensions+0x99) [0x7faadd510889]<br />
[ 304.346] 8: /usr/bin/Xorg (0x7faadd453000+0x41d42) [0x7faadd494d42]<br />
[ 304.346] 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xfd) [0x7faadb4a2ead]<br />
[ 304.346] 10: /usr/bin/Xorg (0x7faadd453000+0x4219d) [0x7faadd49519d]<br />
[ 304.346] <br />
[ 304.346] Segmentation fault at address 0x7fff00000014<br />
[ 304.346] <br />
Fatal server error:<br />
[ 304.346] Caught signal 11 (Segmentation fault). Server aborting<br />
</pre><br />
<br />
The solution is : downgrade AMD driver.<br />
<br />
I could these AMD driver working:<br />
AMD Catalyst installer (legacy) 13.1 ( installer says version 8.97.2 )<br />
AMD Catalyst installer (non-legacy) 13.1 ( installer says version 9.012 ) <br />
<br />
-> both seems to be the same, kernel module version reported in Xorg.0.log is always 8.97.2 !<br />
<br />
They both sticks "AMD Unsupported hardware" in the low-right corner of my monitor ( which can be removed easily ).<br />
<br />
Seems that from version 13.4, the software was deeply modified, that make it buggy.<br />
<br />
<hr><br />
KMS works well ( module radeon.ko ). I have frame buffer kernel module ( radeonfb.ko ) built<br />
but I didnt try for instant to load it simultaneously with KMS.<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 />
==References==<br />
<references/><br />
<br />
[[Category:Installation Documentation]]<br />
<br />
<br />
[[Category:NeedsUpdating]]<br />
{{VCT}}</div>178.168.82.88http://wiki.cchtml.com/index.php?title=Ubuntu_Raring_Installation_Guide&diff=10445Ubuntu Raring Installation Guide2014-04-06T07:31:12Z<p>178.168.82.88: LMnl5V Im obliged for the post.Really looking forward to read more. Really Great.</p>
<hr />
<div> __TOC__<br />
<br />
LMnl5V Im obliged for the post.Really looking forward to read more. Really Great.<br />
<br />
= Updated Open Source Driver PPA's =<br />
* '''"Ubuntu-X"''' : This PPA offers the latest stable releases of video driver-related components. Follow the instructions at: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates<br />
* '''Xorg-edgers''': This bleeding-edge PPA offers video driver-related components straight from their code (git) repositories. Follow the instructions at: https://launchpad.net/~xorg-edgers/+archive/ppa<br />
<br />
= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =<br />
<br />
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;" <br />
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | <font size="-1">'''ATTENTION RADEON USERS'''</font> <br />
|- <br />
| <br />*PLEASE READ FIRST!<br />
'''Which Radeon cards are no longer supported by ATI's Catalyst?'''<br />
<br /><br /><br />
|}<br />
<br />
'''ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500, Mobility RadeonHD 2300'''<br />
If your card is on that list, you are limited to open-source drivers on Ubuntu Lucid/10.04 (and later). If you really need the proprietary Catalyst/fglrx driver, you will have to use an older Linux distribution, such as Debian Lenny/5.0.x or Ubuntu Hardy/8.04.x.<br />
NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Precise (or anything later than Lucid/10,04)! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers.<br />
<br />
'''ATI RadeonHD 2x00 - 4xx0 cards'''<br />
If you have one of these cards, you do have the option of using the Catalyst Legacy driver, but only if you downgrade your Xserver version (the Catalyst Legacy driver does not support the kernel version (3.5) or the Xserver version (1.13) that Ubuntu Quantal/12.10 uses).<br />
This can be done really easily and automaticly (downgrading & installing) by following the instructions given at [[https://launchpad.net/~makson96/+archive/fglrx]]. This PPA downgrades the Xserver and install a patched version of fglrx that supports kernel version 3.5 of Ubuntu Quantal.<br />
<br />
== Installing Catalyst Manually (from AMD/ATI's site) ==<br />
<br />
I recommend copying and pasting the commands to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl '''+ Shift''' + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).<br />
<br />
===''Before you start''===<br />
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section. Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).<br />
or Applications->Ubuntu Software Center->Edit->Software sources->Other software: check canonical partners.<br />
<br />
Install the prerequisite packages:<br />
sudo apt-get install build-essential cdbs dh-make dkms execstack dh-modaliases linux-headers-generic fakeroot libqtgui4 devscripts<br />
<br />
''If you are using the x86_64 architecture (64 bit)'':<br />
sudo apt-get install lib32gcc1<br />
<br />
Create a directory for the build environment and move to that directory<br />
mkdir catalyst{{Catalystversion}} && cd catalyst{{Catalystversion}}<br />
<br />
===''Download the latest Catalyst package.''===<br />
This package contains both the 32-bit and 64-bit driver.<br />
<br />
wget <nowiki>--referer='http://support.amd.com/en-us/download/desktop?os=Linux+x86_64' http://www2.ati.com/drivers/linux/amd-</nowiki>{{Catalystdashversion}}-linux-x86.x86_64.zip<br />
unzip amd-{{Catalystdashversion}}-linux-x86.x86_64.zip<br />
chmod +x amd-{{Catalystdashversion}}-linux-x86.x86_64.run<br />
<br />
===''Create and install .deb packages.'' ===<br />
sudo ./amd-{{Catalystdashversion}}-linux-x86.x86_64.run --buildpkg Ubuntu/raring<br />
sudo dpkg -i fglrx*.deb<br />
<br />
===''In case of failure:''===<br />
<br />
Remember these steps before you reboot your computer.<br />
<br />
If the X server fails to start, switch to a new TTY using ctrl+alt+F2. Log in, and attempt to start the X server.<br />
<br />
sudo startx<br />
<br />
If it fails to start, you will likely see a stacktrace, and immediately above it will be something along the lines of "Could not stat /usr/lib64/fglrx/switchlibGL" which means that you failed to copy the executables properly. Ctrl+c, and immediately copy the switchlibGL and switchlibglx executables to the fglrx folder in /usr/lib64/ or /usr/lib32/. <br />
<br />
If all else fails, revert your xorg.conf and reboot.<br />
<br />
sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf<br />
<br />
This should return your original display.<br />
<br />
==''Generate a new /etc/X11/xorg.conf file''==<br />
<br />
Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.<br />
<br />
=== Generic Config ===<br />
This will work for most people:<br />
sudo amdconfig --initial -f<br />
<br />
=== Minimal Config ===<br />
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that's not fully supported by amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:<br />
<br />
Section "Device"<br />
Identifier "ATI radeon 6870"<br />
Driver "fglrx"<br />
EndSection<br />
<br />
=== X2/Dual GPU Cards ===<br />
If you have an X2 card (e.g. 5970), use... '''!!Do not use for two separate cards in crossfire!!'''<br />
sudo amdconfig --initial -f --adapter<nowiki>=</nowiki>all<br />
<br />
=== Dual/Multi Monitors ===<br />
If you have a dual monitor display (also known as "Big Desktop"), use:<br />
sudo amdconfig --initial -f<br />
sudo amdconfig --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"<br />
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553. Be advised that you may need to manually set the correct refresh rate for your second monitor through catalyst.<br />
<br />
==''Force use of the new xorg.conf (if necessary)''==<br />
Some people find that changes to xorg.conf don't get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:<br />
<br />
sudo amdconfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
<br />
==''Test your installation''==<br />
NOTE: if you don't reboot first, fglrxinfo gives an error message.<br />
Reboot the computer and type<br />
fglrxinfo<br />
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 12-3 and a RadeonHD 4550 returns:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)<br />
OpenGL version string: 3.3.11566 Compatibility Profile Context (This line may be different depending on what graphics card and <br />
Catalyst version you are using.)<br />
</pre><br />
Now, try:<br />
fgl_glxgears<br />
If you experience issues or a hang, you may need to disable fast TLS.<br />
sudo amdconfig --tls=0<br />
<br />
== Installing Catalyst Manually (from AMD/ATI's site) BETA/EXPERIMENTAL ==<br />
<br />
I recommend copying and pasting the commands to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl '''+ Shift''' + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).<br />
<br />
===''Before you start''===<br />
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section. Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).<br />
or Applications->Ubuntu Software Center->Edit->Software sources->Other software: check canonical partners.<br />
<br />
Install the prerequisite packages:<br />
sudo apt-get install build-essential cdbs dh-make dkms execstack dh-modaliases linux-headers-generic fakeroot libqtgui4<br />
<br />
''If you are using the x86_64 architecture (64 bit)'':<br />
sudo apt-get install lib32gcc1<br />
<br />
Create a directory for the build environment and move to that directory<br />
mkdir catalyst13.11beta1 && cd catalyst13.11beta1<br />
<br />
===''Download the latest Catalyst package.''===<br />
This package contains both the 32-bit and 64-bit driver.<br />
<br />
wget http://www2.ati.com/drivers/beta/amd-catalyst-13.11-betav1-linux-x86.x86_64.zip<br />
unzip amd-catalyst-13.11-betav1-linux-x86.x86_64.zip<br />
chmod +x amd-catalyst-13.11-beta1-linux-x86.x86_64.run<br />
<br />
===''Create and install .deb packages.'' ===<br />
sudo ./amd-catalyst-13.11-beta1-linux-x86.x86_64.run --buildpkg Ubuntu/raring<br />
sudo dpkg -i fglrx*.deb<br />
<br />
If building .deb packages fails, there is also an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation]<br />
<br />
When running the dpkg line, you may receive an error like:<br />
Errors were encountered while processing:<br />
fglrx<br />
fglrx-amdcccle<br />
fglrx-dev<br />
<br />
They may have attempted to install out of order. Install them individually as:<br />
<br />
sudo dpkg -i fglrx_*.deb<br />
sudo dpkg -i fglrx-amdcccle*.deb <br />
sudo dpkg -i fglrx-dev*.deb<br />
<br />
You should see a successful result similar to:<br />
<br />
user@user-ubuntu:~# sudo dpkg -i fglrx_9.010-0ubuntu1_amd64.deb <br />
(Reading database ... 168748 files and directories currently installed.)<br />
Preparing to replace fglrx 2:9.010-0ubuntu1 (using fglrx_9.010-0ubuntu1_amd64.deb) ...<br />
Removing all DKMS Modules<br />
Error! There are no instances of module: fglrx<br />
9.010 located in the DKMS tree.<br />
Done.<br />
Unpacking replacement fglrx ...<br />
Setting up fglrx (2:9.010-0ubuntu1) ...<br />
update-alternatives: using /usr/lib/fglrx/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode<br />
update-alternatives: using /usr/lib/fglrx/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode<br />
update-initramfs: deferring update (trigger activated)<br />
Loading new fglrx-9.010 DKMS files...<br />
First Installation: checking all kernels...<br />
Building only for 3.5.0-17-generic<br />
Building for architecture x86_64<br />
Module build for the currently running kernel was skipped since the<br />
kernel source for this kernel does not seem to be installed.<br />
update-initramfs: deferring update (trigger activated)<br />
Processing triggers for ureadahead ...<br />
Processing triggers for bamfdaemon ...<br />
Rebuilding /usr/share/applications/bamf.index...<br />
Processing triggers for initramfs-tools ...<br />
update-initramfs: Generating /boot/initrd.img-3.5.0-17-generic<br />
Processing triggers for libc-bin ...<br />
ldconfig deferred processing now taking place<br />
<br />
user@user-ubuntu:~# sudo dpkg -i fglrx-amdcccle_9.010-0ubuntu1_amd64.deb <br />
(Reading database ... 168748 files and directories currently installed.)<br />
Preparing to replace fglrx-amdcccle 2:9.010-0ubuntu1 (using fglrx-amdcccle_9.010-0ubuntu1_amd64.deb) ...<br />
Unpacking replacement fglrx-amdcccle ...<br />
Setting up fglrx-amdcccle (2:9.010-0ubuntu1) ...<br />
<br />
user@user-ubuntu:~# sudo dpkg -i fglrx-dev_9.010-0ubuntu1_amd64.deb <br />
(Reading database ... 168748 files and directories currently installed.)<br />
Preparing to replace fglrx-dev 2:9.010-0ubuntu1 (using fglrx-dev_9.010-0ubuntu1_amd64.deb) ...<br />
Unpacking replacement fglrx-dev ...<br />
Setting up fglrx-dev (2:9.010-0ubuntu1) ...<br />
<br />
===''In case of failure:''===<br />
<br />
Remember these steps before you reboot your computer.<br />
<br />
If the X server fails to start, switch to a new TTY using ctrl+alt+F2. Log in, and attempt to start the X server.<br />
<br />
sudo startx<br />
<br />
If it fails to start, you will likely see a stacktrace, and immediately above it will be something along the lines of "Could not stat /usr/lib64/fglrx/switchlibGL" which means that you failed to copy the executables properly. Ctrl+c, and immediately copy the switchlibGL and switchlibglx executables to the fglrx folder in /usr/lib64/ or /usr/lib32/. <br />
<br />
If all else fails, revert your xorg.conf and reboot.<br />
<br />
sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf<br />
<br />
This should return your original display.<br />
<br />
==''Generate a new /etc/X11/xorg.conf file''==<br />
<br />
Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.<br />
<br />
=== Generic Config ===<br />
This will work for most people:<br />
sudo amdconfig --initial -f<br />
<br />
=== Minimal Config ===<br />
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that's not fully supported by amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:<br />
<br />
Section "Device"<br />
Identifier "ATI radeon 6870"<br />
Driver "fglrx"<br />
EndSection<br />
<br />
=== X2/Dual GPU Cards ===<br />
If you have an X2 card (e.g. 5970), use... '''!!Do not use for two separate cards in crossfire!!'''<br />
sudo amdconfig --initial -f --adapter<nowiki>=</nowiki>all<br />
<br />
=== Dual/Multi Monitors ===<br />
If you have a dual monitor display (also known as "Big Desktop"), use:<br />
sudo amdconfig --initial -f<br />
sudo amdconfig --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"<br />
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553. Be advised that you may need to manually set the correct refresh rate for your second monitor through catalyst.<br />
<br />
==''Force use of the new xorg.conf (if necessary)''==<br />
Some people find that changes to xorg.conf don't get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:<br />
<br />
sudo amdconfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
<br />
==''Test your installation''==<br />
NOTE: if you don't reboot first, fglrxinfo gives an error message.<br />
Reboot the computer and type<br />
fglrxinfo<br />
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 12-3 and a RadeonHD 4550 returns:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)<br />
OpenGL version string: 3.3.11566 Compatibility Profile Context (This line may be different depending on what graphics card and <br />
Catalyst version you are using.)<br />
</pre><br />
Now, try:<br />
fgl_glxgears<br />
If you experience issues or a hang, you may need to disable fast TLS.<br />
sudo amdconfig --tls=0<br />
<br />
===''Just in case''===<br />
Write down or remember this series of Alt+PrntScr key combinations, just in case your screen should go black and Ctrl+Alt+F1 and Ctrl+Alt+Backspace doesn't work.<br />
<br />
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b<br />
<br />
These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring".<br />
<br />
An alternative would be to hold down Ctrl+Alt+SysRq (SysRq is usually the same key as PrintScreen) and type very slowly R E I S U B. A way to remember this is by inverting the word: "BUSIER" or remembering a phrase: "Restart Even If System Utterly Broken". This would also safely shutdown the system.<br />
<br />
= Hardware Video Decode Acceleration (EXPERIMENTAL) =<br />
<br />
== Using XBMC player (XvBA) ==<br />
<br />
XBMC has added support for accelerating video using XvBA/libxvba directly, but the support is currently not in the xbmc package in Ubuntu's repositories. To install the XvBA-enabled version of xbmc:<br />
<br />
sudo apt-add-repository ppa:wsnipex/xbmc-xvba<br />
sudo apt-get update<br />
sudo apt-get install xbmc<br />
<br />
== Using the xvba-va Driver (VA-API) ==<br />
NOTE: The VA-API wrapper for XvBA has been dead code for a while now. It will probably give you some acceleration of HD formats, but using the previously mentioned xbmc PPA is a better solution.<br />
<br />
This is confirmed to work for newer RadeonHD GPU's (those with UVD2). If you have a RadeonHD 4000-series or newer, you have UVD2. To see the complete list: http://en.wikipedia.org/wiki/Unified_Video_Decoder#UVD_enabled_GPUs<br />
<br />
sudo apt-get install xvba-va-driver libva-glx1 libva-x11-1 vainfo<br />
vainfo<br />
<br />
vainfo should return something like the following (and no errors):<br />
libva: libva version 0.32.0<br />
Xlib: extension "XFree86-DRI" missing on display ":0.0".<br />
libva: va_getDriverName() returns 0<br />
libva: Trying to open /usr/lib/dri/fglrx_drv_video.so<br />
libva: va_openDriver() returns 0<br />
vainfo: VA API version: 0.32<br />
vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8<br />
vainfo: Supported profile and entrypoints<br />
VAProfileH264High : VAEntrypointVLD<br />
VAProfileVC1Advanced : VAEntrypointVLD<br />
<br />
If vainfo returns an error, you may need to create a symlink:<br />
<br />
sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so #for 64-bit<br />
sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/dri/fglrx_drv_video.so #for 32-bit<br />
<br />
Once you've confirmed that vainfo is correct, you can test video playback. A good test player for va-api is VLC. You can enable va-api in Tools -> Preferences -> Input and Codecs. Check the box named "Use GPU acceleration (experimental)" and then restart VLC.<br />
<br />
<br />
== Other ==<br />
There is possibility to enable > H.264 Level 5.1 decoding in the driver which "has been in the driver for some time but not enabled by default"<br />
<br />
sudo amdconfig --set-pcs-u32=MCIL,HWUVD_H264Level51Support,1<br />
<br />
or<br />
<br />
sudo service lightdm stop<br />
sudo cp -p /etc/ati/amdpcsdb /etc/ati/amdpcsdb.bak<br />
sudo sed -i '/UvdEnabled=V1/ a HWUVD_H264Level51Support=V1' /etc/ati/amdpcsdb<br />
sudo reboot<br />
<br />
=Updating Catalyst/fglrx=<br />
<br />
DO NOT try to install a new version over an old one. Follow the 'Removing Catalyst/fglrx' section below to remove your existing driver, and then you can start at 'Downloading the latest Catalyst' to install the new one.<br />
<br />
=Removing Catalyst/fglrx=<br />
The uninstall script in the first command will only exist if you downloaded the drivers and installed them directly (rather than building packages as this guide does). Skip the first command if it does not exist.<br />
sudo sh /usr/share/ati/fglrx-uninstall.sh<br />
sudo apt-get remove --purge fglrx*<br />
<br />
If you plan on using open-source drivers, you will need to reinstall some packages because Catalyst overwrites or diverts some key 3D libraries with proprietary versions. For more information on this issue, see [https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver this Ubuntu wiki page]<br />
sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon<br />
sudo apt-get install xserver-xorg-video-ati<br />
sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core<br />
sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup<br />
sudo rm -rf /etc/ati<br />
<br />
If you receive<br />
<br />
$ E: Internal Error, No file name for libgl1-mesa-dri<br />
<br />
Change the third command above to:<br />
<br />
sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core<br />
<br />
= Issues =<br />
<br />
== Video Tearing ==<br />
<br />
AMD/ATI claims that the "Tear Free Video" option is enabled by default, but that wasn't the case with Catalyst 12-3 installed on Kubuntu 12.04.<br />
If you're having issues with tearing, make sure that "Tear Free Video" is on. You can find this option in the Catalyst Control Center under 'Display Options' or you can use the following command:<br />
sudo amdconfig --sync-video=on<br />
The option will not take effect until you restart X (i.e. log out).<br />
<br />
If you're using compositing, you should also make sure that vsync is enabled in the compositor's settings. I found that vsync was enabled by default, but here are the appropriate settings should you want to experiment.<br />
<br />
=== kwin === <br />
You can enable vsync for kwin in System Settings -> Desktop Effects -> Advanced tab<br />
<br />
=== Compiz (Unity/GNOME-Shell) ===<br />
TODO: See if there's a friendlier way to make sure vsync is enabled without installing ccsm.<br />
<br />
Install the compiz settings manager: <br />
sudo apt-get install compizconfig-settings-manager<br />
ccsm<br />
<br />
The 'Sync to Vblank' is found in the 'OpenGL' subsection of the 'General' group<br />
<br />
== Hybrid Graphics and Catalyst==<br />
<br />
There are two basic types of hybrid designs. Older hybrid systems use a multiplexor (mux) to switch between GPU's. Newer systems (those with PowerXpress >= 4.0) are muxless. As far as I can tell, PowerXpress 4.0 started with RadeonHD 6000-series GPU's, and systems with older ATI GPU's have a mux, but don't quote that.<br />
<br />
=== ATI/ATI Hybrids ===<br />
As of Catalyst 11-8, switching between two ATI cards (and maybe Intel/ATI muxless too?) is supposed to be doable, though it's not clear if that applies to all ATI/ATI hybrids or only the muxless ones. One would use amdconfig's PowerXpress options to switch back and forth between the integrated and discrete cards, like so:<br />
<br />
amdconfig --pxl # List current activated GPU<br />
sudo amdconfig --px-dgpu # Activate discrete GPU (High-Performance mode), must re-start X to take effect<br />
sudo amdconfig --px-igpu # Activate integrated GPU (Power-Saving mode), must re-start X to take effect<br />
<br />
After switching, one would log out and back in to restart X.<br />
<br />
=== Intel/ATI Hybrids ===<br />
<br />
By using the officially provided drivers, there are three problems ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1068404 #1068404]):<br />
: An incompatibility problem between intel and fglrx drivers (This gives segmentation fault at X server)<br />
: An incompatibility problem between intel and fglrx drivers that gives an error related to allocation of resources in Xorg log file.<br />
: Some paths missing for openGL operation of the fglrx driver (This prevents applications that require direct rendering, e.g. Unity/games/etc, from loading correctly)<br />
<br />
If you follow the instructions described in the [https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND Binary Driver HOWTO], you should get functional configuration. <br />
<br />
If however you suffer from the problem related to intel driver not able to allocate resources, you need to install the older intel driver 2.20.2-1ubuntu1 which can be found at https://launchpad.net/ubuntu/quantal/+source/xserver-xorg-video-intel<br />
<br />
There is still another bug if you use the integrated GPU (Intel), making the X server crashing ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1088220 #1088220] )<br />
<br />
A workaround for now is to use the discrete GPU (ATI)<br />
<br />
<br />
For more information you may want to follow this [http://ubuntuforums.org/showthread.php?p=12324761#post12324761 forum topic]<br />
<br />
<br />
[http://ubuntuforums.org/showthread.php?t=1930450&page=82&p=12755069#post12755069 This post] got both the integrated (Intel 3rd Gen Core processor Graphics Controller) and discrete (Radeon HD 7670M) to work on Ubuntu 13.04 x64.<br />
<br />
== Build Fails and Log Shows "mixed implicit and normal rules. Stop." ==<br />
<br />
If the installation fails and you find the above message in /var/lib/dkms/fglrx/<version_number>/build/make.log, it may be because you're using a pentium-build wrapper around gcc. See what the following ls command returns:<br />
ls -la /usr/bin/gcc<br />
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.6 in Ubuntu Precise). This should allow you to install fglrx:<br />
sudo ln -sf /usr/bin/gcc-4.6 /usr/bin/gcc<br />
When you're finished installing the driver, return the gcc link to its original value:<br />
sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc<br />
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957<br />
<br />
== "Errors were encountered while processing: fglrx-amdcccle" (on 64-bit systems) ==<br />
Most likely, you probably did not have the ia32-libs-multiarch:i386 lib32gcc1 libc6-i386 packages installed beforehand. If you have a 64 bit install, the above dpkg command may 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, use the following command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:<br />
<br />
sudo apt-get -f install<br />
<br />
Catalyst {{Template:Catalystversion}} on 64-bit systems may require the ''--force-overwrite'' command in the above ''dpkg'' command:<br />
sudo dpkg -i --force-overwrite fglrx*.deb<br />
<br />
== Problems Starting Xserver ==<br />
<br />
If you get a black screen hang, the first thing to check is if xorg.conf is the problem.<br />
<br />
You can disable the xorg.conf with:<br />
sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.disabled<br />
<br />
Reboot and check to see if things work now.<br />
<br />
You can reinstate the file with:<br />
sudo mv /etc/X11/xorg.conf.disabled /etc/X11/xorg.conf<br />
<br />
Before tweaking ACPI settings, try ensuring /dev/null is chmodded to 0666. This intermittently changes when using the nano (and possibly other) editors with sudo and the group/world permissions are unset. This leads to the ATI drivers hanging on boot or otherwise. A quick and dirty init script saved as /etc/init/chmodnull does the trick -<br />
<br />
start on filesystem<br />
<br />
script<br />
chmod 0666 /dev/null<br />
chmod 0666 /lib/udev/devices/null<br />
end script<br />
<br />
This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It's worth noting that I had to disable TLS (amdconfig --tls=0) to get things to stay stable!<br />
<br />
If you've properly installed the driver, but experience problems when starting the X server, such as hanging, black/white/gray screen, distortion, etc., your system BIOS may have a buggy ACPI implementation. To work around, press Ctrl+Alt+F1 to get to a terminal (or failing that, boot to recovery mode) and run:<br />
sudo amdconfig --acpi-services=off<br />
If this method works, you should consider checking your system vendor's BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver's ACPI services.<br />
<br />
== Unsupported Hardware Watermark ==<br />
This can happen if your card's PCI ID wasn't officially certified to work with a particular version of Catalyst. It does not necessarily mean that your card is unsupported, but it does mean that you shouldn't file bugs with that particular card/driver combination. If you installed the driver by downloading it from AMD/ATI, installing a newer version of Catalyst will probably help. <br />
<br />
If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it is possible to work around the issue. First check if AMD's signature file has a proper signature:<br />
<br />
sudo nano /etc/ati/signature<br />
<br />
If the file only contains the word ''UNSIGNED'', replace the line with:<br />
9777c589791007f4aeef06c922ad54a2:ae59f5b9572136d99fdd36f0109d358fa643f2bd4a2644d9efbb4fe91a9f6590a145:f612f0b01f2565cd9bd834f8119b309bae11a1ed4a2661c49fdf3fad11986cc4f641f1ba1f2265909a8e34ff1699309bf211a7eb4d7662cd9f8e3faf14986d92f646f1bc<br />
<br />
Reboot and see if the watermark is gone. If not, try using a control file from a older version of Catalyst than the one you're running:<br />
<br />
cd ~/; mkdir catalyst12.10; cd catalyst12.10/<br />
wget http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-12.10-x86.x86_64.zip<br />
unzip amd-driver-installer-catalyst-12.10-x86.x86_64.zip<br />
chmod +x amd-driver-installer-catalyst-12.10-x86.x86_64.run<br />
./amd-driver-installer-catalyst-12.10-x86.x86_64.run --extract driver<br />
sudo mv /etc/ati/control ~/control.bak<br />
sudo cp driver/common/etc/ati/control /etc/ati<br />
<br />
== Hang at logout ==<br />
<br />
If you experience hangs when logging out (of X) it is probably due to the /etc/ati/authatieventsd.sh script looking for X authorization files in the wrong place when it starts up. You can kill the hanging authatieventsd.sh processes from a console tty to allow the shutdown of the X server.<br />
<br />
Before the following commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do: <br />
(assuming that the installer is in the directory we used to install)<br />
<br />
cd ~/catalyst{{Catalystversion}}<br />
sh amd-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver<br />
sudo cp driver/packages/Ubuntu/dists/quantal/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh<br />
sudo chmod +x /etc/ati/authatieventsd.sh<br />
<br />
This problem can be fixed permanently with:<br />
<br />
sudo mkdir -p /var/lib/xdm/authdir<br />
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles<br />
<br />
If that doesn't work then you can disable atieventsd with this command:<br />
<br />
sudo /usr/sbin/update-rc.d -f atieventsd remove<br />
<br />
You'll have to restart for this to take effect.<br />
<br />
== Can't remove fglrx with dpkg (diversion issue) ==<br />
<br />
If dpkg refuses to remove an fglrx package and complains about a diversion of a file, you might need to manually remove it. For example, if dpkg complains:<br />
<pre>dpkg-divert: mismatch on divert-to<br />
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'<br />
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre><br />
then:<br />
sudo dpkg-divert --remove /usr/lib/libGL.so.1.2<br />
<br />
== This module/version combo is already installed ==<br />
<br />
If you get this error-message, simply uninstall the previous version before installing the new one with:<br />
sudo dkms remove -m fglrx --all<br />
<br />
== New kernel installed? ==<br />
In theory, DKMS should automatically install the fglrx kernel module for your new kernel the first time you boot it. Should you need to manually install it:<br />
sudo dkms build -m fglrx -k `uname -r`<br />
sudo dkms install -m fglrx -k `uname -r`<br />
<br />
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf<br />
<br />
or specify all the correct parameters. For example:<br />
sudo dkms build -m fglrx -v '''9.012''' -k '''3.5.0-22'''-generic<br />
sudo dkms install -m fglrx -v '''9.012''' -k '''3.5.0-22'''-generic<br />
<br />
[[Category:Installation Documentation]]<br />
<br />
== amdconfig not found after installation ==<br />
This scenario is possible when the driver installation has seemingly succeeded and is possibly related to previous fglrx installs, including those through Jockey (i.e. you first used drivers provided by Ubuntu but then upgraded to ones available from AMD's website). When doing amdconfig --initial after driver installation, you might end up not having the amdconfig available at all:<br />
<pre>amdconfig: command not found</pre><br />
After booting you might receive X error '(EE) Failed to load module "fglrx" (module does not exist, 0)'. These do not necessarily indicate that the installation has failed completely. On command line, do<br />
ls /usr/lib/fglrx/bin<br />
and see if the command lists some Ati related programs. If they are listed but not found from /usr/bin, it is possible that the "update-alternatives" fglrx .deb installation does has been ignored. See man update-alternatives for more information about the concept and workings of alternatives. In practice, update-alternatives is supposed to create several symbolic links to the files in the fglrx directory, but it will be ignored if the alternatives for the very related gl_conf entry has been set to manual. Do<br />
update-alternatives --get-selections | grep gl_conf<br />
and see if the mode is manual instead of auto and if mesa is mentioned instead of fglrx in the path that is printed. In this case you need to <br />
sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf<br />
to set fglrx as the active alternative. You can alternatively (no pun intended) and additionally change the gl_conf into automatic mode before the installation this way:<br />
sudo update-alternatives --auto gl_conf<br />
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.<br />
<br />
== "update-alternatives: error" during install ==<br />
During installation you may receive the following message:<br />
<pre>update-alternatives: error: unable to make /usr/lib/xorg/modules/drivers/fglrx_drv.so.dpkg-tmp a symlink to /etc/alternatives/fglrx_drv: No such file or directory</pre><br />
This can be easily solved by creating directory "drivers" under /usr/lib/xorg/modules/<br />
sudo mkdir /usr/lib/xorg/modules/drivers<br />
<br />
== 'Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.' during deb generation ==<br />
During installation you may receive the following message:<br />
<pre>Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.</pre><br />
This can happen when your /tmp folder is mounted with the option "noexec". The noexec is suggested by many howtos regarding Ubuntu on SSD, when placing the /tmp in memory.<br />
A workaround can be found here: [http://serialized.net/2010/03/getting-around-tmpfs-noexec-problems/]<br />
<br />
== Errors during deb generation ==<br />
You may recieve errors if you do not have devscripts, dh-make, execstack and dh-modaliases installed. Run apt-get to install, and the errors go away and the deb is generated correctly.<br />
<br />
If you recieve the error dpkg-buildpackage: not found:<br />
sudo apt-get install devscripts<br />
<br />
If you recieve the error make: dh: command not found:<br />
sudo apt-get install dh-make<br />
<br />
If you recieve the error make: execstack: Command not found:<br />
sudo apt-get install execstack<br />
<br />
If you recieve the error make: dh_modaliases: Command not found:<br />
sudo apt-get install dh-modaliases<br />
<br />
== Black screen after uninstalling old amd drivers ==<br />
Start you computer in recovery mode and exit to root shell.<br />
Remount your partitions in rw mode:<br />
mount -rw -o remount /<br />
...<br />
Go to your download directory and proceed with building and installing the drivers in recovery mode.<br />
All should be fine after a reboot.<br />
<br />
== References ==<br />
<br />
<references/></div>178.168.82.88http://wiki.cchtml.com/index.php?title=SUSE/openSUSE&diff=10444SUSE/openSUSE2014-04-06T02:37:42Z<p>178.168.82.88: f7nEoo Great, thanks for sharing this blog article.Thanks Again.</p>
<hr />
<div>f7nEoo Great, thanks for sharing this blog article.Thanks Again.<br />
<br />
== Installation ==<br />
<br />
===OpenSuse 13.1 auto install Amd Driver (RADEON 5000,6000,7000,8000 & Up Series)===<br />
<br />
===OpenSuse 12.3 auto install Amd Driver (RADEON 5000,6000,7000,8000 & Up Series)===<br />
*Update your system<br />
*Enable Software Source in YaSt<br />
*Click on your RESPECTIVE ARCH below and OPEN with YaSt<br />
<br />
*X86<br />
http://geeko.ioda.net/mirror/amd-fglrx/raw-src/amd-ati-fglrx.ymp<br />
<br />
*X64<br />
http://geeko.ioda.net/mirror/amd-fglrx/raw-src/amd-ati-fglrx64.ymp<br />
<br />
*Generate Config file via console<br />
sudo aticonfig --initial -f<br />
<br />
*reboot & Have fun people!<br />
<br />
--winglman--<br />
<br />
===OpenSuSe 12.2 auto install Amd Driver (RADEON 5000,6000,7000,8000 Series)===<br />
*Update your system<br />
*Click on The "one-click-installer" and open with YaSt<br />
<br />
*32bit http://geeko.ioda.net/mirror/amd-fglrx/ymp/amd-ati-fglrx.ymp<br />
*64bit http://geeko.ioda.net/mirror/amd-fglrx/ymp/amd-ati-fglrx64.ymp<br />
<br />
*XBMC Media Center can be install via package manager with packman repo install<br />
<br />
*Follow instructions then Reboot<br />
*Your done!<br />
*check out packman repo for extra plugins and stuff,<br />
--winglman--<br />
<br />
===OpenSuSe 12.1 (Driver from AMD website) easy way...===<br />
*Download The Latest AMD Driver from ATI/AMD<br />
wget http://www2.ati.com/drivers/linux/amd-driver-installer-12-10-x86.x86_64.zip<br />
<br />
unzip amd-driver-installer-12-10-x86.x86_64.zip<br />
chmod +x amd-driver-installer-9.002-x86.x86_64.run<br />
<br />
*Open software manager in YAST and install 5 packages by hand:<br />
''kernel-devel kernel-desktop-devel gcc gcc-c++ make'' <br /><br />
OR use the terminal and run:<br />
sudo zypper in kernel-devel kernel-desktop-devel gcc gcc-c++ make kernel-syms<br />
*reboot<br />
*'''If radeon driver is active''' you must blacklist it, add this to boot paramaters (during grub startup menu):<br />
radeon.modeset=0 blacklist=radeon 3<br />
*This will disable radeon driver and boot into runlevel 3. SU to get root, run mkinitrd to make sure radeon stays blacklisted.<br />
*(Comment) in case the above method does not help, you may try add to /etc/modprobe.d/50-blacklist.conf the following line<br />
blacklist radeon<br />
<br />
*(Comment) Either way, when your linux booted, you should check whether the radeon kernel module is not loaded, run <br />
lsmod | grep radeon<br />
if nothing comes up you are good to go<br />
*cd to directory where proprietary "amd-driver-installer" is, <br />
type: <br />
sh amd-driver-installer-*.run <br />
*install default (do not generate distibution package)<br />
*verify /usr/share/ati fglrx-install.log, at the end of the file you should see "build succeeded with return value 0 duplicating results into driver repository...done.<br />
*in terminal type: <br />
aticonfig --initial -f<br />
*then run:<br />
/sbin/shutdown -r now<br />
<br />
===To Uninstall===<br />
Open terminal,SU to get root,type:<br />
sh /usr/share/ati/amd-uninstall.sh<br />
<br />
==Video Playback==<br />
Add Packman Repositories<br />
*Open YAST<br />
*Open Software Source,Click add,From URL<br />
*and add this url http://packman.inode.at/suse/openSUSE_12.1<br />
*This will provide extra packages for video playback and other stuff<br />
<br />
<br />
<br />
Good luck,<br />
<br />
winglman<br />
<br />
knowledge is free so share it!<br />
<br />
== ==<br />
===OpenSuSE 11.0 & 11.1 The Easy Way===<br />
*There is a one click installer available [http://en.opensuse.org/ATI_Driver_HOWTO#1-click_install_for_openSUSE_11.1.2C_11.0_and_10.3] for both of these OS's, this will give you access to a working ATi driver however it may not be the latest one available.<br />
<br />
EDIT: This is currently not working. ATi Repository is down for OpenSUSE.<br />
<br />
===OpenSuSE 11.0 & 11.1 With The Latest Driver===<br />
<br />
You can easily install the latest versions of the ATi driver on OpenSuSE 11.0+.<br />
<br />
*Download The Latest ATi Driver.<br />
*Log in as Root using su<br />
*Install some dependencies with: '''zypper in kernel-source gcc make patch''' ''(I think, this needs more documentation & explanation in and of itself)''<br />
*Install the ATi Driver with: '''sh ./ati-driver-installer-VERSION.run'''<br />
*Configure X to use the ATi Driver with: '''aticonfig --initial -f'''<br />
*Configure sax2 to use the driver with sax2 -r -m 0=fglrx <b>Test May Crash the computer, Press Save</b><br />
*Exit the root account with exit<br />
*Reboot the computer. <i>You can restart X by pressing ctrl-alt-backspace twice however rebooting is more reliable</i><br />
<br />
Which came first, the problem or the sotluion? Luckily it doesn't matter.<br />
<br />
===GUIDE: ATI Installer HOWTO for SUSE/Novell users===<br />
http://www.suse.de/~sndirsch/ati-installer-HOWTO.html<br />
<br />
<br />
===YET ANOTHER Installation Guide:===<br />
<br />
Generally following this guide should help most of you:<br />
http://linux.wordpress.com/2006/05/12/suse-101-ati-drivers-installation/<br />
<br />
What follows is a slightly simplified version that I've used numerous times without fail.<br />
<br />
<br />
1. BACKUP your current <code>/etc/X11/xorg.conf</code> file, preferably to your home directory. Now change to a command shell by hitting Ctrl-Alt-F1.<br />
<br />
<br />
2. Remove any previous versions of the ATI driver by either<br />
<br />
If you have installed a previous ATI driver version without using RPM packages (or if you don't know if you have or not), type the following:<br />
<br />
cd /usr/share/ati <br />
sh ./fglrx-uninstall.sh<br />
<br />
Otherwise, and even if you've done the above type the following,<br />
<br />
rpm -e $(rpm -qa | grep fglrx)<br />
<br />
<br />
3. Change the directory containing the downloaded ati-driver...run file.<br />
<br />
<br />
4. Change the permissions of the driver file to executable by typing the following:<br />
<br />
chmod +x ./ati-driver...<br />
<br />
Use the tab button to complete the rest of the ati-driver... file name.<br />
<br />
<br />
5. Create a SUSE RPM (info is for 32 bit version) from the file by typing<br />
<br />
./ati-driver-installer-*.run --buildpkg SuSE/SUSE101-IA32<br />
<br />
<br />
6. Install the created fglrx... file by typing<br />
<br />
rpm -ivh fglrx_...(hit tab again to get full name)...<br />
<br />
<br />
7. The following command will update your library cache, you're recommended to run it:<br />
<br />
ldconfig<br />
<br />
<br />
8. Now run the ati config commands:<br />
<br />
aticonfig --initial --input=/etc/X11/xorg.conf<br />
<br />
<br />
9. Now run the Sax2 setup.<br />
<br />
sax2 -r -m 0=fglrx<br />
<br />
You may wish to alter the refresh rates and DPI info with this, otherwise just hit save. DO NOT hit the test button, it regually crashes my machine when i do...<br />
<br />
<br />
10. Reboot you machine. Do not use the reboot command, again this messes my machine up on the next boot for whatever reason... try<br />
<br />
shutdown -h now<br />
<br />
<br />
11. Boot up again, and check the new /etc/X11/xorg.conf file, compare it to your old one, and make any changes if you know what you're doing.<br />
<br />
== Resources ==<br />
* [http://www.suse.de/~sndirsch/ati-installer-HOWTO.html Novell HOWTO]<br />
* [http://en.opensuse.org/SDB:ATI_drivers SDB:ATI drivers]<br />
* [http://de.opensuse.org/SDB:AMD/ATI-Grafiktreiber SDB:AMD/ATI-Grafiktreiber (german)]<br />
<br />
AMD Packaging Script Maintainer for openSUSE:<br />
* [http://www.sebastian-siebert.de/ Sebastian Siebert]<br />
<br />
{{VCT}}<br />
<br />
[[Category:Distributions]]</div>178.168.82.88