VESA fb problem with 2.6.7-mm[567]

VESA fb problem with 2.6.7-mm[567]

[Ralf Hildebrandt]

The nvidia graphics card in one of my laptops cannot be talked into
working with vesafb:

...
ACPI: PCI Interrupt Link [LNK5] enabled at IRQ 11
ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 11 (level, low) -> IRQ 11
PCI: Cannot allocate resource region 4 of device 0000:00:01.1
PCI: Cannot allocate resource region 5 of device 0000:00:01.1
vesafb: probe of vesafb0 failed with error -6
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
fb0: VGA16 VGA frame buffer device
Simple Boot Flag at 0x36 set to 0x1
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
...

0000:01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go 32M] (rev a3) (prog-if 00 [VGA])
        Subsystem: Hewlett-Packard Company: Unknown device 006d
        Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 11
        Memory at ea000000 (32-bit, non-prefetchable) [size=16M]
        Memory at f8000000 (32-bit, prefetchable) [size=64M]
        Memory at fc000000 (32-bit, prefetchable) [size=512K]
        Capabilities: [60] Power Management version 2
        Capabilities: [44] AGP version 2.0
	
Short:

* vesafb fails
* vga16fb works

The same kernel works on another laptop with another nvidia card.
The only major difference is the unorthodox display resolution in this
laptop (WXGA, 1280x800).

-- 
Ralf Hildebrandt (Im Auftrag des Referat V a)   Ralf.Hildebrandt@charite.de
Charite - Universitätsmedizin Berlin            Tel.  +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin    Fax.  +49 (0)30-450 570-916
IT-Zentrum Standort Campus Mitte                          AIM.  ralfpostfix

Re: VESA fb problem with 2.6.7-mm[567]

[Grzegorz Kulewski]

On Sun, 11 Jul 2004, Ralf Hildebrandt wrote:

> The nvidia graphics card in one of my laptops cannot be talked into
> working with vesafb:

Maybe try vesafb-tng at http://dev.gentoo.org/~spock/ .
This is completly rewritten, better and more correct implementation with 
maany new features. See docs.

It is working for me with nvidia binary drivers for X and vesafb-tng for 
console.

Please report your success / failure to spock.


Grzegorz Kulewski

Another FB Problem (trindentfb)

[Jim Gifford]

I have a simliar issue with the trindentfb, Is anyone maintaining the
trindentfb, so I can work them to resolve this issue???

The trindentfb does respond to the setting of the refresh rate properly. I
have an omnibook XE2, with the cyberblade i/7 video. I need to setup the
trindentfb to 800x600 with a Horizonatal sync of 35.15 and a fresh rate
between 55-65.

These are the settings required for X trident driver also.

Problem has been in all 2.6.x kernels, Just seeing Ralf's message remindend
me. vesafb works.

Re: VESA fb problem with 2.6.7-mm[567]

[Giuseppe Bilotta]

Grzegorz Kulewski wrote:
> On Sun, 11 Jul 2004, Ralf Hildebrandt wrote:
> 
> > The nvidia graphics card in one of my laptops cannot be talked into
> > working with vesafb:
> 
> Maybe try vesafb-tng at http://dev.gentoo.org/~spock/ .
> This is completly rewritten, better and more correct implementation with 
> maany new features. See docs.
> 
> It is working for me with nvidia binary drivers for X and vesafb-tng for 
> console.

vesafb-tng doesn't work with my GeForce2 Go on an Inspiron 8200 
if I set it to use maximu resolution (1600x1200). The screen 
gets all messed up, as if the video mode wasn't set to match 
the use of the framebuffer.

-- 
Giuseppe "Oblomov" Bilotta

Can't you see
It all makes perfect sense
Expressed in dollar and cents
Pounds shillings and pence
                  (Roger Waters)