When booting Linux, the kernel messages are shown on
screen.
I don't like to show these messages, so "Support for
console on virtual terminal" and "Support for console
on serial port" are not chose when compiling kernel.
But using the new kernel, computer can't boot. If one
of "Support for console on virtual terminal" and
"Support for console on serial port" is chose,
Computer can be booted. If I don??t like the booting
messages shown through terminal or HyperTerminal on
screen.
the following is my lilo.conf
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux-2.4.17
image=/boot/linux2417
label=linux-2.4.17
initrd=/root/initrd
append="root=/dev/ram0 init=linuxrc rw"
I using append="console=quiet root=/dev/ram0
init=linuxrc rw" and
append="console=/dev/null root=/dev/ram0 init=linuxrc
rw" but computer can not be booted.
Would you like to tell me how could I do?
_________________________________________________________
Do You Yahoo!?
?????籭?????һ?棬Ӯȡ???籭??Ʊ??һ?֡?
http://cn.worldcup.yahoo.com/
I think you should use the append="quiet" option. This way use get only
errors shown.
On Fri, 22 Feb 2002, [gb2312] hanhbkernel wrote:
> When booting Linux, the kernel messages are shown on
> screen.
> I don't like to show these messages, so "Support for
> console on virtual terminal" and "Support for console
> on serial port" are not chose when compiling kernel.
> But using the new kernel, computer can't boot. If one
> of "Support for console on virtual terminal" and
> "Support for console on serial port" is chose,
> Computer can be booted. If I don??t like the booting
> messages shown through terminal or HyperTerminal on
> screen.
> the following is my lilo.conf
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> message=/boot/message
> linear
> default=linux-2.4.17
> image=/boot/linux2417
> label=linux-2.4.17
> initrd=/root/initrd
> append="root=/dev/ram0 init=linuxrc rw"
> I using append="console=quiet root=/dev/ram0
> init=linuxrc rw" and
> append="console=/dev/null root=/dev/ram0 init=linuxrc
> rw" but computer can not be booted.
> Would you like to tell me how could I do?
>
>
>
> _________________________________________________________
> Do You Yahoo!?
> ?????籭?????һ?棬Ӯȡ???籭??Ʊ??һ?֡?
> http://cn.worldcup.yahoo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
pozsy
> On Fri, 22 Feb 2002, [gb2312] hanhbkernel wrote:
>
> > When booting Linux, the kernel messages are shown on
> > screen.
> > I don't like to show these messages, so "Support for
[...]
Or, you can put the console on the second tty, and then you will not see the
messages unless you want to.
Compile in support for console on virtual terminal, and also VGA text console
or one of the framebuffer consoles.
Then use append="console=/dev/tty2 CONSOLE=/dev/tty2", and you won't
see anything on the boot screen except the linux logo (if you choose a
framebuffer console). But, you can type "Alt-F2" to bring up the second
console with the boot messages on it. This is useful when things go wrong.
If you want a prettier boot logo, check out http://www.arnor.net/linuxlogo for some
patches that let you build in any logo you want at kernel compile time.
Torrey Hoffman
On Thu, Feb 21, 2002 at 05:34:00PM -0800, Torrey Hoffman wrote:
> Then use append="console=/dev/tty2 CONSOLE=/dev/tty2", and you won't
Why do you use both console and CONSOLE?
> On Thu, Feb 21, 2002 at 05:34:00PM -0800, Torrey Hoffman wrote:
> > Then use append="console=/dev/tty2 CONSOLE=/dev/tty2", and you won't
>
> Why do you use both console and CONSOLE?
hmmm. I can't really remember, but I'm pretty sure it was necessary
when I started doing this 18 months ago, I wouldn't have added it
otherwise.
IIRC, "CONSOLE=/dev/tty2" becomes an environment variable for init, and
with the right intelligence in your startup scripts you get all your rc
script output on tty2 as well. On the other hand, my current startup
scripts don't seem to use it or need it... so I guess I don't know.
cargo-cult system management :-( ("but I've always done it that way")
Torrey