On 7/17/07, Mike Tancsa <[EMAIL PROTECTED]> wrote:
> Take a look in the bios of the unit
Nope. Mark is competing with the system's console getty. To get a
clean ttyS0, you're going to need to do two things:
- point kernel messages elsewhere
- turn off the console getty
Not being familiar with Voyager, I can't give you precise
instructions, but I can give you concepts. To turn off your getty,
simply edit /etc/inittab (or it's equivalent) and comment out the line
that looks like:
s0:12345:respawn:/sbin/agetty 9600 ttyS0 vt100
Then, execute 'telinit q' or reboot; you may have to kill the existing
getty process.
Grub's 'terminal' command simply tells it where to display it's
initial output. By eliminating that and not having any other console,
it may have just not done anything at all, preventing boot all
together. I don't know if it's possible to force it to be completely
silent, but this is what I would do:
###############
default 0
timeout 0
terminal --silent serial
title Voyager
kernel ...
################
That _will_ put some predictable text at 9600bps to ttyS0 at boot, but
that should be the only time. To make sure the kernel doesn't print
any of it's messages out to the serial line,delete any 'console='
argument on the 'kernel ' line.
Like you said, once you do this there is no turning back without
taking out the disk and manually booting/imaging it elsewhere. You
can do remote administration, but that's about it.
RB
_______________________________________________
Soekris-tech mailing list
[email protected]
http://lists.soekris.com/mailman/listinfo/soekris-tech
