Talk:Ubuntu Feisty Installation Guide

Upgrade
Please make how-to how to upgrade fglrx driver

This is all hard
Very hard work indeed and it still doesn't do dual head. is there any way of getting a non 3d driver going, which will just show a movie on my projector. I rebooted a lot today, a lot.

OpenGL not working, so no Google Earth - and many other programs
I did my share of rebooting, too. I'm really frustrated. Is this a hardware limitation (I have X1650 Pro) or a driver limitation?
 * You need to troubleshoot your installation method. -- Mooninite 14:10, 27 March 2007 (CDT)

2.6.20 Patching
IMPORTANT: This method will not work with 2.6.20.* kernels. Is this still true? My feisty install is kernel 2.6.20-13-generic and it was trivial to install fglrx using the first method mentioned. If the second method is still really required, it would be good to say why (eg, something is busted in Ubuntu's 26.20 ?)

aticonfig --overlay-type=Xv: core dumps

 * glibc detected *** aticonfig: munmap_chunk: invalid pointer: 0xbfe04a91 ***

= Backtrace:
=== /lib/tls/i686/cmov/libc.so.6(cfree+0x1bb)[0xb7d65f5b] aticonfig[0x805be17] aticonfig[0x805bf2a] aticonfig[0x8052f5a] aticonfig[0x80531aa] aticonfig[0x804ab0d] aticonfig[0x80497d9] aticonfig[0x80496cb] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc)[0xb7d10ebc] aticonfig[0x8049601]

Doesn't crash with the --initial option.

Rebooted and this time it just hangs. (2.6.20-13 generic; Mobility Radeon 9700.)

aticonfig Core Dumps
I found the problem with these instructions for those of us getting the initial core dumps when using aticonfig --initial or --overlay

The problem is the order in which the instructions are given.

To fix this I had to first black list the fglrx and then reboot.

If you don't black list this driver and reboot first, you will get an error when you run

sudo dpkg -i xorg-driver-fglrx_8.36.5-1*.deb

The error you will get is the following:

Starting atieventsd: already started

This will cause all aticonfig settings to choke.

Dual screen
I finally managed to get fglrx working with two screens with an ATI radeon X1300. Xinerama resulted in buggy mouse pointer on second screen. All in one big desktop seems to work without any problems. I followed this guide: http://ubuntuforums.org/showthread.php?t=301941

Problem with xorg.conf settings?
As i was trying to work through this, I noticed that every time I added those options to the xorg.conf file, KDE would no longer start unless I manually started it (startx), but then it would seem that no graphics drivers would load, and I'd have to restart installing/setting up fglrx. After several rounds of going through this process, I just decided NOT to add the 'Option "AIGLX" "off"' to the xorg.conf file. Then it booted perfectly, and everything was working like it should.

In case you need to know, I am using Kbuntu with a Radeon 9800 Pro

Script
In case anyone's interested, I wrote up a script that installs the driver. It's here, only for Feisty. (I tried making it release-independent, but it was too hard.) My computer gets shut down at night (it's not so much a server as a computer for personal use), so try again later if you get a 503. (Also, could my script be mentioned in the article somehow? I didn't see a good place to put it.) &mdash; SheeEttin {T/C} 17:54, 13 July 2007 (CDT)

AMD Watermark with 8.39.4 Drivers
Just installed the new 8.39.4 drivers as per the guide, and now there is a square overlayed on the lower right corner of the screen that says "AMD Testing use only". It's very annoying, and I'm wondering if anyone else is getting this, or knows how to remove it? I almost wonder if Ati put up a development version on their download page by mistake... This is on Kubuntu 7.04 with a Radeon 9600xt -- 71.34.23.10

edit: just saw this at www.phoronix.com. seems to be an issue with a signiture file that isn't getting generated with the --buildpkg argument. Guess the only solution is to downgrade until Ati fixes it. -- 71.34.23.10


 * Yup. If you must have the drivers now, you can apparently use the GUI installer and it'll work. &mdash; SheeEttin {T/C} 12:30, 20 July 2007 (CDT)


 * ATI is no longer offering the 8.39.4 drivers. Download page is back to 8.38.6. If you managed to grab the file while it was available, there is a workaround posted in this thread. -- 71.34.23.10


 * Re-released. Apparently, it's been fixed. Who wants to update the article? :D (And please sign your posts with  ~ .) &mdash; SheeEttin {T/C} 13:41, 23 July 2007 (CDT)

ATI Catalyst Control Center
Everything works fine, but i don't have CCC. How can I install it? What is the easiest way?

(I need CCC for connecting PC with TV)

--145.236.252.34 03:36, 1 August 2007 (CDT)
 * The Linux control panel should be included with your driver package. The "Catalyst Control Center" is the Windows-only program. -Mooninite 11:14, 1 August 2007 (CDT)

Bold text

volatile-directory already exists on Feisty
I used method 2 to install the latest drivers in Feisty. Unfortunately, it didn't go very well: the old driver still existed in /lib/modules/$(uname -r)/volatile. Even after removing the default restricted-driver package. It took me an hour to figure out what was going wrong. I forgot to blacklist the driver in linux-restricted-modules-common, so I fixed that. Now another problem arises: how do I get the symlink permanently in a directory mounted as tempfs?

At the very least, the mkdir volatile-statement should be removed.

stupid bug... "make-deb-file" step can't deal with spacebars in pathname.
This is so stupid. When I did the following command

sudo bash ati-driver-installer-8.41.7-x86.x86_64.run --buildpkg Ubuntu/feisty

all I got was a bunch of error-msgs. I took a good look at those msgs, and I saw that the stupid thing can't handle the situation if the run-file is in a dir with spaces in its path. So for example, I had this file on

/home/johndoe/things/internet downloads/program files/ati-driver-installer-8.41.7-x86.x86_64.run

The stupid thing tries to do something with /home/johndoe/things/internet. Then it tries to do something with downloads/program. Last but not least, it tries to deal with files/ati-driver-installer-8.41.7-x86.x86_64.run. And everytime it says "could not find dir/file" or whatever.

I just thought you should know.

81.170.138.232 17:29, 15 September 2007 (CDT)