FRAMEBUFFER (and console)
Quoted 6 lines · James Simmons
Quoted 5 lines
My framebuffer (and therefore system console, by definition) come up rather late.
It seems the console doesnt care to check for drivers comming up after a certain time, and thus I get no output despite the driver working.
Quoted 7 lines
The reason for this is because the framebuffers most often depend on the bus being set up. Usually this happening later in the boot process. What are trying to do? Retrieve the earlier printk messages. Do you have
DUMMY_CONSOLEset to Y. I believe the data is transfered from dummycon to fbcon after fbcon is initialized. If you having problems with that try increasing the size of dummycon's "screen". Seedummycon.cfor more details.
Maybe he just enabled vga16 + XXXfb. First vga16 comes up, and start painting characters. Few microseconds after that XXXfb (for example matroxfb) comes up, registers itself as /dev/fb1 and reprograms hardware to non-VGA mode.
Quoted 1 line
From that point on vga16fb paints characters to unmapped memory, and
there is only black on screen.
Petr Vandrovec [email protected]
Quoted 5 lines
Maybe he just enabled vga16 + XXXfb. First vga16 comes up, and start painting characters. Few microseconds after that XXXfb (for example matroxfb) comes up, registers itself as
/dev/fb1and reprograms hardware to non-VGA mode.
It would be nice to do it even soon :-) Its just not setup that way :-(