Re: [suse-xfree86] ATI Driver (fglrx) won't direct render
Am Dienstag, 12. April 2005 16:18 schrieb aga:
On Tuesday 12 April 2005 03:34, Markus Kossmann wrote:
Am Dienstag, 12. April 2005 01:45 schrieb aga:
I've spent a lot of time trying to get direct rendering enabled, but configuration keeps failing with (from sax.log):- (II) fglrx(0): doing DRIScreenInit drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed FATAL: Error inserting fglrx (/lib/modules/2.6.8-24.14-default/kernel/drivers/char/drm/fglrx.ko): No such device [drm] failed to load kernel module "fglrx"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You probably need to (re)compile the kernel module from sources to get a matching version for your updated kernel version.
Hi Marcus
Thanks. If I've downloaded the kernel and the matching kernel-source, I was assuming that I didn't need to recompile. Am I wrong here, then?
The error message says that the kernel-module fglrx couldn't be loaded. Can you load it manually with modprobe ? Which version of the fglrx driver are you running ? If you did update fglrx to a newer version than shipped with SuSE-9.2 you will have to recompile the kernel module coming as part of that driver from sources everytime you update the kernel, because SuSE can ship only the precompiled kernel module matching to the shipped version of the driver in the SuSE release.
On Tuesday 12 April 2005 17:49, Markus Kossmann wrote:
Am Dienstag, 12. April 2005 16:18 schrieb aga:
On Tuesday 12 April 2005 03:34, Markus Kossmann wrote:
Am Dienstag, 12. April 2005 01:45 schrieb aga:
I've spent a lot of time trying to get direct rendering enabled, but configuration keeps failing with (from sax.log):- (II) fglrx(0): doing DRIScreenInit drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed FATAL: Error inserting fglrx (/lib/modules/2.6.8-24.14-default/kernel/drivers/char/drm/fglrx.ko): No such device [drm] failed to load kernel module "fglrx"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You probably need to (re)compile the kernel module from sources to get a matching version for your updated kernel version.
Hi Marcus
Thanks. If I've downloaded the kernel and the matching kernel-source, I was assuming that I didn't need to recompile. Am I wrong here, then?
The error message says that the kernel-module fglrx couldn't be loaded. Can you load it manually with modprobe ?
Which version of the fglrx driver are you running ? If you did update fglrx to a newer version than shipped with SuSE-9.2 you will have to recompile the kernel module coming as part of that driver from sources everytime you update the kernel, because SuSE can ship only the precompiled kernel module matching to the shipped version of the driver in the SuSE release.
Sorry Markus, (couldn't even spell your name correctly. Sorry Sorry) I'm on fglrx 8.12.10 now, which I downloaded from Suse. I followed the included readme so definitely recompiled the kernel module. Doing a modprobe produces the same problem :- FATAL: Error inserting fglrx (/lib/modules/2.6.8-24.10-default/kernel/drivers/char/drm/fglrx.ko): No such device Just to explain this message, I've reverted to the shipped kernel and source, followed by re-install of later X11, followed by re-install of latest fglrx. I was also advised to remove the path for modules dri and glx, which I did but have now failed earlier, with the problem which led me to include the path. In the sax.log, the modules section does not show these modules now, and at the end of its configuration section, this appears :- Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Error: couldn't find RGB GLX visual Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0" It still shows ModulePath set to "/usr/X11R6/lib/modules" so I don't understand why it's not picking them up when the path isn't included, as they're in the extensions sub-folder. Other modules from there do get loaded. I'll put the path back in for the moment. Have you any further suggestions? Many thanks Allan
participants (2)
-
aga
-
Markus Kossmann