From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43481] New: DVI-0 with unknown connection but available modes
Date: Fri, 02 Dec 2011 23:14:51 +0000 [thread overview]
Message-ID: <bug-43481-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=43481
Bug #: 43481
Summary: DVI-0 with unknown connection but available modes
Classification: Unclassified
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: h.judt@gmx.at
This might not be a bug, but a few kernel revisions ago, DVI-0 became active:
xrandr:
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
DVI-0 unknown connection (normal left inverted right x axis y axis)
1024x768 60.0
800x600 60.3
640x480 59.9
512x384 120.0
400x300 120.6
320x240 120.1
LVDS connected 1440x900+0+0 (normal left inverted right x axis y axis) 0mm x
0mm
1440x900 60.0*+
1280x854 59.9
1280x800 59.8
1280x720 59.9
1152x768 59.8
1024x768 59.9
800x600 59.9
848x480 59.7
720x480 59.7
640x480 59.4
VGA-0 disconnected (normal left inverted right x axis y axis)
Hardware: Lenovo Thinkpad T400
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400
Series
What's this DVI-0? LVDS and VGA-0 (when connected) work fine, and DVI-0 does
not hurt, but still I thought I'd report this here in case this shouldn't be as
it is now ;-)
--
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-12-02 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 23:14 bugzilla-daemon [this message]
2011-12-03 0:24 ` [Bug 43481] DVI-0 with unknown connection but available modes bugzilla-daemon
2019-11-19 8: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-43481-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox