It was suggested to me by Sven Luther, that as vesafb is now compiled into the kernel, it would make sense to do the same with fbcon. Can anyone comment on this idea? It sounds like it would solve most of the problems we are seeing, without needing to muck around with isnmoding fbcon by itself.
I've tried with initramfs-tools now, and that works (some messages will be lost to a short period with a blank screen, but that's minor). Maybe initramfs-tools should be preferred over yaird, when choosing the ramdisk generation tool? Willi