| View previous topic :: View next topic |
| Author |
Message |
ithika
n00b
Joined: 14 Dec 2004
Posts: 23
Location: Edinburgh, UK
|
 Posted: Fri Feb 11, 2005 7:03 pm Post subject: [SOLVED] ATI prop, X.org but no DRI |
 |
|
I recently had to re-emerge a lot of stuff that had been working because I was trying to get rid of dependencies in my system that I had compiled in but didn't need (like eSound).
But now my 3D acceleration and DRI is all broken even though it worked before. I have the latest version of the ATI drivers (8.8.25), OpenGL-update (2.1.1) and am running X.org (details abbreviated as follows).
| Code: | ~ # X -version
X Window System Version 6.8.1.904 (6.8.2 RC 4)
Release Date: 2 February 2005
X Protocol Version 11, Revision 0, Release 6.8.1.904
Build Operating System: Linux 2.6.9-gentoo-r1 i686 [ELF]
Current Operating System: Linux glowfish 2.6.9-gentoo-r1 #1 Sun Dec 12 00:20:13 GMT 2004 i686 |
My Xorg.0.log says this:
| Code: |
(WW) fglrx(0): Cannot read colourmap from VGA. Will restore with default
(II) fglrx(0): UMM area: 0xc0501000 (size=0x07aff000)
(II) fglrx(0): driver needs XFree86 version: 4.3.x
(WW) fglrx(0): could not detect XFree86 version (query_status=-3)
(II) Loading extension ATIFGLRXDRI
(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
[drm] failed to load kernel module "fglrx"
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x08000000
(WW) fglrx(0): Failed to set up write-combining range (0xc0000000,0x8000000)
(II) fglrx(0): FBMM initialized for area (0,0)-(1024,8191)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1024,768) (front color buffer - ass
umption)
(==) fglrx(0): Backing store disabled
|
amongst other things. If anyone can explain why this should be it would be a great help. I haven't changed anything from my previous set-up to the best of my knowledge, merely recompiled things. Dammit, it worked before! 
Last edited by ithika on Sat Feb 12, 2005 4:22 pm; edited 1 time in total |
|
| Back to top |
|
 |
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Feb 11, 2005 7:28 pm Post subject: |
|
|
Do you have the fglrx kernel module loaded? If it's not, you'll need to load it. If it is loaded, do you have any errors prefixed with "fglrx" in your "dmesg" output?
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
ithika
n00b
Joined: 14 Dec 2004
Posts: 23
Location: Edinburgh, UK
|
| Posted: Fri Feb 11, 2005 9:02 pm Post subject: |
|
|
| Wedge_ wrote: | | Do you have the fglrx kernel module loaded? If it's not, you'll need to load it. If it is loaded, do you have any errors prefixed with "fglrx" in your "dmesg" output? |
The short answer is, I'm not sure  but this is what I get in my dmesg output:
| Code: | dmesg | grep fglrx
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
fglrx: Unknown symbol remap_pfn_range
|
If I try to add the module manually I get this:
| Code: | # modeprobe fglrx
FATAL: Error inserting fglrx (/lib/modules/2.6.9-gentoo-r1/video/fglrx.ko): Unknown symbol in module, or unknown parameter (see dmesg)
|
Dmesg just gives me the last line it did before about 'unknown symbol ...'.
Before, when it was working, I don't remember having to do any of this stuff which is what makes it all so odd. |
|
| Back to top |
|
|
ithika
n00b
Joined: 14 Dec 2004
Posts: 23
Location: Edinburgh, UK
|
| Posted: Sat Feb 12, 2005 3:54 pm Post subject: A possible cause, and solution? |
|
|
Ok, I found a bit more info in an AMD64 thread related to the ATI drivers. I don't have a 64bit CPU but I think it applies.
Basically, the remap_pfn_range has recently changed name from remap_page_range somewhere between the 2.6.9 and .10 kernel revisions. The ATI drivers seem to expect me to export the newer name but are getting the old one instead? Something like that. Anyway, I though I'd bite the bullet and upgrade to a 2.6.10-gentoo-r7 kernel and see how things pan out. I'll post my results when I've finished compiling it all. |
|
| Back to top |
|
|
ithika
n00b
Joined: 14 Dec 2004
Posts: 23
Location: Edinburgh, UK
|
| Posted: Sat Feb 12, 2005 4:25 pm Post subject: YES! |
|
|
I've changed the subject title now; all is better again. Hopefully the previous post will help out other people too. There must be an awful lot of people who don't recompile a new kernel every week and are wondering why the drivers have stopped working for them.
Process
- recompile new kernel (manually or with genkernel)
- unmerge and remerge the ati-drivers
- opengl-update ati
- reboot... to 3D accelerated loveliness! |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Sat Feb 12, 2005 4:43 pm Post subject: Re: A possible cause, and solution? |
|
|
| ithika wrote: | Ok, I found a bit more info in an AMD64 thread related to the ATI drivers. I don't have a 64bit CPU but I think it applies.
Basically, the remap_pfn_range has recently changed name from remap_page_range somewhere between the 2.6.9 and .10 kernel revisions. The ATI drivers seem to expect me to export the newer name but are getting the old one instead? Something like that. Anyway, I though I'd bite the bullet and upgrade to a 2.6.10-gentoo-r7 kernel and see how things pan out. I'll post my results when I've finished compiling it all. |
This type of problem is fairly common. What's happening is that the driver is expecting to find a kernel function with a given name, but the name has been changed at some point by an update to the kernel, so it isn't able to find it - the function names it can't find are the unresolved symbols that get displayed in the dmesg output.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
