Too optimistic in thinking that the DRM driver will always be loaded in time for scripts/init-top/framebuffer to load; some users find that vesafb gets loaded first anyway, scrambling their console state in the initramfs. Add a one-second sleep before checking if we should fall back to vesafb, which seems to be long enough to work around this. LP: #869119.