Most recent kernel where this bug did not occur: 2.6.13.3 Distribution: Slackware 10.2 Hardware Environment: Matrox Millenium G200 Problem Description: Matrox framebuffer failed to start. Module insert in rc.modules script: /sbin/modprobe matroxfb_base xres=800 yres=600 upper=21 lower=1 vslen=3 left=160 right=16 hslen=80 pixclock=20203 depth=24 /sbin/modprobe fbcon /sbin/modprobe mga Logs looks like ok, but framebuffer console failed to display anything. This works ok with 2.6.13.3 kernel, but fails in 2.6.13.4
No changes in the framebuffer layer from 2.6.14.3 to 2.6.14.4. Anyway, can you post your dmesg, cat /proc/fb, and fbset -i?
cat cat_proc_fb: 0 MATROX dmesg part: matroxfb: Matrox Millennium G200 (AGP) detected matroxfb: MTRR's turned on matroxfb: 832x600x24bpp (virtual: 832x3360) matroxfb: framebuffer at 0xE7000000, mapped to 0xd0a00000, size 8388608 fb0: MATROX frame buffer device fb0: initializing hardware fbset -i: mode "832x600-73" # D: 49.498 MHz, H: 45.494 kHz, V: 72.791 Hz geometry 832 600 832 3360 24 timings 20203 160 16 21 1 80 3 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name : MATROX Address : 0xe7000000 Size : 8388608 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 8 YPanStep : 1 YWrapStep : 0 LineLength : 2496 MMIO Address: 0xe4000000 MMIO Size : 16384 Accelerator : Matrox G200 (Millennium, Mystique)
There is no bug. I've just forget to compile framebuffer console support.