lots of "AIGLX: 3D driver claims to not support visual ....etc." in xorg log

Bug #113082 reported by Sergio Zanchetta
30
This bug affects 2 people
Affects Status Importance Assigned to Milestone
DRI
Fix Released
Medium
mesa (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Into my Xorg.0.log I get a lot of warnings:

(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

My video card is an ATI IGP 340M on Compaq Presario 2136EA
Ubuntu Feisty 7.04.

Revision history for this message
In , Erik Andrén (erik-andren) wrote :

Please post your xorg.conf and your xorg.log

Revision history for this message
In , diego (diego-pemas) wrote :

Created an attachment (id=5345)
Xorg.log

Revision history for this message
In , diego (diego-pemas) wrote :

Created an attachment (id=5346)
xorg.conf

Revision history for this message
In , diego (diego-pemas) wrote :

this is what glxinfo says about the visuals available:

   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 0 0 None
0x24 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x25 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow
0x26 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x27 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None
0x28 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x29 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow
0x2a 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x2b 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 0 0 None
0x2c 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x2d 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow
0x2e 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x2f 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None
0x30 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None
0x31 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow
0x32 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow
0x4b 32 tc 0 32 0 r . . 8 8 8 8 0 0 0 0 0 0 0 0 0 Ncon

Revision history for this message
In , Khashayar Naderehvandi (khashayar) wrote :

Created an attachment (id=5384)
xorg log for 855GM chipset, i810.

Revision history for this message
In , Khashayar Naderehvandi (khashayar) wrote :

(In reply to comment #5)
> Created an attachment (id=5384) [edit]
> xorg log for 855GM chipset, i810.
>

Hm, my post disappeared. Anyway, I have the exact same issue on an intel 855GM,
using i810 1.6.0, and mesa 6.5. I've attached the xorg log file. If I need to
attach anything else, please do tell.

Revision history for this message
In , Khashayar Naderehvandi (khashayar) wrote :

(In reply to comment #6)
> (In reply to comment #5)
> > Created an attachment (id=5384) [edit] [edit]
> > xorg log for 855GM chipset, i810.
> >
>
> Hm, my post disappeared. Anyway, I have the exact same issue on an intel 855GM,
> using i810 1.6.0, and mesa 6.5. I've attached the xorg log file. If I need to
> attach anything else, please do tell.

After upgrading mesa to CVS today, the amount of warnings shrunk to only 1:

 glxinfo | grep render
libGL warning: 3D driver claims to not support visual 0x4b
Mesa: CPU vendor: GenuineIntel
Mesa: CPU name: Intel(R) Pentium(R) M processor 1.20GHz
Mesa: MMX cpu detected.
Mesa: SSE cpu detected.
Mesa: Not testing OS support for SSE, leaving enabled.
direct rendering: Yes
OpenGL renderer string: Mesa DRI Intel(R) 852GM/855GM 20050225 x86/MMX/SSE2

Revision history for this message
In , Erik Andrén (erik-andren) wrote :

I can confirm comment #7, I also get one libGL warning. This is with a radeon
7500 mobility.

libGL warning: 3D driver claims to not support visual 0x4b
Mesa: CPU vendor: GenuineIntel
Mesa: CPU name: Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz
Mesa: MMX cpu detected.
Mesa: SSE cpu detected.
Mesa: Not testing OS support for SSE, leaving enabled.
direct rendering: Yes
OpenGL renderer string: Mesa DRI Radeon 20060327 AGP 4x x86/MMX/SSE2 TCL
erik@Ross154 /tmp/driver/xf86-video-ati $

Revision history for this message
In , diego (diego-pemas) wrote :

maybe this is a MESA or DRM bug itself, because glxgears has this error ...

I'm going to fill it into the MESA tree to see what the developers say.

Revision history for this message
In , Erik Andrén (erik-andren) wrote :

*** Bug 6689 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Harikurniawan (harikurniawan) wrote :

My freebsd box also produce the same result, may be it's not specific to some
os. I use freebsd 7.0, Mesa and DRM from lates CVS.

Revision history for this message
In , diego (diego-pemas) wrote :

ping? so far noone from the XOrg or Mesa/DRI team has answered anything.

Revision history for this message
In , Heijs (heijs) wrote :

I have the same problem with my Radeon r200 on an Asus P4P800.

Revision history for this message
In , Samuli Suominen (sasuomin) wrote :

I'm using r200 (9200 PRO) with xorg-server, libdrm, mesa, xf86-video-ati CVS
from today, rest of X.org is from Gentoo Portage.

Used this option, Option "AIGLX" "false" to get rid of those messages in
Xorg.0.log (as I don't need AIGLX yet) but..

libGL warning: 3D driver claims to not support visual 0x4b

..remains in glxgears/glxinfo.

Revision history for this message
In , Chutzpah (chutzpah) wrote :
Download full text (6.0 KiB)

I am hitting this on my laptop, with the i915 driver (the card is an i855GM),
running kernel 2.6.17

here's the full output of glxinfo with LIBGL_DEBUG=verbose, if there is any
other info you need, let me know.

 # DISPLAY=:0 LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.5.1 i915 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/tls/i915_dri.so
libGL: OpenDriver: trying /usr/lib/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 0x23
libGL warning: 3D driver claims to not support visual 0x25
libGL warning: 3D driver claims to not support visual 0x27
libGL warning: 3D driver claims to not support visual 0x29
libGL warning: 3D driver claims to not support visual 0x2b
libGL warning: 3D driver claims to not support visual 0x2d
libGL warning: 3D driver claims to not support visual 0x2f
libGL warning: 3D driver claims to not support visual 0x31
libGL error:
Can't open configuration file /etc/drirc: No such file or directory.
libGL error:
Can't open configuration file /root/.drirc: No such file or directory.
display: :0 screen: 0
direct rendering: Yes
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_EXT_texture_from_pixmap, 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_copy_sub_buffer, 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_MESA_allocate_memory,
    GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method,
    GLX_SGI_make_current_read, GLX_SGI_video_sync, GLX_SGIS_multisample,
    GLX_SGIX_fbconfig
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 852GM/855GM 20050225 x86/MMX/SSE2
OpenGL version string: 1.3 Mesa 6.5
OpenGL extensions:
    GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture,
    GL_ARB_point_parameters, GL_ARB_texture_border_clamp,
    GL_ARB_texture_compression, 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_vertex_buffer_object,
    GL_...

Read more...

Revision history for this message
In , Sebastian-gentoo (sebastian-gentoo) wrote :

Same problem here with Gentoo Linux, X.org 7.1, and the i810 driver on an
ThinkPad X60s notebook.

Revision history for this message
In , Sebastian-gentoo (sebastian-gentoo) wrote :

After updating to the current MESA CVS (from Hanno Böck's Gentoo Overlay) the
problem is gone.

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

The server side warnings seem fixed. For the client side, see bug 6689.

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

Actually, I'm still seeing this with the radeon/r200 drivers and more or less
current development snapshots. Needs investigation.

That said, it seems mostly if not completely cosmetic.

Revision history for this message
In , Joachim Frieben (jfrieben) wrote :

(In reply to comment #19)
Right, I still see this for my Radeon 7200 (R100), too. "X", etc. are almost up
to date ("Fedora rawhide"). Moreover, the "savage" driver is affected, too ("IBM
ThinkPad T23" sporting a "SuperSavage IX/C"). For the latter, "Xorg.0.log" reports:

"(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".

After launching "glxgears", a "Mesa" warning is spawned to the shell:

 "libGL warning: 3D driver claims to not support visual 0x4b".

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

Please don't clutter up this report with more of the same information that's
already here. Thanks.

Revision history for this message
In , Dark-shadow (dark-shadow) wrote :

(In reply to comment #19)
> Actually, I'm still seeing this with the radeon/r200 drivers and more or less
> current development snapshots. Needs investigation.
>
> That said, it seems mostly if not completely cosmetic.

The `visual 0x4b' warnings disappear when disabling the composite extension
(radeon) in xorg.conf. Or the other way round: They only appear when enabling
the composite extension ;-)

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

*** Bug 8477 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Marki (marki) wrote :

The post mention that the bug is fixed on the CVS tree. Was the fixed included
in version 6.5.1? I am getting a form of it with this version, from a Fedora rpm.

Revision history for this message
In , sergiomb (sergio-sergiomb) wrote :

Created an attachment (id=8208)
xorg log

I tryed with libdrm-2.3.0-1.fc6 Mesa6.5.2 and (II) Module i810: vendor="X.Org
Foundation"
    compiled for 7.1.1, module version = 1.7.3

and nothing new

Revision history for this message
In , Sven-pedersen (sven-pedersen) wrote :

Created an attachment (id=9222)
xorg.conf Radeon Mobility M7 LW [7500]

On this machine a hard freeze happens immediately after the message indicating this bug appears.

Revision history for this message
In , Sven-pedersen (sven-pedersen) wrote :

Created an attachment (id=9224)
xorg.log Radeon Mobility 7500, i845 chipset

Sorry, I'm just learning to use Bugzilla. I wanted to give more info.

I'm using a ThinkPad T30, which has the Intel 845 (82845) chipset and a Radeon Mobility M7 LW (normally called 7500). I'm running the newly released RedHat Enterprise 5, which is based on Fedora Core 6. It has OpenGL 1.3 (Mesa 6.5.1) and Xorg 7.1 on Linux kernel 2.6.18 (heavily patched following RedHat tradition to be more like 2.6.19 or so).

I first noticed the crash bug when I tried to use the Fedora Core 6 livecd a few months back, but thought it was just a buggy distro.

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

(In reply to comment #26)
>
> On this machine a hard freeze happens immediately after the message indicating
> this bug appears.

That can't be directly related to these messages. Please find a bug about a similar freeze or file a new one.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Into my Xorg.0.log I get a lot of warnings:

(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

My video card is an ATI IGP 340M on Compaq Presario 2136EA
Ubuntu Feisty 7.04.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

My Xorg.0.log.

Changed in xorg:
status: Unconfirmed → Confirmed
Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

I assume this is not a duplicate of bug #58541, since that bug was considered about the non-working AIGLX/compositing, not the warnings.

I have the same warnings here, using xserver-xorg-core version 2:1.2.0-3ubuntu8.

Revision history for this message
In , Juan Pablo Salazar Bertín (snifer) wrote :

I think this is being fixed in bug #6689.

*** This bug has been marked as a duplicate of bug 6689 ***

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

This is very unlikely a duplicate:

* The list of visuals warned about is different between libGL and the X server.
* The code in question is different between them as well.

That said, it's quite possibly a similar issue as bug 6689, so maybe the lessons learned there can be applied here.

Changed in dri:
status: Unknown → Invalid
Changed in dri:
status: Invalid → Confirmed
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Confirmaed in Ubuntu Gutsy using xserver-xorg-core 1.3.0.0.dfsg-12ubuntu8_i386.

Revision history for this message
Alessandro Ghersi (alessandro-ghersi) wrote :

Confirm this bug in Kubuntu Hardy.
xserver-xorg-core version 1:7.3+10ubuntu5
My video card is an Intel X3500 integrated in Asus P5E-VM HDMI chipset G35

Revision history for this message
Tomi Urankar (tomi0) wrote :

the same with me. Using Hardy with FGLRX driver

Revision history for this message
arno_b (arno.b) wrote :

The same with me using an ATI card with restricted drivers on hardy RC

Revision history for this message
blubbi (torsten-steiner) wrote :

Same here. Hardy stable.

Revision history for this message
blubbi (torsten-steiner) wrote :

Sorry. Forgot to post my video card. It is an ATI Radeon 9800Pro

Revision history for this message
Ілля Романенко (ilyaromanenko) wrote :

same problem 9600XT

Revision history for this message
SteveZalek (zaleksf) wrote :

Same problem here; Ubuntu Hardy kernel 2.6.24-17 using ATI Radeon X1300/1550 series PCI Express card

Revision history for this message
Alex Krjuger (krjuger) wrote :

Same problem Ubuntu Hardy 8.04.1 using S3 SuperSavage on Notebook Toshiba Satellite 2405

Revision history for this message
pelican64 (pelican69) wrote :

I have: Ubuntu Hardy 8.04 32bit version. My video card is : ATI Technologies Inc RC410 [Radeon Xpress 200M]
I'm having the same problems...

Revision history for this message
AndyAirey (aairey) wrote :

Confirmed on Compaq Presario 2104EA running xubuntu 8.04.1
video card: 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon IGP 330M/340M/350M [1002:4337]
using xorg-server-video-ati 1:6.8.0-1

Revision history for this message
Shaved Wookie (shavedwookie) wrote :

+1

Kubuntu Hardy Remix, ATI HD4870 +fglrx 8.6

Revision history for this message
Timo Salokas (timo-salokas) wrote :

Same here with Kubuntu Hardy Remix, ATI IGP HD3200

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

This shouldn't happen anymore with current xserver.

Changed in dri:
status: Confirmed → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Closed upstream, "shouldn't happen with the current xserver", and jaunty has a recent one.

Changed in mesa:
status: Confirmed → Fix Released
Revision history for this message
In , Anonymous-dodgeit (anonymous-dodgeit) wrote :

(Sorry for logging in anonymous. I don’t want to create an account to drop a singe message.)

This is still not fixed in the current xserver. At least the closed one from ATi.

I have version 8.561 installed right now, and i still get the errors:

(WW) AIGLX: 3D driver claims to not support visual 0x23
                             ⋮
(WW) AIGLX: 3D driver claims to not support visual 0x72

Changed in dri:
importance: Unknown → Medium
Changed in dri:
importance: Medium → Unknown
Changed in dri:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.