It seems that sometimes, particularly with multi-gpu systems, vga16fb claims fb0 ahead of a kernel modesetting driver. This results in a blank display.
Note that even when a kernel modesetting driver is loading first and claiming fb0 there are side-effects to having vga16fb loaded and providing fb1 - bug #527369 is an example. I'm leaving this as a separate bug as it's got very different symptoms and may not necessarily be fixed by the same process.
@vladilinsky: It would be useful if you could provide dmesg logs from a failed boot just to check that we're on the right track
It seems that sometimes, particularly with multi-gpu systems, vga16fb claims fb0 ahead of a kernel modesetting driver. This results in a blank display.
Note that even when a kernel modesetting driver is loading first and claiming fb0 there are side-effects to having vga16fb loaded and providing fb1 - bug #527369 is an example. I'm leaving this as a separate bug as it's got very different symptoms and may not necessarily be fixed by the same process.
@vladilinsky: It would be useful if you could provide dmesg logs from a failed boot just to check that we're on the right track