View Full Version : Problem with ATI radeon driver
mighthawk
21st November 2010, 06:03 PM
Hi guys,
i upgraded my System from Fedora 11 to Fedora 13. My graphics driver crashed (graphics-card: radeon hd-4-series) and i couldn't even start. I managed to reset the driver and now Fedora ist booting again, but it isn't working properly:
$ glxinfo
name of display: :0.0
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 135 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 15
Current serial number in output stream: 15
And every time is boot,, i get this boot-message:
Checking kmods exist for 2.6.34.7-61.fc13.i686 [ OK ]
Checking for module fglrx.ko: [ OK ]
Enabling the catalyst driver: Traceback (most recent call last):
File "/usr/sbin/catalyst-config-display", line 174, in <module>
app.run()
File "/usr/sbin/catalyst-config-display", line 162, in run
except error, errMsg:
NameError: global name 'error' is not defined
[FAIL]
I tried out many HowTos (including:http://forums.fedoraforum.org/forumdisplay.php?f=12) and even another forum, but.... i'm here :D
Does someone has an idea? :confused:
I'd be very thankful for any help
Fenrin
22nd November 2010, 12:04 PM
This (http://forums.fedoraforum.org/showpost.php?p=794362&postcount=2) guide is not working with current kernel versions, because it uses Catalyst 10.9.
Install kernel-devel and kernel-headers of your kernel version and then install the Catalyst 10.11 driver from ati.amd.com. And before you do this you should deinstall kmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs.i686
mighthawk
27th November 2010, 12:12 PM
sry for the long offline time... had a lot of work to do ;)
Thanks for your reply, I'll try that now and report the result.
---------- Post added at 01:12 PM GMT ---------- Previous post was at 12:55 PM GMT ----------
looks good... at least no [FAIL], but i get this message now:
No akmod packages found, nothing to do. [ OK ]
Is that what i want? I thought akmod is the driver... shouldn't that be loaded at boot?
SomeDamFool
27th November 2010, 12:26 PM
The akmod builds kernel modules needed for your app when a new kernel is installed. Your specific akmod may not be available yet. Keep checking for updates periodically and it should appear.
You may also get this message if you uninstalled the app the akmod depends on.
Mike
mighthawk
27th November 2010, 12:31 PM
Ok, thanks a lot! (to both of you)
mighthawk
4th December 2010, 12:12 PM
and it goes on and on and on... :-/
I updated directfb and directfb-devel (need them for a program) and now i get:
$ glxinfo
name of display: :0.0
Error: couldn't find RGB GLX visual or fbconfig
Any ideas? I didn't find a clue in google...
mighthawk
5th December 2010, 05:09 PM
I found something:
When Fedora updates the X-server it replaces the GLX drivers with the Xorg ones. This, generally, breaks propitiatory drivers.
Does someone know something about that?
oldcpu
5th December 2010, 05:21 PM
I found something:
When Fedora updates the X-server it replaces the GLX drivers with the Xorg ones. This, generally, breaks propitiatory drivers.
Does someone know something about that?
I think all Linux distributions "suffer from this". But typically its not a big deal, as one simply needs to rebuild the proprietary Catalyst driver with the new X-server software in place.
mighthawk
23rd December 2010, 11:57 AM
I think i need help again...
I rebuild the proprietary Catalyst driver a few times, the newest version, the "older" version (that did work some time ago), but i get the same error every time again:
$ glxinfo
name of display: :0.0
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 136 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 18
Current serial number in output stream: 18
thanks for help and for your endurance with me ;)
Fenrin
23rd December 2010, 12:37 PM
you could check if the kernel modules were built in the file /usr/share/ati/fglrx-install.log. Only Catalystversions >=10.10 (or >=10.11 ?) will work on F14.
And also make sure that kernel-devel and kernel-headers for your current kernel is installed (in case if the kernel modules were not built).
mighthawk
23rd December 2010, 03:04 PM
Thx for the fast answer!
Packages are installed, gcc installed, Catalyst version 10.12, F13
I found another "error": selinux was blocking (again :rolleyes:), switched it off, but nothing changed.
$ cat /usr/share/ati/fglrx-install.log
[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Error] Kernel Module : Kernel module build environment not found - please consult readme.
[Reboot] Kernel Module : dracut
There is no readme and google does not bring a helpful hit.
Fenrin
23rd December 2010, 03:25 PM
hm ok. I don't know why it doesn't work for you.
Before you try a new install you should deinstall the catalyst driver with the file /usr/share/ati/fglrx-uninstall.sh first. Maybe it makes a difference but I'm not sure. You could also remove your xorg.conf file and then excecute the command "aticonfig --initial".
If you use a pae kernel you need kernel-devel-pae. And versionnumbers of kernel-devel, kernel-headers have always to match with the version of your used kernel.
mighthawk
23rd December 2010, 06:23 PM
Thanks... PAE was a good point. I DID start a PAE kernel (hell knows why)
I removed it and started over again. Kernel numbers were matching
aticonfig --initial didn't work, but everything looks good now:
$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: ATI
server glx version string: 1.4
server glx extensions:
(bla bla)
Thank you again very much! ;)
I hope everything stays as it is for this time :D
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.