From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75401] New: vgaswtitcheroo doesn't work for AMD Radeon 8870m (possibly due to "wrong" PCI class)
Date: Sat, 03 May 2014 17:26:49 +0000 [thread overview]
Message-ID: <bug-75401-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=75401
Bug ID: 75401
Summary: vgaswtitcheroo doesn't work for AMD Radeon 8870m
(possibly due to "wrong" PCI class)
Product: Drivers
Version: 2.5
Kernel Version: 3.11.10
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: drill87@gmail.com
Regression: No
I've got Samsung 870Z5E notebook equipped with AMD Radeon 8870m video card (and
Intel HD 4000 graphics). I always failed to use vgaswitcheroo to disable the
discrete card -- there wasn't even its entry in debugfs.
After a little investigetion of radeon module's source code I found, that the
problem happens, possibly, due to "unusual" PCI class of my Radeon 8870m.
According to command "lspci -nn" Radeon 8870m has PCI class id 0380, which is
corresponds to PCI_CLASS_DISPLAY_OTHER (in pci_ids.h). On the other hand, when
radeon module check number of videocards, it excepts them to have class
PCI_CLASS_DISPLAY_VGA (0300). Thus module concludes that I have only 1
videocard (Intel HD, which has 0300 class id) and decides, that there's no need
for vgaswitcheroo to be initialized.
I tried to edit radeon kernel module by adding additional checks for
PCI_CLASS_DISPLAY_OTHER class id (in 2 places). After that vgaswitcheroo
started to work -- the entry appeared in debugfs and I could disable the
discrete graphics card. Though I'm not sure if everything went right because I
failed to use radeon card for actual rendering through DRI PRIME even in the
newest kernel stable version (3.14.2) -- X server crashes even if I try to
issues glxinfo command.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-05-03 17:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 17:26 bugzilla-daemon [this message]
2014-05-03 17:29 ` [Bug 75401] vgaswtitcheroo doesn't work for AMD Radeon 8870m (possibly due to "wrong" PCI class) bugzilla-daemon
2014-05-04 4:24 ` [Bug 75401] vgaswitcheroo " bugzilla-daemon
2014-05-05 14:07 ` bugzilla-daemon
2014-05-06 4:36 ` bugzilla-daemon
2014-05-06 13:09 ` bugzilla-daemon
2014-05-09 6:14 ` bugzilla-daemon
2014-05-09 6:15 ` bugzilla-daemon
2014-05-09 12:44 ` bugzilla-daemon
2014-05-09 13:05 ` bugzilla-daemon
2014-05-09 13:53 ` bugzilla-daemon
2014-05-09 13:54 ` bugzilla-daemon
2014-05-09 14:35 ` bugzilla-daemon
2014-05-18 20:02 ` bugzilla-daemon
2014-05-19 2:04 ` bugzilla-daemon
2014-05-26 8:42 ` bugzilla-daemon
2014-05-26 8: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-75401-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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