| Priority | medium |
|---|---|
| Bug ID | 71789 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | [r300g] Visuals not found in (default) depth = 24 |
| Severity | normal |
| Classification | Unclassified |
| OS | OpenBSD |
| Reporter | mpi@openbsd.org |
| Hardware | PowerPC |
| Status | NEW |
| Version | 9.2 |
| Component | Drivers/Gallium/r300 |
| Product | Mesa |
Created attachment 89467 [details]
Xorg.log without configuration file
Without xorg.conf or with a pixel depth of 24 bits, any application linked to
libGL will fails to load the "r300" driver and after it the "swarst" driver
with the following message:
libGL error: failed to load driver: r300
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
libGL error: failed to load driver: swrast
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
This problem is present in all the Mesa 9.x release up to 9.2.3. But it is not
in the 8 (which segfault at some point), 7.11 was working without config file.
After a bit of investigation, I found that driConvertConfigs() returns NULL in
dri2CreateScreen() when trying to find matching visuals
(src/glx/dri_glx.c:450). However if I specify a depth of 16 bits in my
xorg.conf I cannot reproduce this problem.
This problem is present on OpenBSD -current (future 5.5) which has the drm
drivers synced with Ubuntu's linux 3.8 kernel.
Created attachment 89468 [details]
Xorg.log with 16 bits depth in xorg.conf
FWIW the patches mentionned in http://lists.freedesktop.org/archives/mesa-dev/2013-December/050218.html work for me.
| What | Removed | Added |
|---|---|---|
| OS | OpenBSD | Linux (All) |
I am seeing the same thing in Debian Testing. Those patches woorked all the way up to mesa 10.5.5 then they began to fail.
Created attachment 116274 [details]
glxinfo output
I noticed in the 11.0.3 release notes that this issue was fix. However I am running Lubuntu 16.04 (development) on my iBook G4 and I am still. Getting the same issue. When I change to Defaul Depth 16 I get 3D acceleration. I ran strace under both conditions and am post them plus my Xorg.0.log
Created attachment 119753 [details]
strace default depth 24
Created attachment 119754 [details]
strace default depth 16
Created attachment 119755 [details]
xorg log
| What | Removed | Added |
|---|---|---|
| Version | 9.2 | 11.0 |
I confirm that this bug is still present with Mesa 11.0.6. Without forcing "DefaultDepth" to 16, I get: $ glxgears libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: r300 libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast
| What | Removed | Added |
|---|---|---|
| Version | 11.0 | 11.1 |
With Ubuntu Mate 16.04a2 on a G4 PowerBook5,8 I have to confirm, that this bug is still present with Mesa 11.1.1.
Can confirm this bug on Ubuntu MATE 16.04 daily, Mesa 11.1.1. On a PowerBook 5,6.
| What | Removed | Added |
|---|---|---|
| Version | 11.1 | 11.2 |
Still here on mesa 11.2 (Ubuntu MATE 16.04 daily). Tested on a PowerMac G5 7,3.
| What | Removed | Added |
|---|---|---|
| CC | mathieu.malaterre@gmail.com |
I also see in apitrace that GLXChooseVisual returns with NULL when I to run glxgears.
I also see in apitrace that GLXChooseVisual returns with NULL when I to run glxgears.
An updated patch is now available from: https://lists.freedesktop.org/archives/mesa-dev/2016-April/114409.html As mentioned over here: https://lists.freedesktop.org/archives/mesa-dev/2016-April/114412.html we'are actively looking forward for feedback. I've also attached the patch directly to this bug tracker for convenience: r300g_be.patch
Created attachment 123267 [details] [review] proposed patch
Patched r300g_be.patch against mesa 11.1.3. -> No acceleration at Depth 24.This is Debian sid.
Same here. Glxinfo says r300 fails to load. dan@powerbook2:~$ glxinfo name of display: :0.0 libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: r300 libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig ...
Applied the patch on top of 43f46caf769b0a6d661850ce2fa64b6f4b085b9f, but unfortunately it didn't work. Tested on a PowerBook G4 5,6 with Linux 4.6-rc4 (5f44abd041c5f3be76d57579ab254d78e601315b) / Debian Sid.
| What | Removed | Added |
|---|---|---|
| Attachment #123267 is obsolete | 1 |
Created attachment 123370 [details] [review] final fix? Could you please test this patch?
Created attachment 123385 [details]
glxinfo output with final fix
Patched it on top of cbcd7b60f573d027337a2390e67f6010e9992aaa and that one did
actually work! I've attached the full glxinfo output in case someone is
interested.
Applied against Debian 11.1.3-1. 3-D acceleration at depth=24 works. Power consumption running foobillardplus is very high. Colors at the Cairo Dock are looking pastel shaded.
Elimar, Nathan or anyone else, can you try if the piglit sanity tests pass with this patch? Also, do OpenGL compositing managers such as gnome-shell show correct colours?
Created attachment 123420 [details]
Piglit Sanity Check Results
I've attached the Piglit result of the sanity check to this issue, GNOME Shell
also has a discolouration (the title bar and activity screen is red) and after
using it for a couple of minutes it crashed (SIGSEGV):
[ 6088.876306] gnome-shell[8144]: unhandled signal 11 at 095b44c0 nip 095b44c0
lr 0de343b4 code 30001
[ 6112.441094] gnome-shell[8701]: unhandled signal 11 at 095b44c0 nip 095b44c0
lr 0de343b4 code 30001