From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92039] glxinfo: Error: couldn't find RGB GLX visual or fbconfig; GetVisualConfigs returns 0 visuals; All fbconfigs have VisDepth = 0
Date: Fri, 18 Sep 2015 10:51:37 +0000 [thread overview]
Message-ID: <bug-92039-502-Rd0tycZp6b@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92039-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 471 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92039
--- Comment #3 from Emil Velikov <emil.l.velikov@gmail.com> ---
Hi Mikolaj
Here are a few things to try (keep in mind that I'm not a radeon dev)
- Afaics this is a PPC - is it big endian (BE) system ?
- Do try a later mesa 10.6.x or 11.0.x. Last (and final) 10.1.x was rolled out
~15 months ago, plus we had some BE fixes that just landed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1393 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 prev parent reply other threads:[~2015-09-18 10:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 7:24 [Bug 92039] glxinfo: Error: couldn't find RGB GLX visual or fbconfig; GetVisualConfigs returns 0 visuals; All fbconfigs have VisDepth = 0 bugzilla-daemon
2015-09-18 7:25 ` bugzilla-daemon
2015-09-18 10:29 ` bugzilla-daemon
2015-09-18 10:29 ` bugzilla-daemon
2015-09-18 10:51 ` bugzilla-daemon [this message]
2015-09-18 13:41 ` bugzilla-daemon
2015-09-18 17:31 ` bugzilla-daemon
2015-09-25 8:58 ` bugzilla-daemon
2015-09-25 11:40 ` bugzilla-daemon
2015-09-28 8:46 ` bugzilla-daemon
2016-01-03 1:02 ` bugzilla-daemon
2018-08-31 6:23 ` 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-92039-502-Rd0tycZp6b@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.