From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107049] monitor not found in 4.17+ kernel
Date: Wed, 27 Jun 2018 10:16:04 +0000 [thread overview]
Message-ID: <bug-107049-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107049
Bug ID: 107049
Summary: monitor not found in 4.17+ kernel
Product: DRI
Version: unspecified
Hardware: PowerPC
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: dan@danny.cz
CC: bcrocker@redhat.com
When booting kernel 4.17 or 4.18-pre on Power9 machine with Radeon Pro WX 4100
I get no output on a monitor connected thru DisplayPort, the monitor is not
detected by the driver and a "PowerPlay" error appears in the kernel log. When
booting 4.16 kernel (kernel-4.16.16-300.fc28.ppc64le), all is OK. See attached
dmesg (resp. journalctl -k -b) outputs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2297 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:[~2018-06-27 10:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 10:16 bugzilla-daemon [this message]
2018-06-27 10:17 ` [Bug 107049] monitor not found in 4.17+ kernel bugzilla-daemon
2018-06-27 10:19 ` bugzilla-daemon
2018-06-27 10:24 ` bugzilla-daemon
2018-06-27 10:51 ` bugzilla-daemon
2018-06-27 11:14 ` bugzilla-daemon
2018-06-27 14:33 ` bugzilla-daemon
2018-06-27 14:44 ` bugzilla-daemon
2018-06-27 14:46 ` bugzilla-daemon
2019-05-02 6:18 ` bugzilla-daemon
2019-05-04 13:04 ` bugzilla-daemon
2019-05-06 8:52 ` 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-107049-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.