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 32645] NV20 GF 3 Ti 200, displays blank screen to DVI
Date: Mon,  3 Jan 2011 21:45:48 -0800 (PST)	[thread overview]
Message-ID: <20110104054548.E983313004D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-32645-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

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

--- Comment #16 from Bryan Quigley <BryanQuigley-sfgG/1UML+TQT0dZR+AlfA@public.gmane.org> 2011-01-03 21:45:48 PST ---
It works but has the artifacts on both monitors that I have that are 1440 x 900
and 1600 x 1200 using DVI (with patch).  Using VGA they both work great.

The monitors are fine (I swapped out the GF3 and put in a GF5 for the time
being)
And the Geforce3 works fine with the nvidia driver, no flickering or artifacts.
But the nv driver doesn't work at all with the GF3 DVI setup.

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

  parent reply	other threads:[~2011-01-04  5:45 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-25  5:00 [Bug 32645] New: NV20 GF 3 Ti 200, displays blank screen to DVI bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-32645-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-12-25  5:01   ` [Bug 32645] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-25  5:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-25  5:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-25  5:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-25  5:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-25 13:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-25 21:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-25 22:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-26 23:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-26 23:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-27 10:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-28  2:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-29 13:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-30  3:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-03 19:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-04  5:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2011-01-04 13:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-07  2:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-07  2:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-07  2:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-07  2:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-07  4:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-09 12:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-16 18:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-20 12:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-21  4:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-21 12:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-22  0:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-22  2:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-22  6:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-22 13:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-22 17:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-22 18:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-23 22:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-24  1:01   ` 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=20110104054548.E983313004D@annarchy.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.