Comment 3 for bug 864149

This can be addressed without reintroducing the problem from bug #839524 with three changes:

 - drop the nvidia "proprietary-graphics-drivers" initramfs hook config.
 - set 'alias nouveau off' in the modprobe blacklist file, *not* 'blacklist nouveau'. (udev ignores module blacklisting by design!)
 - add a fallback in the framebuffer initramfs script to try to load the vesafb module if no other framebuffer has been loaded. This gives us fallback behavior equivalent to what's used post-initramfs when cryptsetup is not installed, and does not negatively impact booting when the vesa linear framebuffer is unavailable (i.e., when booting with gfxpayload=text) other than generating a warning message that vesafb can't be loaded.

This will ensure the nouveau driver will not be loaded in the initramfs when nvidia drivers are installed, that a best effort is made to load the vesafb driver from the initramfs where possible, and that other functionality that keys on FRAMEBUFFER=y - keyboard map setting, brltty support, and plymouth itself - does not regress.