All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 13865] New: DVI corruption with RandR 1.2
Date: Sun, 30 Dec 2007 11:16:57 -0800 (PST)	[thread overview]
Message-ID: <bug-13865-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=13865

           Summary: DVI corruption with RandR 1.2
           Product: xorg
           Version: 7.3
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: drzeus-bugzilla-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


When I'm using my Geforce 7300 GT and a DVI monitor, the bottom 10 lines or so
occasionally fill up with garbage. The data comes from other parts of the
screen, so it's not completely random but rather some kind of transfer error.

I'm using the RandR 1.2 code as the DVI port refuses to work correctly with my
monitor with the old stuff.


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

             reply	other threads:[~2007-12-30 19:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-30 19:16 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-13865-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2007-12-31 13:31   ` [Bug 13865] DVI corruption with RandR 1.2 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-12-31 14:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-12-31 14:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-01 14:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-01 14:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-01 16:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-01 16:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-01 16:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-01 18:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-06  1:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-15 11:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-13865-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.