[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The Ubuntu version this bug was reported against reached
end-of-life. We appreciate that this bug may be old and you might not be
interested in discussing it anymore. But if you are then please upgrade
to the latest
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
Also, should update-initramfs be checking the blacklist before including
modules? That sort of seems like something desirable.
--
vesafb automatically loaded while blacklisted
https://bugs.launchpad.net/bugs/87158
You received this bug notification because you are a member of Ubuntu
Bugs, which i
This bug is still in Lucid, and the effective forced loading of vesafb
causes problems with suspend in some setups.
--
vesafb automatically loaded while blacklisted
https://bugs.launchpad.net/bugs/87158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
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
--
vesafb automatically loaded while blacklisted
https://bugs.launchpad.net/bugs/87158
You received this bug
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
vesafb automatically loaded while blacklisted
https://bugs.launchpad.net/bugs/87158
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
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?
--
vesafb automatically loaded while blacklisted
https://launchpad.net/bugs/87158
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
/usr/share/initramfs-tools/scripts/init-top/framebuffer calls modprobe
without -b
** Changed in: module-init-tools (Ubuntu)
Sourcepackagename: module-init-tools => initramfs-tools
--
vesafb automatically loaded while blacklisted
https://launchpad.net/bugs/87158
--
ubuntu-bugs mailing list
ubun
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-sour
The vesafb module is loaded in the initrd for usplash. As a workaround,
you could disable the boot splashscreen
--
vesafb automatically loaded while blacklisted
https://launchpad.net/bugs/87158
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
11 matches
Mail list logo
