xorg log shows direct rendering enabled, no errors or any other indication of failure. glxinfo shows direct rendering disabled - using Mesa Indirect. How do I actually enable the driver, and why do the reports disagree? ref bug 3982. - This one has an old version of libGL, my machine does not, AFAIK. Attaching verbose glxinfo and xorg logs Thanks!
Created attachment 4534 [details] Xorg startup logs
Created attachment 4535 [details] result of "export LIBGL_DEBUG_VERBOSE=y; glxinfo"
Sorry - forgot some system info: 700m inspiron laptop - Intel i855 chipset. Fedora Core 4 version of xorg. Result of rpm -qa|grep xorg: xorg-x11-doc-6.8.2-37.FC4.49.2 fonts-xorg-base-6.8.2-1 xorg-x11-xauth-6.8.2-37.FC4.49.2 xorg-x11-Mesa-libGLU-6.8.2-37.FC4.49.2 xorg-x11-twm-6.8.2-37.FC4.49.2 xorg-x11-Xdmx-6.8.2-37.FC4.49.2 xorg-x11-libs-6.8.2-37.FC4.49.2 xorg-x11-Mesa-libGL-6.8.2-37.FC4.49.2 xorg-x11-Xvfb-6.8.2-37.FC4.49.2 xorg-x11-6.8.2-37.FC4.49.2 xorg-x11-xdm-6.8.2-37.FC4.49.2 xorg-x11-tools-6.8.2-37.FC4.49.2 xorg-x11-font-utils-6.8.2-37.FC4.49.2 xorg-x11-xfs-6.8.2-37.FC4.49.2 xorg-x11-deprecated-libs-6.8.2-37.FC4.49.2 xorg-x11-devel-6.8.2-37.FC4.49.2 xorg-x11-Xnest-6.8.2-37.FC4.49.2 xorg-x11-sdk-6.8.2-37.FC4.49.2 Thanks!
(In reply to comment #2) > Created an attachment (id=4535) [edit] > result of "export LIBGL_DEBUG_VERBOSE=y; glxinfo" > Try it with LIBGL_DEBUG=verbose.
Created attachment 4536 [details] result of "export LIBGL_DEBUG=verybose; glxinfo"
Done - added attachment. (In reply to comment #5) > Created an attachment (id=4536) [edit] > result of "export LIBGL_DEBUG=verybose; glxinfo" >
Looks like everything works OK in libGL but the screen or context creation fails silently inside the 3D driver. Someone who can reproduce the problem needs to debug the driver and find out what's wrong.
Well, I do know my way around C++, but I'm a java developer, so haven't played with it in awhile. If you can give me instructions and point me in the direction of docs, I'd love to play with it again. :) Thanks! (In reply to comment #7) > Looks like everything works OK in libGL but the screen or context creation fails > silently inside the 3D driver. Someone who can reproduce the problem needs to > debug the driver and find out what's wrong.
Erm, I wasn't paying attention. You're still running Xorg 6.8.2? Before you go into debugging the problem, try if the latest drivers fix this issue. Take a look at http://dri.freedesktop.org/wiki/Download#head-55420c59a1c2e9a70f07a6fa02f0d228ffb87b76. In particular pay attention to the section "Upgrading to Xorg 6.9" before installing the binary snapshots. Then download and install the latest common and i915 snapshots.
Upgraded to latest snapshot, now getting error when running "export LIBGL_DEBUG_VERBOSE=y; glxinfo" Here's the dump: ERROR! sizeof(I830DRIRec) does not match passed size from device driver libGL warning: 3D driver returned no fbconfigs. libGL error: InitDriver failed libGL error: reverting to (slow) indirect rendering What's an I830DRIRec? :) In my xorg.conf, do I still use the i810 as the display driver? Thanks!
I830DRIRec is a data structure shared by 2D and 3D driver. If the size doesn't match that probably means that you're using a bad combination of 2D and 3D drivers. Make sure that both are from the i915 snapshot you installed. After installing the snapshots, you need to kill the Xserver, unload the i915 and drm kernel modules and restart the Xserver. On the Xserver side i810 is still the right driver. BTW, I'm assuming you're not using a 64-bit OS?
Nope - no 64bit OS. I've tried that, and am getting the same error. Here is what I did. init 3 /sbin/rmmod i915 /sbin/rmmod dri reran i915-200.../install.sh init 5 Any other thoughts? Or am I doning this wrong? (In reply to comment #11) > I830DRIRec is a data structure shared by 2D and 3D driver. If the size doesn't > match that probably means that you're using a bad combination of 2D and 3D > drivers. Make sure that both are from the i915 snapshot you installed. After > installing the snapshots, you need to kill the Xserver, unload the i915 and drm > kernel modules and restart the Xserver. On the Xserver side i810 is still the > right driver. BTW, I'm assuming you're not using a 64-bit OS?
Check your Xorg.0.log file to find out which i810_drv.so it is loading. It should load the one from /usr/X11R6/lib/modules/drivers/. Also run LIBGL_DEBUG=verbose glxinfo. It should tell you, which i915_dri.so it is loading. It should load the one from /usr/X11R6/lib/modules/dri/. If any of these don't match, try to find out why. Check the Files section in your xorg.conf and make sure that the environment variable LIBGL_DRIVERS_PATH isn't pointing to some strange location. Also the driver binary i810_drv.so and i915_dri.so files in /usr/X11R6/lib/modules/... with the ones in the snapshot to make sure that they were copied correctly during installation.
The log file and the verbose output are both pointing to the correct place. I didn't know the best way to verify the drivers, but they are the same size as those found in the package. LIBGL_DRIVERS_PATH is not set in the environment, and under the Files section of the xorg.conf are only paths to fonts. One thing that might be the cause though, is my install of X. I started from the upgraded FC4 install, and just installed the xserver package and the i915 driver package per the wiki instructions. I poked around a bit, but those are the only two binary snapshots that I saw on that link. Do I need to install anything else? Thanks! (In reply to comment #13) > Check your Xorg.0.log file to find out which i810_drv.so it is loading. It > should load the one from /usr/X11R6/lib/modules/drivers/. Also run > LIBGL_DEBUG=verbose glxinfo. It should tell you, which i915_dri.so it is > loading. It should load the one from /usr/X11R6/lib/modules/dri/. If any of > these don't match, try to find out why. Check the Files section in your > xorg.conf and make sure that the environment variable LIBGL_DRIVERS_PATH isn't > pointing to some strange location. Also the driver binary i810_drv.so and > i915_dri.so files in /usr/X11R6/lib/modules/... with the ones in the snapshot to > make sure that they were copied correctly during installation.
> One thing that might be the cause though, is my install of X. I started from the > upgraded FC4 install, and just installed the xserver package and the i915 driver > package per the wiki instructions. I poked around a bit, but those are the only > two binary snapshots that I saw on that link. Do I need to install anything else? Have you installed the "common" snapshot?
Right - yes I did. So Common, Xserver package and DRI snapshot are the ones installed.
Could you attach an updated Xorg.0.log?
Created attachment 4550 [details] Response to comment 17
As it turns out this problem is caused by the snapshot builds using outdated Xorg 6.9 sources that are incompatible with the current i915 driver from Mesa. i915 snapshots 20060123 and older should still be OK. Alan Hourihane updated a version check in the Mesa driver so that it will report a more useful error message. Closing this as FIXED. There is still a bug in the snapshot build. It should use the modular Xorg. But that's a different issue.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.