Created attachment 22169 [details]
dmesg w/ "drm debug=1"
In X my video adapter will not use DRI. When doing "startx" DRI fails as reported in the Xorg.0.log.
To reproduce: simply startx.
Actual results: X starts, KDE runs, but without DRI. Error is reported in my Xorg.0.log
Expected results: Both the server, and the hardware ostensibly support DRI. I expect acceleration.
X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Slackware 12.1 Slackware Linux Project
Current Operating System: Linux ira 22.214.171.124 #1 Mon Jan 19 09:57:43 PST 2009 i586
Build Date: 30 June 2008 11:35:29PM
Additional: This behavior existed on the previous server supplied with my distro too. (Though I didn't report it until now.)
I have set my drm module to "drm debug=1".
I am attaching my dmesg, and my Xorg.0.log
Created attachment 22170 [details]
Can you try the drm in git master?
first backup your old drm modules (usually in /lib/modules/`uname -r`/kernel/drivers/char/drm/) , then:
git clone git://anongit.freedesktop.org/mesa/drm
cp *.ko /lib/modules/`uname -r`/kernel/drivers/char/drm/
modprobe -r radeon
Then start X.
Created attachment 22188 [details]
dmesg after apply the modules from the git pull
Created attachment 22189 [details]
Xorg.0.log after installng modules from the git pull
> first backup your old drm modules (usually in /lib/modules/`uname
> -r`/kernel/drivers/char/drm/) , then:
Mine were in:
> cp *.ko /lib/modules/`uname -r`/kernel/drivers/char/drm/
> modprobe -r radeon
> depmod -a
> Then start X.
modprobe -r drm
modprobe -r radeon
after running X I have the dmesg and Xorg.0.log, attached.
(In reply to comment #5)
> Mine were in:
I can't see why the hell this is failing, the only think I can think of is a bug in libdrm somehow,
you could try making libdrm and using it instead of the system one
The other option is to add some debugging to the setversion ioctl in the drm_ioctl.c in the kernel and see why it is failing.
It really should be returning a valid value in GetBusID and you shouldn't see the repeated opening.
I just know of course the answer will be one of the DOH! type things.
Closing due to inactivity. Please reopen if this is still a problem.