From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29941] New: radeon/KMS: Screen hotplugging does not work any more
Date: Wed, 1 Sep 2010 09:32:09 -0700 (PDT) [thread overview]
Message-ID: <bug-29941-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29941
Summary: radeon/KMS: Screen hotplugging does not work any more
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: direx@betriebsdirektor.de
I noticed that in recent kernel versions the runtime detection of newly added
monitors does not work properly.
When I plug in my TV (DVI2HDMI) after booting I cannot enable it. xrandr
correctly shows a new screen and I can even enable the output, but the TV
screen stays black. Restarting X does not help.
The driver also seems to recognize the port status after plugging it in
(/sys/class/drm/card0-DVI-I-2/status) changes from "disconnected" to
"connected".
When I plug the HDMI cable in _before_ booting my computer the TV works just
fine.
GFX: Radeon HD 3870
Linux: 2.6-git (issue appeared in 2.6.35) with KMS
Mesa: git
libdrm: git
xf86-video-ati: git
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-09-01 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 16:32 bugzilla-daemon [this message]
2010-09-01 16:36 ` [Bug 29941] radeon/KMS: Screen hotplugging does not work any more bugzilla-daemon
2010-09-01 17:37 ` bugzilla-daemon
2010-09-01 17:37 ` bugzilla-daemon
2010-09-01 17:39 ` bugzilla-daemon
2010-09-01 18:45 ` bugzilla-daemon
2010-09-02 18:29 ` [Bug 29941] radeon/KMS: Screen hotplugging does not work bugzilla-daemon
2010-09-02 18:37 ` bugzilla-daemon
2019-11-19 8:15 ` 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-29941-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.