public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Koschewski <marc@osknowledge.org>
To: "Calin A. Culianu" <calin@ajvar.org>
Cc: ajoshi@shell.unixbox.com, akpm@osdl.org, adaplas@pol.net,
	linux-kernel@vger.kernel.org, linux-nvidia@lists.surfsouth.com,
	Linus Torvalds <torvalds@osdl.org>
Subject: nvidia fb flicker (was: Re: [PATCH] nvidiafb support for 6600 and 6200)
Date: Mon, 28 Nov 2005 11:35:54 +0100	[thread overview]
Message-ID: <20051128103554.GA7071@stiffy.osknowledge.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0511252358390.25302@rtlab.med.cornell.edu>

* Calin A. Culianu <calin@ajvar.org> [2005-11-26 00:02:46 -0500]:

> Hi,
> 
> This patch can be applied against 2.6.15-rc1 to add support to the 
> nvidiafb driver for a few obscure (yet on-the-market) nvidia 
> boards/chipsets, including various versions of the Geforce 6600 and 6200.
> 
> This patch has been tested and allows the above-mentioned boards to get 
> framebuffer console support.
> 
> Thanks!
> 
> -Calin

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'. 

Regards,
	Marc

  parent reply	other threads:[~2005-11-28 10:35 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 ` Marc Koschewski [this message]
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
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=20051128103554.GA7071@stiffy.osknowledge.org \
    --to=marc@osknowledge.org \
    --cc=adaplas@pol.net \
    --cc=ajoshi@shell.unixbox.com \
    --cc=akpm@osdl.org \
    --cc=calin@ajvar.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvidia@lists.surfsouth.com \
    --cc=torvalds@osdl.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