Direct rendering doesn't work with 1.9.92, drm git, mesa git and xserver 1.2.99.902. (II) intel(0): Attempting memory allocation with tiled buffers and large DRI memory manager reservation: (II) intel(0): Allocating 5112 scanlines for pixmap cache (II) intel(0): Attempting memory allocation with tiled buffers and small DRI memory manager reservation: (II) intel(0): Allocating 5112 scanlines for pixmap cache (WW) intel(0): Failed to allocate texture space. (WW) intel(0): Couldn't allocate tiled memory, page flipping disabled (II) intel(0): Attempting memory allocation with untiled buffers and large DRI memory manager reservation: (II) intel(0): Allocating 5112 scanlines for pixmap cache (II) intel(0): Attempting memory allocation with untiled buffers and small DRI memory manager reservation: (II) intel(0): Allocating 5112 scanlines for pixmap cache (WW) intel(0): Failed to allocate texture space. (WW) intel(0): Not enough video memory. Disabling DRI.
Created attachment 9177 [details] Xorg.log
Could you post your xorg.conf? It looks like you may have specified a VideoRam size. If so, try commenting that out and see what happens.
After removing VideoRam, different error occured: (EE) AIGLX error: dlopen of /usr/lib/dri/i915_dri.so failed (/usr/lib/dri/i915_dri.so: cannot open shared object file: No such file or directory) (EE) AIGLX: reverting to software rendering After creating symlink i915_dri.so pointing to i915tex_dri.so direct rendering is working.
Created attachment 9199 [details] xorg.conf
Created attachment 9200 [details] Xorg.log
(In reply to comment #3) > After removing VideoRam, different error occured: > > (EE) AIGLX error: dlopen of /usr/lib/dri/i915_dri.so failed > (/usr/lib/dri/i915_dri.so: cannot open shared object file: No such file or > directory) Then Mesa wasn't fully installed. The i915tex can be used directly with Option "Legacy3D" "off". Resolving as a configuration issue, not a bug.
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.