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.
--
Giuseppe "Oblomov" Bilotta
"I weep for our generation" -- Charlie Brown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |