From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71789] New: [r300g] Visuals not found in (default) depth = 24
Date: Tue, 19 Nov 2013 14:05:03 +0000 [thread overview]
Message-ID: <bug-71789-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1645 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71789
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
--> https://bugs.freedesktop.org/attachment.cgi?id=89467&action=edit
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3131 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-11-19 14:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 14:05 bugzilla-daemon [this message]
2013-11-19 14:06 ` [Bug 71789] [r300g] Visuals not found in (default) depth = 24 bugzilla-daemon
2014-01-06 15:47 ` bugzilla-daemon
2015-06-04 3:10 ` bugzilla-daemon
2015-06-04 3:15 ` bugzilla-daemon
2015-11-18 4:11 ` bugzilla-daemon
2015-11-18 4:12 ` bugzilla-daemon
2015-11-18 4:13 ` bugzilla-daemon
2015-11-18 4:14 ` bugzilla-daemon
2015-12-19 12:16 ` bugzilla-daemon
2016-02-13 15:05 ` bugzilla-daemon
2016-02-14 13:49 ` bugzilla-daemon
2016-04-12 21:45 ` bugzilla-daemon
2016-04-25 6:06 ` bugzilla-daemon
2016-04-26 7:45 ` bugzilla-daemon
2016-04-26 19:38 ` bugzilla-daemon
2016-04-27 15:13 ` bugzilla-daemon
2016-04-27 16:55 ` bugzilla-daemon
2016-04-30 18:52 ` bugzilla-daemon
2016-05-01 10:22 ` bugzilla-daemon
2016-05-01 16:39 ` bugzilla-daemon
2016-05-02 1:02 ` bugzilla-daemon
2016-05-02 18:56 ` bugzilla-daemon
2016-05-03 1:20 ` bugzilla-daemon
2016-05-03 6:48 ` bugzilla-daemon
2016-05-05 20:07 ` bugzilla-daemon
2016-05-06 8:51 ` bugzilla-daemon
2016-05-06 9:23 ` bugzilla-daemon
2016-05-06 9:48 ` bugzilla-daemon
2016-05-08 6:17 ` bugzilla-daemon
2016-05-09 7:47 ` bugzilla-daemon
2016-05-09 11:22 ` bugzilla-daemon
2017-02-06 21:26 ` bugzilla-daemon
2017-04-08 13:01 ` bugzilla-daemon
2017-04-08 13:05 ` bugzilla-daemon
2017-04-08 16:41 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-71789-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.