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] 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.