Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I upgraded Red Hat v7 from kernel 2.2 to 2.4 thinking that I would then be able to use my modem.
I still do not have a modem. Can someone give me a primer on what steps I have to take to be able to use my modem?
Originally posted by rdaves@earthlink.net I upgraded Red Hat v7 from kernel 2.2 to 2.4 thinking that I would then be able to use my modem.
I still do not have a modem. Can someone give me a primer on what steps I have to take to be able to use my modem?
Depends a lot on what kind of modem. PlugandPray? External?
Get the modem functional. For plug and play I use 'pnpdump > /etc/isapnp.conf' which tickles your pnp devices and makes them barf their contents to the file /etc/isapnp.conf. Check to see if you already have a file like this before you start!)
<usually> setup a link from /dev/ttySn to /dev/modem (where n is the serial tty your modem is setup as. ie: ttyS0 -> dos 'com1', ttyS1 -> dos 'com2', etc... This can make management of the device easier if you change the isapnp.conf settings.
Setup your dialer (wvdial for me). You can also play in minicom to get a command set/setup string you can live with.
Get an autodialing script if you want. (wvdial.dod in SuSE - don't know much 'bout RedHat).
Since I am a newbie at this, there's just a lot I don't know. Please profide a few more details.
-
You write:
<usually> setup a link from /dev/ttySn to /dev/modem (where n is the serial tty your modem is setup as. ie: ttyS0 -> dos 'com1', ttyS1 -> dos 'com2', etc... This can make management of the device easier if you change the isapnp.conf settings.
-
What file do I set this link up in and what are the commands?
-
Setup your dialer (wvdial for me). You can also play in minicom to get a command set/setup string you can live with.
-
I will look in my references for how to set up a dialer. Assume once I find it, it will be somewhat intuitive.
-
Get an autodialing script if you want. (wvdial.dod in SuSE - don't know much 'bout RedHat
Ditto autodialer.
-
By the way, my modem is an internal 56k, v90, 3com-USRobotics 3cp5610 plug and play.
-
In some of the stuff I have found on the net, there are suggestions to do a couple other things:
Boot up Linux and get to a terminal window. Type ‘cat /proc/pci and find the data for the serial controller. Look for Vendor id=12b9 and device id=1008. Make a note of IRQs and I/O port. Then in terminal window type ‘setserial /dev/ttySn port 0xXXXX autoconfig, where n ttySn is the com port and 0xXXXX is the I/O address specific to what you find when you type ‘cat /proc/pci’. The writer suggest that you put this setserial command at the end of thr ‘rc.local’ file.
-
Do you think this stuff is on the right track?
My modem, according to U.S. Robotics, is a 56K, Fax PCI modem (model 3CP5610-00). The driver is as follows: C:\windows\system\serial.vxd. I don't believe it is a winmodem.
Originally posted by rdaves@earthlink.net My modem, according to U.S. Robotics, is a 56K, Fax PCI modem (model 3CP5610-00). The driver is as follows: C:\windows\system\serial.vxd. I don't believe it is a winmodem.
Do a pnpdmp. 'pnpdump' > mypnp.conf and post the results. Then you'll get some suggestions.
Success! Got modem working last night. Followed process suggested in http://www.idir.net/~gromitke/3cp5610.txt. this file suggests using '/cat/proc/pci' to determine correct IRQ & I/O port plus a specific form of the setserial command. In atddition, Poul Petersen's Linux guide - Modem setup gives input on how to set up '/usr/bin/minicom'.
Now, I need:
1.) Configuration file
2.) Autodialer
3.) Configure Netscape Navigator
Any help on this?
I will post this as a new subject also.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.