[no subject]

["Erik Brown" <erb3 ra msstate edu>]

Okay, I may have committed a cardinal sin when I purchased my new ISA 56k
modem recently for use with getting my Windows/newly-installed Linux PC
connected to the internet.

The modem works fine in Windows, but when I try to use it in Linux, it
flounders.

So, after reading page after page on modem configuration, I setup
isapnp.conf to reflect my modem setup and that came back with a positive
response.

I also placed my etc/rc.d/rc.local file the setserial command on /dev/ttyS2.

(i.e. setserial /dev/ttyS2 autoconfig irq 0)

This brings me to my first question -- usually COM2 in windows corresponds
with /dev/ttyS1, or so I've read.  In Linux, though, my modem responds (via
minicom) to /dev/modem that is symbolically linked to /dev/ttyS2.

So what's up with that?

Anyway, when minicom finally picked up and dialed and connected to my isp,
logged in and got the garbage characters transmitting, I rejoiced and
immediatly exited minicom and entered into the configurator tool to setup my
PPP connection.

Well, upon trying to connect, I did not get the desired result (i.e., the
modem didn't respond AT ALL) even though I had set up the connection based
on my minicom settings.

So, what do I need to do, since I can log in via minicom and not via PPP?

Thanks,
Erik
--
Erik Brown
Senior -- Computer Engineering
Mississippi State University
email: erb3 ra msstate edu
ICQ# 2340208
web: http://www2.msstate.edu/~erb3