public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Giuseppe Bilotta <bilotta78@hotpop.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nvidia fb flicker
Date: Tue, 29 Nov 2005 08:20:17 +0800	[thread overview]
Message-ID: <438B9EC1.2090107@gmail.com> (raw)
In-Reply-To: <1drow6iat7zy8.2rt89nl7eodg.dlg@40tude.net>

Giuseppe Bilotta wrote:
> On Mon, 28 Nov 2005 11:35:54 +0100, Marc Koschewski wrote:
> 
>> * Calin A. Culianu <calin@ajvar.org> [2005-11-26 00:02:46 -0500]:
>>
>>> [12 quoted lines suppressed]
>> Hi all,
>>
>> yesterday I compiled a 2.6.15-rc2 on one of my Inspirons (NVIDIA GeForce2 Go)
>> with nvidiafb. I just changed the fb to some 1600x1200 mode and thus seems to
>> work (the source states GeForce2 Go is supported and known). However, the
>> letters seems to 'flicker' in some way. Uhm, it's not really flickering, it's
>> more like the sinle dots a letter is made of seem to randomly turn on an off. I
>> one takes a closer look it seems like the whole screen is 'fluent' or something.
>> Does anybody know how to handle that? I didn't specify a video mode, but
>> 'video=vesafb:mtrr:3'. 
> 
> Let me guess ... you have a Dell Inspiron 8200 or some such? You must
> compile nvidiafb without support for DDC.
> 
> (Antonio, any news on disabling DDC from the command line? like a
> noddc option or some such?)

Yes, I always forget :-).  Let me see if we can have something that is nicer
(Linus' patch looks good so maybe you can help verify that). See the other
thread.

Tony
 
PS: It's best if you don't trim the cc list.


  reply	other threads:[~2005-11-29  0:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-26  5:02 [PATCH] nvidiafb support for 6600 and 6200 Calin A. Culianu
2005-11-26  6:26 ` Antonino A. Daplas
2005-11-26  6:33   ` Antonino A. Daplas
2005-11-26 21:51   ` Antonino A. Daplas
2005-11-28 10:35 ` nvidia fb flicker (was: Re: [PATCH] nvidiafb support for 6600 and 6200) Marc Koschewski
2005-11-28 12:31   ` nvidia fb flicker Antonino A. Daplas
2005-11-28 13:20     ` Marc Koschewski
2005-11-28 14:00       ` Antonino A. Daplas
2005-11-28 21:24         ` Marc Koschewski
2005-11-28 22:20           ` Antonino A. Daplas
2005-11-28 23:01             ` Linus Torvalds
2005-11-29  0:13               ` Antonino A. Daplas
2005-11-28 19:57   ` Giuseppe Bilotta
2005-11-29  0:20     ` Antonino A. Daplas [this message]
2005-11-29  9:08     ` Marc Koschewski

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=438B9EC1.2090107@gmail.com \
    --to=adaplas@gmail.com \
    --cc=bilotta78@hotpop.com \
    --cc=linux-kernel@vger.kernel.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