Difference between revisions of "Talk:Ubuntu Gutsy Installation Guide"

From cchtml.com
Jump to: navigation, search
(Suspend/Hibernation with Catalyst 7.11 & Gutsy)
(Undo revision 6799 by 203.172.208.43 (talk))
 
(21 intermediate revisions by 14 users not shown)
Line 1: Line 1:
== Method 2 for Catalysy 7.11 ==
+
{{Talkpages}}
Done.
+
  
== Suspend/Hibernation with Catalyst 7.11 & Gutsy ==
+
I was unable to execute "sudo sh ati-driver-installer-8-02-x86.x86_64.run --buildpkg Ubuntu/gutsy" because it says missing lib32. i had to install lib32 package which should have been mentioned in the documentation
I hoped that with these drivers and Gutsty, the suspend problem would have been solved. Unfortunately it isn't for me.
+
I tried also to apply the patches to "acpi-support" (like doing with Feisty) but unsuccessfully.
+
Any working experiences? Solutions? Workarounds?
+
  
 +
== dkms? ==
  
'''Update''': it would appear that this problem is not fixed in the latest release 7.12 either.
+
I don't see any instructions for this newfangled dkms thing... Is it it done automatically? — [[User:SheeEttin|SheeEttin]] {[[User_talk:SheeEttin|T]]/[[Special:Contributions/SheeEttin|C]]} 09:13, 24 December 2007 (CST)
Its not even reported under 'known issues'. Does ATI really know about this bug? It is inconceivable that two releases would still leave such a bug open.
+
Comments anyone?
+
  
== installation hint ==
+
ANSWER: just install it before installing fglrx packages... they will invoke it. Nothing to do.
  
I followed this guide and fglrxinfo yielded the desired output.
 
  
But then I still got the following problems:
+
== APT/Aptitude ==
* crash/restart of X when trying to run glxgears
+
This guide use apt-get. Sometimes the apt-get and aptitude are interchangeable, but not always. Please don't edit this guide without knowing how use aptitude. For instance the commend "aptitude install -f" is not secure, can provoke damages (especially for "unstable" distributions).
* crash/restart of X when trying to watch mythtv recording
+
In my opinion apt-get is better for this guide. --[[User:Subvertigo|Subvertigo]] 15:26, 13 January 2008 (CST)
* visual artefacts from window creation
+
  
The cause I assumed in that:
+
== Problems with 3D acceleration ==
 +
When I try to load an app. that lacks 3D acceleration like Celestia, Stellarium etc. my computer just logs off, and I have to log back in!? Please guide me.
  
<code>glxinfo | grep direct</code>
 
  
did not yield 'yes' but 'no' and 'Mesa Indirect'
+
==Found issues==
  
Long search, quick solution:
+
===Mipmapping in Compiz===
 +
When mipmapping is enabled in compiz modules then they the contents don't show up. Disabling mipmapping fixes these problems. Ubunty 7.10 and ATI 8.1.
  
<code>sudo apt-get remove xserver-xgl</code>
+
===Kibadock glitches===
 +
Kibadock has a black background when acceleration is NOT enabled. When acceleration IS enabled it has some problems with some applications where windows aren't visible.
  
'''Note:''' I don't really know what this actually does in the context of a desired installation, so try at your own risk. I assume this being installed from my earlier Feisty installation where I tried out compiz and AIGLX was not supported by the driver.
+
===Flickering video===
 +
When videos are played in various players including embedded on websites with firefox then the video flickers with black.
  
After removing the xserver-xgl package, all problems described above vanished.
+
    * Has anyone found a solution to the flickering?  I find it also occurs in 3d-enabled games. 11:56, 7 March 2008 (CST)
  
Maybe someone with more detailed knowledge might find it useful to add a paragraph to the page.
+
It seems to be tied to compiz. When I disable desktop effects (System --> Preferences --> Appearance --> Visual Effects --> Set to "None") the flickering on videos goes away. If I enable any degree of effects, even the lowest setting, the flickering reappears again. Very annoying. I'm running driver version 8.44.3 (don't recall the Catalyst version associated with this) on an X1950XT.
  
Comment: I had a lot of trouble until I found your solution. Removing xserver-xgl made most of the graphical artifacts disappear (I still have some black bars in the bottom right corner of one screen), and made my dual screen setup work again. Should this be in the general guide?
+
Update: Updated to driver version 8.47.3 and the same flickering on video continues as long as desktop effects are enabled.
  
Comment: I was seeing some very similar behavior after following this tutorial. glxgears would cause gdm to crash and the artifacts were left on the screen. The system would also be dog slow, moving windows was very laggy. Removing xserver-xgl did the trick for me!
+
==Comments==
  
== still Mesa ==
+
===Infinite Loop===
 +
Looks to me like 128.8.120.187, which seems to be a computer name Prospector in a lab of the University of Maryland Institute for Advanced Computer Studies, found my solution at http://ubuntuforums.org/showthread.php?t=663111&p=4109726, and put in a comment on the infinite loop possibility on 23:28, 21 February 2008, under the 4.1 3D desktop effects section. I couldn't find a fix for that anywhere, but finally figured it out myself, and let others know of the solution. It's just cool to see that someone thought my contribution was good enough for the Unofficial ATI Linux Driver Wiki's Ubuntu Gutsy Installation Guide, which I keep coming to over and over as I mess up my system again and again :D
  
Hi,
+
So, whenever you get a solution to anything, put it online. It might be important.
  
I never had problems until Gutsy & 7.11 came:
+
~ pgn674
(bmhm@Sentinux)[~] $ cat /var/log/Xorg.0.log | grep "(WW)"
+
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
+
(WW) Including the default font path  /usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType.
+
(WW) fglrx(0): board is an unknown third party board, chipset is supported
+
(WW) fglrx(0): ***********************************************
+
(WW) fglrx(0): * DRI initialization failed!                  *
+
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
+
(WW) fglrx(0): * 2D acceleraton available (MMIO)            *
+
(WW) fglrx(0): * no 3D acceleration available                *
+
(WW) fglrx(0): ********************************************* *
+
 
+
and
+
 
+
(bmhm@Sentinux)[~] $  cat /var/log/Xorg.0.log | grep "(EE)"
+
(EE) fglrx(0): [pcie] Failed to gather memory of size 262144Kb for PCIe. Error (-1000)
+
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
+
(EE) AIGLX: Screen 0 is not DRI capable
+
 
+
Any Ideas? It did work before (on feisty, using older drivers)!! Help!! --[[User:212.62.64.34|212.62.64.34]] 14:08, 22 November 2007 (CST)
+
 
+
I SOLVED (subvertigo):
+
The problem was the fglrx.ko . The symbolic link have been overwritten at each reboot.
+
Check if the fglrx.ko in the "volatile" folder is a symbolic link or not to that in the "misc" folder (Gnome reports an arrow on the icon if it is, and must have the same dimension). If it is the same problem see the first paragraph to see how I solved.
+
 
+
The symbolic link is gone after a reboot. Filesize of the one in the misc folder is 2084611 bytes and the one in the volatile folder is 1058754 bytes. I don't know where/what this copying is done. :(
+
 
+
Performing the following command:
+
 
+
find / -name 'fglrx*.ko'
+
 
+
Results in:
+
 
+
/lib/modules/2.6.22-14-generic/volatile/fglrx.ko
+
/lib/modules/2.6.22-14-generic/misc/fglrx.ko
+
 
+
So where this 1058754 bytes sized version exists on the system is unclear to me.
+
 
+
== (Partially) Installed but 7.11 Driver NOT used ==
+
 
+
The catalyst control center is available under "accessories" and list the following.
+
 
+
Software:
+
* Driver version : 8.43.2
+
* Catalyst Control Center Version : 1.6
+
 
+
OpenGL:
+
* .. Provider : Mesa project ...
+
* .. Renderer : Mesa GLX Indirect
+
* .. Version : 1.4 (2.1 Mesa 7.0.1)
+
 
+
Checklist:
+
* "Restricted" repositories not commented
+
* The "restricter driver manager" says that the driver is enabled and in use.
+
* Symbolic link exists
+
 
+
Really don't know what the problem is.
+
 
+
EDIT (subvertigo) The problem is almost surely the "fglrx.ko"... see the first paragraph for the solution.
+
Moreover the "restricted manager" should say that the driver is NOT enabled (equivalent to blacklist the original "fglrx" in linux-restricted-modules-common).
+
 
+
== Method 1 fails, since xorg-driver-fglrx and fglrx kernel module versions differ ==
+
xorg-driver-fglrx is version is 8.38.7-1 and the fglrx kernel module version in linux-restricted-modules-generic is still 8.37.6.
+
 
+
Xorg complains:
+
ad@homer:~$ cat /var/log/Xorg.0.log | grep "(EE)"
+
(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
+
(EE) AIGLX: Screen 0 is not DRI capable
+
 
+
== After a reboot this link was always removed automatically ==
+
 
+
I installed the latest Radeon driver using the ATI installer and found myself trying to solve this reboot problem.  Eventually I deduced that the modules in the Gutsy ''/lib/modules/(uname -r)/volatile/'' directory are generated (compiled?) on a reboot from the files in the directories contained in ''/lib/linux-restricted-modules/(uname -r)/''.  By replacing the three files in ''fglrx'' with the matching named files from ATI's ''/lib/modules/fglrx/build_mod/'' it appeared to work happily on a reboot.
+
 
+
I am not entirely convinced by this empirical solution as I do not understand the compilation process well enough.  (Hugh Kernohan)
+
 
+
== Error Executing Gutsy Installation Guide ==
+
When I reach the command,
+
 
+
<pre>
+
sudo aticonfig --initial
+
</pre>
+
 
+
I receive the following error,
+
 
+
john1726@vm-bartok:~/Install$ sudo aticonfig --initial
+
Uninitialised file found, configuring.
+
Using /etc/X11/xorg.conf
+
Saved back-up to /etc/X11/xorg.conf.original-1
+
*** glibc detected *** aticonfig: munmap_chunk(): invalid pointer: 0xbfda69ca ***
+
======= Backtrace: =========
+
/lib/tls/i686/cmov/libc.so.6(cfree+0x1bb)[0xb7db892b]
+
aticonfig[0x8051ce7]
+
aticonfig[0x8052065]
+
aticonfig[0x8055a48]
+
aticonfig[0x804985e]
+
aticonfig[0x80496cb]
+
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7d61050]
+
aticonfig[0x8049601]
+
======= Memory map: ========
+
08048000-0806a000 r-xp 00000000 08:01 1388518    /usr/bin/aticonfig
+
0806a000-0806d000 rw-p 00021000 08:01 1388518    /usr/bin/aticonfig
+
0806d000-0808e000 rw-p 0806d000 00:00 0          [heap]
+
b7d3d000-b7d3e000 rw-p b7d3d000 00:00 0
+
b7d3e000-b7d40000 r-xp 00000000 08:01 33606      /lib/tls/i686/cmov/libdl-2.6.1.so
+
b7d40000-b7d42000 rw-p 00001000 08:01 33606      /lib/tls/i686/cmov/libdl-2.6.1.so
+
b7d42000-b7d43000 rw-p b7d42000 00:00 0
+
b7d43000-b7d47000 r-xp 00000000 08:01 1385811    /usr/lib/libXdmcp.so.6.0.0
+
b7d47000-b7d48000 rw-p 00003000 08:01 1385811    /usr/lib/libXdmcp.so.6.0.0
+
b7d48000-b7d4a000 r-xp 00000000 08:01 1385800    /usr/lib/libXau.so.6.0.0
+
b7d4a000-b7d4b000 rw-p 00001000 08:01 1385800    /usr/lib/libXau.so.6.0.0
+
b7d4b000-b7e8f000 r-xp 00000000 08:01 33603      /lib/tls/i686/cmov/libc-2.6.1.so
+
b7e8f000-b7e90000 r--p 00143000 08:01 33603      /lib/tls/i686/cmov/libc-2.6.1.so
+
b7e90000-b7e92000 rw-p 00144000 08:01 33603      /lib/tls/i686/cmov/libc-2.6.1.so
+
b7e92000-b7e95000 rw-p b7e92000 00:00 0
+
b7e95000-b7eb8000 r-xp 00000000 08:01 33607      /lib/tls/i686/cmov/libm-2.6.1.so
+
b7eb8000-b7eba000 rw-p 00023000 08:01 33607      /lib/tls/i686/cmov/libm-2.6.1.so
+
b7eba000-b7fa7000 r-xp 00000000 08:01 1385794    /usr/lib/libX11.so.6.2.0
+
b7fa7000-b7fab000 rw-p 000ed000 08:01 1385794    /usr/lib/libX11.so.6.2.0
+
b7fab000-b7fb8000 r-xp 00000000 08:01 1385815    /usr/lib/libXext.so.6.4.0
+
b7fb8000-b7fb9000 rw-p 0000d000 08:01 1385815    /usr/lib/libXext.so.6.4.0
+
b7fb9000-b7fba000 rw-p b7fb9000 00:00 0
+
b7fba000-b7fc1000 r-xp 00000000 08:01 1385837    /usr/lib/libXrender.so.1.3.0
+
b7fc1000-b7fc2000 rw-p 00006000 08:01 1385837    /usr/lib/libXrender.so.1.3.0
+
b7fc2000-b7fc7000 r-xp 00000000 08:01 1385835    /usr/lib/libXrandr.so.2.1.0
+
b7fc7000-b7fc8000 rw-p 00005000 08:01 1385835    /usr/lib/libXrandr.so.2.1.0
+
b7fcf000-b7fd9000 r-xp 00000000 08:01 1970915    /lib/libgcc_s.so.1
+
b7fd9000-b7fda000 rw-p 0000a000 08:01 1970915    /lib/libgcc_s.so.1
+
b7fda000-b7fdd000 rw-p b7fda000 00:00 0
+
b7fdd000-b7ff7000 r-xp 00000000 08:01 1970861    /lib/ld-2.6.1.so
+
b7ff7000-b7ff9000 rw-p 00019000 08:01 1970861    /lib/ld-2.6.1.so
+
bfd92000-bfda8000 rw-p bfd92000 00:00 0          [stack]
+
ffffe000-fffff000 r-xp 00000000 00:00 0          [vdso]
+
Aborted (core dumped)
+

Latest revision as of 14:36, 2 June 2011

TALK PAGES ARE NOT SUPPORT FORUMS

If you require help with installing the AMD fglrx driver, please consider a web forum or mailing list.

I was unable to execute "sudo sh ati-driver-installer-8-02-x86.x86_64.run --buildpkg Ubuntu/gutsy" because it says missing lib32. i had to install lib32 package which should have been mentioned in the documentation

Contents

[edit] dkms?

I don't see any instructions for this newfangled dkms thing... Is it it done automatically? — SheeEttin {T/C} 09:13, 24 December 2007 (CST)

ANSWER: just install it before installing fglrx packages... they will invoke it. Nothing to do.


[edit] APT/Aptitude

This guide use apt-get. Sometimes the apt-get and aptitude are interchangeable, but not always. Please don't edit this guide without knowing how use aptitude. For instance the commend "aptitude install -f" is not secure, can provoke damages (especially for "unstable" distributions). In my opinion apt-get is better for this guide. --Subvertigo 15:26, 13 January 2008 (CST)

[edit] Problems with 3D acceleration

When I try to load an app. that lacks 3D acceleration like Celestia, Stellarium etc. my computer just logs off, and I have to log back in!? Please guide me.


[edit] Found issues

[edit] Mipmapping in Compiz

When mipmapping is enabled in compiz modules then they the contents don't show up. Disabling mipmapping fixes these problems. Ubunty 7.10 and ATI 8.1.

[edit] Kibadock glitches

Kibadock has a black background when acceleration is NOT enabled. When acceleration IS enabled it has some problems with some applications where windows aren't visible.

[edit] Flickering video

When videos are played in various players including embedded on websites with firefox then the video flickers with black.

   * Has anyone found a solution to the flickering?  I find it also occurs in 3d-enabled games. 11:56, 7 March 2008 (CST)

It seems to be tied to compiz. When I disable desktop effects (System --> Preferences --> Appearance --> Visual Effects --> Set to "None") the flickering on videos goes away. If I enable any degree of effects, even the lowest setting, the flickering reappears again. Very annoying. I'm running driver version 8.44.3 (don't recall the Catalyst version associated with this) on an X1950XT.

Update: Updated to driver version 8.47.3 and the same flickering on video continues as long as desktop effects are enabled.

[edit] Comments

[edit] Infinite Loop

Looks to me like 128.8.120.187, which seems to be a computer name Prospector in a lab of the University of Maryland Institute for Advanced Computer Studies, found my solution at http://ubuntuforums.org/showthread.php?t=663111&p=4109726, and put in a comment on the infinite loop possibility on 23:28, 21 February 2008, under the 4.1 3D desktop effects section. I couldn't find a fix for that anywhere, but finally figured it out myself, and let others know of the solution. It's just cool to see that someone thought my contribution was good enough for the Unofficial ATI Linux Driver Wiki's Ubuntu Gutsy Installation Guide, which I keep coming to over and over as I mess up my system again and again :D

So, whenever you get a solution to anything, put it online. It might be important.

~ pgn674