I just read from my own blog about that the ATI propriety drivers is now working with Fedora 13 (thanks Jack). So I decided to test and install ATI Catalyst 10.11 (fglrx) proprietary drivers. And try new ATI Catalyst 10.11 Proprietary drivers with my ATI Radeon HD 3650 card. This is guide, howto install and uninstall ATI Catatlyst 10.11 (fglrx) Drivers. Installation is very easy with using RPMFusion Non-Free repository. But this installation guide also includes instructions, how to remove/uninstall ATI drivers. An remove/uninstall guide might be useful, if you have these problems with ATI drivers.
Install ATI Catalyst (fglrx) 10.11 Proprietary Drivers on Fedora 13
1. Change root user
su -
## OR ##sudo-i
2. Backup current xorg.conf file (If you have some customizations)
glxinfo |grep-i"\(render\|opengl\)"
direct rendering: Yes
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 3600 Series
OpenGL version string: 3.3.10057 Compatibility Profile Context
OpenGL shading language version string: 3.30
OpenGL extensions:
GL_NV_conditional_render, GL_NV_copy_depth_to_color,
glxgears comparison between ATI Catalyst 10.11 Proprietary Drivers VS ATI 3D Mesa DRI Radeon Open Source Drivers
ATI Catalyst 10.11 Proprietary Drivers glxgears results
Here is a example screenshot of Thunderbird fetching mails:
Image black areas due to ATI’s drivers.
Due to these problems, I decided to switch back to the ATI open source drivers. If you have same problems and want to revert back to open source drivers then check following, it should be easy if you have all backups.
Fixing ATI Catalyst 10.11 black/grey/white boxes/fragments in Firefox, Thunderbird, Metacity, XFWM…
Jack and Aniruddha reported following nice fix for this problem.
Stop/kill X server first
init 3
Then run following command
aticonfig –set-pcs-str=DDX,ForceXAA,TRUE
Start X server again
init 5
This turn on old (slower xaa) method of 2d rendering. But results is still nice.
Uninstall/Remove and Revert back to ATI Mesa 3D DRI Radeon Open Source Drivers
Nice guide:-) One more hint: you might want to set your initdefault (in /etc/inittab) to 3 for testing purposes before you reboot (in between step 8. and 9. in this guide that is). That way you won’t run into trouble in case something goes wrong and your x server doesn’t start at all. Helped me a lot when testing graphics drivers.
Thanks, I tested ATI drivers and wrote this guide inspired by your message. :)
Really nice hint, I added it to this guide.
Another way to boot any runlevel with grub is following:
1. Access Grub boot menu
2. Press “e” (edit)
3. Select kernel line and press “e” (edit) again
4. Add runlevel (1,3,5) end of line
5. Press Enter
6. Press “b” (boot) and boot with modified kernel line
I managed to get rid of that gray/black fragment problem with the following command:
aticonfig –set-pcs-str=DDX,ForceXAA,TRUE
which obviously sets the driver into a fallback mode using an older rendering method.
Not sure if that’s any disadvantage but fps with glxgears are still roughly 6 times faster than with the open source driver.
Actually, a LOT of people seem to have that issue … I found that hint under: http://forums.fedoraforum.org/showthread.php?t=155503&page=270
Someone in that thread also reported it depends on your window manager and that
compiz works fine, while metacity causes problems. I haven’t checked that out yet, using
XFCE (with standard xfwm) here, and I’m too lazy to figure out how to replace it right now, that everything seems to work so far.
The driver worked after I have rolled back to the previous version but I have noticed that I get kernel crashes very often. does anyone of you have the same problem?
my system(fedora 13 64 bit. kernel 2.6….(latest one), video ati mobility 3670)
I have not had kernel crashes, but I have used ATI Catalyst on 32-bit environment. And mine card is basic ATI Radeon HD 3650 (not ATI Mobility version). How do these kernel crashes occur?
If someone else has encountered these problems, it would be interesting to know. And if someone has solved these problems, it would also be nice to know.
I have kernel crashes as well. I’m running the latest version akmod ATI driver and with the latest kernel. I like you have the Radeon HD 3650, except it’s a plug in AGP card.
The call in question:
Package: kernel
Latest Crash: Mon 16 May 2011 12:16:41 PM
Command: not_applicable
Reason: BUG: sleeping function called from invalid context at mm/slub.c:1701
Comment: None
Bug Reports:
Occasionally (like this morning) it will just hang before launching the KDM login screen. The way I’ve gotten around this (in case anyone else experiences this problem) is press ALT+CTRL+F2 (to F6) log in as root:
init 3
init 5
Then you should get to your log in manager. I’m in process of uninstalling the ATI driver and switching to the open source driver. I need a system that’s more reliable with less intervention.
before i install ati driver, some error found(just installed linux, i dont touch anything).
there are no loading bar animation (when booting) just so fast text showing.
kind of..
—
*error* faild to allocate domain, *error* faild to allocate : size(not sure)
—
looks like it is all about radeon. but xwindow is fine at row res.
Hi. I have installed Fedora 13 64 bit on Dell studio 1555. I have an updated kernel (2.6.34.7-56.fc13.x86_64) that is greater than the one rpmfusion packagers have used to compile and package the catalyst-kmod. I read on their site how to rebuild this kmod but the procedure fail early at the rpmbuild command, giving me this output:
%description -n kmod-catalyst-2.6.34.7-56.fc13.x86_64
This package provides the catalyst kernel modules built for the Linux
kernel 2.6.34.7-56.fc13.x86_64 for the %{_target_cpu} family of processors.
%files -n kmod-catalyst-2.6.34.7-56.fc13.x86_64
%defattr(644,root,root,755)
/lib/modules/2.6.34.7-56.fc13.x86_64/extra/catalyst/
Neither if I do all as root it works. I have the same issue. But trying in the sixth installation step akmod in place of kmod it seems to have no problem installing it, execpt for the fact that when I reboot 3d doesn’t work and either 2d feature seems to have problem.
Sorry I gave up, I reverted all and came back to open driver, which by the way seems to have 3d acceleration enabled but certainly doesn’t have the power to change gpu frequencies and to rule gpu power management as proprietary driver do, which is the reason why I was trying to install proprietary driver.
One thing what you could easily try is to use older kernel and ATI Catalyst proprietary drivers or wait updated ATI Catalyst drivers to RPMFusion repo.
Open Source drivers will generally work well, but the features are really quite far away from proprietary drivers. I personally currently use open source drivers with ATI-cards, because I don’t really need any proprietary driver features.
Haha, clearly nobody that responded is familiar with C code. The kernel devs reimplemented the compat_alloc_user_space() function to fill a major security hole. Unfortunately, they also decided to make it GPL-only, so AMD is no longer allowed to use the function in their driver.
If you use a kernel with the fix (and you should!), driver versions up through 10.9 will no longer compile. 10.10 has a lazily implemented workaround, but I’m not sure RPMFusion has packages for it yet.
I have not yet tested this with Fedora 14, but the situation with ATI support looks once again the same as it always has in the past. So no way yet to get ATI propriety drivers working on Fedora 14. If someone gets ATI propriety drivers to work on Fedora 14, please share it with us. :) So currently I recommend ATI open source drivers on Fedora 14 or Fedora 13 with ATI propriety drivers.
I have tried this nice HOWTO on my FC13 Thinkpad T400 with Radeon HD 3400. Basically, it works. Problem 1: Yum installation of kmod failed for me with –enablerepo=rpmfusion-nonfree-updates-testing
Now there is version 10.11 of Catalyst driver in the regular (non-testing) rpmfusion-nonfree-updates, which I have enabled by default (disabling it would be a fix for problem 1.), so I have installed the regular, not the testing package(s).
Good news is, that I did not experience any the black/grey/white boxes/fragments, at least not in Firefox.
Later I have identified some issues. Problem 2: to attach external display, and use it in a multi-desktop dual screen configuration, krandr/xrandr does not work. One must use “ATI Catalyst Control Center (Administrator)”, which requires root password (!). After few clicks to get the “multi display” configuration you click on apply and you get a hint to restart the system (Ouch! Are we in Windoze?) However, log-out & log-in does the same job as reboot. So, at least till the next boot, you will not need to reboot to use the external screen… (isn’t this stupid?) Problem 3: This is something I was aware off. Suspend to disk is not working. Usually it freezes during suspend. once I have succeeded to suspend (the laptop powered off), but later it did not resume, but just booted as if it was not suspended.
Suspend to RAM also does not work. Well, to tell the truth, it suspends – but does not resume – the system gets frozen instead.
So thanks a lot to JR for publishing also the Uninstall instructions!
I’m back with the good old on-board Intel graphics… where I even have a framebuffer console…
My resume is, that current Catalyst drivers in Fedora 13 work may be on server or a desktop box – and only if you do not suspend it, but just shutdown/boot.
Bottom line: current NVidia drivers can do all this. Have one 210 in my desktop.
BTW, with Catalyst 10.11, glxgears scored 900-1900 FPS and fgl_glxgears approx 170-210 FPS, both using approx 80% of CPU
hi
thanks for your post.
i am new in linux world . i work on fedora 13 ( my laptop Dell N5010)
i follow the step but i have a problem when I reboot in step 6
i can not access to fedora , the prompt is appear when i reboot and ask me login and password.
what can i do ??
any body can help me ???
please please help me ..
thanks for all…
Hello, I followed the instructions word for word and it worked somewhat. The driver worked however it was very slow. glxgears ran at about 600 frames per second. This rendered all of my games uselessly slow.
Has anyone had any success with an Radeon 6xxxM series graphics card or does anyone have any suggestions?
thought I’d ask here again, because this lovely blog with it’s guides helped me so much to get my ati radeon card running with fedora 13 in the first place. Maybe someone’s got a hint for me
My problem is as follows:
I’m still using fedora 13, 32bit,with the ati driver from rpmfusion. As everything worked just perfectly, I never really felt any need to upgrade to fedora 14 or later. Now I recently got some extra memory for my system, upgrading from 2gbs to 4gbs. For some reason fedora only seemed to recognize 3gbs of that memory with the non PAE kernel that I’ve been using so far.
So, even though it says that the PAE kernel is only required for more than 4gbs of memory (and I have exactly 4gbs now, isn’t that odd?) I installed the PAE kernel. That fixed the memory problem but wrecked my video driver. When I try to start X with the PAE kernel, the screen just goes blank and the system completely hangs. The non-PAE kernel still works fine (though with 3gbs of memory). And no, I didn’t forget to install kmod-catalyst-PAE. I also read that ati propriety installer now also works for fedora, so I tried that approach. But the problem remains: I can install the latest release of the driver, buildthe module and so forth, but when I start the x server it goes all blank and hangs (yes, it hangs … can’t even access the system via ssh anymore).
Now I’m pretty much at a loss on what to do now. Go and install the latest fedora, maybe even the 64bit one instead? I should add, I’m rather worried that a 64bit distro migth reduce performance or cause even more driver problems. Or do you have any hint on how to debug my problem? I tried to the x server output in a file, but alas, it hangs before any output is written. Any assitance would be greatly appreciated.
Thanks,
Jack
@Andrew: did you check, if the driver kernel module is loaded properly (with glxinfo)? I’ve noticed that you can run the driver without, but then it’s slow as hell.
Try this:
1. Boot to runlevel 3 without X. On Grub -> select PAE kernel and press ‘e’ -> select kernel row and press ‘e’ again -> add space and 3 end of kernel row -> press ‘enter’ -> and then press ‘b’.
don’t worry about grub, I’ve already set initdefault to 3 anyway. And I did remove and reinstall the driver a couple of times. The problem remains:
the driver runs just perfectly with the non-PAE kernel, while I just get a blank screen with the PAE kernel. This result is exactly the same with the rpmfusion-kmod and the ati propriety installer.
Do you happen to know, where the ati propriety driver kernel modules for each kernel are stored exactly? Maybe it just uses the wrong one. There should be 2 modules, right? One for the PAE and one for the non PAE kernel (the one I’m using right now, or I couldn’t even write this text).
Thanks a lot in advance for any clues you might have.
the module’s there, it’s just it’s not working, or something else’s not working, lsmod output:
“fglrx 2461928 0″
StillI’ve learnt one thing from trying as you suggested: obviuosly the ati installer exclusively places the module for current kernel into the corresponding directory. So, when I have the module, for the PAE kernel, the one for the non-PAE one is removed and vice versa. You’d need to run the installer again if you switch the kernel. However, that doesn’t seem to be the core of my problem. I can run the PAE kernel, load the module, and when I start the x server, the system crashes, while it works just fine with the “normal” kernel.
Alas, duess, I either have to live with 1gb less memory, or I’ll have to switch to 64bits or some other distro where I don’t need that particular PAE kernel, unless you have any other suggestions? In any case thanks so much for all of your advice.
I did as you suggested and checked the log files, but alas, there’s nothing logged at all.
For the same reason that I don’t get anything with “startx &> logfile” Xorg.0.log is
just an empty file. I crashes so fast, that nothing get’s even logged or written.
All I can do is press the reset button, which feels pretty strange on a linux system (with win95 I used to rely on that button a lot, but never with linux so far).
There’s one error in Xorg.9.log:
“[ 68.989] (EE) No input driver/identifier specified (ignoring)”, but I suspect, that’s
some old, non critical error, that has no relevance to my problem.
I did as you suggested and checked the log files, but alas, there’s nothing logged at all.
For the same reason that I don’t get anything with “startx &> logfile” Xorg.0.log is
just an empty file. It crashes so fast, that nothing get’s even logged or written.
All I can do is press the reset button, which feels pretty strange on a linux system (with win95 I used to rely on that button a lot, but never with linux so far).
There’s one error in Xorg.9.log:
“[ 68.989] (EE) No input driver/identifier specified (ignoring)”, but I suspect, that’s
some old, non critical error, that has no relevance to my problem.
This sounds very tricky problem, because you don’t get any errors to log. One thing what you could do is upgrade your Fedora and try to install PAE kernel and drivers on Fedora 14 or even Fedora 15.
Fedora 13 ATI Drivers (Mesa 3D DRI Radeon) - [...] Advertise with If Not True Then FalseLatestCommentsFeaturedPopular Fedora 13 ATI Catalyst 10.7 Proprietary Drivers (fglrx) 09 August ...
I just read from my own blog about that the ATI propriety drivers is now working with Fedora 13 (thanks Jack). So I decided to test and install ATI Catalyst 10.11 (fglrx) proprietary drivers. And try new ATI Catalyst 10.11 Proprietary drivers with my ATI Radeon HD 3650 card. This is guide, howto install and uninstall ATI Catatlyst 10.11 (fglrx) Drivers. Installation is very easy with using RPMFusion Non-Free repository. But this installation guide also includes instructions, how to remove/uninstall ATI drivers. An remove/uninstall guide might be useful, if you have these problems with ATI drivers.
Nice guide:-) One more hint: you might want to set your initdefault (in /etc/inittab) to 3 for testing purposes before you reboot (in between step 8. and 9. in this guide that is). That way you won’t run into trouble in case something goes wrong and your x server doesn’t start at all. Helped me a lot when testing graphics drivers.
Hi again Jack,
Thanks, I tested ATI drivers and wrote this guide inspired by your message. :)
Really nice hint, I added it to this guide.
Another way to boot any runlevel with grub is following:
1. Access Grub boot menu
2. Press “e” (edit)
3. Select kernel line and press “e” (edit) again
4. Add runlevel (1,3,5) end of line
5. Press Enter
6. Press “b” (boot) and boot with modified kernel line
Heya again,
I managed to get rid of that gray/black fragment problem with the following command:
aticonfig –set-pcs-str=DDX,ForceXAA,TRUE
which obviously sets the driver into a fallback mode using an older rendering method.
Not sure if that’s any disadvantage but fps with glxgears are still roughly 6 times faster than with the open source driver.
Actually, a LOT of people seem to have that issue … I found that hint under:
http://forums.fedoraforum.org/showthread.php?t=155503&page=270
Someone in that thread also reported it depends on your window manager and that
compiz works fine, while metacity causes problems. I haven’t checked that out yet, using
XFCE (with standard xfwm) here, and I’m too lazy to figure out how to replace it right now, that everything seems to work so far.
I had the same problem with thunderbird and fglrx. I fixed this on Debian with the following command: # aticonfig –set-pcs-str=DDX,ForceXAA,TRUE
Source: http://wiki.archlinux.org/index.php/ATI_Catalyst
Thanks Jack and Aniruddha
I added your (aticonfig –set-pcs-str=DDX,ForceXAA,TRUE) tip to this guide.
But hey, I recommend keep the uninstall instructions close, when the Fedora 14 is released… ;D
Thank you guys for the advice about the catalyst,
The driver worked after I have rolled back to the previous version but I have noticed that I get kernel crashes very often. does anyone of you have the same problem?
my system(fedora 13 64 bit. kernel 2.6….(latest one), video ati mobility 3670)
Thank you
Hi andreas,
I have not had kernel crashes, but I have used ATI Catalyst on 32-bit environment. And mine card is basic ATI Radeon HD 3650 (not ATI Mobility version). How do these kernel crashes occur?
If someone else has encountered these problems, it would be interesting to know. And if someone has solved these problems, it would also be nice to know.
Hi JR,
I have kernel crashes as well. I’m running the latest version akmod ATI driver and with the latest kernel. I like you have the Radeon HD 3650, except it’s a plug in AGP card.
The call in question:
Package: kernel
Latest Crash: Mon 16 May 2011 12:16:41 PM
Command: not_applicable
Reason: BUG: sleeping function called from invalid context at mm/slub.c:1701
Comment: None
Bug Reports:
Occasionally (like this morning) it will just hang before launching the KDM login screen. The way I’ve gotten around this (in case anyone else experiences this problem) is press ALT+CTRL+F2 (to F6) log in as root:
init 3
init 5
Then you should get to your log in manager. I’m in process of uninstalling the ATI driver and switching to the open source driver. I need a system that’s more reliable with less intervention.
thanks about this post.
but, if i install ati driver like this, i cant boot fedora13. just prompt.
my card is ati5770.
sorry. i cant write english well.
and fedora x64(updated).
before i install ati driver, some error found(just installed linux, i dont touch anything).
there are no loading bar animation (when booting) just so fast text showing.
kind of..
—
*error* faild to allocate domain, *error* faild to allocate : size(not sure)
—
looks like it is all about radeon. but xwindow is fine at row res.
Hi. I have installed Fedora 13 64 bit on Dell studio 1555. I have an updated kernel (2.6.34.7-56.fc13.x86_64) that is greater than the one rpmfusion packagers have used to compile and package the catalyst-kmod. I read on their site how to rebuild this kmod but the procedure fail early at the rpmbuild command, giving me this output:
[paolo@hogwarts ~]$ sudo rpmbuild --rebuild catalyst-kmod*.src.rpm --define "kernels $(uname -r)"
[sudo] password for paolo:
[paolo@hogwarts ~]$ rpmbuild --rebuild catalyst-kmod*.src.rpm --define "kernels $(uname -r)"
Installing catalyst-kmod-10.9-1.fc13.src.rpm
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.ZHfFek
+ umask 022
+ cd /home/paolo/rpmbuild/BUILD
+ kmodtool --target x86_64 --repo rpmfusion --kmodname catalyst-kmod --filterfile /home/paolo/rpmbuild/SOURCES/catalyst-kmodtool-excludekernel-filterfile --for-kernels 2.6.34.7-56.fc13.x86_64
%package -n kmod-catalyst-2.6.34.7-56.fc13.x86_64
Summary: catalyst kernel module(s) for 2.6.34.7-56.fc13.x86_64
Group: System Environment/Kernel
Provides: kernel-modules-for-kernel = 2.6.34.7-56.fc13.x86_64
Provides: catalyst-kmod = %{?epoch:%{epoch}:}%{version}-%{release}
Requires: catalyst-kmod-common >= %{?epoch:%{epoch}:}%{version}
Requires(post): /sbin/depmod
Requires(postun): /sbin/depmod
Requires: kernel-uname-r = 2.6.34.7-56.fc13.x86_64
BuildRequires: kernel-devel-uname-r = 2.6.34.7-56.fc13.x86_64
%post -n kmod-catalyst-2.6.34.7-56.fc13.x86_64
/sbin/depmod -aeF /boot/System.map-2.6.34.7-56.fc13.x86_64 2.6.34.7-56.fc13.x86_64 > /dev/null || :
%postun -n kmod-catalyst-2.6.34.7-56.fc13.x86_64
/sbin/depmod -aF /boot/System.map-2.6.34.7-56.fc13.x86_64 2.6.34.7-56.fc13.x86_64 &> /dev/null || :
%description -n kmod-catalyst-2.6.34.7-56.fc13.x86_64
This package provides the catalyst kernel modules built for the Linux
kernel 2.6.34.7-56.fc13.x86_64 for the %{_target_cpu} family of processors.
%files -n kmod-catalyst-2.6.34.7-56.fc13.x86_64
%defattr(644,root,root,755)
/lib/modules/2.6.34.7-56.fc13.x86_64/extra/catalyst/
%define kmodinstdir_prefix /lib/modules/
%define kmodinstdir_postfix /extra/catalyst/
%define kernel_versions 2.6.34.7-56.fc13.x86_64___%{_usrsrc}/kernels/2.6.34.7-56.fc13.x86_64
+ cd /home/paolo/rpmbuild/BUILD
+ rm -rf catalyst-kmod-10.9
+ /bin/mkdir -p catalyst-kmod-10.9
+ cd catalyst-kmod-10.9
+ /bin/tar -xf -
+ /usr/bin/bzip2 -dc /home/paolo/rpmbuild/SOURCES/catalyst-kmod-data-10.9.tar.bz2
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ cp -p /usr/lib/rpm/find-debuginfo.sh .
+ sed -i -e 's|strict=true|strict=false|' find-debuginfo.sh
+ mkdir fglrxpkg
+ cp -r fglrx/common/lib fglrx/common/usr fglrx/arch/x86_64/lib fglrxpkg/
+ find fglrxpkg/lib/modules/fglrx/build_mod/ -type f -print0
+ xargs -0 chmod 0644
+ for kernel_version in 2.6.34.7-56.fc13.x86_64___/usr/src/kernels/2.6.34.7-56.fc13.x86_64
+ cp -a fglrxpkg/ _kmod_build_2.6.34.7-56.fc13.x86_64
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.RBjziy
+ umask 022
+ cd /home/paolo/rpmbuild/BUILD
+ cd catalyst-kmod-10.9
+ for kernel_version in 2.6.34.7-56.fc13.x86_64___/usr/src/kernels/2.6.34.7-56.fc13.x86_64
+ pushd _kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x
~/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x ~/rpmbuild/BUILD/catalyst-kmod-10.9
+ make CC=gcc PAGE_ATTR_FIX=0 KVER=2.6.34.7-56.fc13.x86_64 KDIR=/usr/src/kernels/2.6.34.7-56.fc13.x86_64
make -C /usr/src/kernels/2.6.34.7-56.fc13.x86_64 SUBDIRS=/home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/kernels/2.6.34.7-56.fc13.x86_64'
CC [M] /home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
CC [M] /home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o
CC [M] /home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x/kcl_agp.o
CC [M] /home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x/kcl_debug.o
CC [M] /home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x/kcl_ioctl.o
/home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x/kcl_ioctl.c: In function 'KCL_IOCTL_AllocUserSpace32':
/home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x/kcl_ioctl.c:196: error: implicit declaration of function 'compat_alloc_user_space'
/home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x/kcl_ioctl.c:196: warning: return makes pointer from integer without a cast
make[2]: *** [/home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x/kcl_ioctl.o] Error 1
make[1]: *** [_module_/home/paolo/rpmbuild/BUILD/catalyst-kmod-10.9/_kmod_build_2.6.34.7-56.fc13.x86_64/lib/modules/fglrx/build_mod/2.6.x] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.34.7-56.fc13.x86_64'
make: *** [kmod_build] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.RBjziy (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.RBjziy (%build)
If you can help on this, I’ll be grateful.
Hi itbhp,
Glad to see you here.
Did it work, when you run the command as root?
Do you follow exactly following procedure:
Another possible option is try to use akmod-catalyst package, which provides a dkms-like (Dynamic Kernel Module Support) functionality.
Neither if I do all as root it works. I have the same issue. But trying in the sixth installation step akmod in place of kmod it seems to have no problem installing it, execpt for the fact that when I reboot 3d doesn’t work and either 2d feature seems to have problem.
Sorry I gave up, I reverted all and came back to open driver, which by the way seems to have 3d acceleration enabled but certainly doesn’t have the power to change gpu frequencies and to rule gpu power management as proprietary driver do, which is the reason why I was trying to install proprietary driver.
Thanks for the help.
One thing what you could easily try is to use older kernel and ATI Catalyst proprietary drivers or wait updated ATI Catalyst drivers to RPMFusion repo.
Open Source drivers will generally work well, but the features are really quite far away from proprietary drivers. I personally currently use open source drivers with ATI-cards, because I don’t really need any proprietary driver features.
Hi, I have SELinux enabled. After following these fine instructions, I was almost there, but I still got:
[ 45.157] (EE) AIGLX error: dlopen of fglrx_dri.so failed
[ 45.157] (EE) AIGLX: reverting to software rendering
But with a selinux alert, suggesting that I did:
chcon -t textrel_shlib_t '/usr/lib/dri/fglrx_dri.so
And reboot (Restart X would probably have done it) – and this solved the final bit.
Haha, clearly nobody that responded is familiar with C code. The kernel devs reimplemented the compat_alloc_user_space() function to fill a major security hole. Unfortunately, they also decided to make it GPL-only, so AMD is no longer allowed to use the function in their driver.
If you use a kernel with the fix (and you should!), driver versions up through 10.9 will no longer compile. 10.10 has a lazily implemented workaround, but I’m not sure RPMFusion has packages for it yet.
Anyone has tested this instructions and packages under Fedora 14?
Hi Luca,
I have not yet tested this with Fedora 14, but the situation with ATI support looks once again the same as it always has in the past. So no way yet to get ATI propriety drivers working on Fedora 14. If someone gets ATI propriety drivers to work on Fedora 14, please share it with us. :) So currently I recommend ATI open source drivers on Fedora 14 or Fedora 13 with ATI propriety drivers.
But under rpmfusion I can’t find ant open source driver for the ATI, have you any hints about? I run a Fedora 14 on 64 bit system…
Hi again Luca,
I have not yet updated/rewrite Fedora 13 ATI drivers guide, but it should work also with Fedora 14.
I think my graphic card (Radeon HD 5650) is not supported under Fedora 14 :(
well, i am trying to run my audio in fedora but it’s not working , is there any possiblity that i can get my own extensions scheme so i can run it..
I have tried this nice HOWTO on my FC13 Thinkpad T400 with Radeon HD 3400. Basically, it works.
Problem 1: Yum installation of kmod failed for me with –enablerepo=rpmfusion-nonfree-updates-testing
Now there is version 10.11 of Catalyst driver in the regular (non-testing) rpmfusion-nonfree-updates, which I have enabled by default (disabling it would be a fix for problem 1.), so I have installed the regular, not the testing package(s).
Good news is, that I did not experience any the black/grey/white boxes/fragments, at least not in Firefox.
Later I have identified some issues.
Problem 2: to attach external display, and use it in a multi-desktop dual screen configuration, krandr/xrandr does not work. One must use “ATI Catalyst Control Center (Administrator)”, which requires root password (!). After few clicks to get the “multi display” configuration you click on apply and you get a hint to restart the system (Ouch! Are we in Windoze?) However, log-out & log-in does the same job as reboot. So, at least till the next boot, you will not need to reboot to use the external screen… (isn’t this stupid?)
Problem 3: This is something I was aware off. Suspend to disk is not working. Usually it freezes during suspend. once I have succeeded to suspend (the laptop powered off), but later it did not resume, but just booted as if it was not suspended.
Suspend to RAM also does not work. Well, to tell the truth, it suspends – but does not resume – the system gets frozen instead.
So thanks a lot to JR for publishing also the Uninstall instructions!
I’m back with the good old on-board Intel graphics… where I even have a framebuffer console…
My resume is, that current Catalyst drivers in Fedora 13 work may be on server or a desktop box – and only if you do not suspend it, but just shutdown/boot.
Bottom line: current NVidia drivers can do all this. Have one 210 in my desktop.
BTW, with Catalyst 10.11, glxgears scored 900-1900 FPS and fgl_glxgears approx 170-210 FPS, both using approx 80% of CPU
Hi Cupy,
I updated this post little bit. Now versions is right and installation part should work as you described :)
Btw. really nice comment :D I completely agree with you, ATI Drivers Linux support is very very bad.
hi
thanks for your post.
i am new in linux world . i work on fedora 13 ( my laptop Dell N5010)
i follow the step but i have a problem when I reboot in step 6
i can not access to fedora , the prompt is appear when i reboot and ask me login and password.
what can i do ??
any body can help me ???
please please help me ..
thanks for all…
Hi viyan,
Are you installing or removing drivers?
Uninstall part have reboot in step 6…?
Running: Fedora Core 14, Radeon HD 6770M, Intel Quad Core i7-2720QM
Hello, I followed the instructions word for word and it worked somewhat. The driver worked however it was very slow. glxgears ran at about 600 frames per second. This rendered all of my games uselessly slow.
Has anyone had any success with an Radeon 6xxxM series graphics card or does anyone have any suggestions?
Thanks.
-Andrew
Hi Andrew,
Like Jack said, please check that the kernel module is loaded properly, with following command:
Hi again JR, hi everyone,
thought I’d ask here again, because this lovely blog with it’s guides helped me so much to get my ati radeon card running with fedora 13 in the first place. Maybe someone’s got a hint for me
My problem is as follows:
I’m still using fedora 13, 32bit,with the ati driver from rpmfusion. As everything worked just perfectly, I never really felt any need to upgrade to fedora 14 or later. Now I recently got some extra memory for my system, upgrading from 2gbs to 4gbs. For some reason fedora only seemed to recognize 3gbs of that memory with the non PAE kernel that I’ve been using so far.
So, even though it says that the PAE kernel is only required for more than 4gbs of memory (and I have exactly 4gbs now, isn’t that odd?) I installed the PAE kernel. That fixed the memory problem but wrecked my video driver. When I try to start X with the PAE kernel, the screen just goes blank and the system completely hangs. The non-PAE kernel still works fine (though with 3gbs of memory). And no, I didn’t forget to install kmod-catalyst-PAE. I also read that ati propriety installer now also works for fedora, so I tried that approach. But the problem remains: I can install the latest release of the driver, buildthe module and so forth, but when I start the x server it goes all blank and hangs (yes, it hangs … can’t even access the system via ssh anymore).
Now I’m pretty much at a loss on what to do now. Go and install the latest fedora, maybe even the 64bit one instead? I should add, I’m rather worried that a 64bit distro migth reduce performance or cause even more driver problems. Or do you have any hint on how to debug my problem? I tried to the x server output in a file, but alas, it hangs before any output is written. Any assitance would be greatly appreciated.
Thanks,
Jack
@Andrew: did you check, if the driver kernel module is loaded properly (with glxinfo)? I’ve noticed that you can run the driver without, but then it’s slow as hell.
Hi Jack,
Try this:
1. Boot to runlevel 3 without X. On Grub -> select PAE kernel and press ‘e’ -> select kernel row and press ‘e’ again -> add space and 3 end of kernel row -> press ‘enter’ -> and then press ‘b’.
2. Install ATI drivers again with this guide.
3. Reboot.
And please let me know, what happens? :)
Hi JR,
don’t worry about grub, I’ve already set initdefault to 3 anyway. And I did remove and reinstall the driver a couple of times. The problem remains:
the driver runs just perfectly with the non-PAE kernel, while I just get a blank screen with the PAE kernel. This result is exactly the same with the rpmfusion-kmod and the ati propriety installer.
Do you happen to know, where the ati propriety driver kernel modules for each kernel are stored exactly? Maybe it just uses the wrong one. There should be 2 modules, right? One for the PAE and one for the non PAE kernel (the one I’m using right now, or I couldn’t even write this text).
Thanks a lot in advance for any clues you might have.
Hi Jack,
Okey, what happens if you boot init 3 level and try to modprobe fglrx driver:
Then try to check is fglrx loaded:
Hi JR,
the module’s there, it’s just it’s not working, or something else’s not working, lsmod output:
“fglrx 2461928 0″
StillI’ve learnt one thing from trying as you suggested: obviuosly the ati installer exclusively places the module for current kernel into the corresponding directory. So, when I have the module, for the PAE kernel, the one for the non-PAE one is removed and vice versa. You’d need to run the installer again if you switch the kernel. However, that doesn’t seem to be the core of my problem. I can run the PAE kernel, load the module, and when I start the x server, the system crashes, while it works just fine with the “normal” kernel.
Alas, duess, I either have to live with 1gb less memory, or I’ll have to switch to 64bits or some other distro where I don’t need that particular PAE kernel, unless you have any other suggestions? In any case thanks so much for all of your advice.
Hi Jack,
Try to check your errors on Xorg.*.log after X crash with PAE-kernel:
Hi JR,
I did as you suggested and checked the log files, but alas, there’s nothing logged at all.
For the same reason that I don’t get anything with “startx &> logfile” Xorg.0.log is
just an empty file. I crashes so fast, that nothing get’s even logged or written.
All I can do is press the reset button, which feels pretty strange on a linux system (with win95 I used to rely on that button a lot, but never with linux so far).
There’s one error in Xorg.9.log:
“[ 68.989] (EE) No input driver/identifier specified (ignoring)”, but I suspect, that’s
some old, non critical error, that has no relevance to my problem.
Hi JR,
I did as you suggested and checked the log files, but alas, there’s nothing logged at all.
For the same reason that I don’t get anything with “startx &> logfile” Xorg.0.log is
just an empty file. It crashes so fast, that nothing get’s even logged or written.
All I can do is press the reset button, which feels pretty strange on a linux system (with win95 I used to rely on that button a lot, but never with linux so far).
There’s one error in Xorg.9.log:
“[ 68.989] (EE) No input driver/identifier specified (ignoring)”, but I suspect, that’s
some old, non critical error, that has no relevance to my problem.
Hi again Jack,
This sounds very tricky problem, because you don’t get any errors to log. One thing what you could do is upgrade your Fedora and try to install PAE kernel and drivers on Fedora 14 or even Fedora 15.
Useful ! Definitely is hugely generous, pleased.
del plz erorr