On Wed, May 23, 2001 at 12:54:19PM -0500, John Hawley wrote: > Anyone else have problems getting mgetty to work with an internal USR > 56K PCI (non-win) modem (on ttyS2)? The mgetty / AUTOppp dial-in > services I've been playing with works fine on an external modem on > ttyS1. > > Minicom connects to ttyS2 fine (when not locked by mgetty) and I'm > seeing the verbose result codes. I can intercept an incoming call by > doing an ATA so I believe I believe the hardware is set up right. > > The mgetty.ttyS2 log shows loops containing this: > > 05/23 11:26:04 yS2 send: \dATQ0V1H0[0d] > 05/23 11:26:04 yS2 waiting for ``OK'' > 05/23 11:26:04 yS2 got: ATQ0V1H0[0d] this tells me two things: 1. You have echo on. I guess you don't need that. 2. Maybe the timeout is too short. You can play with modem's registers And the third thing: when I was in Phoenix,AZ (serviced by [US|Q]West as well) it happened at times for the dialtone to come after 3-5 seconds after I opened the line : it happened both in modem and the phone. Some "," in the dialout string helped. "," is "wait two seconds". Weird enough the PPP dialer on FreeBSD didn't choke as the one from Linux. > 05/23 11:26:04 yS2 CND: ATQ0V1H0 > 05/23 11:26:24 yS2 timeout in chat script, waiting for `OK' > 05/23 11:26:24 yS2 init chat timed out, trying force-init-chat > 05/23 11:26:24 yS2 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d] > 05/23 11:26:28 yS2 waiting for ``OK'' > 05/23 11:26:28 yS2 got: [10][03]+++[0d] > 05/23 11:26:28 yS2 CND: __+++ATQ0V1H0[0d] > 05/23 11:26:28 yS2 CND: ATQ0V1H0 > ... and I do see [RING]'s coming in when I put through a test call. > > Any clues? > -John > > Oh, this is on a Debian Woody with kernel 2.4.2 and mgetty1.1.26-Apr16 > compiled from source. Used to be 2.2.xx back then, but I don't think it matters much. florin -- "you have moved your mouse, please reboot to make this change take effect"