Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!mimbres.cs.unm.edu!tesuque.cs.sandia.gov!lynx.unm.edu!nntp.sunbelt.net!udel!MathWorks.Com!panix!not-for-mail
From: wpaul@panix.com (Bill Paul)
Newsgroups: comp.os.386bsd.questions
Subject: Re: FreeBSD 1.1.5.1 install: dialing out
Date: 26 Jul 1994 14:44:09 -0400
Organization: The M00se Illuminati (bl00p!)
Lines: 126
Message-ID: <313lhp$58f@panix3.panix.com>
References: <CtJC2u.GG5@netnews.asu.edu>
NNTP-Posting-Host: panix3.panix.com
X-Newsreader: TIN [version 1.2 PL2]
Daring to challenge the will of the almighty Leviam00se,
Dan McGuirk (mcguirk@enuxsa.eas.asu.edu) had the courage to say:
: I'm trying to install FreeBSD 1.1.5.1. I've installed the three
: floppies, and now I'd like to get SLIP running and FTP the rest of the
: distribution. Unfortunately, I can't seem to dial out. I have a USR
: Sportster 14.4 internal on port 0x2e8, IRQ 5. FreeBSD detects my
: other serial ports when it boots, but doesn't seem to notice this one.
: What steps do I need to take to access my modem?
: Sorry for posting what certainly must be a frequently asked question,
: but it's not mentioned in any of the (sparse) documentation on
: ftp.cdrom.com.
Unfortunately, the serial ports are hardwired in the kernel to certain
I/O address/IRQ combinations. In the GENERICAH and GENERICBT kernels,
those combinations are as follows:
sio0: 3F8 (COM1) IRQ4
sio1: 2F8 (COM2) IRQ3
sio2: 3E8 (COM3) IRQ5
sio3: 2E8 (COM4) IRQ9
As you can see, your Sportster is not currently set up to match any
of these settings. 3E8/IRQ5 is valid, but 2E8/IRQ5 is not. Unless you
already have a serial port at the COM3 address, I would suggest
configuring the Sportster to 3E8/IRQ5 and trying it that way. If you do
have a serial port already active at that location, disable it, at least
until you can get the system installed and can build yourself a new
kernel with custom port/IRQ settings.
Now, after you get the modem configured correctly, *PLEASE* don't
try to dial out using /dev/ttyd2. Use /dev/cua02 instead, otherwise
you'll just wind up coming back here and asking why all your comm
programs hang whenever you try to access /dev/ttyd2, and we'll have
to go through the serial port FAQs again. :) Use /dev/cua02 for
dialing out, and use /dev/ttyd2 for dialing in. (See /etc/ttys and
you'll see what I'm talking about.)
Assuming you get the modem set up on COM3 (3E8/IRQ5), you will
in fact want to use /dev/cua02. This device should already exist under
/dev in the standard distribution. If not, cd to /dev and type:
# ./MAKEDEV cua02 (or cua00 or cua01 or whichever one you want)
Don't be a wiseguy and leave out the ./ part: you need that. :)
After that, try the following:
# cu -l /dev/cua02 -s 38400
That should connect you to the modem. If cu isn't included in the
basic installation (I can't remember for sure, actually) of if you
want to use tip instead, do the following:
# touch /etc/remote
# echo "cua02|modem:dv=/dev/cua02:br#38400" >> /etc/remote
# tip cua02
(For paranoia's sake, make sure that the directory /var/spool/lock
exists so tip and cu can create their lockfiles properly, otherwise
they'll bitch & moan at you.)
Now you can dial the modem with AT commands. Connect to your provider,
log in, and get SLIP running. When you're ready, suspend cu (or tip)
into the background by pressing 'RETURN' a few times, they typing
the following:
~z (That's tilde followed by a lowercase z)
While you're running tip or cu, you can get a list of available
'tilde' commands by typing: ~?
Once you're back at the shell prompt, do the following:
# ifconfig lo0 127.0.0.1
# ifconfig sl0 your.machine's.ip.address your.server's.ip.address up
# route add default your.server's.ip.address
# route add your.machine's.ip.address 127.0.0.1
# slattach -a -h -s 38400 /dev/cua02
You should now be connected to the Internet. Try to ping a known IP
address to test the link.
A few things: at this point, you don't have any name resolution, which
means you must specify IP addresses rather than hostnames if you expect
to get anywhere. If you have the address of your service provider's
nameserver, you can do the following:
# rm -f /etc/resolv.conf
# cat > /etc/resolv.conf
nameserver ip.address.of.nameserver
domain my.machine's.domain
^D <- that's a CTRL-D
#
For now, you might want to just write down the IP addresses of some
important machines and keep them handy for when you're doing
the installation. You can set the rest of the system up properly later.
Another cute trick to do, if you don't care about wasting bandwidth,
is to NFS mount an FTP site that has the distribution on it and
extract everything directly over the net. This can take a long time,
especially using SLIP, but it will work. (The people at DEC may kill
me for saying this, but the best place to do this with is
gatekeeper.dec.com. Don't tell 'em I said that. :) Once you have
the NFS filesystem mounted, cd to the directory where the bindist
tarballs are and type:
# set_tmp_dir
# extract bin
You can then go off and watch a baseball game or two while the installation
completes. :)
Hope this helps.
-Bill
--
_ /\ _ Join the
/ \_/\_/ \_/\_/ \ .----. M00se Illuminati Bill Paul
\_____/ () \_____/ (bl00p!) Face it: wouldn't <Big City M00se>
/ \ `----' you feel much wpaul@panix.com -or-
/ \__/ \ --' safer? ghod@drycas.club.cc.cmu.edu
/__________\