dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 87856] Driver load fails with no error on ppc64 host
Date: Tue, 30 Dec 2014 08:59:34 +0000	[thread overview]
Message-ID: <bug-87856-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2371 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

            Bug ID: 87856
           Summary: Driver load fails with no error on ppc64 host
           Product: Mesa
           Version: 10.2
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: freedesktopbugs@63bit.net

Created attachment 111507
  --> https://bugs.freedesktop.org/attachment.cgi?id=111507&action=edit
Xorg log, dmesg | fgrep radeon, and glxinfo with LIBGL_DEBUG set

I have a PowerPC G5 (ppc64 with 64-bit userland) with working KMS using a
(ostensibly x86) Radeon HD4650. KMS is enabled and the kernel and Xorg parts of
KMS/DRI2 appear to be attaching correctly.

After X starts, running LIBGL_DEBUG=verbose glxinfo outputs the following:
libGL: OpenDriver: trying /usr/lib64/dri/tls/r600_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/r600_dri.so
libGL: driver does not expose __driDriverGetExtensions_r600():
/usr/lib64/dri/r600_dri.so: undefined symbol: __driDriverGetExtensions_r600
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL error: failed to load driver: r600
libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so
libGL: driver does not expose __driDriverGetExtensions_swrast():
/usr/lib64/dri/swrast_dri.so: undefined symbol: __driDriverGetExtensions_swrast
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL error: failed to load driver: swrast
Error: couldn't find RGB GLX visual or fbconfig
Error: couldn't find RGB GLX visual or fbconfig

I am under the impression that the undefined symbol should not be causing
problems after reading this bug: 
https://bugs.freedesktop.org/show_bug.cgi?id=72198

Nonetheless, glxgears will not run, and in general it appears mesa acceleration
is not occurring. Mesa was compiled with support for llvm and the r600
generator.
I am attaching various logs. I would be glad to test patches or hacks :)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3991 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

             reply	other threads:[~2014-12-30  8:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30  8:59 bugzilla-daemon [this message]
2014-12-30  9:01 ` [Bug 87856] Driver load fails with no error on ppc64 host bugzilla-daemon
2014-12-30  9:01 ` bugzilla-daemon
2015-01-07  7:20 ` bugzilla-daemon
2015-01-10  3:06 ` bugzilla-daemon
2015-01-10  3:37 ` bugzilla-daemon
2015-05-18  9:38 ` bugzilla-daemon
2015-05-18 14:19 ` bugzilla-daemon
2015-05-18 19:22 ` bugzilla-daemon
2015-05-18 21:30 ` bugzilla-daemon
2015-05-19  9:00 ` bugzilla-daemon
2015-05-21  6:55 ` bugzilla-daemon
2015-05-21 13:13 ` bugzilla-daemon
2015-08-23 19:14 ` bugzilla-daemon
2015-08-26 20:15 ` bugzilla-daemon
2016-04-28  9:42 ` bugzilla-daemon
2016-04-30  6:14 ` 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-87856-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox