Just re-installed LINUX 6.0 (RH) on my home PC. Cannot get it to recognize my modem.

1. Installed the modem on COM4 (Works under W95)
2. In Linux used control panel to link to TTYS3 for /modem
3. From root ran minicom -s to create a minicom config
4. Tried to use kppp, but it tells my my modem is busy. No matter how I try to access my modem it tells me it
is busy

Any one else had this problem? From my search on dejanews and here I would have to say yes, however I have found no answers.

Please help. I will post the answer when I find it.

Try going to;

http://www.o2.net/~gromitkc/winmodem.html

and insure its not a winmodem. Winmodems are not real modems and thus don't work with Linux. For Linux I've always got the best results from external modems.

Have Fun :-)
Sterling

Thanks for your reply silverwolffe. I have looked through all of the documentation on my modem. It is an internal Viking PCI V.90 modem. No where in the documentation or on the box does it indicate it as being a WinModem which is why I bought it over a USR WinModem on sale. I knew I would not be able to use it with Linux. I also went to a compatibility list that I found on www.deja.com and found my make and model there. I don't know how reliable the list was as it looked like a private/personal page. I even tried using mknod to create a new ttyS4 and setserial to set it to the IRQ that it is set to in Windows (11 -- Seemed strange to me). I've gone into minicom and checked all of my settings, deleted and recreated ttyS3 (COM4) where Windows says my modem resides. I am at my wits end. Someone, anyone give me a new suggestion (short of buying a new modem)

Thanks,
Natr

Two things.
First, ensure you have PPP configured.
Type `pppd' at the command prompt and see if you get garbage on the screen (it stops after a bit). If you do then go to second step, if not you will need to install PPP and recompile the kernel.

Second, I got this from someone after trying to connect unsuccessfully for three days, it worked first try.

This is what I used from my ISP and it worked good. Now all I have to
do is type ppp-on and boom, Im connected!!!

System Requirement : PPP Daemon (pppd-2.1.2 or higher)
You will need to create the following files to
connect to us:

/usr/sbin/ppp-on
/etc/ppp/options
/etc/ppp/ppp-dialer
/etc/ppp/pap-secrets

/usr/sbin/ppp-on:
#!/bin/sh
echo "Enter the number to dial: "
read NUMBER

export NUMBER
/usr/sbin/pppd


/etc/ppp/options:
lock
domain wt.net
ipcp-accept-local
ipcp-accept-remote
connect /etc/ppp/ppp-dialer
crtscts
defaultroute
debug
modem
/dev/ttyS3
#Change /dev/ttyS3 to your modem port
# /dev/ttyS0 is COM1:
# /dev/ttyS1 is COM2:
# /dev/ttyS2 is COM3:
# /dev/ttyS3 is COM4:
38400
noipdefault
#Change bogus to your username
user bogus


/etc/ppp/ppp-dialer:
#!/bin/sh
# Some of the following lines contain
# ' and " for quoting. Please note
# that both are made with the ' symbol
# Please do not use the "Shift
# apostrophe" Key to make the " symbol
# Just hit the ' key twice.
# The OK "ADTD $NUMBER" \ line
# DOES use the Shift apostrophe key
# for the quotes


/usr/sbin/chat -v \
ABORT BUSY \
ABORT 'NO CARRIER' \
TIMEOUT 60 \
'' ATZ \
OK 'AT+FCLASS=0' \
OK 'AT&F&C1&D2' \
OK "ATDT $NUMBER" \
CONNECT

/etc/ppp/pap-secrets:
# Change "bogus" to your username and
# "bogus_password" to your password in clear text

bogus * bogus_passwd

/etc/resolv.conf:
domain wt.net
nameserver 205.230.159.9
nameserver 205.230.159.7

Connecting to us:
Make sure some file permission is set
correctly by executing the following command:
$ chmod a+x /etc/ppp/ppp-dialer /usr/sbin/ppp-on

Make sure you have
/usr/sbin/pppd and
/usr/sbin/chat binary
executables.

Then type in the following:
$ /usr/sbin/ppp-on
Enter the phone number to dial:
713-843-6878

To Check to see if you are connected:
$ tail /var/log/messages
(you will see messages from the pppd)

Goodluck!


Have Fun :-)
Sterling

I'll give it a shot.

Thanks

make sure you don't have a modem lock file somewhere it will be a hidden file in your home directory.

lordos2: Thanks. The problem turned out to be a packaging problem on the part of Viking. They were selling their 56k software modem as DSP modems, instead of clearly marketing them as WinModems. My own fault I suppose.

War...

hi there, sorry about interrupting, but i'm glad i read this one... thanks guys... you may have solved a problem i'v had for ages....

C-ya...

Karl

Good Luck mckarl

not tried it yet, still tied down... need som....zzzZZZZZ