All of lore.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: Blanky rivafb vs snowy nvidiafb with 2.6.12
Date: Thu, 29 Sep 2005 20:39:18 +0800	[thread overview]
Message-ID: <433BE076.50404@gmail.com> (raw)
In-Reply-To: <1gie1vr78iijd$.qcvoypipyouu.dlg@40tude.net>

Giuseppe Bilotta wrote:
> On Thu, 29 Sep 2005 05:01:15 +0800, Antonino A. Daplas wrote:
> 
>> Giuseppe Bilotta wrote:
>>> Hello all,
>>>
>>> * I have thus tried the new nvidiafb driver, which seems to work ok,
>>> except for the minor detail that the display is extremely snowy.
>>> Attempts to change the timing options with fbset fail: fbset seems to
>>> accept the settings, no error message is given, but nothing is
>>> changed. The X nv driver select the correct timings, so I tried
>>> modeline2fb to make fbset use those, but still nothing changes.
>>>
>> What's the dmesg output?
> 
> """
> nvidiafb: nVidia device/chipset 10DE0112
> nvidiafb: nVidia Corporation NV11 [GeForce2 Go]
> nvidiafb: EDID found from BUS2
> nvidiafb: CRTC 1 is currently programmed for DFP
> nvidiafb: Using DFP on CRTC 1
> Panel size is 1600 x 1200
> nvidiafb: MTRR set to ON
> Console: switching to colour frame buffer device 200x75
> nvidiafb: PCI nVidia NV11 framebuffer (32MB @ 0xE0000000) 
> """
> 
> (do you need more?)
> 
>>  What's fbset -i output?
> 
> Right after modprobing nvidiafb:
> 
> """
> mode "1600x1200-61"
>     # D: 160.000 MHz, H: 75.758 kHz, V: 60.606 Hz
>     geometry 1600 1200 1600 20889 8
>     timings 6250 256 64 46 1 192 3
>     accel true
>     rgba 8/0,8/0,8/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : NV11
>     Address     : 0xe0000000
>     Size        : 33554432
>     Type        : PACKED PIXELS
>     Visual      : PSEUDOCOLOR
>     XPanStep    : 8
>     YPanStep    : 1
>     YWrapStep   : 0
>     LineLength  : 1600
>     MMIO Address: 0xfc000000
>     MMIO Size   : 16777216
>     Accelerator : Unknown (43)  
> """
> 
> After trying fbset "1600x1200":
> 
> """
> mode "1600x1200-61"
>     # D: 160.000 MHz, H: 75.758 kHz, V: 60.606 Hz
>     geometry 1600 1200 1920 17408 8
>     timings 6250 256 64 46 1 192 3
>     accel true
>     rgba 8/0,8/0,8/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : NV11
>     Address     : 0xe0000000
>     Size        : 33554432
>     Type        : PACKED PIXELS
>     Visual      : PSEUDOCOLOR
>     XPanStep    : 8
>     YPanStep    : 1
>     YWrapStep   : 0
>     LineLength  : 1920
>     MMIO Address: 0xfc000000
>     MMIO Size   : 16777216
>     Accelerator : Unknown (43)  
> """
> 
> The "1600x1200" mode is:
> 
> """
> mode "1600x1200"
>   geometry   1600 1200   1920 17467   8
>   timings    6172   304 64   46 1   192 3
>   hsync high
>   vsync high
> endmode 
> """
> 
> So as you can see the problem is that the timings are NOT set by
> fbset. No error messages or anything.
> 
>> Can you try doing fbset -accel false and see if it makes a difference?
> 
> Nope, same thing. Also with modprobe nvidiafb noaccel=1.
> 


  reply	other threads:[~2005-09-29 12:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 14:12 Blanky rivafb vs snowy nvidiafb with 2.6.12 Giuseppe Bilotta
2005-09-28 21:01 ` Antonino A. Daplas
2005-09-29 11:41   ` Giuseppe Bilotta
2005-09-29 12:39     ` Antonino A. Daplas [this message]
2005-09-29 12:40     ` Antonino A. Daplas
2005-09-29 15:43       ` Giuseppe Bilotta
2005-09-29 20:47         ` Antonino A. Daplas
2005-09-30  8:53           ` Giuseppe Bilotta
2005-10-01  5:49             ` Antonino A. Daplas
2005-10-01  7:07               ` Giuseppe Bilotta
2005-10-01 10:49                 ` Antonino A. Daplas
2005-10-02 15:13                   ` Giuseppe Bilotta

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=433BE076.50404@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 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.