vgetty not getting an OK from modem

[Ryan]

I've been using vgetty for years and I just updated my old Fedora box the the newest version of mgetty however it no longer is able to talk to my modem.

I get the following from vgetty

--snip /var/log/vgetty.log.ttyS2--
07/18 16:53:49 yS2 vgetty: experimental test release 0.9.32 / with duplex patch
07/18 16:53:49 yS2 mgetty: interim release 1.1.36-Jun15
07/18 16:53:49 yS2 reading generic configuration from config file /etc/mgetty+sendfax/voice.conf
07/18 16:53:49 yS2 reading program vgetty configuration from config file /etc/mgetty+sendfax/voice.conf
07/18 16:53:49 yS2 reading port ttyS2 configuration from config file /etc/mgetty+sendfax/voice.conf
07/18 16:53:49 yS2 check for lockfiles
07/18 16:53:49 yS2 locking the line
07/18 16:53:50 yS2 lowering DTR to reset Modem
07/18 16:53:50 yS2 send: \d\d\d+++\d\d\dATH0&F[0d]
07/18 16:53:53 yS2 waiting for ``OK''
07/18 16:54:13 yS2 timeout in chat script, waiting for `OK'
07/18 16:54:13 yS2 init chat timed out, trying force-init-chat
07/18 16:54:13 yS2 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
07/18 16:54:17 yS2 waiting for ``OK''
07/18 16:54:37 yS2 timeout in chat script, waiting for `OK'
07/18 16:54:37 yS2 init chat failed, exiting...: Interrupted system call
07/18 16:54:37 ##### failed in mg_init_data, dev=ttyS2, pid=28171
--end snip--

My first guess is its not getting the init chat correctly and I've tried a number of alternatives I've found on the net.

I can use the modem just fine with minicom and kermitc. Here is some info on the modem:

--snip minicom--
ati3
LT V.92 1.0 MT5634ZPX-PCI-V92 Internal Data/Fax/Voice Modem Version 1.25p
--end minicom--

--snip lspci -vv--
00:09.0 Communication controller: Agere Systems Venus Modem (V90, 56KFlex)
Subsystem: Agere Systems Device 5656
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+ INTx-
Latency: 0 (63000ns min, 3500ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at dfffbf00 (32-bit, non-prefetchable) [size=256]
Region 1: I/O ports at d800 [size=256]
Region 2: I/O ports at d400 [size=256]
Region 3: I/O ports at d000 [size=8]
Capabilities: [f8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: serial
--end lspci--

--snip uname -a--
Linux rnelnet.com 2.6.38.8-32.fc15.i686.PAE #1 SMP Mon Jun 13 19:55:27 UTC 2011 i686 i686 i386 GNU/Linux
--end uname -a--

Any help would be great, I hope its something simple that I've neglected to do.

Thanks,
Ryan

[Ryan]

I forgot to say what version of mgetty I'm using:

mgetty-voice-1.1.36-8.fc15.i686
mgetty-1.1.36-8.fc15.i686

Also its:

Fedora release 15 (Lovelock)

[Ryan]

Bump

Anyone use this list or is my problem unknown?

[Edmund H. Ramm]

Post by Ryan
Bump
Anyone use this list or is my problem unknown?

What list? This is a newsgroup.

Do you get the OK prompt from your modem using a terminal program,
e.g minicom? If yes, what is your chat script looking like?

Eddi ._._.

[Ryan]

Post by Edmund H. Ramm
What list? This is a newsgroup.

I misspoke.

Post by Edmund H. Ramm
Do you get the OK prompt from your modem using a terminal program,
e.g minicom? If yes, what is your chat script looking like?

Yes I do, works fine in minicom and kermit. Are you asking about the init-chat line in mgetty.config if so I've tried a number including not setting it at all. Here are the ones I've tried:

#init-chat "" \d\d\d+++\d\d\dAT&FS2=255 OK ATN3S0=0S13.2=1 OK
#init-chat "" \dATQ0V1H0[0d]
#init-chat "" '\dAT\dS7=45\dS0=0\dL1\dV1\dX4\d&c1\dE1\dQ0 OK'

[Edmund H. Ramm]

Post by Ryan

Post by Edmund H. Ramm
Do you get the OK prompt from your modem using a terminal program,
e.g minicom? If yes, what is your chat script looking like?

Yes I do, works fine in minicom and kermit. Are you asking about the
init-chat line in mgetty.config if so I've tried a number including not
#init-chat "" \d\d\d+++\d\d\dAT&FS2=255 OK ATN3S0=0S13.2=1 OK
#init-chat "" \dATQ0V1H0[0d]
#init-chat "" '\dAT\dS7=45\dS0=0\dL1\dV1\dX4\d&c1\dE1\dQ0 OK'

I never used init-chat. I start mgetty from /etc/inittab with e.g.
d1:2345:respawn:/sbin/mgetty -D -x9 -s 115200 -m '"" ATZ0 OK' ttyS4

where the initial chat string, enclosed in apostrophes, follows the
-m switch: Expect nothing, send ATZ0 (which resets my ISDN terminal
adapter to profile 0), expect OK.

These initialisation strings usually are modem specific. The first
one mentioned by you looks like that for a ZyXEL 2864.

Have you tried setting debug for the port your modem is attached to
to a value of 8 or 9 and searched the log for any clues? You are welcome
to send an excerpt from your log to me by e-mail so we won't bore
the readers of this newsgroup.

Eddi ._._.

[Ryan]

Post by Edmund H. Ramm
I never used init-chat. I start mgetty from /etc/inittab with e.g.
d1:2345:respawn:/sbin/mgetty -D -x9 -s 115200 -m '"" ATZ0 OK' ttyS4

I use to use inittab however in Fedora 15 they have migrated away from
SYS V style startup and you know have to use systemd. I create my own
systemd.service file to start vgetty (which might be the problem)
however I get the same result from the command line.

--snip vgetty.service--
# This is a basic .service file used with systemd to control vgetty.
#
# Vgetty turns your voice modem into an answering machine.
# It is apart of the mgetty package. http://alpha.greenie.net/vgetty/

[Unit]
Description=Vgetty turns your voice modem into an answering machine
After=syslog.target

[Service]
ExecStart=-/sbin/vgetty /dev/ttyS2
#Restart=always
Restart=no
#RestartSec=0

[Install]
WantedBy=multi-user.target
--end snip--

Post by Edmund H. Ramm
These initialisation strings usually are modem specific. The first
one mentioned by you looks like that for a ZyXEL 2864.

Prior using SYS V I didn't have to set any init string for my modem to
respond, I have only been playing with init-chat since this problem. I
suspect the do the same thing.

Post by Edmund H. Ramm
Have you tried setting debug for the port your modem is attached to
to a value of 8 or 9 and searched the log for any clues? You are welcome
to send an excerpt from your log to me by e-mail so we won't bore
the readers of this newsgroup.

Yup, and I E-Mailed you the log.

[Ryan]

Post by Edmund H. Ramm
What list? This is a newsgroup.

I misspoke.

Post by Edmund H. Ramm
Do you get the OK prompt from your modem using a terminal program,
e.g minicom? If yes, what is your chat script looking like?

Yes using minicom and kermit I get back OK response. I've tried a number of init-chat lines in mgetty.config, including not setting it all, none responded correctly. Here are the lines I tried:

#init-chat "" \d\d\d+++\d\d\dAT&FS2=255 OK ATN3S0=0S13.2=1 OK
#init-chat "" \dATQ0V1H0[0d]
#init-chat "" '\dAT\dS7=45\dS0=0\dL1\dV1\dX4\d&c1\dE1\dQ0 OK'

[Ryan]

I've solved my problem of mgetty and vgetty not communicating to my
modem. It appears that by looking at the man page which Edmund was able
to point out to me that the hardware flow control settings needs to be
changed in the policy.h file and then recompiled.

--snip man mgetty--
BUGS
Not all of mgetty configuration can be done at run-time yet.
Things like flow control and file paths (log file / lock file) have to
be configured by changing the source and recompiling.

Users never read manuals...
--end snip--

--snip policy.h--
#define DATA_FLOW FLOW_SOFT
--end snip--

After that I was able to get to this point or error from vgetty:

--snip vgetty.log--
08/08 12:03:29 yS2 vgetty: timeout while reading character from voice modem
08/08 12:03:40 yS2 vgetty: timeout while reading character from voice modem
08/08 12:03:51 yS2 vgetty: timeout while reading character from voice modem
08/08 12:04:02 yS2 vgetty: timeout while reading character from voice modem
08/08 12:04:13 yS2 vgetty: timeout while reading character from voice modem
08/08 12:04:13 yS2 waiting...
--end snip--

Looks like in the voice.conf you need to tell vgetty to not set hardware
control as well:

--snip voice.conf--
# Enable hardware flow in record and playback mode if the modem
do_hard_flow false
--end snip--

At least that was in the config file.

Thanks again to Edmund Ramm for bouncing E-Mail back and forth, and
pointing out the man page entry which enabled me to get this working.

Ryan