Unidentified subject!
Subject: Re: ppp install failing (loopback?)
In-Reply-To: Message from David Wright <d.wright@open.ac.uk>
of "Tue, 29 Aug 2000 17:43:13 BST." <20000829174313.C757@tyne.open.ac.uk>
References: <200008291546.e7TFk9u29791@fac13.ds.psu.edu> <20000829174313.C757@tyne.open.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
--------
I thought I sent this earlier, but it doesn't seem to have arrived . . .
I've installed minicom, and can successfully dial out with it. The
speaker works, so I can hear a dial.
After configuring ppp during initial setup, i choose the http option
for installation method. The blue menu system goes away, and a bunch
of apt-get fails splat down the screen, and are covered by the dialog
system again immediately before they can be read. The system never
dials; the failure is immediate.
plog reports the grand total of:
Sep 27 07:14:34 eyry pppd[225]: Connect script failed
Sep 27 07:14:35 eyry pppd[225]: Exit.
the last 20 lines of /var/log/syslog are
Sep 27 07:13:03 eyry kernel: PPP: version 2.3.7 (demand dialling)
Sep 27 07:13:03 eyry kernel: PPP line discipline registered.
Sep 27 07:13:03 eyry kernel: registered device ppp0
Sep 27 07:13:03 eyry pppd[225]: pppd 2.3.11 started by root, uid 0
Sep 27 07:13:04 eyry chat[232]: abort on (BUSY)
Sep 27 07:13:04 eyry chat[232]: abort on (NO CARRIER)
Sep 27 07:13:04 eyry chat[232]: abort on (VOICE)
Sep 27 07:13:04 eyry chat[232]: abort on (NO DIALTONE)
Sep 27 07:13:04 eyry chat[232]: abort on (NO DIAL TONE)
Sep 27 07:13:04 eyry chat[232]: abort on (NO ANSWER)
Sep 27 07:13:04 eyry chat[232]: send (ATZ^M)
Sep 27 07:13:04 eyry chat[232]: expect (OK)
Sep 27 07:13:25 eyry kernel: VFS: Disk change detected on device fd(2,0)
Sep 27 07:13:49 eyry chat[232]: alarm
Sep 27 07:13:49 eyry chat[232]: send (AT^M)
Sep 27 07:13:49 eyry chat[232]: expect (OK)
Sep 27 07:14:34 eyry pppd[225]: Connect script failed
Sep 27 07:14:34 eyry chat[232]: alarm
Sep 27 07:14:34 eyry chat[232]: Failed
Sep 27 07:14:35 eyry pppd[225]: Exit.
while the last 20 lines of /var/log/messages are
Sep 27 07:11:12 eyry kernel: kernel build: 2.2.17 unknown
Sep 27 07:11:12 eyry kernel: options: [pci] [cardbus] [apm]
Sep 27 07:11:12 eyry kernel: Intel PCIC probe: not found.
Sep 27 07:11:12 eyry kernel: ds: no socket drivers loaded!
Sep 27 07:13:03 eyry kernel: CSLIP: code copyright 1989 Regents of the University of California
Sep 27 07:13:03 eyry kernel: PPP: version 2.3.7 (demand dialling)
Sep 27 07:13:03 eyry kernel: PPP line discipline registered.
Sep 27 07:13:03 eyry kernel: registered device ppp0
Sep 27 07:13:03 eyry pppd[225]: pppd 2.3.11 started by root, uid 0
Sep 27 07:13:04 eyry chat[232]: abort on (BUSY)
Sep 27 07:13:04 eyry chat[232]: abort on (NO CARRIER)
Sep 27 07:13:04 eyry chat[232]: abort on (VOICE)
Sep 27 07:13:04 eyry chat[232]: abort on (NO DIALTONE)
Sep 27 07:13:04 eyry chat[232]: abort on (NO DIAL TONE)
Sep 27 07:13:04 eyry chat[232]: abort on (NO ANSWER)
Sep 27 07:13:04 eyry chat[232]: send (ATZ^M)
Sep 27 07:13:04 eyry chat[232]: expect (OK)
Sep 27 07:13:49 eyry chat[232]: alarm
Sep 27 07:13:49 eyry chat[232]: send (AT^M)
Sep 27 07:13:49 eyry chat[232]: expect (OK)
It looks to my inexperienced eye like the modem is responding "OK" to
the ATZ, but never responds to the following AT.
ANd now that I think ofit, why should it send a simple AT??? SHouldn't
it send a command that *does* something instead? :)
hawk, still perplexed
--
Reply to: