ubuntu-x-swat team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

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.

** Changed in: nvidia-graphics-drivers (Ubuntu Oneiric)
     Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: initramfs-tools (Ubuntu Oneiric)
     Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/864149

Title:
  initrd doesn't set keyboard layout when nvidia drivers are installed
  (FRAMEBUFFER=n override)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/864149/+subscriptions