[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#1254: Kppp 1.6.2: Sorry, the modem doesn't respond
From:       Mark Sproull <sproull () earthlink ! net>
Date:       1999-05-03 3:16:45
[Download RAW message or body]

Package: KPPP
Version: 1.6.2

When I click "connect", I get the following messages:  "Modem Ready",
"Sorry, the modem doesn't respond".

This is kppp shipped with Caldera OpenLinux 2.2.
My modem is a Diamond Supra 56K, Plug-N-Play, which gets assigned to
COM3 in Win98.

I'm able to dial with pppd, so I know /dev/modem is set up correctly.

Just to be sure, I tried the specific settings in the device tab for my
other com ports instead of /dev/modem.   I have devices connected to
them.  The messages were "Modem Ready", "Setting Speaker Volume", then
it would just get stuck there.  When I switched back to /dev/modem, I no
longer got the "Sorry, the modem doesn't respond" message.  Instead,
like the other ports, I got "Setting Speaker Volume" and stuck there.

One other thing, The kppp that shipped with Caldera OpenLinux 1.3 worked
fine for me.

Here's the setup:
accounts tab:
    Dial tab:
        connection name -- my provider
        phone number -- my local number
        authentication -- PAP (as specified by my ISP)
        execute program upon connect -- blank
        execute program before disconnect -- blank
        execute program upon disconnect -- blank
        PPPD arguments -- none
     IP tab:
        dynamic IP address -- checked
    DNS tab:
        DNS -- 2 DNS entries provided by ISP
    Gateway tab:
        default Gateway
        login script -- none
    accounting -- none
    device tab:
        modem device --/dev/modem
        flow control --CRTSCTS (also tried XON/XOFF)
        connection speed 115200
        use lock file -- checked
        modem timeout -- 60
    modem tab:
        busy wait -- 0
        modem volume -- 0
        modem commands button: default values

[prev in list] [next in list] [prev in thread] [next in thread]