After the recent upgrade of module-init-tools, high-resolution TTY with uvesafb stops working
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| initramfs-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: module-init-tools
After the recent upgrade to the latest version of module-init-tools in Ubuntu Jaunty, the high-res TTY I had set up using the uvesafb kernel module (with this addition to the kernel boot commands: video=uvesafb:
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
appears many times during the kernel boot messages. It appears several times at the very beginning, before "Reading files needed to boot..." It also appears once or twice in the area of "Loading ACPI Modules."
Related branches
| Michael Marley (mamarley) wrote | #1 |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in initramfs-tools: | |
| status: | New → Fix Released |
I tried using the regular vesafb and vga= kernel options instead, but this caused a black screen until X started. For some reason, certain modules are not getting modprobed after the update.