From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106597] [vga_switcheroo] commit 07f4f97d7b4bf325d9f558c5b58230387e4e57e0 breaks dpm on Alienware 15R3
Date: Mon, 21 May 2018 21:47:32 +0000 [thread overview]
Message-ID: <bug-106597-502-5bzJPt44LB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106597-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1054 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106597
--- Comment #5 from Lukas Wunner <lukas@wunner.de> ---
Ok I found this dmesg ouput of a 4.17 kernel...
https://bugs.freedesktop.org/attachment.cgi?id=139668
However the HDA device 0000:01:00.1 is not enumerated! It *is* enumerated in
the 4.16 dmesg output you've attached. What gives?
We know there are Nvidia GPUs which hide the HDA controller if no external
display is attached:
https://bugs.freedesktop.org/show_bug.cgi?id=75985
Maybe something like that is going on here despite this being an AMD GPU?
Also, there are Dell machines which can be switched to one of two modes in the
BIOS: In one mode, audio is streamed to external displays via the Intel HDA, in
the other mode, it's streamed via the AMD HDA. In the former mode, the AMD HDA
serves no purpose and should thus be hidden as per this patch:
https://lkml.org/lkml/2018/4/20/244
It's possible that something similar is needed here.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2195 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:[~2018-05-21 21:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 20:36 [Bug 106597] [vga_switcheroo] commit 07f4f97d7b4bf325d9f558c5b58230387e4e57e0 breaks dpm on Alienware 15R3 bugzilla-daemon
2018-05-21 20:59 ` bugzilla-daemon
2018-05-21 21:17 ` bugzilla-daemon
2018-05-21 21:26 ` bugzilla-daemon
2018-05-21 21:34 ` bugzilla-daemon
2018-05-21 21:47 ` bugzilla-daemon [this message]
2018-05-21 22:03 ` bugzilla-daemon
2018-05-21 22:43 ` bugzilla-daemon
2018-05-22 8:16 ` bugzilla-daemon
2018-05-22 8:18 ` bugzilla-daemon
2018-05-22 8:19 ` bugzilla-daemon
2018-05-22 8:22 ` bugzilla-daemon
2018-05-22 9:03 ` bugzilla-daemon
2018-05-22 20:40 ` bugzilla-daemon
2018-05-22 21:18 ` bugzilla-daemon
2018-05-22 21:49 ` bugzilla-daemon
2018-05-23 6:54 ` bugzilla-daemon
2018-05-23 9:59 ` bugzilla-daemon
2018-05-23 10:21 ` bugzilla-daemon
2018-05-23 12:19 ` bugzilla-daemon
2018-05-23 23:12 ` bugzilla-daemon
2018-05-24 8:56 ` bugzilla-daemon
2018-05-24 10:01 ` bugzilla-daemon
2018-05-24 10:04 ` bugzilla-daemon
2018-05-24 10:13 ` bugzilla-daemon
2018-05-24 10:28 ` bugzilla-daemon
2018-05-24 13:07 ` bugzilla-daemon
2018-05-24 15:34 ` bugzilla-daemon
2018-05-24 15:43 ` bugzilla-daemon
2018-05-24 16:15 ` bugzilla-daemon
2018-05-24 16:40 ` bugzilla-daemon
2018-05-24 16:40 ` bugzilla-daemon
2018-05-24 17:18 ` bugzilla-daemon
2018-05-24 17:42 ` bugzilla-daemon
2018-05-24 21:08 ` 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-106597-502-5bzJPt44LB@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