From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 48357] New: Display resolutions not detected correctly after startup with VGA over DisplayPort
Date: Thu, 05 Apr 2012 21:12:50 +0000 [thread overview]
Message-ID: <bug-48357-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=48357
Bug #: 48357
Summary: Display resolutions not detected correctly after
startup with VGA over DisplayPort
Classification: Unclassified
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: heroeschman@gmx.de
Created attachment 59545
--> https://bugs.freedesktop.org/attachment.cgi?id=59545
dmesg
Hi.
One of my monitors is a VGA LCD connected over DisplayPort. After startup not
all resolutions are detected but only resolutions up to 1024x768. However if i
disconnect the monitor and reconnect it again (at 287.472381 in the log file)
all screen resolutions are detected correctly.
The initial detection does not work and dmesg shows
"[drm:radeon_dp_i2c_aux_ch], aux i2c too many retries, giving up"
error messages. drm_helper_probe_single_connector_modes() then falls back and
probes some modes up to 1024x768 that is why higher resolutions are missing. No
idea why it works after reconnecting the monitor.
dmesg log is "dmesg | grep drm" with drm.debug=0x0e from a 3.4-rc1 kernel but
the problem already happend in earlier versions. The problem also happens if
only the VGA monitor is connected.
--
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:[~2012-04-05 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 21:12 bugzilla-daemon [this message]
2012-04-05 21:25 ` [Bug 48357] Display resolutions not detected correctly after startup with VGA over DisplayPort bugzilla-daemon
2014-06-28 14:12 ` 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-48357-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;
as well as URLs for NNTP newsgroup(s).