Howto for fglrx / catalyst (Ati driver)

[leigh123linux]

Originally Posted by reader69

Today, after an "yum upgrade" my F11 system has been stopped working. After reboot, when the X should starting, I got only a black screen. I tried to reinstall catalyst drivers, re-make initrd, but no success. Any ideas ?

Updated packages :

Jan 23 09:09:37 Updated: kdepimlibs-4.3.4-2.fc11.i586
Jan 23 09:09:39 Updated: PolicyKit-kde-4.3.4-6.fc11.i586
Jan 23 09:09:39 Updated: kdepimlibs-akonadi-4.3.4-2.fc11.i586
Jan 23 09:09:41 Updated: amarok-utils-2.2.2-3.fc11.i586
Jan 23 09:09:41 Updated: ksysguardd-4.3.4-6.fc11.i586
Jan 23 09:09:43 Updated: 2:ntfs-3g-2010.1.16-1.fc11.i586
Jan 23 09:09:44 Updated: k9copy-2.3.4-1.fc11.i586
Jan 23 09:09:46 Updated: kernel-firmware-2.6.30.10-105.2.4.fc11.noarch
Jan 23 09:10:05 Updated: thunderbird-3.0.1-1.fc11.i586
Jan 23 09:10:34 Installed: kernel-PAE-devel-2.6.30.10-105.2.4.fc11.i686
Jan 23 09:10:36 Updated: kernel-headers-2.6.30.10-105.2.4.fc11.i586
Jan 23 09:11:01 Installed: kernel-PAE-2.6.30.10-105.2.4.fc11.i686
Jan 23 09:11:21 Installed: kernel-2.6.30.10-105.2.4.fc11.i586
Jan 23 09:11:23 Installed: kmod-VirtualBox-OSE-2.6.30.10-105.2.4.fc11.i586-3.0.10-1.fc11.7.i586
Jan 23 09:11:24 Installed: kmod-VirtualBox-OSE-2.6.30.10-105.2.4.fc11.i686.PAE-3.0.10-1.fc11.7.i686
Jan 23 09:11:24 Updated: kmod-VirtualBox-OSE-PAE-3.0.10-1.fc11.7.i686
Jan 23 09:11:24 Updated: kmod-VirtualBox-OSE-3.0.10-1.fc11.7.i586
Jan 23 09:11:25 Updated: kdebase-workspace-libs-4.3.4-6.fc11.i586
Jan 23 09:11:26 Updated: kmod-catalyst-PAE-9.12-1.fc11.1.i686
Jan 23 09:11:27 Installed: kmod-catalyst-2.6.30.10-105.2.4.fc11.i686.PAE-9.12-1.fc11.1.i686
Jan 23 09:11:28 Updated: amarok-libs-2.2.2-3.fc11.i586
Jan 23 09:11:30 Updated: kdm-4.3.4-6.fc11.i586
Jan 23 09:11:35 Updated: kdebase-workspace-4.3.4-6.fc11.i586
Jan 23 09:11:39 Updated: amarok-2.2.2-3.fc11.i586
Jan 23 09:11:42 Updated: xorg-x11-drv-catalyst-9.12-1.fc11.i586
Jan 23 09:11:45 Updated: xorg-x11-drv-catalyst-libs-9.12-1.fc11.i586
Jan 23 09:11:46 Installed: kmod-catalyst-2.6.30.10-105.2.4.fc11.i586-9.12-1.fc11.1.i586
Jan 23 09:11:48 Updated: kmod-catalyst-2.6.30.10-105.fc11.i686.PAE-9.12-1.fc11.i686
Jan 23 09:11:49 Updated: kmod-catalyst-2.6.30.10-105.fc11.i586-9.12-1.fc11.i586
Jan 23 09:11:49 Updated: kmod-catalyst-9.12-1.fc11.1.i586
Jan 23 09:11:54 Erased: kmod-VirtualBox-OSE-2.6.30.9-99.fc11.i586
Jan 23 09:12:06 Erased: kmod-catalyst-2.6.30.9-99.fc11.i686.PAE
Jan 23 09:12:20 Erased: kmod-catalyst-2.6.30.9-99.fc11.i586
Jan 23 09:12:23 Erased: kmod-VirtualBox-OSE-2.6.30.9-99.fc11.i686.PAE

Try deleting this kernel

su
rpm -e kernel-2.6.30.10-105.2.4.fc11.i586

[corp769]

I am also experiencing this same problem. My question is how you guys reverted back to the default driver? I started messing with it when I was drunk, and messed it up even worse

currently 2.6.30.10-105.2.4.fc11.x86_64

[pballok]

I removed the kernel as Leigh suggested above (thanks!). It also removed the kmod-catalyst packages as dependencies. Unfortunately I still got the same black screen after reboot, although my GRUB problem was solved.

I then continued to remove other packages that got installed with the last yum update. I removed the xorg-x11-drv-catalyst* packages and their dependencies, and the kernel-firmware-2.6.30.10-105.2.4 package as well.

After these are gone, I do get the graphical login screen back and I can log in, gnome starts,
the panel loads, but then the whole screen goes white. I use compiz fusion and I suggest the white screen comes from compiz, since I get the "desktop on cube" animation if I switch desktops with keyboard shortcuts. So it works, but the whole screen is plain white.

How can I disable compiz from command line?

[hajo01]

OK, digged a little deeper. Problem is in fact the upgrade from Catalyst 9.10 to 9.12. So we're in for some more trouble I fear...

My findings so far:
- X in fact starts properly, nothing seems to throw an error message
- The LCD display goes _off_, not only black. The backlight gets turned off.

While I didn't find the root of the problem yet, here are 2 interim fixes you can do to at least get your system back:

1) switch to the vesa driver
- During boot, press a key to get to the grub boot menu
- Go to the first entry, edit it. Edit the line saying "kernel /boot/...". At the end, add a "init=/sbin/init 3"
- Boot
- Edit /etx/X11/xorg.conf. Replace the line saying 'Driver "fglrx"' by 'Driver "vesa"'
- reboot

2) roll back to the previous catalyst (Haven't tried this yet but will do soon if no fix found)
- find all catalyst-rpms and remove them (rpm -qa | grep catalyst)
- remove the latest kernel (2.6.30.10-105.2.4.fc11), rpmfusiion only has a catalyst 9.12 driver for it
- make sure you also delete the respective kernel entry in /boot/grub/menu.lst), not sure whether the rpm -e removes it automatically, I doubt it...
- Manually download and install the previous catalyst rpms (cat /var/log/yum.log* | grep catalyst), but remember you don't want the meta-packages but only the rpms with the real payload)
- Make sure yum/packagekit/... won't pull the latest kernel or the latest catalyst driver next time you do an update.

Or, better yet, stay with Catalyst 9.12, find the problem and tell us the solution

BTW: compiz is automatically disabled when the acceleration is not found.

[leigh123linux]

Originally Posted by pballok

I removed the kernel as Leigh suggested above (thanks!). It also removed the kmod-catalyst packages as dependencies. Unfortunately I still got the same black screen after reboot, although my GRUB problem was solved.

I then continued to remove other packages that got installed with the last yum update. I removed the xorg-x11-drv-catalyst* packages and their dependencies, and the kernel-firmware-2.6.30.10-105.2.4 package as well.

After these are gone, I do get the graphical login screen back and I can log in, gnome starts,
the panel loads, but then the whole screen goes white. I use compiz fusion and I suggest the white screen comes from compiz, since I get the "desktop on cube" animation if I switch desktops with keyboard shortcuts. So it works, but the whole screen is plain white.

How can I disable compiz from command line?

Post

uname -r

and

rpm -qa |grep -e catalyst -e kernel |sort

[pballok]

Originally Posted by leigh123linux

Post

uname -r

and

rpm -qa |grep -e catalyst -e kernel |sort

$ uname -r
2.6.30.10-105.fc11.x86_64
$ rpm -qa |grep -e catalyst -e kernel |sort
kernel-2.6.30.10-105.fc11.x86_64
kernel-2.6.30.9-102.fc11.x86_64
kernel-headers-2.6.30.10-105.2.4.fc11.x86_64
kerneloops-0.12-5.fc11.x86_64

By the way I now removed all compiz-related packages so I can use my F11 again, but I guess it's far from optimal solution...
The list of all packages I removed to get my system to work again (from /var/log/yum.log):

Jan 25 11:06:34 Erased: kernel
Jan 25 11:06:36 Erased: kmod-catalyst-2.6.30.10-105.2.4.fc11.x86_64
Jan 25 11:06:36 Erased: kmod-catalyst
Jan 25 11:09:46 Erased: xorg-x11-drv-catalyst
Jan 25 11:09:48 Erased: kmod-catalyst-2.6.30.10-105.fc11.x86_64
Jan 25 11:09:52 Erased: kmod-catalyst-2.6.30.9-102.fc11.x86_64
Jan 25 11:09:57 Erased: xorg-x11-drv-catalyst-libs
Jan 25 11:09:58 Erased: xorg-x11-drv-catalyst-libs
Jan 25 11:13:51 Erased: kernel-firmware
Jan 25 12:00:36 Erased: compiz-fusion
Jan 25 12:00:37 Erased: compiz-fusion-extras
Jan 25 12:00:38 Erased: compizconfig-backend-gconf
Jan 25 12:00:39 Erased: fusion-icon-gtk
Jan 25 12:00:39 Erased: compiz
Jan 25 12:00:41 Erased: compiz-bcop
Jan 25 12:00:42 Erased: emerald-themes
Jan 25 12:00:43 Erased: compizconfig-python
Jan 25 12:00:53 Erased: compiz-fusion-extras-gnome
Jan 25 12:01:02 Erased: compiz-fusion-gnome
Jan 25 12:01:02 Erased: emerald
Jan 25 12:01:20 Erased: compiz-gnome
Jan 25 12:01:23 Erased: ccsm
Jan 25 12:01:24 Erased: fusion-icon

[AltGrendel]

I wound up having to restore from a current backup.

Not happy with this development. I've already complained at ATI about their lack of updates.

[Vladi]

Originally Posted by corp769

I am also experiencing this same problem. My question is how you guys reverted back to the default driver? I started messing with it when I was drunk, and messed it up even worse

currently 2.6.30.10-105.2.4.fc11.x86_64

I have the same issue. Here a bugreport, maybe the same.

Driver work fine, with: 2.6.30.10-105.fc11

[rshartog]

Hi Leigh123linux,

I posted about having this F11/Catalyst driver update problem a few posts back (post #3855 to this thread). At the moment, my system is "fully functional" without the Catalyst driver, but, of course, I cannot run any 3D accelerated applications.

Would you recommend that I just wait for the next revision of the Catalyst driver to arrive and then attempt to reinstall according to your guide (which, by the way, is very useful)? Or would you recommend that I try to get a better understanding of my problem with the current Catalyst driver with the hope of resolving it somehow?

--Scott

[corp769]

yea i got my system fully working again, but now my fan is at full speed without the fglrx driver running. so has anyone figured anything out yet? i'm still working on it...

[hajo01]

If someone can spare a few hours on this, it could be interesting to remove the rpmfusion fglrx completely and instead install the stock ATI Catalyst 9.12. At least this would verify whether the problem stems from rpmfusion's packaging or from the ATI-driver itself.

[peter121]

typed that in

su
gedit /etc/X11/xorg.conf

opened the config page but it is empty .do i just ad the config u put i have a radion 9600

[hajo01]

Good news -- I got Catalyst 9.12 working properly on my system now. To fix the broken update, do the following:
- Upgrade to catalyst 9.12, boot.
- If your screen is black, switch to console with CTRL-ALT-F2
- log in. Make sure you have the file "/etc/ati/amdpcsdb.default" If not, don't continue but get this file first!
- Now, simply "rm /etc/ati/amdpcsdb"
- Reboot, and voila!

Apparently, shame on ATI, the Catalyst 9.12 chokes on amdpcsdb being created by earlier versions. The driver will automatically restore the file on boot from the amdpcsdb.default. You may have to go through your settings in the ATI Catalyst Control Center, these are stored in the above file I believe...

@leigh123linux: Do you think it'd make sense to pull this into into a separate thread -- possibly with the install-instructions on page 1 of this thread? I believe in a month from now nobody will find this info given that the thread is now at 258 pages...

[leigh123linux]

Originally Posted by hajo01

Good news -- I got Catalyst 9.12 working properly on my system now. To fix the broken update, do the following:
- Upgrade to catalyst 9.12, boot.
- If your screen is black, switch to console with CTRL-ALT-F2
- log in. Make sure you have the file "/etc/ati/amdpcsdb.default" If not, don't continue but get this file first!
- Now, simply "rm /etc/ati/amdpcsdb"
- Reboot, and voila!

Apparently, shame on ATI, the Catalyst 9.12 chokes on amdpcsdb being created by earlier versions. The driver will automatically restore the file on boot from the amdpcsdb.default. You may have to go through your settings in the ATI Catalyst Control Center, these are stored in the above file I believe...

@leigh123linux: Do you think it'd make sense to pull this into into a separate thread -- possibly with the install-instructions on page 1 of this thread? I believe in a month from now nobody will find this info given that the thread is now at 258 pages...

I will add it a soon as the fix is verified by other users.

[renevielma]

Originally Posted by leigh123linux

I will add it a soon as the fix is verified by other users.

This didn't work for me