Jush Alv wrote :
> Hm, Why not fix this irlap problem?
> It have been there 2.4.0 -> 2.4.2 & every patch
>
> Feb 24 15:19:28 smulte chat[1680]: timeout set to 14 seconds
> Feb 24 15:19:28 smulte chat[1680]: abort on (BUSY)
> Feb 24 15:19:28 smulte chat[1680]: abort on (NO DIAL TONE)
> Feb 24 15:19:28 smulte chat[1680]: abort on (\nRINGING\r\n\r\nRINGING\r)
> Feb 24 15:19:28 smulte chat[1680]: abort on (NO CARRIER)
> Feb 24 15:19:28 smulte chat[1680]: send (^M^MATZ^M)
> Feb 24 15:19:28 smulte chat[1680]: expect (OK)
> Feb 24 15:19:31 smulte kernel: IrLAP, no activity on link!
> Feb 24 15:19:40 smulte chat[1680]: warning: read() on stdin returned 0
> Feb 24 15:19:40 smulte chat[1680]: send (+++)
> Feb 24 15:19:40 smulte chat[1680]: -- write failed: Input/output error
> Feb 24 15:19:40 smulte chat[1680]: Failed
> Feb 24 15:19:40 smulte chat[1680]: Can't restore terminal parameters:
> Input/output error
> Feb 24 15:19:40 smulte pppd[1677]: Connect script failed
> Feb 24 15:19:41 smulte pppd[1677]: Exit.
>
>
> Linux version 2.4.2 (root@smulte) (gcc version 2.96 20000731 (Red Hat Linux
> 7.0)) #1 SMP Sat Feb 24 15:37:27 CET 2001
>
> Thanks
Excuse me, but I don't see any bug that need fixing. No
activity on link mean just that, the stack doesn't receive anything
from the other node, so decide to quit trying. Of course, at this
point the higher layer quit as well.
To investigate more, we would need a more complete bug report,
including irdadump.
Most likely the problem is with the other guy. If the
discovery is happening properly and nothing happen after, you may try
setting a slower speed.
Jean
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
