Bug#293430: matrox frame buffer console: mode switching broken
Package: kernel-image-2.6.8-2-386
Version: 2.6.8-13
When using the Matrox frame buffer driver and switching between consoles
of different resolution, the mode timings get messed up.
How to reproduce the problem:
- if you are still in text mode, load the framebuffer modules:
# modprobe matroxfb_base; modprobe fbcon
- set a higher resolution mode on the first console only
(this is my custom mode, I will show the timings below)
# fbset 1024x640-85
# fbset
mode "1024x640-85"
# D: 77.682 MHz, H: 57.119 kHz, V: 84.999 Hz
geometry 1024 640 1024 1600 8
timings 12873 168 56 28 1 112 3
accel true
rgba 8/0,8/0,8/0,0/0
endmode
- switch to another console: press <Alt>+<F2>
- switch back to console 1: press <Alt>+<F1>
- you will see the following output:
matroxfb: cannot set xres to 1400, rounded up to 1664
matroxfb: cannot set xres to 1400, rounded up to 1664
matroxfb: cannot set xres to 1400, rounded up to 1664
matroxfb: cannot set xres to 1600, rounded up to 1664
matroxfb: cannot set xres to 1600, rounded up to 1664
matroxfb: cannot set xres to 1600, rounded up to 1664
matroxfb: cannot set xres to 1600, rounded up to 1664
matroxfb: cannot set xres to 1800, rounded up to 1920
matroxfb: cannot set xres to 1800, rounded up to 1920
- The image looks interlaced, and indeed it is.
The timings and geometry have also changed:
# fbset
mode "1024x768-87"
# D: 44.901 MHz, H: 35.523 kHz, V: 86.960 Hz
geometry 1024 768 1024 768 8
timings 22271 56 24 33 8 160 8
laced true
accel true
rgba 8/0,8/0,8/0,0/0
endmode
This bug is fixed in kernel-image-2.6.10-1-386, Version 2.6.10-4. It
would be nice to have the fix in 2.6.8 too, which is supposed to ship
with sarge.
Mirko
Reply to: