rivafb still broken in 2.6.0-test2?

Hi,

I'm trying to get rivafb working with a GeForce 4 MX 440 and 2.6.0-test2. The penguin logo and the cursor are displayed correctly, but the rest of the screen is garbage (I assume I can find a more verbose graphical description for the garbage if it is helpful :)).

The original problem was encountered on a UP kernel running ACPI, local APIC and MTRR support, but removing these features didn't help.

This is what rivafb has to say:

rivafb: nVidia device/chipset 10DE0171
rivafb: Detected CRTC controller 0 being used
rivafb: PCI nVidia NV20 framebuffer ver 0.9.5b (nVidiaGeForce4-M, 64MB @ 0xD0000000)
Console: switching to colour frame buffer device 80x30

with MTRR enabled, it's:

rivafb: nVidia device/chipset 10DE0171
rivafb: Detected CRTC controller 0 being used
rivafb: RIVA MTRR set to ON
rivafb: PCI nVidia NV20 framebuffer ver 0.9.5b (nVidiaGeForce4-M, 64MB @ 0xD0000000)
Console: switching to colour frame buffer device 80x30

but gives the same result. Is this supposed to work?

ciao,

[*Thomas  Themel*] "That doesn't make it bad, but it's also not
[extended contact]  spectacular nerd porn."
[info provided in] 	- ExtremeTech review of IA-64
[*message header*]	

Not sure about the GeForce4's, but I can attest that rivafb works fine under -test1 and -test2 on my GeForce2:

rivafb: nVidia device/chipset 10DE0150
rivafb: RIVA MTRR set to ON
rivafb: PCI nVidia NV10 framebuffer ver 0.9.5b (nVidiaGeForce2-G, 32MB @ 0xE8000000)
Console: switching to colour frame buffer device 128x48

I'm running on SMP, and don't have ACPI enabled. MTRR support also works fine for me.

The problem you have seems isolated to your board/chip.