Unidentified subject!
cc: David Wright <d.wright@open.ac.uk>, hawk
Subject: Re: ppp install failing (loopback?)
In-Reply-To: Message from hawk <hawk@fac13.ds.psu.edu>
of "Tue, 29 Aug 2000 13:06:07 EDT." <200008291707.e7TH67j00518@fac13.ds.psu.edu>
References: <200008291546.e7TFk9u29791@fac13.ds.psu.edu> <20000829174313.C757@tyne.open.ac.uk> <200008291707.e7TH67j00518@fac13.ds.psu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
--------
OK, here's the new data. I can dial out with minicom with no problem,
and the speaker is definitely on. PPP doesn't get as far as actually
dialing, unless it's sending a command string to silence the modem.
When, during post-reboot installation, I get as far as being asked what
method I want to use to install (immediately after configuring ppp), I
choose http. THe blue menus go away, a string of "failed to get
aaaa.bbb" type messages come in white on black, and then are instantly
replaced with the blue menu.
plog reports:
Sep 27 07:14:34 eyry pppd[225]: Connect script failed
Sep 27 07:14:35 eyry pppd[225]: Exit.
(this is the entire output).
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)
while the last 20 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.
It seems that for some reason, it doesn't get an "OK" back from the
modem in response to its "AT". However, it m must be getting one
earlier after ATZ, or it wouldn't get this far.
hawk, still baffled.
Reply to: