As far as I remember we changed CONFIG_DRM_VMWGFX_FBCON to 'y ' now. Generally it is getting more complicated nowadays. Grub2 initializes some framebuffer graphics mode (unless console mode is enforced in /etc/default/grub), hands this fb over to plymouth and that hands things over to X. And somewhere between grub and plymouth starting, the kernel may start a gfx device specific modeset driver which may have its own fb driver. Many opportunities for things to go wrong. Btw, I think I mentioned it before but the vga= argument may be becoming more a problem than helping. Grub sets a gfx mode already and that is kept if no modeset driver is not changing it. And all newer modeset drivers use video= for specifying the preferred resolution. (like video=1280x800@32). But in theory that should not be necessary at all when the gfx mode is set ok by grub. Anyway, I tend to declare this bug as "fixed" and have people with other gfx cards/drivers open individual bug reports. Mixing things in one single report will only cause confusion.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1270656 Title: Ubuntu 14.04 boots to blank console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
