Serial admin console program

[Alan Johnson]

On Mon, Oct 6, 2008 at 8:08 AM, <VirginSnow at vfemail.net> wrote:

> Serial is tough in comparison to other technologies because it has so
> many different parameters (baud rate, parity, stop bits, IO port, IRQ,
> flow control, DTE/DCE, any I'm missing?)


I manged to get into the device by moving the serial interface to a
different server and power cycling the device.  Then, as soon as I ran the
config utility, it locked up again after spewing a bunch of funny characters
in the same spot.  That ring any bells for some parameter I am missing?

I found reference to the cu command in the manual, so perhaps I'll try.  All
the rest of the params are set as suggested by the manual, but the manual
makes no mention of flow control.  This last bit of success (able to login)
was with software off and hardware on.  Given that, is it possible I might
have also had success with hardware off?  That is how the first server was
configured when I checked it, but I don't remember changing it from the
default of yes.

Assuming this in on a PCI-based PC (I have to admit I haven't read the
> entire thread), you might try "cat /proc/interrupts" while mc has the
> port open.  This will show you if anything else is trying to share the
> interrupt with the serial port.  Personal experience has shown me that
> serial ports sometimes don't like to share. :)
>

yes, an HP DL-(360? maybe) running ubuntu server 8.


> See also /proc/ioports and /sbin/setserial.
>

I don't think those will help me as I know the ports are setup right and I
am going to the right tty, but maybe I need to talk a closer look.

All this serial port stuff is really stretching my memory cells... ouch, I
think I pulled something.  Time to stop typing for the night. =/

__________________
Alan Johnson
alan at datdec.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/mailman/private/gnhlug-discuss/attachments/20081006/d1fd4c64/attachment.html