After working with Colin Watson, using VMware Workstation as a reproducer, we found that vesafb was not getting loaded. You can experiment with this by replacing 'quiet --' with 'BOOT_DEBUG=3', then blindly entering 'modprobe vesafb'.
This regression is almost surely due to the modularization of vesafb (CONFIG_FB_VESA=m) which prevents adverse graphics interaction with Plymouth on the desktop. One possible workaround is to revert this change for the -server flavour, e.g., CONFIG_FB_VESA=y. The desktop install does not use the 'vga=788' boot option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745947 Title: Fails to display video after grub (kernel lacks video output) -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
