public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Koschewski <marc@osknowledge.org>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Marc Koschewski <marc@osknowledge.org>,
	"Calin A. Culianu" <calin@ajvar.org>,
	akpm@osdl.org, adaplas@pol.net, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: nvidia fb flicker
Date: Mon, 28 Nov 2005 14:20:35 +0100	[thread overview]
Message-ID: <20051128132035.GA7265@stiffy.osknowledge.org> (raw)
In-Reply-To: <438AF8A2.6030403@gmail.com>

* Antonino A. Daplas <adaplas@gmail.com> [2005-11-28 20:31:30 +0800]:

> Marc Koschewski wrote:
> > * 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
> 
> Can you try booting with video=nvidiafb:1600x1200MR@60?
> 
> If that still does not work, can you open drivers/video/fbmon.c then change
> the line #undef DEBUG to #define DEBUG, recompile, reboot and post your
> dmesg?
> 
> > 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'. 
> > 
> 
> No, remove any vga= and video=vesafb: strings in your boot options.

So, I just booted with the parameter given by you (and without vga= as usual), as
well as without any parameter. No change though.

Here's my relevant messages stuff with DEBUG enabled:

Nov 28 14:02:31 stiffy kernel: nvidiafb: nVidia device/chipset 10DE0112
Nov 28 14:02:31 stiffy kernel: nvidiafb: EDID found from BUS2
Nov 28 14:02:31 stiffy kernel: ========================================
Nov 28 14:02:31 stiffy kernel: Display Information (EDID)
Nov 28 14:02:31 stiffy kernel: ========================================
Nov 28 14:02:31 stiffy kernel:    EDID Version 1.3
Nov 28 14:02:31 stiffy kernel:    Manufacturer: SHP
Nov 28 14:02:31 stiffy kernel:    Model: 138e
Nov 28 14:02:31 stiffy kernel:    Serial#: 0
Nov 28 14:02:31 stiffy kernel:    Year: 1990 Week 0
Nov 28 14:02:31 stiffy kernel:    Display Characteristics:
Nov 28 14:02:32 stiffy kernel:       Monitor Operating Limits:    Detailed Timings
Nov 28 14:02:32 stiffy kernel:       160 MHz 1600 1664 1856 2112 1200 1201 1204 1250 -HSync -VSync
Nov 28 14:02:32 stiffy kernel: 
Nov 28 14:02:32 stiffy kernel:    Supported VESA Modes
Nov 28 14:02:32 stiffy kernel:       Manufacturer's mask: 0
Nov 28 14:02:32 stiffy kernel:    Standard Timings
Nov 28 14:02:32 stiffy kernel:       1600x1200@60Hz
Nov 28 14:02:32 stiffy kernel: Extrapolated
Nov 28 14:02:32 stiffy kernel:            H: 75-75KHz V: 60-60Hz DCLK: 162MHz
Nov 28 14:02:32 stiffy kernel:       Digital Display Input

Marc

  reply	other threads:[~2005-11-28 13: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 [this message]
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=20051128132035.GA7265@stiffy.osknowledge.org \
    --to=marc@osknowledge.org \
    --cc=adaplas@gmail.com \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=calin@ajvar.org \
    --cc=linux-kernel@vger.kernel.org \
    --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