Howto for fglrx / catalyst (Ati driver) and Compiz-fusion

[Ashish Sood]

guys i have a big issue

when i try to install kmod-catalyst-PAE for my F11 following error is coming

#yum install kmod-catalyst-PAE

--> Running transaction check
---> Package kmod-catalyst-PAE.i686 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kmod-catalyst-2.6.30.9-90.fc11.i686.PAE >= 9.10-1.fc11 for package: kmod-catalyst-PAE
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i686.PAE.i686 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i686.PAE for package: kmod-catalyst-2.6.30.9-90.fc11.i686.PAE
--> Processing Dependency: catalyst-kmod-common >= 9.10 for package: kmod-catalyst-2.6.30.9-90.fc11.i686.PAE
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i686.PAE.i686 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i686.PAE for package: kmod-catalyst-2.6.30.9-90.fc11.i686.PAE
---> Package xorg-x11-drv-catalyst.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: xorg-x11-drv-catalyst-libs-i586 = 9.10-1.fc11 for package: xorg-x11-drv-catalyst
--> Processing Dependency: livna-config-display >= 0.0.23 for package: xorg-x11-drv-catalyst
--> Processing Dependency: libfglrx_gamma.so.1 for package: xorg-x11-drv-catalyst
--> Processing Dependency: livna-config-display for package: xorg-x11-drv-catalyst
--> Processing Dependency: livna-config-display for package: xorg-x11-drv-catalyst
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i686.PAE.i686 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i686.PAE for package: kmod-catalyst-2.6.30.9-90.fc11.i686.PAE
---> Package livna-config-display.noarch 0:0.0.23-1.fc11 set to be updated
--> Processing Dependency: system-config-display for package: livna-config-display
---> Package xorg-x11-drv-catalyst-libs.i586 0:9.10-1.fc11 set to be updated
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i686.PAE.i686 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i686.PAE for package: kmod-catalyst-2.6.30.9-90.fc11.i686.PAE
---> Package system-config-display.noarch 0:1.1.3-2.fc11 set to be updated
--> Processing Dependency: rhpxl >= 0.34-1 for package: system-config-display
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i686.PAE.i686 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i686.PAE for package: kmod-catalyst-2.6.30.9-90.fc11.i686.PAE
---> Package rhpxl.i586 0:1.12-2.fc11 set to be updated
--> Finished Dependency Resolution
kmod-catalyst-2.6.30.9-90.fc11.i686.PAE-9.10-1.fc11.i686 from rpmfusion-nonfree-updates has depsolving problems
--> Missing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i686.PAE is needed by package kmod-catalyst-2.6.30.9-90.fc11.i686.PAE-9.10-1.fc11.i686 (rpmfusion-nonfree-updates)
Error: Missing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i686.PAE is needed by package kmod-catalyst-2.6.30.9-90.fc11.i686.PAE-9.10-1.fc11.i686 (rpmfusion-nonfree-updates)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest

[adrianx]

guys i have a big issue

when i try to install kmod-catalyst-PAE for my F11 following error is coming

#yum install kmod-catalyst-PAE


It looks as if you don't have the latest kernel.
When you run:
uname -r
the result should be:
2.6.30.9-90.fc11.i686.PAE

[randomdood]

Hi,
been using catalyst for a bit now.. got compiz working, however i seem to get quite a bit of frame tearing.
running f11, catalyst 9.10 installed with RPM

in SMPlayer all gl and xv renderers result in frame tearing.

my xorg.conf: (I did have the dri 0666 option previously but it didn't seem to help)

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection

Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/catalyst"
ModulePath "/usr/lib64/xorg/modules"
EndSection

Section "Module"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
Option "Xinerama" "off"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
Option "TexturedVideo" "on"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "TexturedVideoSync" "on"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection


any suggestions?

[DriftNismo]

Hi, just install Fedora V11 today, but have had problems installing the graphics driver for the past few hours. I've tried your method, but I just get this:

[root@James James]# yum install kmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs.i586
Loaded plugins: refresh-packagekit
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package kmod-catalyst.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kmod-catalyst-2.6.30.9-90.fc11.i586 >= 9.10-1.fc11 for package: kmod-catalyst-9.10-1.fc11.i586
---> Package xorg-x11-drv-catalyst.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: livna-config-display >= 0.0.23 for package: xorg-x11-drv-catalyst-9.10-1.fc11.i586
--> Processing Dependency: livna-config-display for package: xorg-x11-drv-catalyst-9.10-1.fc11.i586
--> Processing Dependency: livna-config-display for package: xorg-x11-drv-catalyst-9.10-1.fc11.i586
---> Package xorg-x11-drv-catalyst-libs.i586 0:9.10-1.fc11 set to be updated
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i586.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 for package: kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586
---> Package livna-config-display.noarch 0:0.0.23-1.fc11 set to be updated
--> Processing Dependency: system-config-display for package: livna-config-display-0.0.23-1.fc11.noarch
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i586.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 for package: kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586
---> Package system-config-display.noarch 0:1.1.3-2.fc11 set to be updated
--> Processing Dependency: rhpxl >= 0.34-1 for package: system-config-display-1.1.3-2.fc11.noarch
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i586.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 for package: kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586
---> Package rhpxl.i586 0:1.12-2.fc11 set to be updated
--> Finished Dependency Resolution
kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586 from rpmfusion-nonfree-updates has depsolving problems
--> Missing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 is needed by package kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586 (rpmfusion-nonfree-updates)
Error: Missing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 is needed by package kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586 (rpmfusion-nonfree-updates)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest

Sorry if the solution is obvious, I'm new to Linux :p.

[otnateos]

Hi, just install Fedora V11 today, but have had problems installing the graphics driver for the past few hours. I've tried your method, but I just get this:

[root@James James]# yum install kmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs.i586
Loaded plugins: refresh-packagekit
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package kmod-catalyst.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kmod-catalyst-2.6.30.9-90.fc11.i586 >= 9.10-1.fc11 for package: kmod-catalyst-9.10-1.fc11.i586
---> Package xorg-x11-drv-catalyst.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: livna-config-display >= 0.0.23 for package: xorg-x11-drv-catalyst-9.10-1.fc11.i586
--> Processing Dependency: livna-config-display for package: xorg-x11-drv-catalyst-9.10-1.fc11.i586
--> Processing Dependency: livna-config-display for package: xorg-x11-drv-catalyst-9.10-1.fc11.i586
---> Package xorg-x11-drv-catalyst-libs.i586 0:9.10-1.fc11 set to be updated
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i586.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 for package: kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586
---> Package livna-config-display.noarch 0:0.0.23-1.fc11 set to be updated
--> Processing Dependency: system-config-display for package: livna-config-display-0.0.23-1.fc11.noarch
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i586.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 for package: kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586
---> Package system-config-display.noarch 0:1.1.3-2.fc11 set to be updated
--> Processing Dependency: rhpxl >= 0.34-1 for package: system-config-display-1.1.3-2.fc11.noarch
--> Running transaction check
---> Package kmod-catalyst-2.6.30.9-90.fc11.i586.i586 0:9.10-1.fc11 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 for package: kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586
---> Package rhpxl.i586 0:1.12-2.fc11 set to be updated
--> Finished Dependency Resolution
kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586 from rpmfusion-nonfree-updates has depsolving problems
--> Missing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 is needed by package kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586 (rpmfusion-nonfree-updates)
Error: Missing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 is needed by package kmod-catalyst-2.6.30.9-90.fc11.i586-9.10-1.fc11.i586 (rpmfusion-nonfree-updates)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest

Sorry if the solution is obvious, I'm new to Linux :p.

like what adrianx said, it seems like you don't have the latest kernel. install the latest kernel first

[Ashish Sood]

It looks as if you don't have the latest kernel.
When you run:
uname -r
the result should be:
2.6.30.9-90.fc11.i686.PAE


@Adrianx

i output of my uname -r is
2.6.30.9-96.fc11.i686.PAE

I have A latest kernel

according to uname -r

[otnateos]

@Adrianx

i output of my uname -r is
2.6.30.9-96.fc11.i686.PAE

I have A latest kernel

according to uname -r

In that case you either

boot up your old kernel 2.6.30.9-90 as specified by rpmfusion requirement then reboot with your latest kernel and let kmod rebuild the driver for your latest kernel (i am not 100% sure this going to work)
wait for rpmfusion to release the driver for the latest kernel
use your older kernel

[DriftNismo]

like what adrianx said, it seems like you don't have the latest kernel. install the latest kernel first

Eventually got the official driver installed last night, but I got black screen upon reboot, so I booted into text-only mode and found and deleted the ATi driver. I then rebooted and reset the driver to the default radeon hd one. Then I tried this driver and it managed to install fine, but upon reboot it then black screened too, and I wasn't too sure on how to edit the xorg.conf yet, so I re-installed. But after using it for the past couple of hours, the lag (mouse, flash, just general use) is getting quite annoying, but it is running Compiz Fusion really well.

So my question is; is there anything else I can do? I tried to update the kernel, but I just get this:
[root@James James]# yum update kernel
Loaded plugins: refresh-packagekit
Setting up Update Process
No Packages marked for Update

So i'm assuming I have the latest version.

[otnateos]

Eventually got the official driver installed last night, but I got black screen upon reboot, so I booted into text-only mode and found and deleted the ATi driver. I then rebooted and reset the driver to the default radeon hd one. Then I tried this driver and it managed to install fine, but upon reboot it then black screened too, and I wasn't too sure on how to edit the xorg.conf yet, so I re-installed. But after using it for the past couple of hours, the lag (mouse, flash, just general use) is getting quite annoying, but it is running Compiz Fusion really well.

try to reconfigure the driver using aticonfig after removing your xorg.config

aticonfig --initial



So my question is; is there anything else I can do? I tried to update the kernel, but I just get this:
[root@James James]# yum update kernel
Loaded plugins: refresh-packagekit
Setting up Update Process
No Packages marked for Update

So i'm assuming I have the latest version.
you got the latest kernel

[DriftNismo]

try to reconfigure the driver using aticonfig after removing your xorg.config

aticonfig --initial


Ok, done that, re-booted, got black screen with this error:

ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready

So I re-booted into mode 3, removed xorg.conf and tried running aticonfig --initial and now I get this error:

[root@James /]# aticonfig --initial
aticonfig: error while loading shared libraries: /usr/lib/catalyst/libGL.so.1: cannot restore segment prot after reloc: Permission denied

:(

EDIT:

Just rebooted again, now getting this:

tg3 0000:03:02.0: PME# disabled
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
ADDRCONF (NETDEV_CHANGE): eth0: link becomes ready
type=1300 audit(1257646768.573:43026): arch=40000003 syscall=11 success=yes exit=0 a0=9a536e8 a1=9a53718 a2=9a54658 a3=9a536e8 items=2 ppid=2213 pid=2214 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="Xorg" exe="/usr/bin/Xorg" subj=system_u:system_r:xserver_t:s0-s0:c0.c1023 key=(null)
type=1309 audit(1257646768.573:43026): argc=8 a0="usr/bin/Xorg" a1=":5" a2="-br" a3="-verbose" a4="-auth" a5="/var/run/gdm/auth-for-gdm-FpJN3m/database" a6="-nolisten" a7="tcp"
type=1307 audit(1257646768.573:43026): cwd="/var/gdm"
type=1302 audit(1257646768.573:43026): item=0 name="usr/bin/Xorg" inode=83209 dev=fd:00 mode=0104711 ouid=0 ogid=0 rev=00:00 obj=system_u:object_r:xserver_exec_t:s0
type=1302 audit(1257646768.573:43026): item=1 name=(null) inod=82391 dev=fd:00
mode=0100755 ouid=0 ogid=0 rdev=00:00 obj=system_u:object_r:ld_so_t:s0
audit(1257646768.871:43025): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=system_u:system_r:readahead_t:s0 res=1

I don't really know what i'm looking at, but it looks to me like I deleted xorg.conf when I shouldn't have done (without a backup) and now i'm gonna have to re-install in the morning again :|.

[joe.pelayo]

Hey guys, it's unbelievable!

I just installed the Catalyst drivers and they work like a charm in my ATI Radeon HD3200 with Fedora 11 x86_64.

It's awesome.

Good luck,
Joe.

[otnateos]

Ok, done that, re-booted, got black screen with this error:

ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready

So I re-booted into mode 3, removed xorg.conf and tried running aticonfig --initial and now I get this error:

[root@James /]# aticonfig --initial
aticonfig: error while loading shared libraries: /usr/lib/catalyst/libGL.so.1: cannot restore segment prot after reloc: Permission denied

:(

EDIT:

Just rebooted again, now getting this:

tg3 0000:03:02.0: PME# disabled
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
ADDRCONF (NETDEV_CHANGE): eth0: link becomes ready
type=1300 audit(1257646768.573:43026): arch=40000003 syscall=11 success=yes exit=0 a0=9a536e8 a1=9a53718 a2=9a54658 a3=9a536e8 items=2 ppid=2213 pid=2214 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="Xorg" exe="/usr/bin/Xorg" subj=system_u:system_r:xserver_t:s0-s0:c0.c1023 key=(null)
type=1309 audit(1257646768.573:43026): argc=8 a0="usr/bin/Xorg" a1=":5" a2="-br" a3="-verbose" a4="-auth" a5="/var/run/gdm/auth-for-gdm-FpJN3m/database" a6="-nolisten" a7="tcp"
type=1307 audit(1257646768.573:43026): cwd="/var/gdm"
type=1302 audit(1257646768.573:43026): item=0 name="usr/bin/Xorg" inode=83209 dev=fd:00 mode=0104711 ouid=0 ogid=0 rev=00:00 obj=system_u:object_r:xserver_exec_t:s0
type=1302 audit(1257646768.573:43026): item=1 name=(null) inod=82391 dev=fd:00
mode=0100755 ouid=0 ogid=0 rdev=00:00 obj=system_u:object_r:ld_so_t:s0
audit(1257646768.871:43025): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=system_u:system_r:readahead_t:s0 res=1

I don't really know what i'm looking at, but it looks to me like I deleted xorg.conf when I shouldn't have done (without a backup) and now i'm gonna have to re-install in the morning again :|.

I think you should have execute aticonfig --initial as superuser, my mistake not to point that out earlier
sudo aticonfig --initial
I believe that catalyst driver has conflict with radeon, i am not really sure whether when you installed it will automatically add a radeon blacklist into your system or not. in my system i got a file /etc/modprobe.d/blacklist-fglrx.conf with content

# Advanced Micro Devices, Inc.
# radeon conflicts with AMD Linux Graphics Driver
blacklist radeon


In my system I had to tweak my xorg.conf differently, I am not really sure whether this is going to work for you.

Firstly I removed file f/etc/ati/amdpcsdb (probably better if you backup the file)
Then I run sudo aticonfig --initial
I replaced my "Files" section with
Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/catalyst"
ModulePath "/usr/lib64/xorg/modules/extensions"
ModulePath "/usr/lib64/xorg/modules"
EndSection



You may have to change that files section if you are not on x86_64 architecture.

[leigh123linux]

Ok, done that, re-booted, got black screen with this error:

ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not readySo I re-booted into mode 3, removed xorg.conf and tried running aticonfig --initial and now I get this error:

[root@James /]# aticonfig --initial
aticonfig: error while loading shared libraries: /usr/lib/catalyst/libGL.so.1: cannot restore segment prot after reloc: Permission denied:(

EDIT:

Just rebooted again, now getting this:

tg3 0000:03:02.0: PME# disabled
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
ADDRCONF (NETDEV_CHANGE): eth0: link becomes ready
type=1300 audit(1257646768.573:43026): arch=40000003 syscall=11 success=yes exit=0 a0=9a536e8 a1=9a53718 a2=9a54658 a3=9a536e8 items=2 ppid=2213 pid=2214 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="Xorg" exe="/usr/bin/Xorg" subj=system_u:system_r:xserver_t:s0-s0:c0.c1023 key=(null)
type=1309 audit(1257646768.573:43026): argc=8 a0="usr/bin/Xorg" a1=":5" a2="-br" a3="-verbose" a4="-auth" a5="/var/run/gdm/auth-for-gdm-FpJN3m/database" a6="-nolisten" a7="tcp"
type=1307 audit(1257646768.573:43026): cwd="/var/gdm"
type=1302 audit(1257646768.573:43026): item=0 name="usr/bin/Xorg" inode=83209 dev=fd:00 mode=0104711 ouid=0 ogid=0 rev=00:00 obj=system_u:object_r:xserver_exec_t:s0
type=1302 audit(1257646768.573:43026): item=1 name=(null) inod=82391 dev=fd:00
mode=0100755 ouid=0 ogid=0 rdev=00:00 obj=system_u:object_r:ld_so_t:s0
audit(1257646768.871:43025): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=system_u:system_r:readahead_t:s0 res=1I don't really know what i'm looking at, but it looks to me like I deleted xorg.conf when I shouldn't have done (without a backup) and now i'm gonna have to re-install in the morning again :|.


Selinux is blocking the driver from starting.

[Ashish Sood]

Finally i sucessfully install the the ATI driver of my notebook

but after that i m facing the problem while try to upgrade the , my initial ram disk image(initrd)


after the firing the command following r the error is coming

#mkinitrd -v /boot/initrd-'uname -r'.img 'uname -r'

/sbin/mkinitrd: line 964: [: too many arguments
/sbin/mkinitrd: line 969: [: /lib/modules/uname: binary operator expected
Creating initramfs
Looking for driver for /dev/mapper/VolGroup00-LogVol00 in /sys/block/dm-0
Found DeviceMapper component dm-0
Looking for deps of module scsi:t-0x00
Looking for deps of module pci:v00008086d00002929sv00001028sd000002BEbc01sc06 i01
Looking for driver for /dev/sda10 in /sys/block/sda/sda10
Using modules:
mkdir: invalid option -- 'r'
Try `mkdir --help' for more information.
Building initrd in /tmp/initrd.rpd4f4
/sbin/nash -> /tmp/initrd.rpd4f4/bin/nash
/usr/lib/libnash.so.6.0.86 -> /tmp/initrd.rpd4f4/usr/lib/libnash.so.6.0.86
/usr/lib/libbdevid.so.6.0.86 -> /tmp/initrd.rpd4f4/usr/lib/libbdevid.so.6.0.86
/lib/libdevmapper.so.1.02 -> /tmp/initrd.rpd4f4/lib/libdevmapper.so.1.02

/lib/i686/nosegneg//librt-2.10.1.so -> /tmp/initrd.rpd4f4/lib//librt-2.10.1.so
/lib/i686/nosegneg/libpthread.so.0 -> /tmp/initrd.rpd4f4/lib/libpthread.so.0
/lib/i686/nosegneg//libpthread-2.10.1.so -> /tmp/initrd.rpd4f4/lib//libpthread-2.10.1.so
/lib/libtinfo.so.5 -> /tmp/initrd.rpd4f4/lib/libtinfo.so.5
/lib//libtinfo.so.5.7 -> /tmp/initrd.rpd4f4/lib//libtinfo.so.5.7
/sbin/modprobe -> /tmp/initrd.rpd4f4/bin/modprobe
/sbin/rmmod -> /tmp/initrd.rpd4f4/bin/rmmod

/usr/lib/plymouth/text.so -> /tmp/initrd.rpd4f4/usr/lib/plymouth/text.so
/usr/share/plymouth/themes/details/details.plymouth -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/details/details.plymouth
/usr/lib/plymouth/details.so -> /tmp/initrd.rpd4f4/usr/lib/plymouth/details.so
/usr/share/pixmaps/system-logo-white.png -> /tmp/initrd.rpd4f4/usr/share/pixmaps/system-logo-white.png
/etc/system-release -> /tmp/initrd.rpd4f4/etc/system-release
/etc//fedora-release -> /tmp/initrd.rpd4f4/etc//fedora-release
/usr/lib/plymouth/two-step.so -> /tmp/initrd.rpd4f4/usr/lib/plymouth/two-step.so
/usr/share/plymouth/themes/charge/box.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/box.png
/usr/share/plymouth/themes/charge/bullet.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/bullet.png
/usr/share/plymouth/themes/charge/charge.plymouth -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/charge.plymouth
/usr/share/plymouth/themes/charge/entry.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/entry.png
/usr/share/plymouth/themes/charge/lock.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/lock.png
/usr/share/plymouth/themes/charge/progress-00.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-00.png
/usr/share/plymouth/themes/charge/progress-01.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-01.png
/usr/share/plymouth/themes/charge/progress-02.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-02.png
/usr/share/plymouth/themes/charge/progress-03.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-03.png
/usr/share/plymouth/themes/charge/progress-04.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-04.png
/usr/share/plymouth/themes/charge/progress-05.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-05.png
/usr/share/plymouth/themes/charge/progress-06.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-06.png
/usr/share/plymouth/themes/charge/progress-07.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-07.png
/usr/share/plymouth/themes/charge/progress-08.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-08.png
/usr/share/plymouth/themes/charge/progress-09.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-09.png
/usr/share/plymouth/themes/charge/progress-10.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-10.png
/usr/share/plymouth/themes/charge/progress-11.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-11.png
/usr/share/plymouth/themes/charge/progress-12.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-12.png
/usr/share/plymouth/themes/charge/progress-13.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-13.png
/usr/share/plymouth/themes/charge/progress-14.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-14.png
/usr/share/plymouth/themes/charge/progress-15.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-15.png
/usr/share/plymouth/themes/charge/progress-16.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-16.png
/usr/share/plymouth/themes/charge/progress-17.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-17.png
/usr/share/plymouth/themes/charge/progress-18.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/progress-18.png
/usr/share/plymouth/themes/charge/throbber-00.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-00.png
/usr/share/plymouth/themes/charge/throbber-01.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-01.png
/usr/share/plymouth/themes/charge/throbber-02.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-02.png
/usr/share/plymouth/themes/charge/throbber-03.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-03.png
/usr/share/plymouth/themes/charge/throbber-04.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-04.png
/usr/share/plymouth/themes/charge/throbber-05.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-05.png
/usr/share/plymouth/themes/charge/throbber-06.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-06.png
/usr/share/plymouth/themes/charge/throbber-07.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-07.png
/usr/share/plymouth/themes/charge/throbber-08.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-08.png
/usr/share/plymouth/themes/charge/throbber-09.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-09.png
/usr/share/plymouth/themes/charge/throbber-10.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-10.png
/usr/share/plymouth/themes/charge/throbber-11.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-11.png
/usr/share/plymouth/themes/charge/throbber-12.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-12.png
/usr/share/plymouth/themes/charge/throbber-13.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-13.png
/usr/share/plymouth/themes/charge/throbber-14.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-14.png
/usr/share/plymouth/themes/charge/throbber-15.png -> /tmp/initrd.rpd4f4/usr/share/plymouth/themes/charge/throbber-15.png
Adding module scsi_wait_scan
WARNING: Couldn't open directory /tmp/initrd.rpd4f4/lib/modules/2.6.29.4-167.fc11.i686.PAE: No such file or directory
FATAL: Could not open /tmp/initrd.rpd4f4/lib/modules/2.6.29.4-167.fc11.i686.PAE/modules.dep.temp for writing: No such file or directory
"/sbin/depmod -a uname -r" failed.

[DriftNismo]

I think you should have execute aticonfig --initial as superuser, my mistake not to point that out earlier
sudo aticonfig --initial

Tried that too, it just said the same thing, just took a bit longer.

Selinux is blocking the driver from starting.

Is there any way to make it allow the driver to start?

[leigh123linux]

Tried that too, it just said the same thing, just took a bit longer.



Is there any way to make it allow the driver to start?


Try

su
chcon -t textrel_shlib_t '/usr/lib/catalyst/libGL.so.1.2'
chcon -t textrel_shlib_t '/usr/lib/catalyst/libatiadlxx.so'

[DriftNismo]

Try

su
chcon -t textrel_shlib_t '/usr/lib/catalyst/libGL.so.1.2'
chcon -t textrel_shlib_t '/usr/lib/catalyst/libatiadlxx.so'

I tried:
echo 0 >/selinux/enforce

Just for the time being so I could run the driver, and then when I ran the driver it didn't have a permission problem, but it is now saying:

[root@James ~]# sudo aticonfig --initial
aticonfig: No supported adapters detected

Sorry for asking so many questions, I always seem to have the most problems with Linux.

EDIT: Upon speaking with a couple friends who all run Ubuntu/Fedora as their main OS, I think I'll switch back to the Nvidia Quadro until the majority of the ATi problems are cleared up. Thanks to everybody who helped though :).

[Mudhoney]

any idea why this line would not work for me:

# yum install kmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs.i586
Loaded plugins: protectbase, refresh-packagekit
0 packages excluded due to repository protections
Setting up Install Process
No package kmod-catalyst available.
No package xorg-x11-drv-catalyst available.
No package xorg-x11-drv-catalyst-libs.i586 available.
Nothing to do



# yum repolist
Loaded plugins: protectbase, refresh-packagekit
repo id repo name status
adobe-linux-i386 Adobe Systems Incorporated enabled: 17
fedora Fedora 11 - x86_64 enabled: 16,577
livna rpm.livna.org for 11 - x86_64 enabled: 3
rpmfusion-free RPM Fusion for Fedora 11 - Free enabled: 423
rpmfusion-free-updates RPM Fusion for Fedora 11 - Free - Updates enabled: 502
updates Fedora 11 - x86_64 - Updates enabled: 7,837
repolist: 25,359

[Demz]

try thisyum -noplugins install kmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs.i586
or itsyum --noplugins install kmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs.i586

[Mudhoney]

# yum --noplugins install kmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs.i586
Setting up Install Process
No package kmod-catalyst available.
No package xorg-x11-drv-catalyst available.
No package xorg-x11-drv-catalyst-libs.i586 available.
Nothing to do

[Demz]

did you try both? do this instead yum --noplugins install kmod-catalyst let yum handle the deps

you may need to use C an not a lowercase c in cat

[AdamW]

He doesn't have the RPM Fusion non-free repos enabled, only free. The driver's in non-free, obviously :)

[Mudhoney]

yeah that was it - added the non-free packages to yum manually and works fine now.

Thanks for help.

[Demz]

do you have that repo enabled now? cause its gonna need to get updates

[Mudhoney]

yes, thanks. I initially followed the instructions here (http://rpmfusion.org/Configuration/) but it didn't seem to work, so i just copied the files for the free repos under /etc/yum.repos.d/ and searched and replaced everything "free" with "nonfree". I had to import the GPG key for nonfree, but all seems to work now.

So previously I was doing this whenever a kernel upgrade happened:
1. uninstall proprietary ATi driver as per uninstall instructions here (http://www.fedoraforum.org/forum/showthread.php?t=228689)
2. download and run ati linux driver from ati
3. follow the bits of the instructions at the start of this thread that worked (all expect the catalyst yum stuff)
4. reboot

So from now on I guess I can skip step 2 - correct?

[Demz]

you should be able to

[randomdood]

just wondering if anybody else has frame tearing..
gets quite annoying sometimes.

[winglessbuzzard]

Howto for F12







There is currently no FGLRX support for F12 at the moment, please file your complaints on the ATI website.







.
This post:
http://gofedora.com/news-ati-catalyst-graphics-drivers-9-11-released/
seems to indicate 9.11 drivers are compatible with Fedora 12.

I am a complete linux n00b. I installed Fedora 12 yesterday (my first Linux OS). It seems like the 9.11 drivers (released yesterday) may work with Fedora 12. I can't get them installed and I have no idea what I'm doing wrong... since I really am not too sure of what I'm doing in the first place. Here's a copy/paste of my Terminal - attempted running of the installation file:

[Wes@localhost ~]$ su
Password:
[root@localhost Wes]# $ bash ./home/Wes/Downloads/ati-driver-installer-9-11-x86.x86_64.run
bash: $: command not found
[root@localhost Wes]# /home/Wes/Downloads/ati-driver-installer-9-11-x86.x86_64.run
bash: /home/Wes/Downloads/ati-driver-installer-9-11-x86.x86_64.run: Permission denied

Sorry for my n00bgnorance, but what do I need to do to get this installed?

[Hlingler]

The correct command is 'sh', not 'bash'. But the *.run will probably fail.

V

[winglessbuzzard]

Actually I think I tried the 'sh' yesterday and it did fail. I'll try it again tonight when I get home from work.

[Hlingler]

Might need to make it executable first:
[Wes@localhost ~]$ chmod +x /home/Wes/Downloads/ati-driver-installer-9-11-x86.x86_64.run
su
cd Downloads
[...]

V

P.S. make sure you've already got kernel-devel to match running kernel, plus kernel-headers, make, gcc, gcc-c++, autoconf, automake ... that should be enough.

P.P.S. You might want to have a look here too: http://forums.fedoraforum.org/showthread.php?t=228689
since it pertains to using the ATI binary installers. NOTE however that some of the info may or may not be applicable to F12.

[mariuszs]

off-topic, but Compiz play nice with ATI cards WITHOUT f***d Catalyst Drivers in F12. Just install
sudo yum -y install mesa-dri-drivers-experimental
and enable effects.

[Hlingler]

Compiz play nice with ATI cards WITHOUT ... Catalyst Drivers in F12Yeah, but: WHICH ATI chipsets are supported ???

V

[leigh123linux]

Tar ball contents

http://dnmouse.org/fedora/leigh123linux/fglrx_x86_PAE.tar.bz2

kmod-catalyst-2.6.31.5-127.fc12.i686.PAE-9.11-1.fc12.i686.rpm
kmod-catalyst-PAE-9.11-1.fc12.i686.rpm
xorg-x11-drv-catalyst-9.11-1.fc12.i686.rpm
xorg-x11-drv-catalyst-libs-9.11-1.fc12.i686.rpmInstall with


su
yum --nogpgcheck install *catalyst*rpmExtra tweaks will be needed i.e add nomodeset to grub.conf

[leigh123linux]

http://dnmouse.org/fedora/leigh123linux/fglrx-x86_64.tar.bz2

kmod-catalyst-2.6.31.5-127.fc12.x86_64-9.11-1.fc12.x86_64.rpm
kmod-catalyst-9.11-1.fc12.x86_64.rpm
xorg-x11-drv-catalyst-9.11-1.fc12.x86_64.rpm
xorg-x11-drv-catalyst-libs-9.11-1.fc12.x86_64.rpm

[AdamW]

hlingler: without -experimental, up to r500. with -experimental, r600 seems to mostly work okay, some r700s are also reported to work. r800, all bets are off so far, but we should have something soonish (weeks or months).

winglessbuzzard managed to screw up all his attempts; if you look closely the first one fails because of a spurious $ character he wrote into the command (and a spurious . before the /home). The second would've worked if the chmod hlingler suggested had been done.

I don't think we know for sure yet whether 9.11 can work with F12. The big question is the X server version, not the kernel version. F12 uses X server 1.7.1, other distros are all still on 1.6, so it may work for other distros but not F12. Be interested to know whether it does work when someone tries it.

[leigh123linux]

hlingler: without -experimental, up to r500. with -experimental, r600 seems to mostly work okay, some r700s are also reported to work. r800, all bets are off so far, but we should have something soonish (weeks or months).

winglessbuzzard managed to screw up all his attempts; if you look closely the first one fails because of a spurious $ character he wrote into the command (and a spurious . before the /home). The second would've worked if the chmod hlingler suggested had been done.

I don't think we know for sure yet whether 9.11 can work with F12. The big question is the X server version, not the kernel version. F12 uses X server 1.7.1, other distros are all still on 1.6, so it may work for other distros but not F12. Be interested to know whether it does work when someone tries it.


It didn't work well with my Nvidia card ;)

[leigh123linux]

Tar ball contents

http://dnmouse.org/fedora/leigh123linux/fglrx_x86_PAE.tar.bz2

kmod-catalyst-2.6.31.5-127.fc12.i686.PAE-9.11-1.fc12.i686.rpm
kmod-catalyst-PAE-9.11-1.fc12.i686.rpm
xorg-x11-drv-catalyst-9.11-1.fc12.i686.rpm
xorg-x11-drv-catalyst-libs-9.11-1.fc12.i686.rpmInstall with


su
yum --nogpgcheck install *catalyst*rpmExtra tweaks will be needed i.e add nomodeset to grub.conf


Nearly 1 1/2 hours and nobody has tried it :p

[Soapta]

http://dnmouse.org/fedora/leigh123linux/fglrx-x86_64.tar.bz2

kmod-catalyst-2.6.31.5-127.fc12.x86_64-9.11-1.fc12.x86_64.rpm
kmod-catalyst-9.11-1.fc12.x86_64.rpm
xorg-x11-drv-catalyst-9.11-1.fc12.x86_64.rpm
xorg-x11-drv-catalyst-libs-9.11-1.fc12.x86_64.rpm

i tried it, no go :(

II) LoadModule: "fglrx"
(II) Loading /usr/lib64/xorg/modules/drivers/fglrx_drv.so
dlopen: /usr/lib64/xorg/modules/drivers/fglrx_drv.so: undefined symbol: resVgaShared
(EE) Failed to load /usr/lib64/xorg/modules/drivers/fglrx_drv.so
(II) UnloadModule: "fglrx"
(EE) Failed to load module "fglrx" (loader failed, 7)
(EE) No drivers available.

[leigh123linux]

i tried it, no go :(

II) LoadModule: "fglrx"
(II) Loading /usr/lib64/xorg/modules/drivers/fglrx_drv.so
dlopen: /usr/lib64/xorg/modules/drivers/fglrx_drv.so: undefined symbol: resVgaShared
(EE) Failed to load /usr/lib64/xorg/modules/drivers/fglrx_drv.so
(II) UnloadModule: "fglrx"
(EE) Failed to load module "fglrx" (loader failed, 7)
(EE) No drivers available.


You didn't edit grub.conf ! ( I believe the open source driver is blocking fglrx from loading)


Kernel command line: ro root=UUID=9dfc4cc6-f1aa-4b4e-8102-29af0c3b1061 LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quietThere is no warning about the Xorg version which is good.

[AdamW]

leigh: nope, you're wrong. That's the *X driver module* failing to load, not the kernel module. So obviously he _did_ edit xorg.conf (or it wouldn't be trying to load the fglrx X driver), and this has nothing to do with grub.conf. It looks like what I feared - incompatibility with our X server.

[Soapta]

You didn't edit grub.conf ! ( I believe the open source driver is blocking fglrx from loading)

tried again:
- booted with "nomodeset" option to runlevel 3
- manually removed all other kernel modules except ide/sata/sound/usb
- loaded kernel module fglrx.ko (wich worked)
- aticonfig --initial (also worked)
- xinit
result: same error. then i searched all files in / for (containing) the text "resVgaShared" but to no avail ...

lThat's the *X driver module* failing to load, not the kernel module. So obviously he _did_ edit xorg.conf (or it wouldn't be trying to load the fglrx X driver)
yes, it's the X driver module not the kernel module.

[leigh123linux]

leigh: nope, you're wrong. That's the *X driver module* failing to load, not the kernel module. So obviously he _did_ edit xorg.conf (or it wouldn't be trying to load the fglrx X driver), and this has nothing to do with grub.conf. It looks like what I feared - incompatibility with our X server.


Thanks , it looks like ATI users will have to wait another month till ATI releases 9.12 ( hopefully they will add support for the new Xorg version by then) .

[Demz]

month?.. try a few months

[leigh123linux]

month?.. try months

They can live in hope that ATI will be quick, but I wouldn't put money on it :(

[Demz]

They can live in hope that ATI will be quick, but I wouldn't put money on it :(

exactly, ATI have never been quick to release a workable driver, what was it X-Server 1.5? when other distro's were still on 1.4. how long did ATI take to release a workable driver for that

[mariuszs]

Yeah, but: WHICH ATI chipsets are supported ???

V
As AdamW said r500 works (my x1200 works excellent), and r600 works (my HD3430 works excellent), and some of r700 works too

[mck182]

leigh, what about catalyst for F11? Any packages yet?

[leigh123linux]

leigh, what about catalyst for F11? Any packages yet?

See post #2

[mck182]

See post #2

Sorry, I forgot to add _9.11_ catalyst drivers :) As they are not in rpmfusion(-testing) yet and because I saw couple posts earlier that you did F12 packages, that's why I asked about those 9.11 for F11 ;)

[JordanN]

AMD referred me to their Linux Crew survey form: http://www.amd.com/us/LinuxCrewSurvey

[AltGrendel]

This is why I now wait until Leigh is done working his magic before I upgrade.

[Ravnos]

Have anyone tried downgrading related packages to use the F11 version ? It might be an option for those not willing to wait for the sluggish support from ATI ... when I have time I will give it a shot (haven't upgraded to F12 yet). It should be something like we did before in F9:

1- Create F11 repo
2- Blacklist some packages in the F12 repos, these were blacklisted in F9 before:

perl -i -pe "s/(\[.*\])/\1\nexclude=xorg* linuxwacom* rhpxl* mesa* libsynaptics synaptics/" /etc/yum.repos.d/fedora-updates.repo

3- Remove F12 mesa packages (I am not sure which ones should be removed to make the error go away, these were removed in F9)

rpm -e --nodeps --allmatches mesa-libGL mesa-libGLU mesa-libGL-devel mesa-libGLU-devel mesa-
dri-drivers glx-utils

4- Install F11 packages with yum

Of course the packages that should be downgraded are probably different now, so do not try doing like I have mentioned above. And other problems might also arise after that ...

[ppesci]

I am using F10 and do not planed to upgrade upgrade until a good open source radeon driver appear for my Mobility Radeon X1600 (R500 series) and R500 drivers are not currently developed by ATI.

But to my surprise is this phoronix article:

http://www.phoronix.com/scan.php?page=article&item=fedora_12_ati&num=1

English is not my first but they are doing test with F12 and X1800 (R520) card. In this thread (The Mother of All Threads i think) states in post #1 there is no support for ATI drivers in F12.

What I am missing?

Can I think in upgrade to F12 and use fglrx driver for my X1600 some day?

TIA

[joe.pelayo]

I am using F10 and do not planed to upgrade upgrade until a good open source radeon driver appear for my Mobility Radeon X1600 (R500 series) and R500 drivers are not currently developed by ATI.

But to my surprise is this phoronix article:

http://www.phoronix.com/scan.php?page=article&item=fedora_12_ati&num=1

English is not my first but they are doing test with F12 and X1800 (R520) card. In this thread (The Mother of All Threads i think) states in post #1 there is no support for ATI drivers in F12.

What I am missing?

Can I think in upgrade to F12 and use fglrx driver for my X1600 some day?

TIA
Someone correct me if I am wrong, but what I understood from the article is that tests were being done with some sort of successor of the 'classic' radeon driver (the one that in principle ain't proprietary), not with fglrx (Catalyst), the proprietary ATI driver.

So, in conclusion, I'd say that while the Catalyst driver has dropped support for older ATI chips (I seriously doubt it would support them again latter), the experimental "OSS" radeon drivers are consistently catching up to support them properly.

So yes, if your card is adequately supported by the radeon driver you might as well use F12.

Thanks,
Joe.

[AdamW]

ravnos: I suspect the ATI driver doesn't work with X server 1.7, which would mean you'd need to revert the entire X stack to the version from F11. Which would be extremely painful, and likely to cause other problems.

[Ravnos]

ravnos: I suspect the ATI driver doesn't work with X server 1.7, which would mean you'd need to revert the entire X stack to the version from F11. Which would be extremely painful, and likely to cause other problems.

Yeah, I know that :D

And I don't think it is a good solution either, but I guess it will not hurt trying ;)

[ppesci]

Someone correct me if I am wrong, but what I understood from the article is that tests were being done with some sort of successor of the 'classic' radeon driver (the one that in principle ain't proprietary), not with fglrx (Catalyst), the proprietary ATI driver.

So, in conclusion, I'd say that while the Catalyst driver has dropped support for older ATI chips (I seriously doubt it would support them again latter), the experimental "OSS" radeon drivers are consistently catching up to support them properly.

So yes, if your card is adequately supported by the radeon driver you might as well use F12.

Thanks,
Joe.

Thanks Joe, I didn't see the open source driver in page 1.

On the other side I am following the radeon and radeonhd development in an Xorg pages and in some cases 3D programs doesn't run yet.

[tdaniel]

I'm still wondering why ATI keeps messing up when it comes to other things than games.

I believe that ATI should focus on beating nvidia at tflops since at software they are unable to keep up the pace with the rest of the world.

Unfortunately for me, i have ATI tflop units, because at this moment i cannot consider them graphic cards, on my desktop and notebook as well.

The notebook chip is not supported anymore by their driver. Its an ATI Mobility FireGL v5200. The desktop one is an ATI RadeonHD 3870 that does not work due to the X server being not supported by the proprietary driver.

At the moment the radeon driver, which i use on the notebook, and the radeonhd driver on the desktop are at a fallback level since the level of functionality is like a car with the spare tire on.

I also thought at reverting back to X 1.6 with the aid of F11 repos but i don't have the required knowledge.

I'm willing to experiment with the desktop system if someone will lend me a hand and provide me with some advices.

I apologize for the rant but this situation is at least ridiculous, for ATI that is :)

[spynic]

I found a temporary solution that works for me:

# yum install mesa-dri-drivers-experimental

F12, ATI HD 4670

As of now, desktop effects work. Will try compiz fusion with all its bells and whistles, and update.

[Demz]

Thanks Joe, I didn't see the open source driver in page 1.

On the other side I am following the radeon and radeonhd development in an Xorg pages and in some cases 3D programs doesn't run yet.

i thought radeonhd was dropped for just radeon

[tdaniel]

I found a temporary solution that works for me:

# yum install mesa-dri-drivers-experimental

F12, ATI HD 4670

As of now, desktop effects work. Will try compiz fusion with all its bells and whistles, and update.

That's the spare tire i mentioned :)

This is what i currently use on the desktop system with KDE 4.3.3, try enabling a HDTV with that and see what happens.

To update my experience so far with this i will make a short list of what does work acceptably and what doesn't.

First of all, I use KDE 4.3.3 as a desktop.

What works:

- Desktop effects: performance good, artefacts minor.
- 3D acceleration: DRI on, acceleration functional

glxinfo:
[daniel@localhost]$ glxinfo
name of display: :0.0
IRQ's not enabled, falling back to busy waits: 2 0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample,
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_make_current_read,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (RV670 9501) 20090101 TCL
OpenGL version string: 1.5 Mesa 7.7-devel

glxgears:

[daniel@localhost ovz]$ glxgears -fullscreen
IRQ's not enabled, falling back to busy waits: 2 0
2566 frames in 5.0 seconds = 513.017 FPS
2694 frames in 5.0 seconds = 538.616 FPS
2694 frames in 5.0 seconds = 538.635 FPS
2683 frames in 5.0 seconds = 536.499 FPS
2694 frames in 5.0 seconds = 538.791 FPS

HD Movies: Played a 720p movie with DTS sound.

What does not work:

- Web browsing experience is poor. Occasional artefacts when scrolling. Flash performance poor with alphablended and multiple animated objects.
- Occasional desktop artefacts.
- In dual display mode with different resolutions on the panels i didn't managed to have a consistent display in clone mode. In spanning mode, the apps have the tendency to display on the larger one (HDTV) even if the computer monitor is the primary one. Without the proprietary driver, multiple displays management is a nightmare.
- 2D performance poor, rendering is slow as with the case of flash, artefacts are more frequent than with 3D renderings.

[AdamW]

it's worth testing with modesetting disabled (performance with the 3D stuff turned on is better without KMS, currently) and also with all the latest stuff from Koji - try the latest F12 radeon, libdrm, mesa and kernel packages, see if they change anything.

[tdaniel]

KMS is off since more problems are exhibited if turned on. Also, the proprietary driver would never load as long as KMS is enabled since this loads the radeon module anyway.

What does the "latest" mean ?

I currently have the following versions:

[root@localhost ~]# rpm -qa | grep -i ati
xorg-x11-drv-ati-6.13.0-0.11.20091119git437113124.fc12.i686

[root@localhost ~]# rpm -qa | grep -i radeon
xorg-x11-drv-radeonhd-1.3.0-3.15.20091112git.fc12.i686

[root@localhost ~]# rpm -qa | grep -i libdrm
libdrm-2.4.15-5.fc12.i686

[root@localhost ~]# rpm -qa | grep -i mesa
mesa-demos-7.6-0.15.fc12.i686
mesa-libGL-devel-7.6-0.15.fc12.i686
mesa-libGLU-7.6-0.15.fc12.i686
mesa-dri-drivers-experimental-7.6-0.15.fc12.i686
mesa-libGLw-6.5.1-8.fc12.i686
mesa-libGLU-devel-7.6-0.15.fc12.i686
mesa-libOSMesa-devel-7.6-0.15.fc12.i686
mesa-dri-drivers-7.6-0.15.fc12.i686
mesa-libOSMesa-7.6-0.15.fc12.i686
mesa-libGLw-devel-6.5.1-8.fc12.i686
mesa-libGL-7.6-0.15.fc12.i686

[root@localhost ~]# rpm -qa | grep -i kernel
abrt-addon-kerneloops-1.0.0-1.fc12.i686
kernel-2.6.31.5-127.fc12.i686
kernel-headers-2.6.31.6-145.fc12.i686
abrt-plugin-kerneloopsreporter-1.0.0-1.fc12.i686
kernel-devel-2.6.31.6-145.fc12.i686
kernel-2.6.31.6-145.fc12.i686
kernel-firmware-2.6.31.6-145.fc12.noarch
kernel-devel-2.6.31.5-127.fc12.i686
[root@localhost ~]#

[spynic]

That's the spare tire i mentioned :)

This is what i currently use on the desktop system with KDE 4.3.3, try enabling a HDTV with that and see what happens.

To update my experience so far with this i will make a short list of what does work acceptably and what doesn't.

First of all, I use KDE 4.3.3 as a desktop.

What works:

- Desktop effects: performance good, artefacts minor.
- 3D acceleration: DRI on, acceleration functional

glxinfo:
[daniel@localhost]$ glxinfo
name of display: :0.0
IRQ's not enabled, falling back to busy waits: 2 0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample,
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_make_current_read,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (RV670 9501) 20090101 TCL
OpenGL version string: 1.5 Mesa 7.7-devel

glxgears:

[daniel@localhost ovz]$ glxgears -fullscreen
IRQ's not enabled, falling back to busy waits: 2 0
2566 frames in 5.0 seconds = 513.017 FPS
2694 frames in 5.0 seconds = 538.616 FPS
2694 frames in 5.0 seconds = 538.635 FPS
2683 frames in 5.0 seconds = 536.499 FPS
2694 frames in 5.0 seconds = 538.791 FPS

HD Movies: Played a 720p movie with DTS sound.

What does not work:

- Web browsing experience is poor. Occasional artefacts when scrolling. Flash performance poor with alphablended and multiple animated objects.
- Occasional desktop artefacts.
- In dual display mode with different resolutions on the panels i didn't managed to have a consistent display in clone mode. In spanning mode, the apps have the tendency to display on the larger one (HDTV) even if the computer monitor is the primary one. Without the proprietary driver, multiple displays management is a nightmare.
- 2D performance poor, rendering is slow as with the case of flash, artefacts are more frequent than with 3D renderings.

oh sorry, I may have overlooked it.
And yea, true, it still can't give you the best performance. Can't wait for the ATI drivers.

[Naraku]

Still no FGLRX support for F12? :(

[Demz]

Still no FGLRX support for F12? :(

complain to AMD/ATI, its not fedora's fault that there isnt any support for ATI users

[tdaniel]

Still no FGLRX support for F12? :(

Let me rephrase that for you: Still no F12 support by FGLRX ? :D

[Naraku]

It wasn't my intention to blame Fedora. ;)

[moley2k8]

anyone got any idea when a full driver will be available? Not having any problems other than occasional artefacts and dual monitor resolution issues.

don't really want half a driver though, debating whether to downgrade back to F11.

[leigh123linux]

anyone got any idea when a full driver will be available? Not having any problems other than occasional artefacts and dual monitor resolution issues.

don't really want half a driver though, debating whether to downgrade back to F11.


Ask ATI :(

[Demz]

my guess the same problem will happen in F13 when thats released to the public

since F13 should have X-Server-1.8.x

[moley2k8]

DOH! I should have read things through!

I've downgraded back to 11 but still have problems because my laptop only has a Mobility Radeon X1350 in it. From what I'm seeing, I won't get much further in F11 will I?

Get a faster frame rate in glxgears though. More than doubled from 350 odd to 800fps now. Something to be pleased about I suppose.

[Ravnos]

DOH! I should have read things through!

I've downgraded back to 11 but still have problems because my laptop only has a Mobility Radeon X1350 in it. From what I'm seeing, I won't get much further in F11 will I?

Get a faster frame rate in glxgears though. More than doubled from 350 odd to 800fps now. Something to be pleased about I suppose.

I guess you would have better luck with the radeon driver in F12 than you have in F11, unfortunately I don't have a X1350 to give you feedback ...

[amrlima]

Aparently catalyst 9.12 will be released in December 16. http://twitter.com/CatalystMaker/statuses/6503170288

If this is really a catalyst developer :). Hope it's will work with Fedora 12 Xorg. Radeon power management is really bad with with my laptop (HD3400). I get less half an hour of battery with radeon then what I would have with fglrx.

[vall]

Aparently catalyst 9.12 will be released in December 16. http://twitter.com/CatalystMaker/statuses/6503170288

If this is really a catalyst developer :). Hope it's will work with Fedora 12 Xorg. Radeon power management is really bad with with my laptop (HD3400). I get less half an hour of battery with radeon then what I would have with fglrx.

I also hope they will release it soon. I have HD4370 on my Sony and with the redeon driver the CPU runs some 15-20 degrees hotter than with catalyst.

[gauchao]

I used to run my phenomX4 + radeon 3870x2 in Fedora11 with the basic radeon video driver. In F12, when I started the fresh install process, I could only go on when chose the "install with basic video drivers" method. Now I have F12 running slower than with my previous F11 installation. I have looked into xorg.conf:

Section "Device"
Identifier "Videocard0"
Driver "vesa"
EndSection

Any idea on how I can improve it, without throwing this ATI card in the wastebasket? It wasn't cheap and ATI is to be blamed about it... but I am a redhat/fedora user since 1995.... we always fix up things around here ;)

PS.: has anyone here tried this? (http://ubuntuforums.org/showthread.php?t=1272346&highlight=3870x2)

[tdaniel]

Hello,

You will have to disable kernel mode setting first. It's a new feature present in the Linux kernel that is shipped with F12.

Modify your kernel boot parameters in the grub's configuration file with the "nomodeset" paramater.

After that, modify the "Driver" line in your xorg.conf file with "radeon" or "radeonhd" instead of "vesa".

Test which driver works best for you between radeon and radeonhd. I found radeonhd to provide better 3d support but exhibits more problems than the radeon driver.

[rsingh]

Catalyst 9.12 is out!!! Yay!

http://www.phoronix.com/scan.php?page=news_item&px=NzgxOA

A quote from the Release notes:

Before attempting to install the ATI CatalystTM Linux software suite, the following
software must be installed:
XOrg 6.8, 6.9, 7.0, 7.1, 7.2, 7.3 or 7.4 :D finally!
Linux kernel 2.6 or above
glibc version 2.2 or 2.3
POSIX Shared Memory (/dev/shm) support is required for 3D applications

[leigh123linux]

Catalyst 9.12 is out!!! Yay!

http://www.phoronix.com/scan.php?page=news_item&px=NzgxOA

A quote from the Release notes:

Before attempting to install the ATI CatalystTM Linux software suite, the following
software must be installed:
XOrg 6.8, 6.9, 7.0, 7.1, 7.2, 7.3 or 7.4 :D finally!
Linux kernel 2.6 or above
glibc version 2.2 or 2.3
POSIX Shared Memory (/dev/shm) support is required for 3D applications


I don't see any mention of Xorg 7.5 :(

[Demz]

isnt F12 still using Xorg7.4?

[leigh123linux]

isnt F12 still using Xorg7.4?

9.10 supported 7.4

http://support.amd.com/us/gpudownload/linux/9-9/Pages/radeon_linux.aspx

[Demz]

ohh ok, i didnt think F12 had Xorg7.5 in it.

[amrlima]

I tried to install the driver in Fedora 12 following this guide http://forums.fedoraforum.org/showthread.php?t=228689&language=en

It didn't work :(

(II) LoadModule: "fglrx"
(II) Loading /usr/lib64/xorg/modules/drivers/fglrx_drv.so
dlopen: /usr/lib64/xorg/modules/drivers/fglrx_drv.so: undefined symbol: UpdateSpriteForScreen
(EE) Failed to load /usr/lib64/xorg/modules/drivers/fglrx_drv.so
(II) UnloadModule: "fglrx"
(EE) Failed to load module "fglrx" (loader failed, 7)
(EE) No drivers available.

I need better power management then the radeon driver provides :(. I really don't feel like changing distro, I love Fedora but AMD is killing me here. By the time the next driver is available Fedora 13 will be here and... here we go again :(

[maladeus]

I need better power management then the radeon driver provides :(. I really don't feel like changing distro, I love Fedora but AMD is killing me here. By the time the next driver is available Fedora 13 will be here and... here we go again :(

I'm in the same boat. Still on 11 because on 12 my laptop goes to 90ºC with the open source drivers. Actually 12 is has a 10ºC improvement on the radeon drivers over 11.
From what I read on phoronix there have been continuous improvements regarding power management on the radeon stack since 12 came out, with a little luck, 13 might be the number that frees us from catalyst. That or a nightbuild on 12.

[rsingh]

DAMMIT DAMMIT DAMMIT... :mad:

I thought F12 had xorg 7.4
Oh well, back to the waiting game.

[tdaniel]

That is the problem with the proprietary driver, it does not support X.org's 7.5.

The problem is caused by the Xorg module that the Catalyst package provides to interface with the kernel module.

The Xorg module is not compatible anymore since it uses deprecated code to interface with the Xorg server.

Xorg alone is unable to use the fglrx kernel module directly. It requires a helper that materializes in the form of a Xorg module. This is the point where it all falls apart :|

[joe.pelayo]

Come on guys! F11 isn't that bad.

I've been enjoying it very much since I installed the Catalyst driver about 2 months ago. Hope to 'catch up' with F12 in late January.

Thanks,
Joe.

[rsingh]

For people missing out on compiz effects, I would recommend trying out mesa-dri-drivers-experimental. Compiz works flawlessly and video playback also. Not sure about games though. The drivers seem pretty stable and I haven't had a crash at all till now. Performance also is proper.

to install all that is required is:

# yum install mesa-dri-drivers-experimental

and a reboot.

[tdaniel]

For people missing out on compiz effects, I would recommend trying out mesa-dri-drivers-experimental. Compiz works flawlessly and video playback also. Not sure about games though. The drivers seem pretty stable and I haven't had a crash at all till now. Performance also is proper.

to install all that is required is:

# yum install mesa-dri-drivers-experimental

and a reboot.

Please see: http://forums.fedoraforum.org/showpost.php?p=1300815&postcount=3812

This "solution" was proposed one page behind this one.

[HMSS013]

ATI Releases Catalyst Control 9.12... can we expect an RPM Fusion package soon?!

[Demz]

ATI Releases Catalyst Control 9.12... can we expect an RPM Fusion package soon?!

9.12 does not work in F12

[HMSS013]

9.12 does not work in F12

you've come to that conclusion in a little over 48 hours?

[Demz]

you've come to that conclusion in a little over 48 hours?
pretty clever dont you think eh

---------- Post added at 01:19 PM CST ---------- Previous post was at 01:17 PM CST ----------

though would help if you had said what fedora version you have

---------- Post added at 01:33 PM CST ---------- Previous post was at 01:19 PM CST ----------

http://forums.fedoraforum.org/showpost.php?p=1307234&postcount=3830

consider this my last post to you, i dont help smarta$$es

[HMSS013]

pretty clever dont you think eh

---------- Post added at 01:19 PM CST ---------- Previous post was at 01:17 PM CST ----------

though would help if you had said what fedora version you have

---------- Post added at 01:33 PM CST ---------- Previous post was at 01:19 PM CST ----------

http://forums.fedoraforum.org/showpost.php?p=1307234&postcount=3830

consider this my last post to you, i dont help smarta$$es

lol... says the guy with the sarcastic responses. :rolleyes:

fear not tho... as you've been literally no help to me you're record for assisting 'smarta$$es' remains untarnished.

[fz1rider]

I've got a HD 3870 running on Fedora 11. Instructions have worked great since fedora9 (Thanks!). However I'm currently having a problem where the screen just locks up occasionally. System is fine, I can ssh in, run any commands I want. But all video output is dead, I can't Ctrl-F2 to a new terminal I can init 3 from a ssh session but it won't affect the monitor output. There are no messages in the log indicating an error.

Ideas?

I'm usually not doing much when this happens. I don't use many graphics intensive apps (other than desktop cube and other compiz utils). 90% of the time I'm just moving my mouse across the screen when the problem occurs. My only solution is to reboot.

[gordoco]

I've got a HD 3870 running on Fedora 11. Instructions have worked great since fedora9 (Thanks!). However I'm currently having a problem where the screen just locks up occasionally. System is fine, I can ssh in, run any commands I want. But all video output is dead, I can't Ctrl-F2 to a new terminal I can init 3 from a ssh session but it won't affect the monitor output. There are no messages in the log indicating an error.

Ideas?

I'm usually not doing much when this happens. I don't use many graphics intensive apps (other than desktop cube and other compiz utils). 90% of the time I'm just moving my mouse across the screen when the problem occurs. My only solution is to reboot.

Similar symptoms here. I have an HD 5770, Fedora 11, fglrx 9.12 with two monitors. I've had several lockups and crashes by moving the mouse off the bottom edge of the second monitor (first is 1920x1200, second is 1280x1024). I haven't experimented to see if other actions cause it to fail.

I've seen two failure modes: either the display locks up with exactly the symptoms described above (I can ssh in, but no Ctrl-F2), or the system immediately reboots as though I hit the reset button: no panic, no oops.

[fz1rider]

Similar symptoms here. I have an HD 5770, Fedora 11, fglrx 9.12 with two monitors. I've had several lockups and crashes by moving the mouse off the bottom edge of the second monitor (first is 1920x1200, second is 1280x1024). I haven't experimented to see if other actions cause it to fail.

I've seen two failure modes: either the display locks up with exactly the symptoms described above (I can ssh in, but no Ctrl-F2), or the system immediately reboots as though I hit the reset button: no panic, no oops.

I want to say my locking also happens when moving from one monitor to the other, I know the last time it occured was switching between monitors. I've not paid close enough attention on the previous locks. I'm running dual monitors in one large desktop configuration (3200x1200) so the locking would be moving between them on the edge (1600-1601 if you will). I've not had the reboot scenario yet, only locking.

Also, I'm quite certain this is not some hardware issue as the system was running fine under fedora 10. It was not until I upgraded and followed the procedures at the beginning of this post that the locking started to occur.

Thanks again for any help.

[fairmonk]

Hi there,
got a Radeon X1950 Pro, apparently no drivers available yet for it on Fedora 12, pls correct me if I'm wrong.
Also after issuing lspci -v I get 01:00.0 VGA compatible controller: ATI Technologies Inc RV570 [Radeon X1950 Pro] (rev 9a) (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited Device e190
Flags: bus master, fast devsel, latency 0, IRQ 28
Memory at d0000000 (64-bit, prefetchable)
Memory at fade0000 (64-bit, non-prefetchable) [size=64K]
I/O ports at c000 [size=256]
Expansion ROM at fadc0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
Kernel modules: radeon
which takes me to conclusion that the video board doesn't run at its full capacity. However I could enable Compiz from desktop effects.
I got a question, what is Compiz-fusion? a link to some explanations about it would be very appreciated or just in a couple words pls....and of course my second question is whether I can make use of it with current video configuration. That's it for now :D

[SIZE=1]---------- Post added at 12:26 AM CST ---------- Previous post was at 12:24 AM CST ----------

and ye, this Video Card is 256MB/256bit

[fz1rider]

I want to say my locking also happens when moving from one monitor to the other, I know the last time it occured was switching between monitors. I've not paid close enough attention on the previous locks. I'm running dual monitors in one large desktop configuration (3200x1200) so the locking would be moving between them on the edge (1600-1601 if you will). I've not had the reboot scenario yet, only locking.

Just had another lockup (getting very frustrating). This time it did not occur when I was switching screens, I was on one screen (left if it matters) and had been for a good minute or so and then the system locked.

Please help, this doesn't appear to be an isolated incident as another user has reported similar problems.

Thanks.

[tdaniel]

Well, this is not a support thread as the category name mentions (Guides & Solutions (No Questions) Post your guides here. You can also add your comments to a guide, but don't start a thread to ask a question. Use another forum for that.).

I hardly think that assistance from capable members will be obtained here.

What i do recommend, based on my experience so far is that you collect some details from your environment and create a thread with this issue in the section of the forums for issue reports.

Another approach would be to create a bug report in the fedora bugzilla or search the bugzilla for similar reports, maybe there is a fix available already.

The details regarding your environment should contain things like:

- Xorg.conf file
- Xorg log file for the respective session when the screen output stopped (i think it is a screen output issue than a lockup due to the fact that you are able to ssh the machine)
- dmesg output
- lspci -v output

---------- Post added at 10:45 AM CST ---------- Previous post was at 10:35 AM CST ----------

Hi there,
got a Radeon X1950 Pro, apparently no drivers available yet for it on Fedora 12, pls correct me if I'm wrong.
Also after issuing lspci -v I get 01:00.0 VGA compatible controller: ATI Technologies Inc RV570 [Radeon X1950 Pro] (rev 9a) (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited Device e190
Flags: bus master, fast devsel, latency 0, IRQ 28
Memory at d0000000 (64-bit, prefetchable)
Memory at fade0000 (64-bit, non-prefetchable) [size=64K]
I/O ports at c000 [size=256]
Expansion ROM at fadc0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
Kernel modules: radeon
which takes me to conclusion that the video board doesn't run at its full capacity. However I could enable Compiz from desktop effects.
I got a question, what is Compiz-fusion? a link to some explanations about it would be very appreciated or just in a couple words pls....and of course my second question is whether I can make use of it with current video configuration. That's it for now :D

[SIZE=1]---------- Post added at 12:26 AM CST ---------- Previous post was at 12:24 AM CST ----------

and ye, this Video Card is 256MB/256bit

This thread contains detailed explanations why your board is not fully supported at this moment in Fedora 12. I recommend on reading the last few pages to get a more detailed picture of the current situation.

The short version is that ATI did not released a driver, yet, that supports the xorg server version used in F12. The Xorg server provides graphic screen output and is the backbone of all the graphical desktop environments available on Linux.

The current driver (Catalyst 9.12) still lacks support for xorg version 1.7.1 (7.6) and the only drivers available are the open source ones (radeon and radeonhd).

Compiz-fusion is a merger (hence the "fusion") of two projects with the same goal (Compiz and Beryl). It provides a 3d accelerated desktop (the famous spinning cube) using the OpenGL 3d framework and OpenGL hardware acceleration support found in most of the video cards today.

[Jeff72]

I've got a HD 3870 running on Fedora 11. Instructions have worked great since fedora9 (Thanks!). However I'm currently having a problem where the screen just locks up occasionally. System is fine, I can ssh in, run any commands I want. But all video output is dead, I can't Ctrl-F2 to a new terminal I can init 3 from a ssh session but it won't affect the monitor output. There are no messages in the log indicating an error.

Ideas?

I'm usually not doing much when this happens. I don't use many graphics intensive apps (other than desktop cube and other compiz utils). 90% of the time I'm just moving my mouse across the screen when the problem occurs. My only solution is to reboot.

For Fedora 11, please look at the Additional Considerations link at the end of post #2 (http://forums.fedoraforum.org/showpost.php?p=1257973&postcount=3564) for help with your system lock ups.

Specifically, look at this section on the Additional Considerations link:
"Fix desktop locking up after login and while moving windows around:"

[ajamison]

you've come to that conclusion in a little over 48 hours?

It says on the release notes for 9.12 that it only supports xorg up to 7.4 and Fedora 12 shipps with 7.5 so by definition it does not work

[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

[rshartog]

I have the same problem as the poster above.

I have an F11 install with the Catalyst drivers installed according to this guide. The installation has worked correctly since Nov 2009 and I have performed a system update (using "System-->Administration-->Software Update") about every week.

Today I performed a system update as usual. Everything appeared to go smoothly, but now when I reboot, my screen is black when I normally see the login screen. I don't even see the little spinning cursor that appears before the logon screen. I can VNC into my desktop from another machine, so the system is up and running behind the curtain.

I have tried reinstalling the driver according to this guide, but the results are the same (black screen). At the moment, I have the driver uninstalled which allows my system to function normally but is, of course, sub-optimal.

So my questions are these...

Was there a bad release of the drivers and many are experiencing this problem or this a problem on my end?
If it is on my end, how do I even begin to debug a problem like this?


Help will be appreciated. If more information is needed (logs, config files), please let me know and I will psot them.

--Scott

[hajo01]

Same problem here, update as of 2 days ago broke the system. For now I have switched back to the stock radeon driver, will investigate deeper in the next 2-3 days, time permitting.

I'm not in front of my box right now, but it appears that this was actually an update of catalyst 9.10 -> 9.12.

[pballok]

I have exactly the same problem since I updated this morning. I'm using F11
I try to boot to older kernel versions (that are still present in my GRUB menu) but no help, I get the same black screen. I can switch to text terminal with Ctrl-Alt-2 for example, and the system works fine, just no X.

I also noticed something else, although I might have nothing to do with this problem:
my GRUB also started acting strangely, although there was no grub package updated. Before this update, my GRUB just displayed the default boot target and started the countdown in the same line (top line of the screen). Now, after the yum update this morning, it starts filling the screen with new lines of text in every second. It does not update the top line with the new countdown value, but instead prints a new line, complete with boot target name and the new countdown value.
I don't see how this is related to the "black screen after boot", I just thought I'd mention it since it also occurred right after the last yum update.

Any help is greatly appreciated, thanks in advance ;)

[leigh123linux]

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]

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]

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]

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 (https://bugzilla.rpmfusion.org/show_bug.cgi?id=1054)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]

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]

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


This didn't work for me :(

[adrianx]

Mine is working now (inspired by hajo01)...

Booted into runlevel 3 (CTRL+ALT+F2 would probably also work)
Log in as root
yum reinstall *catalyst*
livna-config-display --active off
restored my most recent backup of /etc/X11/xorg.conf
reboot

I'm not sure if "livna-config-display --active off" and restoring /etc/X11/xorg.conf were necessary, but my xorg.conf isn't quite default.
I think the reinstall part may have (somehow) done the trick.

Edit: B.t.w., here is a list of the files that were reinstalled (F11 x86_64):

xorg-x11-drv-catalyst-libs-9.12-1.fc11.x86_64
xorg-x11-drv-catalyst-9.12-1.fc11.x86_64
kmod-catalyst-2.6.30.10-105.2.4.fc11.x86_64-9.12-1.fc11.1.x86_64
kmod-catalyst-2.6.30.9-102.fc11.x86_64-9.10-1.fc11.3.x86_64
kmod-catalyst-9.12-1.fc11.1.x86_64
kmod-catalyst-2.6.30.10-105.fc11.x86_64-9.12-1.fc11.x86_64
xorg-x11-drv-catalyst-libs-9.12-1.fc11.i586

[space-hunter]

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...

That's my solution after update and black screen (no screen)
Thanks a lot for that :)

[leigh123linux]

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...


Thanks, post added to post #2

[Demz]

Catalyst 10.1 for Linux continues to lack X Server 1.7 support, but the Linux 2.6.32 kernel may work with this release.

http://www.phoronix.com/scan.php?page=news_item&px=NzkzMQ

[Firewing1]

Updated RPM Fusion packages for F-11 coming soon :)

[Demz]

almost like ATI are forcing people to use the opensource Radeon driver

---------- Post added at 10:23 AM CST ---------- Previous post was at 10:22 AM CST ----------

gonna suck for those people using Ubuntu 10.04 also

[AltGrendel]

That's my solution after update and black screen (no screen)
Thanks a lot for that :)

Confirmed here too.

[pballok]

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!


Worked like a charm, thanks a lot hajo ;)

[corp769]

for me, that definitely helped. i had to reinstall some packages and I had to remake my initrd for the fourth time. if anyone is still having trouble, try this, it worked for me:

yum reinstall kmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs
init 3 (optional, but recommended)
mkinitrd -v /boot/initrd-`uname -r`.img `uname -r`
rm /etc/ati/amdpcsdb
aticonfig --initial -f
reboot


of course as root.... but yea, this worked perfectly for me, and took all errors away. thanks to the guys who first found the fix for this, hopefully my some-what different way can help others who still have problems.

[HMSS013]

are the opensource Radeon drivers even useable?! ...i'm going nuts thinking that ATI isn't working to remedy this issue.

[Demz]

are the opensource Radeon drivers even useable?! ...i'm going nuts thinking that ATI isn't working to remedy this issue.

dont expect ATI to release a working driver in a Hurry for F13 either. but i think there is someone else using the opensource driver in this thread

[hajo01]

I'm actually not so sure how much ATI can be blamed for this problem. I didn't look at their original installer lately, but they may very well be deleting the /etc/ati/amdpcsdb during install, at least for selected versions -- I guess they know by which update the old DB creates incompatibilities.
The RPM-packager however has decided not to delete the file on upgrade with the argument that user's settings would be deleted when erasing the file. They have however indicated that the issue will be mentioned in the RPM's README and on their wiki. I leave it up to the individual to decide who's at fault, it's a grey area for me...

[ajamison]

How is it that Nvidia allways seems to support xorg servers latest version yet ATI lacks

[leigh123linux]

How is it that Nvidia allways seems to support xorg servers latest version yet ATI lacks

I believe nvidia has some deal with the film industry :cool:


http://www.phoronix.com/scan.php?page=news_item&px=NjM3MQ


FYI nvidia works with kernel 2.6.33 rc and the latest Xorg server (1.8 testing) :D


http://forums.fedoraforum.org/showthread.php?t=239527

[Fuzzie]

Hi guys,

I can confirm that it is actually possible to use catalyst in Fedora 12 if you downgrade your xorg from 1.7 to 1.6 (see terminal output):

http://img690.imageshack.us/img690/5675/screenshotxv.th.png (http://img690.imageshack.us/i/screenshotxv.png/)

However, I honestly cannot recommend this "solution" and you are seriously better off with either Fedora 11, VESA graphics or a nVidia replacement card. (I'm pretty sure I broke a couple of things)

Be patient. Just thought I should let you guys know ;)

Edit: the startup applications fixed itself....

[Icm76]

Would it be a terrible mistake to get an ATi card to use with Fedora? I was going to get a 5830 for Windows gaming, but I much prefer Fedora for everything else. After reading post 1 of this guide and skimmed through some of the comments it sounds really frustrating to use Catalyst and impossible to keep up with the latest Fedora. I've never had an Ati card so it's difficult to judge for sure. Should the ATi cards be completely avoided or am I reading too much into this?

[tkalfaoglu]

Not at all.. I just rebuilt myself a PC, an ASUS motherboard, AMD chip (my first!), and ATI HD 4670 PCI Express display, fedora 12. Runs like crazy, it's so fast and stable that I weep every time I sit down to play Warcraft on it.. My glxgears is over 10,000 :)

-turgut

[Fuzzie]

Not at all.. I just rebuilt myself a PC, an ASUS motherboard, AMD chip (my first!), and ATI HD 4670 PCI Express display, fedora 12. Runs like crazy, it's so fast and stable that I weep every time I sit down to play Warcraft on it.. My glxgears is over 10,000 :)

-turgut

That's great. :)

I have a HD 5xxx myself, but sadly no mesa-dri-drivers-experimental support for me. So, your mileage might vary.

[5hady]

I have a 4770 myself, the mesa experimental drivers work fin for me, but admittedly I do no gaming in Linux.

What would happen if I got another 4770 to run in crossfire? I don't really expect mesa to run both cards, but would it break fedora entirely? Hmmm

[Icm76]

I have a HD 5xxx myself, but sadly no mesa-dri-drivers-experimental support for me.I wouldn't be gaming on Linux, but I do want Compiz support and a system that doesn't break frequently with updates. Nvidia with the akmod version drivers has been pretty good in this regard.

[Fuzzie]

I wouldn't be gaming on Linux, but I do want Compiz support and a system that doesn't break frequently with updates. Nvidia with the akmod version drivers has been pretty good in this regard.

Honestly, I've only been using my ATI card just very recently (I had an older Nvidia 9600GT but the fan started rattling), so I wouldn't know about the track record so far.

The Radeon HD 5830 card you want to buy will need ATI's drivers because there's no opensource driver that can support it (yet), and ATI's drivers do not support the current Xorg in Fedora 12 (yet). Unless you downgrade your Xorg, you won't get Compiz support or resolutions other than VESA. Chances are, this will happen every time there is a major upgrade of Xorg, so you might want to keep that in mind.

Edit: I found a page listing the status of the opensource driver here (http://xorg.freedesktop.org/wiki/RadeonFeature). 5830 is a "Evergreen" card.

[Jeff72]

Catalyst 10.2 (http://ati.amd.com/support/driver.html) is available now.

Apparently there is no xorg-server 1.7 support (no Fedora 12 support) yet, according to Phoronix (http://www.phoronix.com/scan.php?page=news_item&px=Nzk5MQ).

[del_diablo]

Regardless, it should work. Unless 1.8 gets pushed over us............

[Demz]

The release notes for the Catalyst 10.2 Linux release are not yet available nor is the AMD web-site updated, but savvy readers have located the 10.2 download link. Upsetting many users is the fact that Catalyst 10.2 still lacks support for X Server 1.7, which has been released as stable since last October and has already had five point releases. With the X.Org Server 1.7-using Ubuntu 10.04 LTS coming in April, Catalyst 10.3 or 10.4 will support this updated X.Org Server finally. However, at the end of March this cycle will be restarted all over again once X Server 1.8 has been released. http://www.phoronix.com/scan.php?page=news_item&px=Nzk5MQ

[del_diablo]

*sigh* So we need to rip of the 10.04 beta of Ubuntu?

Edit: So we need to backport in the old xorg........ Or pray that blender runs under the lateast radeon driver.

[HMSS013]

anyone have any luck with Catalyst 10.2??


... also... i've been reading that the generic Radeon drivers now fully support HD 2400 cards... any opinions?!

[Demz]

anyone have any luck with Catalyst 10.2??


... also... i've been reading that the generic Radeon drivers now fully support HD 2400 cards... any opinions?!

did you read the post above?. 10.2 still lacks support for x-server 1.7 an above

[HMSS013]

did you read the post above?. 10.2 still lacks support for x-server 1.7 an above

wow bro... i think you have anger issues.

[Demz]

wow bro... i think you have anger issues.

yes i do, i get it from stupid people

[Dan]

Okey, dokey. That'll be enough of that.

[5hady]

having these ati gpus kinda makes me angry tho.

[shep]

Almost working - compiz would work fine in KDE (except for a strange mouse cursor issue that was present in both de's), but switching to Gnome(my preferred desktop) resulted in major instability: random locks/hangs/restarts of window manager with no window borders. Every successful reboot required the deletion of all compiz configs so that I could actually use my GUI in any way, shape or form. Eventually, I just altered the gconf-editor to switch back to metacity as default and checked the composite_manager checkbox to get some true transparency for my terminal.

My ATi drivers are obviously working - "glxinfo | grep render" gives my a "yes", and fgl_glxgears was running at ~3200fps (fullscreen) on my 4870.

I didn't even want anything too fancy - some transparency was all I was after, so I switched to xfce and everything is now as I wanted it without running compiz. The system is not sluggish in any way, and the mouse cursor artefact issue is not present at all.

Got to admit (slightly off topic) - i'm really liking xfce. The de is easily as fast as Gnome on my system.

[Cyberhawk]

...
With the X.Org Server 1.7-using Ubuntu 10.04 LTS coming in April, Catalyst 10.3 or 10.4 will support this updated X.Org Server finally.
...


Why is the issue so fixed to a release of a new Ubuntu version?
That basically means one is better of with using Ubuntu to have
good support of Radeon-cards?

[Demz]

Why is the issue so fixed to a release of a new Ubuntu version?
That basically means one is better of with using Ubuntu to have
good support of Radeon-cards?

Ubuntu Probably use a hack like everything else they do :D . 10.3 Driver should have 1.7 support

[AdamW]

Canonical has some kind of relationship with ATI here. Obviously, since Red Hat and Fedora prioritize the development of free software over non-free, we don't have any such relationship over the proprietary driver, though we do work together with ATI/AMD on developing the free driver.