From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98751] New: radeon: multihead "no signal" on one of the monitors - regression
Date: Thu, 21 May 2015 20:35:50 +0000 [thread overview]
Message-ID: <bug-98751-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=98751
Bug ID: 98751
Summary: radeon: multihead "no signal" on one of the monitors -
regression
Product: Drivers
Version: 2.5
Kernel Version: 4.0.3+
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: mikkeloscar@gmail.com
Regression: No
Since this commit:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=d5c3b64
one of my two monitors doesn't get a signal (it just says "no signal").
The monitors are connected to a Radeon HD 6990 card. One is connected through
HDMI and one through DVI. I'm using the radeon driver.
Most of the time it is the monitor connected through HDMI which doesn't get a
signal, but I was able to switch it around somehow by messing around with
screen orientation in X (not quite sure how to replicate or if it's even
relevant).
I tried to revert the commit in kernel 4.0.4 (latest I tried) and that solves
the problem for me.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-05-21 20:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 20:35 bugzilla-daemon [this message]
2015-05-21 20:36 ` [Bug 98751] radeon: multihead "no signal" on one of the monitors - regression bugzilla-daemon
2015-05-21 20:53 ` bugzilla-daemon
2015-05-21 20:58 ` bugzilla-daemon
2015-05-21 20:59 ` bugzilla-daemon
2015-05-21 23:58 ` bugzilla-daemon
2015-05-21 23:59 ` bugzilla-daemon
2015-05-21 23:59 ` bugzilla-daemon
2015-05-25 10:22 ` bugzilla-daemon
2015-05-25 10:29 ` bugzilla-daemon
2015-05-25 11:16 ` bugzilla-daemon
2015-05-26 22:05 ` bugzilla-daemon
2015-05-26 22:39 ` bugzilla-daemon
2015-05-27 0:15 ` bugzilla-daemon
2015-05-27 9:46 ` bugzilla-daemon
2015-05-27 11:19 ` bugzilla-daemon
2015-05-27 11:24 ` bugzilla-daemon
2015-05-27 13:49 ` bugzilla-daemon
2015-05-27 15:26 ` bugzilla-daemon
2015-05-27 15:26 ` bugzilla-daemon
2015-06-14 11:38 ` bugzilla-daemon
2015-06-14 11:39 ` bugzilla-daemon
2015-06-14 12:23 ` 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-98751-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;
as well as URLs for NNTP newsgroup(s).