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 54587] [NV1F] Flickering screen on Geforece 4
Date: Sat, 08 Feb 2014 20:57:44 +0000	[thread overview]
Message-ID: <bug-54587-8800-WTDPC3sGoM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-54587-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #27 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to comment #26)
> I noticed that traffic with hard disk causes big interference! Even when
> nothing changes in the screen.

This makes it really sound like you're having analog isolation issues. Does
your VGA cable have a ferrite core on it? (Here's an image of what I'm talking
about:
http://image.made-in-china.com/2f1j00cSjErnoMZtkg/VGA-Computer-Monitor-Cable-with-Ferrite-Cores-Hdb15m-Hdb15m.jpg
-- the things on the cable that aren't the connector itself.)

Did you not see these issues with the nvidia binary driver? That'd be very
surprising...

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-02-08 20:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  9:00 [Bug 54587] New: Flickering screen on Geforece 4 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-54587-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-09-06 17:45   ` [Bug 54587] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-07 12:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-07 12:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-07 12:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-07 13:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-07 19:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-08  9:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-08 13:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09  5:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09  5:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09  5:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09  5:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09  5:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 10:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 21:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-10 11:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-02 18:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-06 11:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-07 11:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05  8:24   ` [Bug 54587] [NV1F] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08  8:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08  8:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08  8:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08  8:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08  9:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 13:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 15:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 20:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-02-09  8:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-09  8:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-09  8:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-10 12:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-10 12:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-17  1:34   ` [Bug 54587] [NV1F] Flickering screen on Geforce 4 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-03  4:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-03  4:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:29   ` 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-54587-8800-WTDPC3sGoM@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.