On Mon, 18 May 2009 15:29:03 +0200 (CEST)
Werner LEMBERG [off-list ref] wrote:

quoted

What I see here is that for 2.6.27 you use the VESA framebuffer
while you do not use it for the 2.6.28

Compare your configs:
2.6.27 : CONFIG_FB_VESA=y
2.6.28: # CONFIG_FB_VESA is not set

This is intentional.  Reason is that in 2.6.28 option
`CONFIG_FB_BOOT_VESA_SUPPORT' has been added, and it seems that this
change introduced a bug.

quoted

My advice is try using the Intel framebuffer (change it to Y not 'M'
like module).  It should be faster than VESA on your hardware.
Unselect VESA.

I'm doing a git bisect right now to find out why
CONFIG_FB_BOOT_VESA_SUPPORT doesn't work as advertised.

Probably, it does work as supposed to. The CONFIG_FB_BOOT_VESA_SUPPORT
tells Linux to allow VESA modes values for the "vga=" switch. It also switches
on the VESA graphics modes. However, without a framebuffer which makes 
use of the graphics display (vesafb, intelfb, sisfb) it only garbles screen.

Regards,
Krzysztof

----------------------------------------------------------------------
Fantastyczne nagrody do zgarniecia!
Zagraj >> http://link.interia.pl/f2177 



------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects