From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94249] Linux incorrectly detects a Radeon GPU
Date: Mon, 22 Feb 2016 15:58:25 +0000 [thread overview]
Message-ID: <bug-94249-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1384 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94249
Bug ID: 94249
Summary: Linux incorrectly detects a Radeon GPU
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: krejzi@email.com
I've recently got a HP Probook 470 G3 laptop, which has an onboard Intel
Skylake Graphics and an AMD Radeon R7 M340 GPU.
However, the Linux seems to detect the GPU as following:
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Topaz
XT [Radeon R7 M260/M265] [1002:6900] (rev 83)
Which makes it a GCN 1.2 GPU which tries to use AMDGPU. That of course doesn't
work. The driver loads, but as soon as it does, it corrupts all the available
data from lspci -v output. I also can't use it with DRI_PRIME, since X server
crashes while loading amdgpu (probably due to it not being an amdgpu supported
GPU).
Wikipedia identifies the mentioned card as GCN 1.0 OLAND GPU. Windows catalyst
also claims it's R7 M340 and not R7 M360.
It's probably a BIOS issue, but can it be worked around somehow?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2602 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:[~2016-02-22 15:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 15:58 bugzilla-daemon [this message]
2016-02-22 16:15 ` [Bug 94249] Topaz GPU not working correctly bugzilla-daemon
2016-03-01 15:31 ` bugzilla-daemon
2016-04-14 16:31 ` bugzilla-daemon
2016-07-29 6:35 ` bugzilla-daemon
2016-07-29 14:28 ` bugzilla-daemon
2016-07-29 14:30 ` bugzilla-daemon
2016-07-29 14:31 ` bugzilla-daemon
2016-07-29 14:32 ` bugzilla-daemon
2016-07-29 14:34 ` bugzilla-daemon
2016-07-30 15:04 ` bugzilla-daemon
2016-08-02 9:33 ` bugzilla-daemon
2016-08-02 9:37 ` bugzilla-daemon
2016-08-02 9:44 ` [Bug 94249] libdrm_amdgpu: Crash when built with clang bugzilla-daemon
2016-08-02 9:49 ` bugzilla-daemon
2016-08-02 10:04 ` bugzilla-daemon
2016-08-03 9:38 ` 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-94249-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;
as well as URLs for NNTP newsgroup(s).