Re: Modem stopped working

From: Bruce A. Mallett (bam_at_SNIP_nightstorm_SNIP.com)
Date: 07/18/03


Date: Fri, 18 Jul 2003 18:32:48 GMT

Lena wrote:
>>>Go into Yast2 -> Network Devices and select "Modem".
>>>On the first page, below where it says "Already configured devices: ..."
>>>click on the "Change..." button.
>>>
>>>Your window will now show "Modems" and "Providers". Under "Modems"
>>>ensure that your ppp entry is highlighted (it probably will be by
>>>default) and click on the "Edit" button.
>>>
>>>You will now see a "Modem parameters" page. Click on the "Details"
>
> button.
>
>>>You will now see the "Modem parameter details" page. Make your three
>>>"Init" sections read as follows:
>>>
>>>Init 1
>>> ATZ
>>>
>>>Init 2
>>>AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W0
>>>
>>>Init 3
>>>ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4
>>>
>>>
>>>Click "OK", then keep clicking "Next", until you can finally click
>
> "Finish".
>
>>>Now try the dial up again. Let us know what happens (and if it does not
>>>work please send along the new log).
>>>
>>> - Bruce
>>
>>Thanks for the help Bruce, but unfortunately, that didn't work. My
>>error log looks like:
>>
>>SuSE Meta pppd (smpppd-ifcfg), Version 1.00 on linux.
>>We are disconnected.
>>trying to connect to smpppd
>>connect to smpppd
>>We are disconnected.
>>We are connecting.
>>pppd: Plugin passwordfd.so loaded.
>>pppd: Removed stale lock on modem (pid 2141)
>>pppd: --> WvDial: Internet dialer version 1.42
>>pppd: --> Initializing modem.
>>pppd: --> Sending: ATZ
>>pppd: OK
>>pppd: --> Sending: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W0
>>pppd: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W0
>>pppd: OK
>>pppd: --> Sending: ATM1
>>pppd: OK
>>pppd: --> Modem initialized.
>>pppd: --> Sending: ATDT4105464279
>>pppd: --> Waiting for carrier.
>>We are disconnecting.
>>pppd: Terminating on signal 15.
>>We are disconnecting.
>>pppd: --> Disconnecting at Thu Jul 17 21:36:27 2003
>>We are disconnected.
>>pppd died: non-normal exit
>>
>>I went back into Yast2 to check the modem configuation to make sure I
>>did it properly and it deleted the Init 3. I reentered the Init 3
>>string and tried again...still didn't work. I hear the modem dial, the
>>typical "modem noise" and then nothing. Went back into Yast2 and the
>>Init 3 input box was blank, again. Any other ideas?
>
>
> One other thing...when I went into Yast this morning to check the modem
> configuration, it had defaulted to the original Init 2 setting:
> AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
>
> This surprised me considering I changed the Init 2 and Init 3 setting
> yesterday to match the configuration through Windows 98. Any ideas?

I'm sorry Lena that I could not help, but you've got me stumped. I
don't know why Yast2 would have changed your modem settings back to the
way they were originally. And I don't know why your modem does not even
sync. with the provider. I don't have a dial-up account, so to try it
here on my laptop I looked up a local provider, got their access number,
and added it to kinternet via Yast2. Since I don't have an account I
just wanted to see if I could connect and get the login prompt. And I
do ...

pppd: --> Modem initialized.
pppd: --> Sending: ATDT*70,xxxyyyy
pppd: --> Waiting for carrier.
pppd: ATDT*70,xxxyyyy
pppd: CONNECT 115200
pppd: --> Carrier detected. Waiting for prompt.
pppd: ** Lucent APX8000 APX1.MHT.NH.G4.NET Terminal Server **
pppd: Login:
pppd: --> Looks like a login prompt.
pppd: --> Sending: dummyuser
pppd: dummyuser
pppd: Password:
pppd: --> Looks like a password prompt.
pppd: --> Sending: (password)
pppd: Request Denied

But you don't even get the "CONNECT".

I'm assuming that the phone # you dial all works ok (I notice there is
no prefix to the area code) and that if you were to dial it by hand just
as you see it in your kinternet log (i.e., "4105464279") that you'd hear
the modem on the other end answer and start to sing? I cannot think of
what else it could be.

             - Bruce



Relevant Pages

  • Re: Newbie internet connection issue
    ... Doesn't your modem have a speaker? ... Not really true - pppd doesn't send commands to the modem - it depends ... It's the ISP. ... is not searching for a login prompt. ...
    (alt.os.linux.suse)
  • Re: Modem stopped working
    ... > pppd: Plugin passwordfd.so loaded. ... > We are disconnecting. ... > Init 3 input box was blank, ... yesterday to match the configuration through Windows 98. ...
    (alt.os.linux.suse)
  • Re: Modem stopped working
    ... > We are disconnecting. ... > pppd: Terminating on signal 15. ... directly from a terminal and try issuing the commands by hand. ...
    (alt.os.linux.suse)
  • RE: [SLE] Kinternet will not connect (modem working)
    ... Here is the Kinternet log for a failure: ... SuSE Meta pppd, Version 1.06 on linux. ... trying to connect to smpppd ... Status is: disconnecting ...
    (SuSE)
  • Re: sound/modem/wine/email 8.2
    ... Using Kinternet, but looks like it calls up wvdial, too. ... SuSE Meta pppd, Version 1.00 on Georges. ... pppd: --> Initializing modem. ... We are disconnecting. ...
    (alt.os.linux.suse)