I've tested the parameters you gave to me, with no success : all is right with
vesafb and wrong with matroxfb. vesa:0x105 does not work, the monitor is out of
sync (I've tried 0x305 too).
Here are parts of the syslog at system boot for matroxfb and vesafb :
matroxfb: Matrox Mystique (PCI) detected
matroxfb: MTRR's turned on
matroxfb: 640x480x8bpp (virtual: 640x13075)
matroxfb: framebuffer at 0xE7000000, mapped to 0xc8805000, size 8388608
Console: switching to colour frame buffer device 80x30
fb0: MATROX VGA frame buffer device
vesafb: framebuffer at 0xe7000000, mapped to 0xc8000000, size 8192k
vesafb: mode is 640x480x8, linelength=640, pages=11
vesafb: protected mode interface info at c000:7820
vesafb: scrolling: redraw
Console: switching to colour frame buffer device 80x30
fb0: VESA VGA frame buffer device
After booting and having the display shifted to the middle of the screen, I've
played a bit with fbset and the -left, -right, -move, -match options. After a
while I got an 'acceptable' picture (some pixels missing on the left). At this
point, fbset -s give me the following :
mode "640x480-60"
# D: 25.176 MHz, H: 31.628 kHz, V: 60.243 Hz
geometry 640 480 640 480 8
timings 39721 50 10 32 11 96 2
accel true
rgba 8/0,8/0,8/0,0/0
endmode
I've replaced these values in /etc/fb.modes instead of the original values and
after login in the system, entering 'fbset -match -a' set the virtual consoles
correctly.
How can I pass the parameters at boot time ?
I've tried :
video=matrox:vesa:0x301,pixclock:39721,left:50,right:10,upper:32,lower:11,hslen:96,vslen:2
... without any success...
-- Regards Jean-Luc - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/