[Gllug] set serial port irq

[Jack Richards]

Looks like you have hardware flow control turned on DSR is a problem if its 
expecting it and not getting it. 

This looks like a cable issue, does your cable have DSR, CTS DTR RTS ( tx, rx 
and gnd ) all connected ?

Have you tried the "paper clip loopback" method of testing each serial port ?

 

Quoting Ben Fitzgerald <ben_m_f at yahoo.co.uk>:

> On Mon, Apr 19, 2004 at 04:22:35PM +0100, Doug Winter wrote:
> > On Mon 19 Apr Ben Fitzgerald wrote:
> > > I'm connecting using minicom from box 1 to mgetty on box 2.
> > > I don't get a login: prompt!
> > 
> > I doubt that you want mgetty as is, that's for modems.  use getty (or
> > run mgetty as getty, or use the -r switch to mgetty).
> 
> I did wonder about that. I've added -r into inittab now.
> > 
> > check that your getty is really being spawned from the inittab.  it
> > often isn't by default.
> 
> It's being spawned alright.
> > 
> > check that you have the following set correctly at both ends:
> > 
> >     baud rate
> >     stop bits
> >     parity
> >     flow control
> 
> When you say check these, do you mean by comparing setserial output
> or by comparing values in 
> minicom config vs. /etc/mgetty+sendfax/mgetty.config?
> 
> setserial's output is the same for both and the values in the other
> two files are also the same.
> 
> This is the output of /var/log/mgetty.log.ttyS0 after killing
> mgetty (thus inittab respawns). Debug level is 8:
> 
> 04/19 16:41:33 yS0  mgetty: experimental test release 1.1.30-Dec16
> 04/19 16:41:33 yS0  check for lockfiles
> 04/19 16:41:33 yS0   checklock: stat failed, no file
> 04/19 16:41:33 yS0  locking the line
> 04/19 16:41:33 yS0   makelock(ttyS0) called
> 04/19 16:41:33 yS0   do_makelock: lock='/var/lock/LCK..ttyS0'
> 04/19 16:41:33 yS0   lock made
> 04/19 16:41:33 yS0   tio_get_rs232_lines: status: RTS DTR
> 04/19 16:41:33 yS0  WARNING: DSR is off - modem turned off or bad cable?
> 04/19 16:41:33 yS0  lowering DTR to reset Modem
> 04/19 16:41:34 yS0   tss: set speed to 115200 (10002)
> 04/19 16:41:34 yS0   tio_set_flow_control( HARD )
> 04/19 16:41:34 yS0   waiting for line to clear (VTIME), read:
> 04/19 16:41:34 yS0   waiting for line to clear (VTIME), read:
> 04/19 16:41:34 yS0   removing lock file
> 04/19 16:41:34 yS0  waiting...
> 
> is the "DSR is off" a problem?
> 
> > are you sure you have the right cable?
> 
> I've been passed it by a colleague who tells me it's a null-modem
> cable! It's an RJ-45 to DB-9 female an all in one cable. The rj-45
> end has an adapter that converts to a com port. The adapter has
> no markings except the interface has the pin numbers on it. These
> are the same as the other end. The only difference is that one
> has "l" on the face, the other "DD" (?). Perhaps this has significance
> to others?
> 
> It's actually on this page:
> http://www.cisco.com/warp/public/701/14.html
> 
> The third last cable, numbered 72-3383-01
> 
> > > Typing AT<cr> doesn't get a response either.
> > 
> > unless you have a getty that talks the Hayes command set (which you
> > don't :) that's not going to help.
> 
> Right, I'll cut that out then.
> 
> > hitting return a few times can help wake up getty though.
> 
> Unfortunately that doesn't have an effect either for a login
> prompt or an entry into the mgetty logfile.
> 
> Sorry to come back negative but I believe your "mgetty -r"
> suggestion has helped, so many thanks,
> 
> Ben
> -- 
> Gllug mailing list  -  Gllug at gllug.org.uk
> http://lists.gllug.org.uk/mailman/listinfo/gllug
> 


Jack Richards

GNU Solutions Ltd
Atlantic House
Imperial Way 
Reading
Berks.
RG2 0TD

web   : www.gnu-solutions.com
email : jack at gnu-solutions.com
Office: +44 (0)870  250 9219
DDI   : +44 (0)1462 634 410
Mobile: +44 (0)7788 437 904
Fax   : +44 (0)871  277 1937

*******************************************************************************
*



THIS MESSAGE IS INTENDED ONLY 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.  

If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering the message to the 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 accept our apology.
We should be obliged if you would email them by return.

Thank you.

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug