All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34395] New: Evergreen KMS DRM setting 1922x1080 resolution
Date: Thu, 17 Feb 2011 07:10:45 -0800 (PST)	[thread overview]
Message-ID: <bug-34395-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=34395

           Summary: Evergreen KMS DRM setting 1922x1080 resolution
           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: mattr@kde.org


I have an HP Envy 14 with a Radeon HD 5650 and Intel switchable graphics. HDMI
and DisplayPort output are only routed to the Radeon chipset. When initializing
KMS for the Radeon card, I get a 1922x1080 output and the pink line on the left
hand side of the connected monitor, regardless of the port the monitor is
plugged into.

This is very similar to Bug #27452 but the code change made there has no effect
for me, hence this new bug. A quick google search didn't give me any pages that
describe what other info I needed to provide as part of the initial report.
Please let me know what information you need and I'll provide it as soon as
possible.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-02-17 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 15:10 bugzilla-daemon [this message]
2011-02-18  2:50 ` [Bug 34395] Evergreen KMS DRM setting 1922x1080 resolution 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-34395-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.