From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103968] No Hardware Acceleration with AMD RX 550
Date: Thu, 30 Nov 2017 11:38:51 +0000 [thread overview]
Message-ID: <bug-103968-502-ls5UqqWJt9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103968-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1832 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103968
--- Comment #4 from Odo Wolbers <moz-bugzilla.20.darkover@spamgourmet.com> ---
ldd /usr/lib/xorg/modules/libglamoregl.so
linux-vdso.so.1 (0x00007ffefbab0000)
libgbm.so.1 => /usr/local/lib/libgbm.so.1 (0x00007f4d676cd000)
libepoxy.so.0 => /usr/lib/x86_64-linux-gnu/libepoxy.so.0
(0x00007f4d673cc000)
libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1
(0x00007f4d671a3000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4d66e90000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007f4d66c7b000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f4d66a5d000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4d666ba000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f4d664a0000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1
(0x00007f4d6626e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4d6606a000)
libdrm.so.2 => /usr/local/lib/libdrm.so.2 (0x00007f4d65e5a000)
libcap-ng.so.0 => /lib/x86_64-linux-gnu/libcap-ng.so.0
(0x00007f4d65c55000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4d67b0d000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f4d65a4d000)
Looking for leftovers, after all the tweaking, re-linking and compiling I've
done, seems to be harder than just to fire up a complete re-install.
What would be a reasonable strategy? Starting with debian 4.9.2 and upgrading
the kernel to 4.13 or 4.14? Before kernel 4.11 the only available graphic mode
was 1024x768. On the other hand would I be left exactly where I started
tweaking because the hardware acceleration didn't work.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2656 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-30 11:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 12:06 [Bug 103968] No Hardware Acceleration with AMD RX 550 bugzilla-daemon
2017-11-29 14:16 ` bugzilla-daemon
2017-11-29 14:24 ` bugzilla-daemon
2017-11-30 10:55 ` bugzilla-daemon
2017-11-30 11:10 ` bugzilla-daemon
2017-11-30 11:38 ` bugzilla-daemon [this message]
2017-11-30 11:44 ` bugzilla-daemon
2017-11-30 12:18 ` bugzilla-daemon
2017-11-30 14:59 ` bugzilla-daemon
2017-11-30 15:37 ` bugzilla-daemon
2017-11-30 15:43 ` bugzilla-daemon
2017-11-30 15:48 ` 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-103968-502-ls5UqqWJt9@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