[Bug 789141] Re: initramfs.conf: please document FRAMEBUFFER option
mTim
789141 at bugs.launchpad.net
Fri May 25 15:52:20 UTC 2012
The code to determine if the option is set seems to be buggy (expecting
the FRAMEBUFFER variable to be set)
The plymouth code uses this option but does not need the framebuffer if
the arg --tty=ttyO0 is used for devices on a serial console. If
frabebuffer and/or plymouth is disabled via this the init scripts do not
utilize the serial console.
For some reason this bug is just now being triggered, it was not being
triggered early in the install.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/789141
Title:
initramfs.conf: please document FRAMEBUFFER option
Status in “initramfs-tools” package in Ubuntu:
Confirmed
Bug description:
Binary package hint: initramfs-tools
According to changelog 0.98.8ubuntu1:
- Restore the framebuffer hook and script, copying KMS and other framebuffer drivers into the initramfs, but make them optional; you need to set FRAMEBUFFER=y for these to be included.
Availability of FRAMEBUFFER option was not documented and it seems to
be disabled by default.
The result is broken console fonts in framebuffer consoles (example,
bug 750636). Console-setup script is not copied to initramfs if
FRAMEBUFFER is not set. Also console-setup in natty does not call
setupcon from init scripts. So console-setup does not have a chance to
configure font and all messages in non-english languages becomes
unreadable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/789141/+subscriptions
More information about the foundations-bugs
mailing list