Re: [opensuse] New ATI Drivers today

On Fri, May 23, 2008 at 1:02 AM, David C. Rankin wrote:

John Andersen wrote:

...

On Wed, May 21, 2008 at 10:58 PM, David C. Rankin wrote:

...

John Andersen wrote:

...

https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/catalyst_8...

ATI has released new drivers that appear to fix a number of issues that have plagued users on this list.

[00:43 Rankin-P35a/home/david] # rpm -qa | grep fglrx fglrx_7_1_0_SUSE103-8.493-1

Installed and working fine, compiz works without problems. 8.3, 8.4 and 8.5 have now been phenomenal.

Not for me. Its been a struggle upgrading each time. I think this has to do with the bug mentioned in the list of fixes:

"The Linux kernel module is no longer installed to wrong location if the Linux kernel is updated."

Each time I've had to generate the steps by hand, and each time when I get to the SaX2 step it insists it can't do 3D, but then goes ahead and does it anyway.

Your not holding your tongue right during the driver install. The key is to:

1. build the new rpm with:

sh ati-driver-installer-8-5-x86.x86_64.run --buildpkg SuSE/SUSE103-IA32

or SuSE/SUSE103-AMD64

2. SAVE YOUR XORG.CONF: cp /etc/X11/xorg.conf /tmp/xorg.conf

3. drop to runlevel 3

4. Uninstall the existing driver: rpm -e $(rpm -qa | grep fglrx)

5. Install the new one: rpm -Uvh fglrx64_7_1_0_SUSE103-8.493-1.x86_64.rpm

6. Put you old xorg.conf back in place: cp /tmp/xorg.conf /etc/X11/xorg.conf

7. reboot (yes rmmod && modprobe && depmod ...) but on uninstall the radeon driver replaces the fglrx driver and it does not unload cleanly when the new fglrx driver is installed.

The key is to copy your xorg.conf *before* you *uninstall* the existing driver, otherwise, your xorg.conf in modified during the uninstall and you will have to mess with sax2 if you don't have a backup. With the backup, simply putting your old xorg.conf back in place takes care of it all and you never have to see sax2 again. (it's past its prime)

You may be doing it this way.

I am in fact doing it that way. (That qualifies as "By Hand" in my book.) I also have a script, but you have to modify the silly script every time for version numbers etc, and they have been inconsistent in the naming of the generated RPM, so it has ended up being pretty much a manual task one way or another. This last time, the rpm generated did the depmod for me, (but I did it again anyway). -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org