Skip to contentSkip to conversation

display problem with matroxfb

DISCUSSION Trevor Hemsley 1 participant 1 message Jan 29, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 16 lines · Petr Vandrovec
Quoted 10 lines
Quoted 2 lines

you do not have to specify vesa,pixclock,hslen and vslen, as you leave them on defaults.

Talking of defaults for matroxfb, would you consider limiting the fv:
value default to something reasonable that'll work on all monitors? It took me several recompiles/reboots to get a setting that would not put my monitor into auto-powerdown. If you defaulted to fv:60 then it would work on 99.9% of monitors and then people could override that upwards. I have a Philips 201B 21" monitor and was using

Quoted 5 lines

append="video=matrox:vesa:400"

and this was setting too high a vertical refresh rate for the monitors capabilities. Adding fv:85 lets it work. The card is a Matrox Millennium G200 8MB SDRAM.

Quoted 7 lines

Are you sure that it did not run out of horizontal sync, or something like that? vesa:400 == vesa:0x190 == 1152x864/60Hz... And it powers up in 60Hz, at least here ;-)

See timmings array in drivers/video/matrox/matroxfb_base.c - all videomodes except XXXx400 powerups in fv=60Hz unless you specified fh/fv/pixclock. XXXx400 powerups with fv=70Hz, like standard VGA does.

Looks like one you've already fixed. I've retested and recreated it but it only happens with 2.2.13 not with the other two kernel sources I have (2.2.18 and 2.4.0). I also misinformed you about the way to recreate it, I had specified only append="matrox" in my lilo.conf. It was 2.2.13 that I did my experimentation on to get it to work in the first place and never bothered to retest afterwards. Sorry for the false alarm...

Signature · 6 lines
Trevor Hemsley, Brighton, UK.
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/