successive X.org 1.3.0 w/ xf86-video-intel-2.* fail to initalize DRI
René Rebe
rene at exactcode.de
Sat Apr 21 10:12:38 PDT 2007
Hi Michel,
On Saturday 21 April 2007 16:50:03 Michel Dänzer wrote:
> > drmOpenDevice: node name is /dev/dri/card0
> > drmOpenDevice: open result is 10, (OK)
> > drmOpenDevice: node name is /dev/dri/card0
> > drmOpenDevice: open result is 10, (OK)
> > drmOpenByBusid: Searching for BusID pci:0000:00:02.0
> > drmOpenDevice: node name is /dev/dri/card0
> > drmOpenDevice: open result is 10, (OK)
> > drmOpenByBusid: drmOpenMinor returns 10
> > drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
> > (II) intel(0): [drm] DRM interface version 1.0
> > (II) intel(0): [drm] drmSetBusid failed (10, pci:0000:00:02.0), Permission denied
> > (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
>
> Does
>
> sudo lsof /dev/dri/card0
>
> show any process keeping the DRM device open when this happens?
Indeed!:
root at blackrider:~# lsof /dev/dri/card0
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
dbus-daem 2195 rene 4u CHR 226,0 6988 /dev/dri/card0
How the heck does this gonna happen?!?!? Killing it away gives me
DRI and thus a pretty 3D desktop back.
If the error message would not have been -EPERM but -EBUSY (or so) I
would have noticed weeks ago, but with -EPERM I basically thought "what
the heck" is going on in the kernel, ...
Anyone any idea why this dbus-daemon open the device?
Yours,
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
More information about the xorg
mailing list