glxinfo, xorg in sarge claiming to not support certain visuals
I recently did an aptitude update and aptitude upgrade, pulling in
several new packages from security and updates.
Previously, on xserver-xfree86 I had (finally) managed to get dri
working with the help of using a more recent kernel than that in sarge
(compiled custom 2..6.13). The upshot of this is that various 3d things
like tuxracer, stellarium, etc. worked fine and at a reasonable speed.
My video card is a Matrox Millennium G450 (not dualhead) and running
sarge on an Athlon 1ghz box.
After the upgrade (installing xserver-xorg doesn't affect this, but dri
does work now in xserver-xorg) glxinfo -b reports:
libGL warning: 3D driver claims to not support visual 0x23
libGL warning: 3D driver claims to not support visual 0x24
libGL warning: 3D driver claims to not support visual 0x27
libGL warning: 3D driver claims to not support visual 0x28
libGL warning: 3D driver claims to not support visual 0x2b
libGL warning: 3D driver claims to not support visual 0x2c
libGL warning: 3D driver claims to not support visual 0x2f
libGL warning: 3D driver claims to not support visual 0x30
37
glxinfo does run OK as does glxgears (even though it prints the same
warnings). Other things that are more 3d intensive simply segfault or
lock up (stellarium and fgfs both report the same libGL warning lines,
then segfault, whilst tuxracer goes to a black screen and locks the
system hard -- at that point I can't keyboard or nothing - and having
only one system, I can't ssh into the box to bring X etc. down, so it's
"big red switch" time). Prior to the update, these apps all ran fine.
I note another user (on stellarium.sourceforge.net) reported similar
behavior, but he was running Fedora core 4. As of now, no one has
responded.
I'm beginning to google but I see a number of posts with similar
problems.
--
------------------------------------------------------------------------
David E. Fox Thanks for letting me
dfox@tsoft.com change magnetic patterns
dfox@m206-157.dsl.tsoft.com on your hard disk.
-----------------------------------------------------------------------
Reply to: