Ubuntu
initramfs-tools package

vesafb automatically loaded while blacklisted

Bug #87158 reported by Nicolò Chieffo
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
initramfs-tools (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: module-init-tools

even if the vesafb module is listed in /etc/modprobe.d/blacklist-framebuffer it loads automatically...
I'm using feisty.
I want this module not to be loaded because sometimes it causes flickering!

Revision history for this message
Laurent Bigonville (bigon) wrote :

The vesafb module is loaded in the initrd for usplash. As a workaround, you could disable the boot splashscreen

Revision history for this message
Nicolò Chieffo (yelo3) wrote : Re: [Bug 87158] Re: vesafb automatically loaded while blacklisted

well... so I cannot understand why it is blacklisted! usplash is
enabled by default! this confuses uses/developers...
I've opened a bug for the flickering when framebuffer is enabled, and
Matthew Garret told me that usplash doesn't use any fb-module!

https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/24270

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

/usr/share/initramfs-tools/scripts/init-top/framebuffer calls modprobe without -b

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

So what is the problem? who is right? usplash really needs vesafb (or any other fb module) or there is a bug it that file?

Nicolò Chieffo (yelo3)
Changed in initramfs-tools:
status: New → Confirmed
Revision history for this message
Tomas Šaduikis (tomas-saduikis) wrote :

I think the bug is still in Lucid. because if I set vga=xxx parameter in grub, then dmesg shows that vesafb module was loaded, but it is listed as blacklisted in blacklist-framebuffer.conf

Revision history for this message
Alex James (alex-n-james) wrote :

This bug is still in Lucid, and the effective forced loading of vesafb causes problems with suspend in some setups.

Revision history for this message
Alex James (alex-n-james) wrote :

Not sure we should really call this a bug. This behaviour results from initramfs-tools.conf containing the line 'MODULES=most' which includes all sorts of unnecessary things by default, maybe good for a livecd but perhaps not for an installation. A better behaviour would be 'MODULES=dep' which only loads modules based on dependencies, results in a much smaller initramfs, and still leaves the user with a fully working/bootable system without forcing in unwanted modules.

Revision history for this message
Alex James (alex-n-james) wrote :

Also, should update-initramfs be checking the blacklist before including modules? That sort of seems like something desirable.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.