Comment 57 for bug 246269

Hello. Sorry for extra comment (should have included in previous), but I note that the framebuffer comes into effect only later, i.e. after first few kernel messages (as you can see, for first 23 seconds) pass. It is unlike the previous vga=792 functionality where right from the start, the framebuffer is ready. What do I have to do to achieve that previous functionality? Or is it designed to display like this only? Because it is "user mode" vesafb (if I read the meaning of the name uvesafb correctly).