3d acceleration broken in Edgy Knot 1

Anybody working on this? Just wanted to confirm that it wasn't lost in the confusion.

Hi Travis, thanks for the bug report!

Just a few minutes ago I have uploaded a new version of the i810 driver to Edgy (1.6.4) - it should hit the mirrors in a few hours.

I'd like to ask you to test 3D acceleration with this new version of the driver, and if it doesn't works, please attach the following information to this bug report:

- /var/log/Xorg.0.log
- /etc/X11/xorg.conf
- output of 'lspci -vv'

We'd also like to hear from you, in case the new version solves your problems.

I can see this problem with 1.6.4. To recap (i'll attach the required patches) Xorg.0.log says DRI enabled, glxinfo says disabled.

I am experiencing the same so I post my logs too in case of :)

I also noticed that a new version of the driver was out in the afternoon: 1.6.5 (http://lists.freedesktop.org/archives/xorg/2006-August/017449.html). It notably fixes bug #7835 on the freedesktop bug tracker (https://bugs.freedesktop.org/show_bug.cgi?id=7835). Description of the fix: "Restore unused fields in I830DRIRec to avoid i915 DRI breakage".

I think it would be nice to upload 1.6.5 to edgy.

Many thanks to Miguel who reported the bug on freedesktop and also on launchpad (bug 55907).

1.6.5 was uploaded to edgy just a few minutes ago.

Note that the 3D acceleration is not fixed by this driver (at least not directly)

3D acceleration will (or should be) fixed with upgrades of libdrm and mesa, which I'm taking care of in this very moment. Stay tuned.

This bug is not a duplicate of 55907, duplicate mark removed.

Fixed after uploads updated libdrm, mesa, xorg-server and xserver-xorg-video-i810. Please give it a few hours for these packages to be built and published. (it will only be finished when the last of them: xserver-xorg-video-i810 1.6.5-0ubuntu2 is published to the archive).

This package combination restores DRI support for intel video boards I have locally - please reopen this bug if it doesn't for your board.

I am still having:
glxinfo | grep rendering > direct rendering: No

I checked several times all the version of the packages: mine are up to date.

Kaleo,

DRI appears to be enabled on your machine, see:

(II) I810(0): [drm] installed DRM signal handler
(II) I810(0): [DRI] installation complete
(II) I810(0): direct rendering: Enabled

(from your Xorg.0.log)

What is the output of 'xdriinfo'?

On my i945gm, I get this:

rodarvus@wakko:~$ xdriinfo
Screen 0: i915
rodarvus@wakko:~$

Meaning that DRI is enabled for this board, and that it uses driver i915 for DRI. (the dri driver, in turn, is provided by libgl1-mesa-dri)

I can verify the 'not working' state.

Rodrigo Novo wrote:
> DRI appears to be enabled on your machine, see:
>
> (II) I810(0): [drm] installed DRM signal handler
> (II) I810(0): [DRI] installation complete
> (II) I810(0): direct rendering: Enabled

I'm currently seeing:

(II) I810(0): [drm] installed DRM signal handler
(II) I810(0): [DRI] installation complete
(II) I810(0): direct rendering: Enabled
---8<---
(EE) AIGLX error: Calling driver entry point failed(EE) AIGLX: reverting
to software rendering

> What is the output of 'xdriinfo'?

ressu@denial:~/ > xdriinfo
Screen 0: i915

> Meaning that DRI is enabled for this board, and that it uses driver i915
> for DRI. (the dri driver, in turn, is provided by libgl1-mesa-dri)

But still i'm seeing:

ressu@denial:~/ > glxinfo | grep direct
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect

After trying with glxgears, i can see that software rendering is being used.

- S

florian@samantha:~$ xdriinfo
Screen 0: i915
florian@samantha:~$

but still:

glflorian@samantha:~$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: No

and as for Sami I can tell that the software rendering is being used.

I tried all sorts of options in xorg.conf after the one provided by "dpkg-reconfigure -phigh".

I've got this:

$ xdriinfo
Screen 0: i915

~$ glxgears
i915 DRI driver expected DDX version 4-4.1.x but got version 1.6.4
libGL warning: 3D driver returned no fbconfigs.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering

dmesg | grep drm
[17179607.564000] [drm] Initialized drm 1.0.1 20051102
[17179607.568000] [drm] Initialized i915 1.4.0 20060119 on minor 0

Xorg.0.log:
(**) I810(0): Depth 16, (--) framebuffer bpp 16
(==) I810(0): RGB weight 565
(==) I810(0): Default visual is TrueColor
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules/libint10.so
(II) I810(0): initializing int10
(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 7872 kB
(II) I810(0): VESA VBE OEM: Intel(r)915GM/910ML/915MS Graphics Chip Accelerated VGA BIOS
(II) I810(0): VESA VBE OEM Software Rev: 1.0
(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
(II) I810(0): VESA VBE OEM Product: Intel(r)915GM/910ML/915MS Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) I810(0): Integrated Graphics Chipset: Intel(R) 915GM
(--) I810(0): Chipset: "915GM"
(--) I810(0): Linear framebuffer at 0xA0000000
(--) I810(0): IO registers at addr 0xD0000000
(II) I810(0): 2 display pipes available.
(II) I810(0): detected 7932 kB stolen memory.
(II) I810(0): Kernel reported 110336 total, 1 used
(II) I810(0): I830CheckAvailableMemory: 441340 kB available
(II) I810(0): Monitoring connected displays enabled
(II) I810(0): Will attempt to tell the BIOS that there is 12288 kB VideoRAM
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules/libint10.so
(II) I810(0): initializing int10
(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 7872 kB
(II) I810(0): VESA VBE OEM: Intel(r)915GM/910ML/915MS Graphics Chip Accelerated VGA BIOS
(II) I810(0): VESA VBE OEM Software Rev: 1.0
(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
(II) I810(0): VESA VBE OEM Product: Intel(r)915GM/910ML/915MS Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) I810(0): Integrated Graphics Chipset: Intel(R) 915GM
(--) I810(0): Chipset: "915GM"
(--) I810(0): Linear framebuffer at 0xA0000000
(--) I810(0): IO registers at addr 0xD0000000
(II) I810(0): 2 display pipes available.
(II) I810(0): detected 7932 kB stolen memory.
(II) I810(0): Kernel reported 110336 total, 1 used
(II) I810(0): I830CheckAvailableMemory: 441340 kB available
(II) I810(0): Monitoring connected displays enabled
(II) I810(0): Will attempt to tell the BIOS that there is 12288 kB VideoRAM
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules/libint10.so
(II) I810(0): initializing int10
(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 12288 kB
(II)...

with "LIBGL_DEBUG=verbose glxinfo", I suddenly realize that it was trying to access the file "/usr/X11R6/lib/modules/dri/i915_dri.so" that I do not have. I created a symlink:

sudo mkdir /usr/X11R6/lib/modules
sudo ln -s /usr/lib/dri /usr/X11R6/lib/modules/

and then the error messages of glxinfo started to look like Marcelo's:

i915 DRI driver expected DDX version 4-4.1.x but got version 1.6.4
libGL warning: 3D driver returned no fbconfigs.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
display: :0 screen: 0
direct rendering: No

I noticed the following:

mesa (6.5.0.git.20060809-0ubuntu1) edgy; urgency=low

  * New Upstream release
    - Based on http://www.intellinuxgraphics.org/mesa-git-master-08092006.tgz

but on http://intellinuxgraphics.org/download.html is proposed:

Mesa (6.5) Mesa-20060810.tar.bz2

I went through the changes between the two and it's quite a lot for just one day. However I found an extremely interesting difference:

"old" one:
   static const __DRIversion ddx_expected = { 4, 1, 0 };
   static const __DRIversion dri_expected = { 4, 0, 0 };
   static const __DRIversion drm_expected = { 1, 3, 0 };

new one:
   static const __DRIversion ddx_expected = { 1, 5, 0 };
   static const __DRIversion dri_expected = { 4, 0, 0 };
   static const __DRIversion drm_expected = { 1, 4, 0 };

Patch attached.

I hope it helps!

Well, still not getting DRI, and in my Xorg.0.log (full version attached):
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so
(II) GLX: Initialized DRI GL provider for screen 0

Toby, can you please attach your xorg.conf and the output of "lspci -v" ?

Here thou goest.

And again.

Hello,

Attaching files from my system, as I also have a lack of DRI.

--
$ apt-cache policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 6.5.0.git.20060810-0ubuntu1
  Candidate: 6.5.0.git.20060810-0ubuntu1

--
$ LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/i915_dri.so
libGL error: dlopen /usr/X11R6/lib/modules/dri/i915_dri.so failed (/usr/X11R6/lib/modules/dri/i915_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to find driver: i915_dri.so
display: :0 screen: 0
direct rendering: No

It's exactly the same output on my system.

I made a symlink from /usr/X11R6/lib/modules/dri to /usr/lib/dri and all was happy. Seems that it's looking for the files in the wrong place.

OK. So it's libgl1-mesa-dri that's looking for the files in the wrong place. Xorg.0.log shows that Xorg loads them fine. Hence,
"(II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so"
but also,
"libGL error: unable to find driver: i915_dri.so"

Now, libGL gives this warning which I've never seen before:
"libGL warning: 3D driver claims to not support visual 0x5b"

Hi guys, do you all have DRI working with the symlink from /usr/X11R6/lib/modules/dri to /usr/lib/dri ?

If yes, it should not be a problem to correct this in the packages and we can then close the bug.

Or maybe it has to do with this bug:

https://bugs.freedesktop.org/show_bug.cgi?id=7169

fixed yesterday in mesa CVS:

http://gitweb.freedesktop.org/?p=users/krh/mesa.git;a=commit;h=addaf26054d94041767d46ad970a7d6b80d17d60

Well. I don't think it's fully working. Some GL apps (eg slune) run as slow as when rendered indirectly. Slune output (LIBGL_DEBUG=verbose):

libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/i915_dri.so
libGL error: dlopen /usr/X11R6/lib/modules/dri/i915_dri.so failed (/usr/X11R6/lib/modules/dri/i915_dri.so: undefined symbol: _glapi_Dispatch)
libGL error: unable to find driver: i915_dri.so
* Soya * Using 8 bits stencil buffer

* Soya * version 0.11.2
* Using OpenGL 1.2 (1.3 Mesa 6.5.1)
* - renderer : Mesa DRI Intel(R) 915GM 20050225
* - vendor : Tungsten Graphics, Inc
* - maximum number of lights : 8
* - maximum number of clip planes : 6
* - maximum number of texture units : 8
* - maximum texture size : 2048 pixels

compiz output:
libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/i915_dri.so
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenByBusid: drmOpenMinor returns 5
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
libGL warning: 3D driver claims to not support visual 0x5b
libGL error:
Can't open configuration file /etc/drirc: No such file or directory.
libGL error:
Can't open configuration file /home/toby/.drirc: No such file or directory.
compiz.real: GLX_EXT_texture_from_pixmap is missing
compiz.real: Failed to manage screen: 0
compiz.real: No managable screens found on display :0.0

There's definitely some inconsistency there. compiz loads the driver fine, gives out the libGL warning I mentioned above, but cannot find the GLX_EXT_texture_from_pixmap extension. Slune just fails miserably to load the driver. glxinfo is working as well, which is why it outputs "direct rendering: Yes".

This makes me think that the fault is due to both. The version of Mesa we're using looks for the files in the wrong place, but also suffers from the bug (7169) at freedesktop.org; our fault displays symptoms of both.

Concerning Compiz and GLX_EXT_texture_from_pixmap, the problem lies in Compiz and can be solved with the specific Compiz-AIGLX patches : http://<email address hidden>/msg00006.html

From those applications that "fail" (and show symptoms related to freedesktop.org bug #7169), may I draw your attention to:

libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/i915_dri.so
libGL error: dlopen /usr/X11R6/lib/modules/dri/i915_dri.so failed (/usr/X11R6/lib/modules/dri/i915_dri.so: undefined symbol: _glapi_Dispatch)
libGL error: unable to find driver: i915_dri.so

Wasn't the problem at freedesktop to do with a Dispatch function; whatever that may be?

About Slune, I see the same problem which is definitely related to https://bugs.freedesktop.org/show_bug.cgi?id=7169.

The issue has been discussed on mesa's mailing lists and the patch approved (http://<email address hidden>/msg01152.html).

That's great, and good sleuthing by everyone! I'll be glad to see this fix released.

previous patch was ill formed

If someone can try these:

http://boucault.iiens.net/libgl1-mesa-dri_6.5.0.git.20060810-0ubuntu1_i386.deb
http://boucault.iiens.net/libgl1-mesa-glx_6.5.0.git.20060810-0ubuntu1_i386.deb

They are the Ubuntu ones patched with the previously posted patch.

Apparently, the symlink problem is still here but the symbol issue (_glapi_Dispatch) is gone.

Will do.

Well; they seem to work, it (Slune) just runs very slowly still. Here's the (important) output:

[snip]
libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/i915_dri.so
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenByBusid: drmOpenMinor returns 6
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
libGL warning: 3D driver claims to not support visual 0x5b
libGL error:
Can't open configuration file /etc/drirc: No such file or directory.
* Soya * Using 8 bits stencil buffer

* Soya * version 0.11.2
* Using OpenGL 1.3 Mesa 6.5.1
* - renderer : Mesa DRI Intel(R) 915GM 20050225
* - vendor : Tungsten Graphics, Inc
* - maximum number of lights : 8
* - maximum number of clip planes : 6
* - maximum number of texture units : 8
* - maximum texture size : 2048 pixels
[snip]

And still from ppracer:
libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/i915_dri.so
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
libGL warning: 3D driver claims to not support visual 0x5b
*** ppracer error: Couldn't initialize video: Couldn't find matching GLX visual

I have no problems with ppracer.

Using Kaleo's patched debs, and creating a symbolic link for i915_dri.so, dri appears to be working correctly.

--
$ LIBGL_DEBUG=verbose glxinfo

libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/i915_dri.so
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 warning: 3D driver claims to not support visual 0x5b
libGL error:
Can't open configuration file /etc/drirc: No such file or directory.

--
$ LIBGL_DEBUG=verbose ppracer

libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/i915_dri.so
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
libGL warning: 3D driver claims to not support visual 0x5b
libGL error:
Can't open configuration file /etc/drirc: No such file or directory.
libGL error:
Can't open configuration file /home/shenki/.drirc: No such file or directory.

OK. I'll look into my ppracer problems. Obviously they're not related to
this bug. However, I still don't know what libGL means by
"libGL warning: 3D driver claims to not support visual 0x5b".

This never happened before, I'm sure.

after installing the mesa libgl1 packages from above I got these errors:

(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
 compiled for 7.1.1, module version = 1.0.0
 ABI class: X.Org Server Extension, version 0.3
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/lib/xorg/modules/linux/libdrm.so
(EE) /usr/lib/xorg/modules/linux/libdrm.so is an unrecognized module type
(II) UnloadModule: "drm"
(II) UnloadModule: "dri"
(II) Unloading /usr/lib/xorg/modules/extensions/libdri.so
(EE) Failed to load module "dri" (a required submodule could not be loaded, 6)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so

(see full log attached for more)

A few things to keep in mind:

Edgy system (up-to-date) using kernel from Dapper (current stable kernel)

$> ls /lib/modules/2.6.15-26-686/volatile/
ath_hal.ko fcdslusb2.ko fcusb.ko mach64.ko r128.ko
drm.ko fcdslusba.ko fglrx.ko mga.ko radeon.ko
fcdsl2.ko fcdslusb.ko fxusb.ko new_ath_hal.ko savage.ko
fcdsl.ko fcpci.ko i810.ko nvidia.ko sis.ko
fcdslsl.ko fcpcmcia_cs.ko i830.ko nvidia_legacy.ko tdfx.ko
fcdslslusb.ko fcpcmcia.ko i915.ko nv.ko via.ko

drm and i810 kernel drivers come from package:

$> dpkg -S /lib/linux-dri-modules/2.6.15-26-686/i810.ko
linux-dri-modules-2.6.15-26-686: /lib/linux-dri-modules/2.6.15-26-686/i810.ko

Which in turn comes from:

http://ubuntuforums.org/showthread.php?t=145068&highlight=aiglx

I removed the i810 driver from the kernel so that volatile takes over...
Let me do the same for drm.ko

same error even after ensuring that there is only one drm.ko file.

$> dpkg -S /usr/lib/xorg/modules/linux/libdrm.so
xserver-xorg-core: /usr/lib/xorg/modules/linux/libdrm.so

perhaps xserver-xorg-core needs to be updated.

Now everything works fine. The combination turned out to be:

ii xserver-xorg-c 1.1.1-0ubuntu7 X.Org X server -- core server

ii linux-image-2. 2.6.15-26.46 Linux kernel image for version 2.6.15 on PPr

removing:

linux-dri-* (modules, common, everything not provided by official ubuntu repos)

Now if I could get Compiz to work with AIGLX ...

Xorg log attached...

OK. Now this has been fixed locally, does anyone know when it should be in the repos? Cos apt is bugging me about updating libGL1-mesa-dri and -glx to the repo version, and I don't really wanna hold it.

I just installed Edgy again (alternate CD of the 26 of august) and it works perfectly out of the box.