Minicom + Procurve switch

Thu May 5 20:20:04 UTC 2011

On Thu, 2011-05-05 at 16:07 -0400, cliff here wrote:
> I agree, except all the hardware and settings were exactly the same, only
> difference was one was minicom launched from a terminal inside X and one was
> from run level 3
> 
> On Thu, May 5, 2011 at 3:59 PM, Grzegorz Witkowski <geslinux at gmail.com>wrote:
> 
> > On Thu, 2011-05-05 at 10:21 -0400, cliff here wrote:
> > > *** Update ***
> > >
> > > So I took the switch out of a rack and hooked it up to a workstation with
> > > the exact same hardware using the exact same build of RHEL, ONLY
> > difference
> > > is that this machine had X installed. Worked the first time. Now, is
> > there
> > > some difference in the way that  minicom interprets a tty console vice
> > the
> > > 'terminal' prog in X?
> > >
> > > On Wed, May 4, 2011 at 6:20 PM, Grzegorz Witkowski <geslinux at gmail.com
> > >wrote:
> > >
> > > > On Wed, 2011-05-04 at 16:16 -0400, cliff here wrote:
> > > > > Yea it's set to 9600, like i said I"m duplicating the same settings I
> > > > used
> > > > > in hyperterm that worked fine.
> > > > >
> > > > > On Wed, May 4, 2011 at 3:40 PM, Grzegorz Witkowski <
> > geslinux at gmail.com
> > > > >wrote:
> > > > >
> > > > > > On Wed, 2011-05-04 at 15:18 -0400, cliff here wrote:
> > > > > > > Good afternoon list compatriots;
> > > > > > >
> > > > > > > Having a weird issue using minicom to connect a  2400 series
> > Procurve
> > > > > > > switch.  I am using 8N1 and I start by leaving minicom listening
> > and
> > > > then
> > > > > > > reboot the switch.
> > > > > > >
> > > > > > > Switch comes up and I see it's ROM decompress and post,  then
> > asks me
> > > > to
> > > > > > hit
> > > > > > > enter twice to confirm speed test. However minicom doesn't seem
> > to be
> > > > > > > responding to any keystrokes.  I believe the terminal emulation
> > is
> > > > set to
> > > > > > > VT102.
> > > > > > >
> > > > > > > The other item that seems odd is that even though I can see
> > output
> > > > from
> > > > > > the
> > > > > > > switch minicom still says 'offline'
> > > > > > >
> > > > > > > I know my settings are correct since I've used hyperterm to get
> > it
> > > > > > working
> > > > > > > before, I'm assuming I just am not understanding a setting or
> > > > behavior of
> > > > > > > minicom.
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > >
> > > >
> > -------------------------------------------------------------------------------------------------------------------------------------
> > > > > > > NOTICE: This message, including all attachments, is intended for
> > the
> > > > use
> > > > > > of
> > > > > > > the individual or entity to which it is addressed and may contain
> > > > > > > information that is privileged, confidential and exempt from
> > > > disclosure
> > > > > > > under applicable law. If the reader of this message is not the
> > > > intended
> > > > > > > recipient, or the employee or agent responsible for delivering
> > this
> > > > > > message
> > > > > > > to its intended recipient, you are hereby notified that any
> > > > > > dissemination,
> > > > > > > distribution or copying of this communication is strictly
> > prohibited.
> > > > If
> > > > > > you
> > > > > > > have received this communication in error, please notify the
> > sender
> > > > > > > immediately by replying "Received in error" and immediately
> > delete
> > > > this
> > > > > > > message and all its attachments.
> > > > > > >
> > > > > >
> > > >
> > -------------------------------------------------------------------------------------------------------------------------------------
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > You did not say anything about boud rate and flow control.
> > > > > > They are very important. Typically you set flow control to none
> > when
> > > > > > connecting to switches. Check documentation of your switch for baud
> > > > > > rate. Usually it's 9600, but some switches may have 115200 default.
> > > > > > If those are incorrect, you may see connection problems.
> > > > > >
> > > > > > Hope this will help.
> > > > > >
> > > > > > Regards,
> > > > > > Ges
> > > > > > --------------------------------------------------------------
> > > > > > 01000111 01100101 01110011 01100011 01100001 01110000 01100101
> > > > > > http://counter.li.org #239224 Registration 2001-10-29 07:19:32
> > > > > >        -= GNU/Linux - The Experience of Freedom =-
> > > > > >
> > > > > > --
> > > > > > redhat-list mailing list
> > > > > > unsubscribe mailto:redhat-list-request at redhat.com
> > ?subject=unsubscribe
> > > > > > https://www.redhat.com/mailman/listinfo/redhat-list
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > >
> > -------------------------------------------------------------------------------------------------------------------------------------
> > > > > NOTICE: This message, including all attachments, is intended for the
> > use
> > > > of
> > > > > the individual or entity to which it is addressed and may contain
> > > > > information that is privileged, confidential and exempt from
> > disclosure
> > > > > under applicable law. If the reader of this message is not the
> > intended
> > > > > recipient, or the employee or agent responsible for delivering this
> > > > message
> > > > > to its intended recipient, you are hereby notified that any
> > > > dissemination,
> > > > > distribution or copying of this communication is strictly prohibited.
> > If
> > > > you
> > > > > have received this communication in error, please notify the sender
> > > > > immediately by replying "Received in error" and immediately delete
> > this
> > > > > message and all its attachments.
> > > > >
> > > >
> > -------------------------------------------------------------------------------------------------------------------------------------
> > > >
> > > > Were you using the same machine with hyperterm?
> > > > Use dmesg and setserial to check the if your serial is initialized,
> > > > enabled and set up properly. There is no magic really with minicom if
> > > > your hardware is working and setup properly.
> > > > Vivek has nice simple tutorial, you probably know that one already.
> > > >
> > > >
> > http://www.cyberciti.biz/tips/connect-soekris-single-board-computer-using-minicom.html
> > > > Run minicom with -s and select Filenames and paths, then F - Logging
> > > > options and make sure you can see minicom.log and B,C=yes.
> > > > Then save a dfl and exit once still connected to the switch.
> > > > You should see:
> > > >
> > > > Welcome to minicom
> > > > 2.5
> > > > OPTIONS:
> > > > I18n
> > > > Compiled on Feb 24 2011,
> > > > 11:25:53.
> > > > Port /dev/ttyS0
> > > > Press CTRL-A Z for help on special keys
> > > >
> > > > Now press Ctrl-A L to capture the session to the file and then press
> > > > Ctrl-A F to send a break. See if you will be able to connect. If not,
> > in
> > > > you ~ should be a minicom capture log, try to see if there is anything
> > > > in it.
> > > >
> > > > Regards,
> > > > Ges
> > > >
> > > > --
> > > > redhat-list mailing list
> > > > unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> > > > https://www.redhat.com/mailman/listinfo/redhat-list
> > > >
> > >
> > >
> > >
> > > --
> > >
> > -------------------------------------------------------------------------------------------------------------------------------------
> > > NOTICE: This message, including all attachments, is intended for the use
> > of
> > > the individual or entity to which it is addressed and may contain
> > > information that is privileged, confidential and exempt from disclosure
> > > under applicable law. If the reader of this message is not the intended
> > > recipient, or the employee or agent responsible for delivering this
> > message
> > > to its intended recipient, you are hereby notified that any
> > dissemination,
> > > distribution or copying of this communication is strictly prohibited. If
> > you
> > > have received this communication in error, please notify the sender
> > > immediately by replying "Received in error" and immediately delete this
> > > message and all its attachments.
> > >
> > -------------------------------------------------------------------------------------------------------------------------------------
> >
> > No, there should be no difference, as you would be using the "same"
> > device /dev/ttyS0 (COM1) or /dev/ttyS1 (COM2) for example.
> > The difference though may be in settings of the interface. You should
> > check in the hardware manual of your system for serial interface
> > settings.
> >
> > Regards,
> > Ges
> >
> >
> >
> >
> > --
> > redhat-list mailing list
> > unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/redhat-list
> >
> 
> 
> 
> -- 
> -------------------------------------------------------------------------------------------------------------------------------------
> NOTICE: This message, including all attachments, is intended for the use of
> the individual or entity to which it is addressed and may contain
> information that is privileged, confidential and exempt from disclosure
> under applicable law. If the reader of this message is not the intended
> recipient, or the employee or agent responsible for delivering this message
> to its intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If you
> have received this communication in error, please notify the sender
> immediately by replying "Received in error" and immediately delete this
> message and all its attachments.
> -------------------------------------------------------------------------------------------------------------------------------------

Hi Cliff,

Check ch.10 & 16 of the serial howto
http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Serial-HOWTO.html 
Maybe it will help you to narrow down the root cause of the
communication problem on the host with no X.
I hope this will help.

Regards,
Ges