I just checked through windows, interrogating the modem:
US Robotics 56K FAX INT PnP
Identifier *USR3031,ISAPNP\USR3031
Port: COM3
Interrupt: 10
Addr 3E8
My impression is that under Linux, the modem is not responding at all (of
course I am using it to communicate here), so I take it that I have some
mismatch in the setup, etc
I also had a second winmodem installed and physically removed it to avoid
any potential of a conflict/confusion
As per below, I changed the reference to S2 for COM3, changed the nameserver
entries in /etc/resolv.conf (although that should not affect dialtone)
I assume the settings in Windows are the same for Linux, but perhaps I
should run a little experiment, trying S0 and S1
I will check out minicom
David
----- Original Message -----
From: Chris Bennett <[EMAIL PROTECTED]>
To: 'davidturetsky' <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, August 02, 2000 1:42 PM
Subject: RE: Chat/ppp
> David,
>
> Try using minicom, make sure you are using the correct com port,
> does your modem respond to An AT command?
>
> > -----Original Message-----
> > From: davidturetsky [SMTP:[EMAIL PROTECTED]]
> > Sent: Wednesday, August 02, 2000 6:06 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Chat/ppp
> >
> > Well, I checked everything... including making sure I did not have the
> > winmodem inadvertently installed. I also corrected the nameserver
entries,
> > although this should not prevent me from getting a dialtone
> >
> > The chatlog given below is accurate and only omits "pppd[484]: pppd
2.3.5
> > started by root uid0" and ends with "pppd[484]: Exit."
> >
> > I then went in and ran pppconfig (again) followed by pon
> >
> > This is what the chatlog showed:
> >
> > Aug 2 14:07:58 debian pppd[258]: pppdd 2.3.5 started by root, uid0
> > chat[259]: abort on (BUSY)
> > chat[259]: abort on (NO CARRIER)
> > chat[259]: abort on (VOICE)
> > chat[259]: abort on (NO DIALTONE)
> > chat[259]: abort on (NO ANSWER)
> > chat[259]: send (ATZ^M)
> > chat[259]: expect (OK)
> > chat[259]: alarm
> > pppd[258]: Connect script failed
> > chat[259]: failed
> > pppd[258]: Exit
> >
> > As I recalled, when I first installed debian last year I used pppconfig
> > and
> > then pon (but with the wrong nameservers) and got dialtone and some
dialog
> > before the server disconnected, but now... no dialtone, no chance for
MSN
> > to
> > even kick me off!
> >
> > David
> >
> > ----- Original Message -----
> > From: Ray Olszewski <[EMAIL PROTECTED]>
> > To: davidturetsky <[EMAIL PROTECTED]>;
> > <[EMAIL PROTECTED]>
> > Sent: Wednesday, August 02, 2000 9:02 AM
> > Subject: Re: Chat/ppp
> >
> >
> > > At 02:08 AM 8/2/00 -0700, davidturetsky wrote:
> > > >I changed the ln entry per Mike's suggestion:
> > > >
> > > >My chat log now reads:
> > > > pppd[155]: Connect script failed
> > >
> > > The connect script you posted looks okay, but there is no way to tell
> > for
> > > sure without knowing WHY it failed. Could be a hidden typo,
> > incompatibility
> > > with what the ISP wants, modem problems, ... or something else I'm not
> > > thinking of offhand.
> > >
> > > Surely the above line is not the ONLY log entry; chatscripts will log
> > their
> > > own results is for run chat with the appropriate flag (I think -v).
Tey
> > > again, and this time be sure to get chatscript log output.
> > >
> > >
> > > --
> > > ------------------------------------"Never tell me the odds!"---
> > > Ray Olszewski -- Han Solo
> > > Palo Alto, CA [EMAIL PROTECTED]
> > > ----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
