[Soekris] Comm Port Help!

[Bob Camp]

Hi

I think I would leave Grub on the serial port. That way you will have  
some kind of access if things go very wrong. Grub will be completely  
out of the way long before the kernel is done loading and any  
application will load.

Bob


On Jul 17, 2007, at 2:11 PM, Mark wrote:

> Thanks, RB.  I had tried killing agetty, but of course, it was  
> respawning-duh.  I'll try to go slowly as I don't want a brick on  
> my hands--the flash is soldered to the board.
>
> --Mark
>
> -----Original Message-----
> From: RB [mailto:aoz.syn at gmail.com]
> Sent: Tuesday, July 17, 2007 1:59 PM
> To: Mike Tancsa
> Cc: mnichols at spanalytics.com; soekris-tech at lists.soekris.com
> Subject: Re: [Soekris] Comm Port Help!
>
> On 7/17/07, Mike Tancsa <mike at sentex.net> 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
> Soekris-tech at lists.soekris.com
> http://lists.soekris.com/mailman/listinfo/soekris-tech
>