Can't load r200_dri in libGL (ATI Radeon R250 Lf [FireGL 9000])

Bug #48029 reported by Laurent Voisin on 2006-06-02
18
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: libgl1-mesa-dri

The command:

   LIBGL_DEBUG=verbose glxinfo

gives the following output:

  libGL: XF86DRIGetClientDriverName: 5.0.3 r200 (screen 0)
  libGL: OpenDriver: trying /usr/lib/dri/r200_dri.so
  libGL error: dlopen /usr/lib/dri/r200_dri.so failed (/usr/lib/dri/r200_dri.so: undefined symbol: _glapi_get_dispatch)
  libGL error: unable to find driver: r200_dri.so
  libGL: XF86DRIGetClientDriverName: 5.0.3 r200 (screen 0)
  libGL: OpenDriver: trying /usr/lib/dri/r200_dri.so
  libGL error: dlopen /usr/lib/dri/r200_dri.so failed (/usr/lib/dri/r200_dri.so: undefined symbol: _glapi_get_dispatch)
  libGL error: unable to find driver: r200_dri.so
  name of display: :0.0
  display: :0 screen: 0
  direct rendering: No
  ...

hence, no graphic acceleration is available.

This happens on an IBM T40p, with graphic card:

  0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [FireGL 9000] (rev 02)

My xorg.conf file contains:

  ...
  Section "Device"
        Identifier "ATI Technologies, Inc. Radeon Mobility 9000 M9 (R250 Lf)"
        Driver "radeon"
        BusID "PCI:1:0:0"
  EndSection
  ...

Any help is welcome.

cprise (cprise-yahoo) wrote :
Download full text (3.7 KiB)

I also don't have dri capability with my Radeon 7000 due to the same problem: undefined symbols.

# export LIBGL_DEBUG=verbose
# glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 5.0.3 radeon (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/radeon_dri.so
libGL error: dlopen /usr/lib/dri/radeon_dri.so failed (/usr/lib/dri/radeon_dri.so: undefined symbol: _glapi_get_dispatch)
libGL error: unable to find driver: radeon_dri.so
libGL: XF86DRIGetClientDriverName: 5.0.3 radeon (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/radeon_dri.so
libGL error: dlopen /usr/lib/dri/radeon_dri.so failed (/usr/lib/dri/radeon_dri.so: undefined symbol: _glapi_get_dispatch)
libGL error: unable to find driver: radeon_dri.so
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: ATI
client glx version string: 1.3
client glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float,
    GLX_ATI_render_texture
GLX version: 1.2
GLX extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
    GLX_ARB_multisample
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_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
    GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
    GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
    GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
    GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
    GL_EXT_texture_lod_bias
glu version: 1.3
glu extensions:
    GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

   visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
 id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x23 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 1 0 None
0x24 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x25 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow
0x26 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow
0x27 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 1 0 None
0x28 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x29 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow
0x2a 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow
0x2b 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 1 0 None
0x2c 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x2d 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow
0x2e 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow
0x2f 24 d...

Read more...

Martin Hoefling (martoss) wrote :

same here on my r100 (Radeon 7500 mobility),
fixed it (temporary) by linking /usr/lib/dri /usr/X11R6/lib/modules/dri

Laurent Voisin (lvoisin-inf) wrote :

Hi Martin,

where did you get that "/usr/X11R6/lib/modules/dri" directory?
I don't have it on my computer, nor could I find any Dapper package providing that folder.

Did you install a fresh Xorg distribution, by-passing dpkg?

Same problem here. _glapi_get_dispatch is undefined symbol in
/usr/lib/dri/r200_dri.so

and thus DRI is disabled with my ATI Radeon 9100.

On Dapper I fixed this problem compiling and installing my own libGL: quoting from http://dri.freedesktop.org/wiki/DriTroubleshooting :

"If the driver complains about unresolved symbols then your libGL is out of sync with your DRI drivers. Because APIs change, you typically need a libGL from the latest X.Org release to run DRI drivers, and sometimes you need a libGL from X.Org CVS for the latest drivers. Reinstall both your drivers and your libGL from sources from the same date."

since I remember it was a pain, I'd really like to have DRI work out of the box on Edgy - please fix this ASAP !!

Thanks!

I also have this problem with a Ati Radeon 9200 (Mobility M9+ I think) inside a notebook.

danny@laptop:~$ LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 5.2.0 r200 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/r200_dri.so
libGL error: dlopen /usr/lib/dri/r200_dri.so failed (/usr/lib/dri/r200_dri.so: undefined symbol: _glapi_get_dispatch)
libGL error: unable to find driver: r200_dri.so
libGL: XF86DRIGetClientDriverName: 5.2.0 r200 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/r200_dri.so
libGL error: dlopen /usr/lib/dri/r200_dri.so failed (/usr/lib/dri/r200_dri.so: undefined symbol: _glapi_get_dispatch)
libGL error: unable to find driver: r200_dri.so
display: :0 screen: 0
direct rendering: No

I stumbled upon a message on the internet while searching for a resolution that said something like:
"After debugging and looking at loaded drivers and such it seems that even if I use the 'ati' driver it tries to load some DRI components from the 'fglrx' driver. After uninstalling the xorg-video-fglrx driver this problem was gone."

I have tried the same, and it worked flawlessly for me. So I would advise anyone else to try this. (And you could also try the other way around: uninstall 'ati' and use 'fglrx' if that's preferred. Haven't tested this though.)

It seems like those two drivers might conflict with each other. (At least they did for me.)

Timo Aaltonen (tjaalton) wrote :

fglrx can't be installed when trying to use the free driver with acceleration.

Changed in mesa:
status: Unconfirmed → Rejected

Same with the r300 driver:
the distribution is bleeding edge (20 June 2007) gutsy, the card is a R423 (although, i guess it's pretty irrelevant)
libgl1-mesa-dri version is 6.5.3-1ubuntu1

deepfire@betelheise:~$ LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 5.2.0 r300 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
libGL error: dlopen /usr/lib/dri/r300_dri.so failed (/usr/lib/dri/r300_dri.so: undefined symbol: _glapi_add_dispatch)
libGL error: unable to find driver: r300_dri.so
libGL: XF86DRIGetClientDriverName: 5.2.0 r300 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
libGL error: dlopen /usr/lib/dri/r300_dri.so failed (/usr/lib/dri/r300_dri.so: undefined symbol: _glapi_add_dispatch)
libGL error: unable to find driver: r300_dri.so
display: :0 screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
s

Samium Gromoff (deepfire) wrote :

I noticed the solution specified above by Danny van Heumen, hunted down all remains of hand-installed fglrx, deleted them, and it just worked, as promised.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers