Wrong module directory used when loading i915_dri.so ?

This assumes it works the same as the 945G.

I've tested this lightly on my machine (a VAIO VGN-SZ17SP), and it works well enough to play TuxRacer.

Note that for direct rendering to work, patches are also needed to the kernel and xserver-xorg-driver-i810.

I can confirm this behavior on my ThinkPad X60s ( https://wiki.ubuntu.com/LaptopTestingTeam/ThinkpadX60s ) and Dapper nightly for March 22nd.

Even if i915 is manually loaded with modprobe, DRI is not activated.

lspci outputs for my ThinkPad which exhibits this behavior can be found at https://wiki.ubuntu.com/LaptopTestingTeam/ThinkpadX60s/lspci

i don't get it. Is the dri working or not?
I can't get it to work on my vaio sz 110. I only have mesa indirect rendering.

To get DRI, working you need three patches:

- this one for mesa
- 35742 for linux-source
- 35739 for xserver-xorg-driver-i810

Somebody is changing the source package names for the bug reports, which is rather confusing things.

Thanks James.

 mesa (6.4.1-0ubuntu7) dapper; urgency=low

   * debian/patches/mesa-6.4.1-i945gm.patch [Malone: #35741]

Can you check if that fixes things for you?

the dri still doesn't work for me.

i've just updated my dapper and got the new mesa. I'm running a patched kernel and agpgart and drm is working. I don't know if i have the right patch for the xorg i810 driver though. Was that part of the latest ubuntu updates or do i have to do it by hand? If yes, how? :)

The xorg i810 driver hasn't been updated yet. Just get the source, apply the patch from 35739, build it and install the new i810_drv.so.

This should have been in since yesterday, Ariel: could you confirm if it works with vanilla (eg. unpatched) packages straight from the archives.

it doesn't work on my machine unless i screwed up somewhere. Everything loads fine, the xorg log shows that the DRI is enabled, but glxinfo says it's disabled. glxgears runs extremely slow so i guess there's a pb. Have any of you been able to have 3D acceleration?

it didn't complain about an already applied patch when i patch the sources i got using an apt-get source. So i guess the patch wasn't applied, right?

now how do i build it? I tried configure but it complains:

checking for XORG... configure: error: Package requirements (xorg-server xproto xvmc fontsproto ) were not met:

No package 'xorg-server' found
No package 'xvmc' found
No package 'fontsproto' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XORG_CFLAGS
and XORG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

ok i managed to compile the thing, did a make and make install,
restarted X, and still no dri. I don't get it!

On Thu, 2006-03-23 at 22:23 +0000, Ariel Vardi wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/35741
>
> Comment:
> it didn't complain about an already applied patch when i patch the
> sources i got using an apt-get source. So i guess the patch wasn't
> applied, right?
>
> now how do i build it? I tried configure but it complains:
>
> checking for XORG... configure: error: Package requirements (xorg-server
> xproto xvmc fontsproto ) were not met:
>
> No package 'xorg-server' found
> No package 'xvmc' found
> No package 'fontsproto' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables XORG_CFLAGS
> and XORG_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.

/var/log/syslog should contain a line like this

agpgart: Detected an Intel 945GM Chipset.

/var/log/Xorg.0.log should contain

(II) I810(0): [drm] loaded kernel module for "i915" driver
(II) I810(0): [drm] DRM interface version 1.2
(II) I810(0): [drm] created "i915" driver at busid "pci:0000:00:02.0"

and then later

(II) I810(0): [DRI] installation complete
(II) I810(0): direct rendering: Enabled

Finally glxinfo should say:

direct rendering: Yes

What are you seeing different?

Well i have everything you said except the last glxinfo. All the other
things you said were in syslog and Xorg.0.log

ariel@haifa:~$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
    GLX_EXT_import_context, GLX_OML_swap_method,
GLX_SGI_make_current_read,
    GLX_SGIS_multisample, GLX_SGIX_hyperpipe, GLX_SGIX_swap_barrier,
    GLX_SGIX_fbconfig
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample,
GLX_EXT_import_context,
    GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_MESA_allocate_memory,
    GLX_MESA_swap_control, GLX_MESA_swap_frame_usage,
GLX_OML_swap_method,
    GLX_OML_sync_control, GLX_SGI_make_current_read,
GLX_SGI_swap_control,
    GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
    GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group,
    GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample,
GLX_EXT_import_context,
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method,
    GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
    GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
OpenGL extensions:
    GL_ARB_depth_texture, GL_ARB_imaging, GL_ARB_multitexture,
    GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shadow,
    GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp,
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
    GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
    GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat,
    GL_ARB_texture_rectangle, GL_ARB_transpose_matrix,
GL_ARB_window_pos,
    GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
GL_EXT_blend_func_separate,
    GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract,
    GL_EXT_clip_volume_hint, GL_EXT_copy_texture,
GL_EXT_draw_range_elements,
    GL_EXT_fog_coord, GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels,
    GL_EXT_point_parameters, GL_EXT_polygon_offset,
GL_EXT_rescale_normal,
    GL_EXT_secondary_color, GL_EXT_separate_specular_color,
    GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap,
    GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D,
    GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add,
    GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
    GL_EXT_texture_lod_bias, GL_EXT_texture_object,
GL_EXT_texture_rectangle,
    GL_EXT_vertex_array, GL_APPLE_packed_pixels,
GL_ATI_texture_env_combine3,
    GL_ATI_texture_mirror_once, GL_ATIX_texture_env_combine3,
    GL_HP_occlusion_test, GL_IBM_texture_mirrored_repeat,
    GL_INGR_blend_func_separate, GL_MESA_pack_invert,
GL_MESA_ycbcr_texture,
    GL_NV_blend_square, GL_NV_point_sprite, GL_NV_texgen_reflection,
    GL_NV_texture_rectangle, GL_SGIS_generate_mipmap,
    GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp,
    GL_SGIS_texture_lod, GL_SGI...

So mesa isn't loading the DRI driver. What version of libgl1-mesa-dri do you have installed? I have 6.4.1-0ubuntu7.

Also check your xorg.conf is loading dri and glx modules in the Module section and includes

Section "DRI"
   Mode 0666
EndSection

For what it's worth I have done the following things and the Intel i945GM video on my Dell Inspiron 6400 notebook is working now (in DRI mode with all bells and whistles):

* Updated xserver-xorg-driver-i810 which now has the i945GM PCI IDs patch etc applied (1.4.1.3-0ubuntu2).

* Built my own mesa packages from the 6.4.1-0ubuntu6 sources, with the patch at the top of this thread applied.

* Built my own kernel from the latest vanilla 2.6.16 sources using the dapper 2.6.15-19 config.

* Used the 855resolution hack program to set my video bios modes to include the native panel resolution 1280x800.

I've checked the kernel changelog:

  zless /usr/share/doc/linux-image-2.6.15-19-386/changelog.Debian.gz

and it's not in the one I have here so you might need to wait a couple of days for another one.

Yes i have this version of libgl1-mesa-dri.
Attached is my Xorg conf and log.

On Fri, 2006-03-24 at 07:45 +0000, James Clark wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/35741
>
> Comment:
> So mesa isn't loading the DRI driver. What version of libgl1-mesa-dri do
> you have installed? I have 6.4.1-0ubuntu7.
>
> Also check your xorg.conf is loading dri and glx modules in the Module
> section and includes
>
> Section "DRI"
> Mode 0666
> EndSection

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Wed Dec 14 16:39:22 PST 2005

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "ServerLayout"
    Identifier "Default Layout"
    Screen "Default Screen" 0 0
    InputDevice "Configured Mouse"
    InputDevice "Generic Keyboard"
    InputDevice "Synaptics Touchpad"
EndSection

Section "Files"

        # paths to defoma fonts
    FontPath "/usr/share/X11/fonts/misc"
    FontPath "/usr/share/X11/fonts/cyrillic"
    FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
    FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
    FontPath "/usr/share/X11/fonts/Type1"
    FontPath "/usr/share/X11/fonts/CID"
    FontPath "/usr/share/X11/fonts/100dpi"
    FontPath "/usr/share/X11/fonts/75dpi"
    FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
    FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
        Load "dbe" # Double buffer extension
        SubSection "extmod"
                Option "omit xfree86-dga" # don't initialise the DGA extension
        EndSubSection
        Load "type1"
        Load "speedo"
        Load "freetype"
        # Load "xtt"
        Load "glx"
        Load "dri"
EndSection

Section "InputDevice"
    Identifier "Generic Keyboard"
    Driver "kbd"
    Option "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc104"
    Option "XkbLayout" "us"
EndSection

Section "InputDevice"
    Identifier "Configured Mouse"
    Driver "mouse"
    Option "CorePointer"
    Option "Device" "/dev/input/mice"
    Option "Protocol" "ImPS/2"
    Option "Emulate3Buttons" "true"
    Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    Identifier "Synaptics Touchpad"
    Driver "synaptics"
    Option "...

Ariel: please can you post the currently installed versions of packages you have:

    $ dpkg -l | awk '/^ii.*(libgl1|linux-image|driver-i810)/{print $2,$3}'

Here you go:

ariel@haifa:~$ dpkg -l | awk '/^ii.*(libgl1|linux-image|
driver-i810)/{print $2,$3}'
libgl1-mesa 6.4.1-0ubuntu7
libgl1-mesa-dev 6.4.1-0ubuntu7
libgl1-mesa-dri 6.4.1-0ubuntu7
linux-image-2.6.12-10-386 2.6.12-10.28
linux-image-2.6.12-10-686-smp 2.6.12-10.28
linux-image-2.6.12-9-386 2.6.12-9.23
linux-image-2.6.15-15-686 2.6.15-15.21
linux-image-2.6.15-16-386 2.6.15-16.23
linux-image-2.6.15-16-686 2.6.15-16.23
linux-image-2.6.15-17-386 2.6.15-17.26
linux-image-2.6.15-17-686 2.6.15-17.26
linux-image-2.6.15-18-386 2.6.15-18.27
linux-image-2.6.15-18-686 2.6.15-18.27
linux-image-2.6.15-19-386 2.6.15-19.29
linux-image-2.6.15-19-686 2.6.15-19.29
linux-image-2.6.15.5-ubuntu1 custom.1.0
linux-image-686 2.6.15.18
linux-image-686-smp 2.6.12.16.1
xserver-xorg-driver-i810 1.4.1.3-0ubuntu2

On Fri, 2006-03-24 at 19:43 +0000, Paul Sladen wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/35741
>
> Comment:
> Ariel: please can you post the currently installed versions of packages you have:
>
> $ dpkg -l | awk '/^ii.*(libgl1|linux-image|driver-i810)/{print $2,$3}'

root@haifa:/home/ariel# export LIBGL_DEBUG=verbose
root@haifa:/home/ariel# export MESA_DEBUG=verbose
root@haifa:/home/ariel# glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.4.1 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

probably got a lead here!

Indeed:

  $ ls -l /usr/X11R6/lib/modules/dri/i915_dri.so
  No such file or directory
  $ dpkg -S i915_dri
  libgl1-mesa-dri: /usr/lib/dri/i915_dri.so

...

root@haifa:/home/ariel# export LIBGL_DEBUG=verbose
root@haifa:/home/ariel# export MESA_DEBUG=verbose
root@haifa:/home/ariel# glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.4.1 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

probably got a lead here!

fixed it with a symlink in /usr/X11R6/lib/modules to /usr/lib/dri
how come this didn't happen to you guys?

On Sat, 2006-03-25 at 02:22 +0000, Paul Sladen wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/35741
>
> Comment:
> Indeed:
>
> $ ls -l /usr/X11R6/lib/modules/dri/i915_dri.so
> No such file or directory
> $ dpkg -S i915_dri
> libgl1-mesa-dri: /usr/lib/dri/i915_dri.so
>
> ...

Hi Ariel, could you help to debug this further, it needs to work out
of the box rather than being solvable by a symlink! :-)

The search path for the modules is stored in the binary, this is what I get on mine:

  $ dpkg -L libgl1-mesa | xargs strings | grep /usr
  /usr/lib/dri
  /usr/share/common-licenses/LGPL.
  /usr/lib/dri

and is setup here:

  $ grep -r DEFAULT_DRIVER_DIR .
  ./configs/debian-dri: ... -DDEFAULT_DRIVER_DIR=\"/usr/lib/dri\"

But also defaults to:

  ./src/glx/x11/dri_glx.c:#define DEFAULT_DRIVER_DIR "/usr/X11R6/lib/modules/dri"

if that is not defined. It is also overriddable with setting the environment variable:

  libPaths = getenv("LIBGL_DRIVERS_PATH");

Is that that environment variable being set anywhere, or do you by chance have a custom compiled 'mesa' installed on your system?

I've re-read through all the above messages and I think I guess what has happened:

   "it didn't complain about an already applied patch when i patch the sources i got using an apt-get source. So i guess the patch wasn't applied, right?"

The patch is in a delta-patch in 'debian/patches' so is only applied when the system is built; so yes, ...the patch would have appiled quite cleanly! :-)

 "ok i managed to compile the thing, did a make and make install, restarted X, and still no dri. I don't get it!"

Ahhh a make install. Normally when building debian packages we'd use something like:

  $ debuild -uc -us -i
  $ sudo dpkg -i ../mesa-*.deb

What's happened here is that the *packaging system* thinks you've got version 'mesa...ubuntu7' installed, but the copy that you compiled yourself and installed has overwritten the files in that package---except that the compiled copy wasn't built with the debian Makefile and settings so the module load directory is defaulting to the previous one.

Can you do:

  $ sudo apt-get --reinstall install libgl1-mesa libgl1-mesa-dri mesa-common-dev

and hopefully that should tidy things up for you...

wow, that's a pretty impressive guess! :)
However, from your first post I managed to see that the package nvidia-glx had diverted libGL.so.1.2 to /usr/lib/nvidia/libGL.so.1.2.xlibmesa

I tried to temporarily remove nvidia-glx but it said:

Removing nvidia-glx ...
dpkg-divert: rename involves overwriting `/usr/lib/libGL.so.1.2' with
  different file `/usr/lib/nvidia/libGL.so.1.2.xlibmesa', not allowed
dpkg: error processing nvidia-glx (--remove):
 subprocess post-removal script returned error exit status 2

Just out of curiosity i removed the symlink i had previously created, resulting in dri not working again. I replaced manually libGL by the one that had been diverted by nvidia-glx and it worked. DRI is enabled without any dirty symlink.

The problem is therefore with nvidia-glx.
The new Vaio SZ laptops have both an intel 945gm and an nvidia chipset between which you can switch to save battery life.

i945GM *and* an Nvidia. Now that's just crack.

Yes, definately time to start a new bug report! :)

FWIW, in Windows XP, when you hot-switch the nvidia-945gm mode, a window pops up saying "reboot if you want to change graphics card".

If this could be hot-switched in Linux, it would be uber cool.

It probably actually is, if both drivers leave the hardware in a sane state - I think you'll have to file it as a wish list and we'll concentrate on getting *one* of the drivers to work with everything first ;-)

A silly proposition, but Gentoo uses a mechanism similar to our /etc/alternatives to switch GLX/TLS symlinks between Mesa and NVidia. Could we implement something like that, so users can use something like update-alternatives --config opengl to switch between different GLX implementations? I'll have to say that the way nvidia-glx overwrites symlinks is kind of crude :-)

This bug (or a varint of it) is still around (I'm using Ubuntu 6.06 LTS).

I wasn't able to enable DRI for i915 despite all the hints available until I stumbled across this thread and repeated some of the experimentation's that Ariel did. This solved my issue, and it possibly also provides a hint to this (or a related) bug.

The symptoms I got was that /var/log/Xorg.0.log and dmsg both showed all the signs that DRI was enabled. But still, no matter how I tried, I couldn't get glxinfo show that "direct rendering" was enabled.

Eventually my suspicions lead me to believe that there was something broken between glx and the lower layers and that the symptoms resembled the ones mentioned here. (I didn't however see any message about i915_dri.so not being found.)

So I did the following:
-------------------------------------
dpkg -L libgl1-mesa-dri
:
usr/lib/libGL.so.1.2
diverted by xorg-driver-fglrx to: /usr/lib/fglrx/libGL.so.1.2.xlibmesa
:
-------------------------------------

errm, wait-a-minute what's this...? fglrx? That's for ATI cards. Further investigation showed that this file belongs to xorg-driver-fglrx, which was installed, but so was also all other drivers (xorg-driver-all) as well.

I simply removing xorg-driver-fglrx, restarted X and all worked peaches. Repeating the command above now showed that usr/lib/libGL.so.1.2 no longer was diverted either (whatever that is ;) ).

Noticeable is that the system I'm using is almost brand new and I didn't recompile neither the kernel nor any of the kernel- or X- drivers/modules. Furthermore I think that the symlink patches above isn't needed any longer (at least not for my current version of the system).

Hope this helps and thanx for a good job with Ubuntu.

/Michael

Albert & Paul, as for supporting dynamic switching between the two cards, I'm pretty sure one is disabled when the other is in use. If both were enabled (powered on), then the switch wouldn't have much utility in terms of saving the battery. So, the only thing we could do is have a similar message.

I don't know if this bug fits in this thread or not. The problem I have is that my Sony Vaio SZ2MB has two video cards. One 945GM intel and one nvidia card.

With the nvidia card I have all the 3d acceleration working but with the 945GM I don't. The problem is that I don't why this is not working.

My xorg.conf loads GLX and DRI, and the driver that I'm using is i810. I have tried to load i915 and intel-agp manually and I get the same. The most interesting error is found in /var/log/xorg.0.log

(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
error opening security policy file /usr/lib/xserver/SecurityPolicy

I don't know why is trying to load an nvidia compatible driver.

Could anyone help me?

Thanks in advance

this happened to me as well. but, if i uninstall the nvidia-glx
package, then i do have 3D accel working with the i965 card. beryl
does not working with xinerama, though.

so it seems as if the nvidia-glx package interferes with the
acceleration for the i965 card.

On 2/5/07, Daniel Lombraña <email address hidden> wrote:
> I don't know if this bug fits in this thread or not. The problem I have
> is that my Sony Vaio SZ2MB has two video cards. One 945GM intel and one
> nvidia card.
>
> With the nvidia card I have all the 3d acceleration working but with the
> 945GM I don't. The problem is that I don't why this is not working.
>
> My xorg.conf loads GLX and DRI, and the driver that I'm using is i810. I
> have tried to load i915 and intel-agp manually and I get the same. The
> most interesting error is found in /var/log/xorg.0.log
>
> (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
> error opening security policy file /usr/lib/xserver/SecurityPolicy
>
> I don't know why is trying to load an nvidia compatible driver.
>
> Could anyone help me?
>
> Thanks in advance
>
> --
> Wrong module directory used when loading i915_dri.so ?
> https://launchpad.net/bugs/35741
>

>
> so it seems as if the nvidia-glx package interferes with the
> acceleration for the i965 card.
>

Yes, this was my conclusion also.

As I recall it (i could remember it wrong so better double check this)
the nvidia variant of libGL.so is not compatible with DRI. I.e. other
cards should have the same problem with DRI and not only i965.

I.e. in case one has any other card than nividia, remove all nvidia
related packages, restart X and DRI should work.

/Michael

I confirm via a variation, Michael Ambrus's comments.

In this machine, all of the above symptoms are observed.

The final resolution was that the fglrx packages had been installed and were interfering with mesa.

       aptitude remove xorg-driver-fglrx fglrx-control

Fixed it.