From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103968] No Hardware Acceleration with AMD RX 550
Date: Wed, 29 Nov 2017 12:06:02 +0000 [thread overview]
Message-ID: <bug-103968-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 8358 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103968
Bug ID: 103968
Summary: No Hardware Acceleration with AMD RX 550
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: moz-bugzilla.20.darkover@spamgourmet.com
Created attachment 135796
--> https://bugs.freedesktop.org/attachment.cgi?id=135796&action=edit
Xorg.log showing e.g. glamor/EGL fails to initialise
Hello Community,
sorry, I'm not an English mothertongue.
Since three month now I try to activate the hardware acceleration of an AMD RX
550 with debian (tried 4.9, 4.11, 4.12, 4.13, 4.14). I tried different
configurations, self-compiled kernels, self-compiled bleeding edge mesa,
self-compiled xorg - no luck.
Researching the web I found disturbing info about a disfunct hardware
acceleration of the RS 550 with debian. But I couldn't find related bugs on any
list.
So hopefully this is the right bugtracker for this kind of issues.
I tried to keep the logs short and I hope I provided all necessary parts. If
not, just ask.
Until the new machine, I ran linux in virtual machines on MacOS. Therefore I'm
not very experienced in hunting down hardware/driver issues. It looks to me -
without being an expert in X11R7 - that the right driver fails to load or
initialise.
Had to revert to an 4.9 built Xorg because I tweaked the newer one until it
broke. The newest 4.14 source had problems with a dependency of linux-headers
with
libssl; linux-headers-4.14.0-041400-generic : depends on : libssl1.0.0 (>=
1.0.0) cannot be installed. (my translation).
apt list libssl*
Auflistung... Fertig
libssl-dev/testing,unstable,now 1.1.0g-2 amd64 [installiert]
libssl-doc/testing,testing,unstable,unstable 1.1.0g-2 all
libssl-ocaml/unstable 0.5.3-1+b1 amd64
libssl-ocaml-dev/unstable 0.5.3-1+b1 amd64
libssl-utils-clojure/testing,testing,unstable,unstable 0.8.3-1 all
libssl1.0-dev/testing,unstable 1.0.2m-3 amd64
libssl1.0.2/testing,unstable,now 1.0.2m-3 amd64 [installiert]
libssl1.1/testing,unstable,now 1.1.0g-2 amd64 [installiert]
Should be ok, IMHO but doesn't work
uname -a
Linux Monster 4.14.0-041400-generic #201711122031 SMP Sun Nov 12 20:32:29 UTC
2017 x86_64 GNU/Linux
-------------------------------------------------------------
dmesg | grep amdgpu || dri || drm || powerplay
[ 4.357694] [drm] amdgpu kernel modesetting enabled.
[ 4.413575] fb: switching to amdgpudrmfb from EFI VGA
[ 4.414195] amdgpu 0000:24:00.0: Invalid PCI ROM header signature: expecting
0xaa55, got 0xffff
[ 4.415022] amdgpu 0000:24:00.0: VRAM: 2048M 0x000000F400000000 -
0x000000F47FFFFFFF (2048M used)
[ 4.415025] amdgpu 0000:24:00.0: GTT: 256M 0x0000000000000000 -
0x000000000FFFFFFF
[ 4.415125] [drm] amdgpu: 2048M of VRAM memory ready
[ 4.415126] [drm] amdgpu: 3072M of GTT memory ready.
[ 4.415260] amdgpu 0000:24:00.0: amdgpu: using MSI.
[ 4.415279] [drm] amdgpu: irq initialized.
[ 4.611879] amdgpu: [powerplay] amdgpu: powerplay sw initialized
[ 4.614395] amdgpu 0000:24:00.0: fence driver on ring 0 use gpu addr
0x0000000000400040, cpu addr 0xffffb0d788495040
[ 4.614433] amdgpu 0000:24:00.0: fence driver on ring 1 use gpu addr
0x00000000004000c0, cpu addr 0xffffb0d7884950c0
[ 4.614460] amdgpu 0000:24:00.0: fence driver on ring 2 use gpu addr
0x0000000000400140, cpu addr 0xffffb0d788495140
[ 4.614486] amdgpu 0000:24:00.0: fence driver on ring 3 use gpu addr
0x00000000004001c0, cpu addr 0xffffb0d7884951c0
[ 4.614511] amdgpu 0000:24:00.0: fence driver on ring 4 use gpu addr
0x0000000000400240, cpu addr 0xffffb0d788495240
[ 4.614535] amdgpu 0000:24:00.0: fence driver on ring 5 use gpu addr
0x00000000004002c0, cpu addr 0xffffb0d7884952c0
[ 4.614564] amdgpu 0000:24:00.0: fence driver on ring 6 use gpu addr
0x0000000000400340, cpu addr 0xffffb0d788495340
[ 4.614589] amdgpu 0000:24:00.0: fence driver on ring 7 use gpu addr
0x00000000004003c0, cpu addr 0xffffb0d7884953c0
[ 4.614611] amdgpu 0000:24:00.0: fence driver on ring 8 use gpu addr
0x0000000000400440, cpu addr 0xffffb0d788495440
[ 4.614626] amdgpu 0000:24:00.0: fence driver on ring 9 use gpu addr
0x00000000004004e0, cpu addr 0xffffb0d7884954e0
[ 4.615441] amdgpu 0000:24:00.0: fence driver on ring 10 use gpu addr
0x0000000000400560, cpu addr 0xffffb0d788495560
[ 4.615471] amdgpu 0000:24:00.0: fence driver on ring 11 use gpu addr
0x00000000004005e0, cpu addr 0xffffb0d7884955e0
[ 4.616226] amdgpu 0000:24:00.0: fence driver on ring 12 use gpu addr
0x000000f4002ad420, cpu addr 0xffffb0d78945a420
[ 4.616578] amdgpu 0000:24:00.0: fence driver on ring 13 use gpu addr
0x00000000004006e0, cpu addr 0xffffb0d7884956e0
[ 4.616600] amdgpu 0000:24:00.0: fence driver on ring 14 use gpu addr
0x0000000000400760, cpu addr 0xffffb0d788495760
[ 4.901739] fbcon: amdgpudrmfb (fb0) is primary device
[ 5.116401] amdgpu 0000:24:00.0: fb0: amdgpudrmfb frame buffer device
[ 5.136551] amdgpu 0000:24:00.0: kfd not supported on this ASIC
[ 5.136588] [drm] Initialized amdgpu 3.19.0 20150101 for 0000:24:00.0 on
minor 0
------------------------------------------------------------
It states the RX 550 is on PCI 24:00.0 but in the Xorg.log (attached) you'll
find this:
[ 5.774] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 5.781] (--) PCI:*(0:36:0:0) 1002:699f:1043:0511 rev 199, Mem @
0xe0000000/268435456, 0xf0000000/2097152, 0xfe800000/262144, I/O @
0x0000e000/256, BIOS @ 0x????????/131072
-------------------------------------------------------------
lspci -v
24:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa
PRO [Radeon RX 550] (rev c7) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Lexa PRO [Radeon RX 550]
Flags: bus master, fast devsel, latency 0, IRQ 67
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f0000000 (64-bit, prefetchable) [size=2M]
I/O ports at e000 [size=256]
Memory at fe800000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
Capabilities: [150] Advanced Error Reporting
Capabilities: [200] #15
Capabilities: [270] #19
Capabilities: [2b0] Address Translation Service (ATS)
Capabilities: [2c0] Page Request Interface (PRI)
Capabilities: [2d0] Process Address Space ID (PASID)
Capabilities: [320] Latency Tolerance Reporting
Capabilities: [328] Alternative Routing-ID Interpretation (ARI)
Capabilities: [370] L1 PM Substates
Kernel driver in use: amdgpu
Kernel modules: amdgpu
------------------------------------------------------------------
This looks ok, the gpu is working (otherwise I couldn't type :-)) but only with
llvm:
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 3.9, 128 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.4.0-devel
(git-1eab327ba7)
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 17.4.0-devel (git-1eab327ba7)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.4.0-devel
(git-1eab327ba7)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
------------------------------------------------------------
Attached please find the Xorg.log.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 9869 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 reply other threads:[~2017-11-29 12:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 12:06 bugzilla-daemon [this message]
2017-11-29 14:16 ` [Bug 103968] No Hardware Acceleration with AMD RX 550 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
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@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.