Your message dated Wed, 26 Oct 2011 23:47:18 +0200
with message-id <[email protected]>
and subject line Closing bug / Not a bug
has caused the Debian Bug report #646363,
regarding Kernel parameter "boot_delay=1000" prevents system from booting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
646363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646363
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub2-common
Version: 1.99-12
Severity: normal
File: grub2
In GRUB2 edit mode, appending to the kernel line "boot_delay=1000" results in:
***
(black screen)
Reading a command list
Loading Linux 3.0.0-1-686-pae ...
Loading initial ramdisk ...
***
And stays in there. Have to hard-reset the system to be able to boot.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub2-common depends on:
ii dpkg 1.16.1.1
ii grub-common 1.99-12
ii install-info 4.13a.dfsg.1-8
grub2-common recommends no packages.
grub2-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Closing bug as this finally has turned to be not a bug at all, nor for
GRUB2 nor kernel (linux-image) package.
Explanation:
I was passing "ro quiet boot_delay=1000" to the kernel line and it seems
that "quiet" paremeter prevented all of the kernel messages to be
displayed at the screen though the system is booting and kernel messages
are being passed inadvertently and slowly (at the choosen delay). Once
the kernel messages are over (it can take up to 15 minutes to finish),
the system usual start up logs come into play and are properly
displayed and system boots as usual.
Sorry for the noise.
Greetings,
--
Camaleón
--- End Message ---
