On 26/03/2008, Stephan Assmus <superstippi@xxxxxx> wrote: > Urias McCullough wrote: > > I will probably create a Trac ticket for this within the next day or two. > > You can file the ticket if you like, but I already know the reason: I > disabled the code in case you are not running in 15, 16, 24 or 32 bit VESA > mode. You are probably running in 8 bit palette mode, which the old boot > splash code supported. I had in mind to generate the perfect 256 bit > palette in the boot splash generator, and configure the VESA mode > accordingly, but this is not done yet. I thought that pretty much any gfx > board would support at least the 16 bit mode. Not so it appears... :-) Oh it certainly supports 32-bit mode - but I'm guessing it isn't selecting the right mode at startup. Before the intel_extreme driver worked with the laptop, I had to use VESA instead, and it always started up in 8-bit mode requiring me to change it after the first boot. (you even asked me when we met in Mountain View why I was running 8-bit instead of 16 or higher... it was simply the default that was detected) So, I guess this maybe comes down to EDID issues. Strange that I'm having this problem only with the intel chips - as the same CRT monitor seems to work fine with a Radeon card on the desktop machine. So, should the VESA driver try to find the highest supported resolution with 15bpp or higher from EDID then? I can provide the serial log from both machines in a ticket and see if anyone can make heads or tails out of the EDID info.