Marv,
Obviously, Dante's ISP is BruinOnLine (BOL) http://www.bol.ucla.edu/
Dante does not explictly write which dialer program generated his log
(which shows that the dialer uses wvdial), not reporting further wvdial
output once the modem-to-modem connection is set up and works.
It would tremendously help if Dante would use uninterfaced wvdial
because we would see the behavior of wvdial during the clearly failing
logon procedure.
The BOL setup (Win, Mac, no Linux) instructions are hyper-standard and
leave no room for some trick which could fool a standard ppp (for
example it uses PAP, not some possibly "proprietary" variant).
My bet is that Dante's SuSE box uses a conflicting "verbessert" version
of ppp.
No doubt, Dante: use PLAIN wvdial to try to connect.
If it still fails:
Edit /etc/ppp/options
Add one line:
debug
In the following console 1 is where you use wvdial.
Create an extra console which will be console 2. Be root or use
su in console 2 (and already before in console 1).
In console 2 type exactly as shown:
tail -f /var/log/messages | tee mybug2.txt
Now go to console 1 and type:
wvdial | tee mybug1.txt
When wvdial terminates or hangs up,
go to console 2 and hit CTRL-C
If wvdial did not exit go to console 1 and hit CTRL-C
You now will have two files, mybug1.txt and mybug2.txt
Send them to us.
ADDITION: Dante, if you believe that your kppp works better except for
the NO CARRIER issue, add ATX3 in the initialization string field
available under Modem Configuration.
Jacques
Marvin Stodolsky wrote:
Dante,
My earlier email likely wasn't cogent
pppd[0]: --> Carrier detected. Waiting for prompt.
pppd[0]: --> Don't know what to do! Starting pppd and hoping for the best.
pppd[0]: Serial connection established.
This is a login protocol problem, and probably not a driver problem.
Go through the PostInstall howto at
http://132.68.73.235/linmodems/index.html
Who is your Internet Provider.
http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
might be cogent
MarvS
scanModem maintainer
On 4/10/07, Dante ZePasta <dixuaf7@xxxxxxxx> wrote:
Sorry about that. Oh - and in my main message, when I
said "desktop," I meant laptop.
Thanks again.
SuSE Meta pppd (smpppd-ifcfg), Version 1.59 on sprite.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: --> WvDial: Internet dialer version 1.54.0
pppd[0]: --> Initializing modem.
pppd[0]: --> Sending: ATZ
pppd[0]: ATZ
pppd[0]: OK
pppd[0]: --> Sending: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: OK
pppd[0]: --> Sending: ATM1
pppd[0]: ATM1
pppd[0]: OK
pppd[0]: --> Modem initialized.
pppd[0]: --> Sending: ATDT13102068311
pppd[0]: --> Waiting for carrier.
pppd[0]: ATDT13102068311
pppd[0]: CONNECT 41333
pppd[0]: --> Carrier detected. Waiting for prompt.
pppd[0]: --> Don't know what to do! Starting pppd and hoping for the
best.
pppd[0]: Serial connection established.
pppd[0]: Renamed interface ppp0 to modem0
pppd[0]: Using interface modem0
Status is: connecting
pppd[0]: Connect: modem0 <--> /dev/ttySL0