GLX failure: couldn't get an RGB, Double-buffered visual

Bug #41349 reported by John Moser
8
Affects Status Importance Assigned to Milestone
xserver-xorg-video-via (Ubuntu)
Invalid
Medium
Unassigned
Dapper
Invalid
Undecided
Unassigned

Bug Description

This happens with the via driver:

bluefox@icebox:~$ glxgears
__driCreateNewScreen_20050727 - succeeded
libGL warning: 3D driver claims to not support visual 0x22
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 0x25
libGL warning: 3D driver claims to not support visual 0x26
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 0x29
libGL warning: 3D driver claims to not support visual 0x2a
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 0x2d
Error: couldn't get an RGB, Double-buffered visual

The vesa driver reports other libGL warnings I believe, but the same error occurs.

Here is a clip of Xorg.0.log showing DRI is enabled:

----Xorg.0.log----
(II) VIA(0): [drm] Detected AGP vendor 0x1106, device 0x204
(II) VIA(0): [drm] Found AGP v3 compatible device. Trying AGP 8X mode.
(II) VIA(0): [drm] Trying to enable AGP fast writes.
(II) VIA(0): [drm] drmAgpEnabled succeeded
(II) VIA(0): [drm] agpAddr = 0xe0000000
(II) VIA(0): [drm] agpBase = (nil)
(II) VIA(0): [drm] agpAddr = 0xe0000000
(II) VIA(0): [drm] agpSize = 0x01e00000
(II) VIA(0): [drm] agp physical addr = 0x00000000
(II) VIA(0): [dri] use agp.
(II) VIA(0): [drm] FBFreeStart= 0x00a00000 FBFreeEnd= 0x03fbf000 FBSize= 0x035bf000
(II) VIA(0): [dri] frame buffer initialized.
(II) VIA(0): X context handle = 0x1
(II) VIA(0): [drm] installed DRM signal handler
(II) VIA(0): [DRI] installation complete
(II) VIA(0): [dri] kernel data initialized.
(II) VIA(0): [drm] Irq handler installed, using IRQ 201.
(II) VIA(0): direct rendering enabled
----END Xorg.0.log----

This bug is related to (and possibly a duplicate of):
  #29493

This bug produces symptoms similar to similar but is fundamentally different from:
  #36314 (DRI is disabled in Xorg.0.log)

This bug may affect other open source and binary Xorg drivers.

Revision history for this message
John Moser (nigelenki) wrote : Xorg.conf affected by the bug

This Xorg.conf is fresh, but the bug still happens. I'm attaching it and its matching Xorg.0.log.

Revision history for this message
John Moser (nigelenki) wrote : Xorg.0.log matching xorg.conf

Xorg.0.log from server running with above configuration. Also relavent interesting information from a terminal:

bluefox@icebox:~$ glxgears
__driCreateNewScreen_20050727 - succeeded
libGL warning: 3D driver claims to not support visual 0x22
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 0x25
libGL warning: 3D driver claims to not support visual 0x26
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 0x29
libGL warning: 3D driver claims to not support visual 0x2a
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 0x2d
Error: couldn't get an RGB, Double-buffered visual

bluefox@icebox:~$ uname -a
Linux icebox 2.6.15-22-amd64-k8 #1 SMP PREEMPT Sun May 7 16:15:46 UTC 2006 x86_64 GNU/Linux

Revision history for this message
John Moser (nigelenki) wrote :

It appears this may be (yet another) 64-bit bug. According to the man page, the via driver is not entirely 64-bit clean, and 3D accel is busted on 64-bit.

http://ftp.x.org/pub/X11R7.0/doc/html/via.4.html

Revision history for this message
Rodrigo Novo (rodarvus) wrote :

John, "man via" on an Edgy system will show the current man page for the via driver - and on this current man page, I see on reference of 64-bits related bugs on the driver.

Anyhow, I've uploaded a new version of this driver today, and wold be immensely grateful if someone could try to reproduce this error with it, and report here the result (also feel free to close the bug, if the error is gone)

Revision history for this message
Martin Schaaf (mascha) wrote :

I have this bug with dapper and a bug fix release for dapper would be fine.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

John, Martin: do you get this error with edgy/feisty?

Changed in xserver-xorg-video-via:
status: Unconfirmed → Needs Info
Revision history for this message
Martin Schaaf (mascha) wrote :

I can't test for now, but I plan an update on the end of this month.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

you can try with the livecd, I think.. no need to install.

Revision history for this message
Martin Schaaf (mascha) wrote :

This isn't possible if try without the "safe graphics" I get a black screen. (Ubuntu 6.10 livecd)

Revision history for this message
Martin Schaaf (mascha) wrote :

I do not get it with the feisty beta live cd.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-video-via (Ubuntu) because there has been no activity for 60 days.]

Revision history for this message
JC Hulce (soaringsky) wrote :

Thank you for reporting this bug to Ubuntu. The version of Ubuntu referenced in this issue has reached end of life, and the issue is fixed in newer versions of Ubuntu. Therefore, I am closing the Dapper task.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Changed in xserver-xorg-video-via (Ubuntu Dapper):
status: New → Invalid
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.