All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41418] New: [RV350] Screen corruption with certain resolutions on LVDS (scaled)
Date: Mon,  3 Oct 2011 07:40:12 -0700 (PDT)	[thread overview]
Message-ID: <bug-41418-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [RV350] Screen corruption with certain resolutions on
                    LVDS (scaled)
           Product: DRI
           Version: unspecified
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: dev@karlchenofhell.org


I'm getting a screen corruption with the resolutions
  1400x1050
  1440x900
on a RV350, using kernel-3.0.4, libdrm-2.4.26.

A photograph of the corrupted screen under X is attached, though the corruption
also appears using tests/modetest w/o X started.

--------
# lspci -nns1:0.0
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M10 NT [FireGL
Mobility T2] [1002:4e54] (rev 80)
--------

-- 
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-10-03 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 14:40 bugzilla-daemon [this message]
2011-10-03 14:42 ` [Bug 41418] [RV350] Screen corruption with certain resolutions on LVDS (scaled) bugzilla-daemon
2011-10-03 14:45 ` bugzilla-daemon
2011-10-03 14:46 ` bugzilla-daemon
2011-10-03 15:36 ` bugzilla-daemon
2011-10-03 15:42 ` bugzilla-daemon
2011-10-04 13:43 ` bugzilla-daemon
2011-10-05 18:40 ` bugzilla-daemon
2019-11-19  8:21 ` 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-41418-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.