Very Computer

Same problem! modem is fine, but KPPP cant consistently talk to it.

Have you got the lock off in /etc/ppp/options?

--

     My GV x2 modem comes with a fairly long and complex script for use with the
MacOS.  When I was having problems similar to what you describe (intermittent
though, not all the time) I took a look at the script (how is another story. . .
) and I discovered that when the modem is not responding DTR is toggled off then
on.  I think this is what is needed with the intermittent problem that I am
having, but I haven't figured out how to do this in Linux.  For now when it
happens I have to reboot MacOS, dial the modem to get things working, then reboot
Linux.  Another thing that may be going on in your case is that the display
result code option may be disabled so the modem is not signaling "OK" to any of
the computer's commands.  In my modem this is enabled by "ATQ0".  Kppp has a
window you can use to communicate with the modem directly.  My modem responds
with a list of commands it responds to if you type "AT$".
     Charles Yates

In that case, I'm curious as to know what else it might be,
without seeing your settings.

No old lockfile in /var/lock/ ?  I've had problems with kppp
not reporting old lockfiles there in the past.

I use the same modem without any problems at all, but I tend
to use it from the shell via dip, rather than via kppp. Have
you tried it from the shell? Does it work ok there?

Would you like me to send you copies of my shell scripts
so you can test it with scripts that I know work?

If so, drop me an email and I'll get them off to you.

--

I face exactly the same problem as yours but with 56kbps modem of other brand.
The modem works well in MkLinux but do not function properly in Linuxppc. Kppp
does not go beyond the stage of modem initialization. As Kppp works well in
MkLinux, I think the basic settings are OK. But after switching to Linuxppc, it
stops to work. Why......?

Yanchee Lau