🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.linux.misc
Article #1

New Modem won't connect/Linux

#1
From: pp001356
Date: Mon, 30 Oct 1995 07:35
65 lines
2508 bytes
For several months I've been running a Linux box with a 14.4 Boca 
modem -- no problems.  Recently I duplicated the setup on a second 
pc, the only differences being that the new system has a USR 
Sportster 28.8 "plug and play" internal modem.  The new Linux 
system works fine, but the modem won't connect.  I don't think 
there's anything wrong with the modem.  It works fine under 
Windows 3.1, but not under Linux, where it's run through 
/dev/cua3.  Here's the info 'setsetial' gives on /dev/cua3:

Line 3, UART 16550a, Port: 0x02e8, IRQ 3
Buad_base: 115200, close_delay: 50, divisor 0
Flags: spd_normal	skip_test

Here's the script I'm using to attempt a connection -- identical 
to the one on my other machine except for buad_rate, 
initialization string, and the fact that I'm using /dev/cua3 
instead of /dev/cua2, which I use for the original machine.

#!/bin/sh
# 	/usr/bin/ppp-on
#	set up a ppp-link with ISP
cd /usr/lib/ppp
DEVICE=cua3

if [ -f $LOCKDIR/LCK..$DEVICE ]
then
	echo "ppp device is locked"
	exit 1
fi

fix-cua $DEVICE

/usr/lib/ppp/pppd connect '/usr/lib/ppp/chat -v "" \
"AT&F1&H1&R2&B1&K1&M4&W" OK ATDT703-904-7087\r CONNECT 'login
	pap-restart \
10 +ua /etc/ppp/pap-secrets /dev/cua3 115200 netmask 
	255.255.255.0 \
debug crtscts modem defaultroute noipdefault kdebug 2
############################################################


Here's what I see in /usr/adm/messages after the script runs:

pppd[120]: pppd 2.1.2 started by pp001356, uid 501
pppd[121]: connecting with </usr/lib/ppp/chat -v "" \ "AT&F1&H1
	&R2&B1&K1&M4&W" OK ATDT703-904-7087\r CONNECT login>
chat[136]: ATDT703-904-7087r^M^M
chat[136]: NO CARRIER^M
chat[136]: send (AT&F1&H1&R2&B1&K1&M4&W^M)
chat[136]: expect (OK)
chat[136]: AT&F1&H1&R2&B1&M4&W^M^M
chat[136]: OK^M
chat[136]: alarm
chat[136]: Failed
chat[136]: Exit

Any ideas on what's going on and whatI'm doing wrong or should do 
to get connected much appreciated.

Thanks in advance.


John Carroll
pp001356@interramp.com
Technical Details
Message-ID: <471qho$7ba@usenet1.interramp.com>
Path: arc1-ca.pugleaf.net!interramp.com!usenet

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!interramp.com!usenet
From: pp001356@interramp.com
Newsgroups: comp.os.linux.misc,comp.dcom.modems
Subject: New Modem won't connect/Linux
Date: Mon, 30 Oct 95 00:35:02 PDT
Organization: PSI Public Usenet Link
Message-ID: <471qho$7ba@usenet1.interramp.com>
NNTP-Posting-Host: ip140.herndon4.va.interramp.com
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Newsreader: NEWTNews & Chameleon -- TCP/IP for MS Windows from NetManage