[Openchrome-users] Direct Rendering is not enabled

[Shixin Zeng]

Hi!

On 11/28/05, Thomas Hellstr?m <unichrome at shipmail.org> wrote:
>
> Hi!
>
> > Hi!
> >
> > On 11/28/05, Thomas Hellstr?m <unichrome at shipmail.org> wrote:
> >>
> >> Hi.
> >> Shixin Zeng wrote:
> >>
> >> Hi
> >> >From Xorg.0.log, the Direct Rendering is enabled, but from glxinfo, it
> >> wasn't. Why?
> >> Is it enable or not on earth?
> >> The output of glxinfo and Xorg.log are attached.
> >>
> >> Thanks.
> >>
> >>  Pls check out the 3D troubleshooting guide in our docs section.
> >
> >
> > I've read the docs. But I still can't get direct rendering working.
> > I've build Mesa(checkout from mesa_6_4_branch) and libdrm(cvs HEAD).
> > I've a question about installing libdrm:
> > I used the command "./configure --prefix=/usr --libdir=/usr/X11R6/lib64;
> > make; make install" to install libdrm, and libdrm.a is installed in
> > /usr/X11R6/lib64/. But from the Xorg.log, I could see that Xserver is
> > still
> > loading the old one(/usr/X11R6/lib64/modules/linux/libdrm.a). If I
> replace
> > '/usr/X11R6/lib64/modules/linux/libdrm.a' with 'libdrm.a' from drm,
> > Xserver
> > will fail to load drm, and then fail to load dri.
> > Did I do anything wrong?
> > Thanks!
> >
> > /Thomas
>
> What does "glxgears" say when you run with LIBGL_DEBUG=verbose?

Actually, I attached it in the previous e-mail. Now paste it here for your
convinience:
#sudo glxgears
libGL: XF86DRIGetClientDriverName: 5.0.0 unichrome (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/unichrome_dri.so
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0

ERROR!  sizeof(VIADRIRec) does not match passed size from device driver
__driCreateNewScreen_20050727 - succeeded
libGL warning: 3D driver returned no fbconfigs.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
627 frames in 6.0 seconds = 104.500 FPS
600 frames in 5.0 seconds = 120.000 FPS
480 frames in 5.0 seconds = 96.000 FPS
X connection to :0.0 broken (explicit kill or server shutdown).

/Thomas
>
>
>


--
Best regards

Shixin Zeng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://wiki.openchrome.org/pipermail/openchrome-users/attachments/20051128/8cc88a8f/attachment-0001.html