On Sunday 18 April 2010, you wrote: > On Sat, 2010-04-17 at 17:18 +0200, Frans Pop wrote: > > Initially all messages from init scripts are displayed correctly, but > > after the init script to set up the VT1-VT6 is run, messages from init > > scripts are no longer displayed. Instead the display is blank with > > only a cursor. > > > > However, if I switch back to VT1 from X.Org after the boot has > > completed, the missing messages are visible. > > > > System is x86_64 running Debian stable ("Lenny"). I'm using VESAFB > > (vga=791) and no KMS. > > > > I've bisected this to the following commit: > > commit 477346ff74f4c2aed50e8a0db96a61069f3e5b80 > > Author: Dave Airlie > > Date: Thu Jan 7 17:04:54 2010 +1000 > > x86-64: Allow fbdev primary video code > > Can you diff dmesg with/without this? There is no relevant difference between the dmesg for 477346ff ("bisect-5": bad) and its predecessor b0483e78 ("bisect-6": good). See attachment. > It shouldn't do anything unless you have multiple framebuffer drivers. Unfortunately "shouldn't" isn't always the same as "doesn't" :-) $ cat /proc/fb 0 VESA VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c) Cheers, FJP