dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90668] vertical stripes/glitches on secondary screen r9 280x
Date: Tue, 26 May 2015 21:50:53 +0000	[thread overview]
Message-ID: <bug-90668-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1954 bytes --]

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

            Bug ID: 90668
           Summary: vertical stripes/glitches on secondary screen r9 280x
           Product: Mesa
           Version: 10.5
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: net@ianni.de
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 116062
  --> https://bugs.freedesktop.org/attachment.cgi?id=116062&action=edit
photo

This is my first bug report here, so I hope i got everything right.

My system is Fedora 22. My GPU is a Sapphire 280x OC. My secondary screen,
connected via dvi, is showing strange vertical stripes, ca 3 cm wide. It seems
like someone cut the actual image in stripes and glued it together slightly
overlapping with flickering borders. 

If I take a screenshot everything looks normal (as it actually should look).

If I use it as the only screen, the stripes are also there.
(Is it a problem with the screen or the dvi connection?) I tried the second dvi
connection with the same result.

Using Windows, the screen has no issues.

output of xrandr:
http://paste.fedoraproject.org/225798/67516614

output of glxinfo:
http://paste.fedoraproject.org/225799/43267525

As mentioned, screenshots show the image as it should be, I had to take a photo
of the screen. I used a text file with the repeated series if numbers from 1 to
7.So one can see where the overlapping I mentioned happens (also in the spacing
of the buttons, missing glyphs etc..)
for example, after the first 1-7 sequence, the 1 and 2 are left out and so on.
I am sorry but I found no better way to show it, except making a video

If you need more information please let me know.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3484 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-05-26 21:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 21:50 bugzilla-daemon [this message]
2015-05-26 21:51 ` [Bug 90668] vertical stripes/glitches on secondary screen r9 280x bugzilla-daemon
2015-05-26 22:13 ` bugzilla-daemon
2015-05-26 22:53 ` bugzilla-daemon
2015-05-26 22:57 ` bugzilla-daemon
2015-05-26 23:01 ` bugzilla-daemon
2015-07-18 11:34 ` [Bug 90668] vertical stripes/glitches on screen connected via dvi in 1680 x 1050 resolution only bugzilla-daemon
2015-07-18 11:37 ` bugzilla-daemon
2015-07-18 11:42 ` bugzilla-daemon
2015-07-18 11:42 ` bugzilla-daemon
2015-07-18 11:43 ` bugzilla-daemon
2015-07-18 11:44 ` bugzilla-daemon
2019-09-25 17:52 ` 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-90668-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