Direct rendering fails after updating xf86-video-i810 from 2.1.1 to 2.3.0. I noticed AIGLX errors like (EE) AIGLX error: drmMap of framebuffer failed (Invalid argument)(EE) AIGLX: reverting to software rendering so I disabled AIGLX, with no success. Running glxinfo with LIBGL_DEBUG=verbose gives me the following information: libGL: XF86DRIGetClientDriverName: 1.9.0 i965 (screen 0) libGL: OpenDriver: trying /usr/lib64/dri/i965_dri.so drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: Searching for BusID pci:0000:00:02.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: drmOpenMinor returns 4 drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 libGL error: drmMap of framebuffer failed (Invalid argument) libGL error: reverting to (slow) indirect rendering display: :0 screen: 0 direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose) I don't find any DRI/DRM related errors in the Xorg logfile, though. Software versions are: xorg-server 1.3.0.0-r5 mesa 7.0.3 i915 drm module from 2.6.25-gentoo-r1 Graphic device is a GMA965. Reproducible: Always Steps to Reproduce:
Created attachment 151452 [details] Xorg.0.log xorg logfile. [...] stands for a lot of "not using mode..." lines
Created attachment 151454 [details] xorg.conf
Same problem here
Created attachment 151498 [details] Xorg.log
Created attachment 151499 [details] xorg.conf
These are the same symptoms reported in bug #201030
Hrm, could all of you try upgrading to xorg-server 1.4.0.90 ? Also, could you reproduce that bug with any of the versions between 2.1.1 and 2.3.0, like 2.2.1 ? Thanks
Upgrading to xorg-server 1.4.0.90 fixes this for me.
(In reply to comment #7) > Hrm, could all of you try upgrading to xorg-server 1.4.0.90 ? > > Also, could you reproduce that bug with any of the versions between 2.1.1 and > 2.3.0, like 2.2.1 ? > > Thanks > Remi, I get the same error with 2.2.99.903-r1 ... I'm using xorg-server-1.3.0.0-r5 atm. I'll try upgrading and will report back ...
Ok - after some hazzle with upgrading to xorg-server 1.4.0.90 (I didn't want to run the unstable version of X-related packages) I can now report that this fixed the problem ...
I have the same problem: az@macbook ~ $ glxgears libGL error: drmMap of framebuffer failed (Invalid argument) libGL error: reverting to (slow) indirect rendering My card: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) Kernel: Linux macbook 2.6.24-gentoo #8 SMP Thu May 1 22:58:15 CEST 2008 i686 Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz GenuineIntel GNU/Linux Xorg-Server 1.3.0.0-r5 Mesa 7.0.3 xf86-video-i810 2.3.0 I tried also xf86-video-i810 2.2.99.903 which produces the same error. Previous versions of 2.2.* does not compile for me because of bug 215639. xf86-video-i810 2.1.1 works mostly (but also not perfect; for example compiz has a lot of problems, that is why I am trying a more recent version).
Upgrading to Xorg-Server 1.4.0.90-r3 solves the problem for me. az@macbook ~ $ glxgears 4734 frames in 5.0 seconds = 946.527 FPS
Hi, I had the same problem with xorg-server-1.3.x after upgrading xf86-video-i810 to version 2.3.0. With xorg-server-1.4.0.90 AIGLX works again. I filed a bug report at fd.o some time ago: http://bugs.freedesktop.org/show_bug.cgi?id=15896 But still no answer. BTW: Are you experiencing system-lockups when switching to virtual-terminal?
(In reply to comment #13) > I had the same problem with xorg-server-1.3.x after upgrading xf86-video-i810 > to version 2.3.0. With xorg-server-1.4.0.90 AIGLX works again. Erf, that's one more :) > I filed a bug report at fd.o some time ago: > http://bugs.freedesktop.org/show_bug.cgi?id=15896 > But still no answer. I guess 1.3 is _very_ low on the priority list. I'm slightly annoyed by the whole situation, but hopefully once Donnie pushes 1.4.0.90-r4 to stable, we should be fine. > BTW: Are you experiencing system-lockups when switching to virtual-terminal? 2.3.1 should have a fix for that. If you have any more issues, don't hesitate to open a new bug (to keep this one on the topic of DRI). Thanks
(In reply to comment #14) > (In reply to comment #13) > > I filed a bug report at fd.o some time ago: > > http://bugs.freedesktop.org/show_bug.cgi?id=15896 > > But still no answer. > > I guess 1.3 is _very_ low on the priority list. I'm slightly annoyed by the > whole situation, but hopefully once Donnie pushes 1.4.0.90-r4 to stable, we > should be fine. 1.3 is so low on the priority list upstream that nobody's even mentioned it for probably a year. We're working on getting a new 1.4 ebuild that can go stable, as Rémi said.
*** Bug 201030 has been marked as a duplicate of this bug. ***
Upstream confirmed it in the bug report, 1.3 is a dead end. Upgrade to xorg-server-1.4.2 is more or less mandatory for optimal functionality. Thanks