This bug was fixed in the package grub2 - 1.97~beta1-1ubuntu2
---
grub2 (1.97~beta1-1ubuntu2) karmic; urgency=low
* debian/patches/953_no_eh_frame.diff: Build with -fno-dwarf2-cfi-asm to
stop gcc-4.4 generating .eh_frame sections that cause core.img to be too
big to embed
6) is disabled now except for recovery-mode boots:
initramfs-tools (0.92bubuntu42) karmic; urgency=low
* Don't display Loading, please wait... message when 'quiet' is in
/proc/cmdline.
-- Colin Watson cjwat...@ubuntu.com Thu, 03 Sep 2009 23:31:28 +0100
** Also affects: initramfs-tools
1) is tricky as it's in the assembly bootstrap right at the start, so
I'll have to think about that.
2) I'm just going to patch out unconditionally for now although I'm not
sure I'm entirely happy about that.
3) is a bug, although I may work around it in our packaging for now; see
** Changed in: grub2 (Ubuntu)
Importance: Undecided = Wishlist
--
grub2 is not quiet enough
https://bugs.launchpad.net/bugs/386922
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
These things will be targeted by
https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicBootExperienceDesignSpec
--
grub2 is not quiet enough
https://bugs.launchpad.net/bugs/386922
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
6) comes from the kernel and not the initrd
See the top of /usr/share/initramfs-tools/init
--
grub2 is not quiet enough
https://bugs.launchpad.net/bugs/386922
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Here is the locations of some of the text (in the source package):
2) kern/main.c: grub_printf (Welcome to GRUB!\n\n);
4) normal/menu_text.c: grub_printf ( Booting \'%s\'\n\n,
entry-title);
--
grub2 is not quiet enough
https://bugs.launchpad.net/bugs/386922
You received this bug
6) comes from the kernel and not the initrd
The problem with a bootloader is, that if you remove all of it's output and it
hangs then it's too late to print out an error message.
So in case it fails it's much harder if not even impossible to debug if there
is absolutely no output
I'm not sure
Well, they are _misused_ for debugging. You're programs don't come with
debug mode enabled by default so why should GRUB2?
One fix would be to make it possible to install GRUB2 in two verbose
modes. The default verbose mode would print messages iff they are errors
or warnings while a verbose mode
Actually (6) 'Loading please wait' comes from the initrd and not from
grub.
--
grub2 is not quiet enough
https://bugs.launchpad.net/bugs/386922
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Couldn't agree more.
** Changed in: grub2 (Ubuntu)
Status: New = Confirmed
--
grub2 is not quiet enough
https://bugs.launchpad.net/bugs/386922
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: video-of-noisy-grub2
http://launchpadlibrarian.net/27890158/untitled.avi
--
grub2 is not quiet enough
https://bugs.launchpad.net/bugs/386922
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
12 matches
Mail list logo
