Re: [Linux-fbdev-users] rivafb woes...

[Jurriaan <thu...@xs...>]

From: Saurabh Nanda <na...@ii...>
Date: Thu, Sep 12, 2002 at 08:54:01AM +0530
> Hi,
> Been trying to get my system work with the framebuffer but have some 
> troubles.
> I compiled 2.4.19 with the 
> * VGA Text Console
> * Video Mode Selection Support
> * Support for frame buffer devices
> * nVidia Riva Support
> * VESA VGA Graphics Console
> 
> I have a Riva TNT2 32MB.
> When I try to go into the video mode "314" (or any other mode) I always 
> get /dev/fb0 with the following resolution:
> 
> mode "640x480-60"
>     # D: 25.176 MHz, H: 31.469 kHz, V: 59.942 Hz
>     geometry 640 480 640 480 8
>     timings 39721 40 24 32 11 96 2
>     accel true
>     rgba 8/0,8/0,8/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : nVidia RIVA-VTNT
>     Address     : 0xde000000
>     Size        : 33554432
>     Type        : PACKED PIXELS
>     Visual      : PSEUDOCOLOR
>     XPanStep    : 1
>     YPanStep    : 1
>     YWrapStep   : 0
>     LineLength  : 640
>     MMIO Address: 0xdc000000
>     MMIO Size   : 16777216
>     Accelerator : Unknown (28)
> 
> And /dev/fb1 with the following:
> mode "800x600-75"
>     # D: 48.001 MHz, H: 46.876 kHz, V: 75.121 Hz
>     geometry 800 600 800 600 16
>     timings 20833 96 32 16 4 96 4
>     rgba 5/11,6/5,5/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : VESA VGA
>     Address     : 0xde000000
>     Size        : 33554432
>     Type        : PACKED PIXELS
>     Visual      : TRUECOLOR
>     XPanStep    : 0
>     YPanStep    : 0
>     YWrapStep   : 0
>     LineLength  : 1600
>     Accelerator : No
> 
> I do not understand what is happening.
> I have also attached my dmesg output along with this message.
> 
> rivafb: RIVA MTRR set to ON
> Console: switching to colour frame buffer device 80x30
> rivafb: PCI nVidia NV4 framebuffer ver 0.9.3 (RIVA-VTNT2, 32MB @ 0xDE000000)
> vesafb: abort, cannot reserve video memory at 0xde000000

It looks like you have compiled in both rivafb and vesafb into your
kernel. rivafb starts first, vesafb second and vesafb then complains
rivafb has taken all memory. vesafb then can only use a very low-grade
resolution. Recompile your kernel without vesafb, would be my
suggestion.

Good luck,
Jurriaan

-- 
Remember, Unix on some machines is nUxi.
GNU/Linux 2.4.19-ac4 SMP/ReiserFS 2x1402 bogomips load av: 0.22 1.24 1.49