[PLUG] mgetty help SOLVED

[Keith Nasman]

I figured it out. I believe the compiled in modem initialization doesn't 
work for this modem so you have to specify the init in the config or on 
the mgetty command line. My specification of the init chat was 
syntactically incorrect but when I passed the init via the command line 
the modem and mgetty would listen for the call.

Kdog

On Fri, 9 Aug 2002, Keith Nasman wrote:

> 
> I am setting up a dial-in service on one of my servers. I've got the modem 
> installed and setup with drivers. (It's one of those Connexant/Rockwell 
> winmodems. It works, I can dial out with minicom just fine). I've 
> installed the mgetty package and read the various docs/howtos that I've 
> come across but am still having difficulty.
> 
> I try to run mgetty with "mgetty ttySHCF0" or "mgetty modem" and it 
> fails. It looks like the mgetty.config file doesn't have the right 
> settings. Here is what I get when I comment out all but the debug line:
> 
> date host mgetty[pid]: init chat failed, exiting...: Invalid argument
> date host mgetty[pid]: failed in mg_init_data, dev=ttySHCF0, pid=pid
> 
> Here is what I get when I use what I think is the correct config:
> 
> date host mgetty[pid]: init chat failed, exiting>>>: Interrupted system 
> call
> date host mgetty[pid]: failed in mg_init_data, dev=ttySHCF0, pid=pid
> 
> Here are my configuration lines from mgetty.config:
> port ttySHCF0
>    speed 38400
>    modem-type data
>    data-only yes
>    toggle-dtr no
>    direct no
>    init-chat send ATQ0V1E0 expect AT send AT&K3S0=0 expect ok
> 
> 
> Any suggestions, insights?
> 
> TIA,
> Kdog
> 
> 
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
> 

--