From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41366] New: HDMI on a Fusion board only comes up when LVDS is already enabled
Date: Fri, 30 Sep 2011 10:12:20 -0700 (PDT) [thread overview]
Message-ID: <bug-41366-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=41366
Summary: HDMI on a Fusion board only comes up when LVDS is
already enabled
Product: DRI
Version: XOrg CVS
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: simon.farnsworth@onelan.co.uk
I'm running airlied's drm-fixes, git revision
fdfc61594e6de21c23f955818ef78bcab9bafe40, and experiencing "interesting" times
trying to get HDMI to work on a Fusion GPU (detected by X as [ 49.876] (--)
RADEON(0): Chipset: "AMD Radeon HD 6310 Graphics" (ChipID = 0x9802)).
If I run:
xrandr --output HDMI-0 --off
xrandr --output LVDS --auto
xrandr --output HDMI-0 --mode 1920x1200
the HDMI monitor comes up at 1920x1200
If I run:
xrandr --output HDMI-0 --off
xrandr --output LVDS --off
xrandr --output HDMI-0 --mode 1920x1200
the HDMI monitor immediately enters DPMS Off state, and stays there.
I've confirmed with "grep . /sys/class/drm/card0-HDMI-A-1/*" that the kernel
thinks the HDMI connector is switched on. The only difference I can see is that
HDMI works when it gets CRTC 1, but not when it gets CRTC 0.
I have captured logs from the kernel with drm.debug=0x6 during the runs, in
case that explains what's going on; I will attach them to this bug.
--
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:[~2011-09-30 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 17:12 bugzilla-daemon [this message]
2011-09-30 17:13 ` [Bug 41366] HDMI on a Fusion board only comes up when LVDS is already enabled bugzilla-daemon
2011-09-30 17:13 ` bugzilla-daemon
2011-09-30 17:14 ` [Bug 41366] [r600 KMS] " bugzilla-daemon
2011-10-05 22:08 ` bugzilla-daemon
2011-10-05 22:35 ` bugzilla-daemon
2011-10-06 10:10 ` bugzilla-daemon
2012-01-12 22:46 ` bugzilla-daemon
2019-11-19 8:20 ` 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-41366-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.