LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-11-2003, 09:48 PM   #1
Viper
Member
 
Registered: Jul 2002
Location: Kalispell, Montana
Distribution: Slackware Linux "ONLY"
Posts: 168

Rep: Reputation: 30
Cool How to configure modem for dialup?


I've been using a conexant HCF modem with mandrake, now I've got Slackware back up and running, after deleting mandrake, I rpm2tgz the mandrake modem drivers, then installed them without any problems, and it won't dialup, any suggestions, will the mandrake drivers not work correctly.
 
Old 10-11-2003, 10:26 PM   #2
egh128
Member
 
Registered: Mar 2002
Location: Asheville, NC
Distribution: Slackware
Posts: 257

Rep: Reputation: 30
The drivers aren't Mandrake specific so they should work.
 
Old 10-11-2003, 10:35 PM   #3
Viper
Member
 
Registered: Jul 2002
Location: Kalispell, Montana
Distribution: Slackware Linux "ONLY"
Posts: 168

Original Poster
Rep: Reputation: 30
You know what, I'm glad that I fried Slackware, when installing, I made the error of selecting a modem on com2 not a pci modem, I thought it meant if this were windows, what com port would it be on. Once again, the problem was in the seat not in computer!

Thanks that still verifys what I was thinking, that it should work, especially since it installed without any problem...
 
Old 10-12-2003, 01:26 AM   #4
Viper
Member
 
Registered: Jul 2002
Location: Kalispell, Montana
Distribution: Slackware Linux "ONLY"
Posts: 168

Original Poster
Rep: Reputation: 30
ok, I'm back up and running, once again the drivers install with no problem at all, but when I use KPPP it jsut says modem is busy.
one thing I did notice was that when I installed Slackware, it asked to setup modem, I selected yes, then the first PCI modem available was on TTYS4, KPPP only goes up to TTYS3, would this be part of the problem? and how do I get around this?
 
Old 10-12-2003, 04:36 AM   #5
Viper
Member
 
Registered: Jul 2002
Location: Kalispell, Montana
Distribution: Slackware Linux "ONLY"
Posts: 168

Original Poster
Rep: Reputation: 30
could it be a problem that I installed these drivers by doing:
installpkg modemdriver.i586.tgz
 
Old 10-12-2003, 03:33 PM   #6
shepper
Member
 
Registered: Mar 2003
Location: Dry, Dusty and Conservative
Distribution: OpenBSD, Debian Wheezy/Jessie
Posts: 449

Rep: Reputation: 33
The conexant HCF modem is a winmodem aka software modem. Software based modems are cheap to manufacture and can implement new protocols with changes in the software. They put more of a load on your CPU and require a driver. It relies on software (the driver) to have the cpu do some of the work of a modem connection. In contrast, a hardware modem goes straight to the com port or in linux /dev/ttyS* where * the number of your port.

The software for conexant modems used to be free but within the last month or so the developer has begun to charge $15 US for the full featured driver. A crippled version of the driver with a limited connect speed is free and the previously free driver that connected at 56K has been removed from the website. The drivers for most software modems are propriatary and are usually made by a programer within the chipset company. They either give (Lucent/Agere) or sell (Conexant) it to a linux developer who usually writes a script that compiles and installs the driver for you.

I suspect that you used a mandrake specific rpm file to load the Conexant HCF modem driver.
In slackware you have to make the package yourself: extra work but you lean about your system and the package is then optimized for your system. If you are trying to link /dev/modem to a /dev/ttyS* port you did not install the Conexant driver which is /dev/ttyHCF

You have a couple of choices 1) Buy the driver 2) Use the crippled driver 3) Get someone to email you the the older 56K tarball 4) Get a new modem and if money is an issue I would recommend a software modem based on the Lucent/Agere LTmodem chipset as full featured drivers are available for free (at the time this was written). If you have the money and it looks like you will be using dial-up for a long time I would consider getting a hardware modem like a US Robotics Performance Pro (PCI slot = /dev/ttyS4) or an external serial port hardware modem.

Personally, I would use a lucent/agere based modem for the following reasons.
1) We vote for linux support with our money. Lucent/Agere modems cost about $10.00,
which is about $1 more than conexant modems. That $1 comes back to you in the
form of a free driver. Lucent/Agere modems also support fax like the conexant
modems.

2) Modems will someday be a relic. Why spend $50-80 on a topline hardware modem
when it will gather dust when you move to broadband?

3) New CPUs can generally handle the increased load a software modem presents without
a noticable decrease in performance.
 
Old 10-12-2003, 04:05 PM   #7
Viper
Member
 
Registered: Jul 2002
Location: Kalispell, Montana
Distribution: Slackware Linux "ONLY"
Posts: 168

Original Poster
Rep: Reputation: 30
Well I just happen to have a US Robotics Modem ( U.S. Robotics 56k Fax INT PNP ) sitting in another computer / Server that I won't need for that computer, it would take me a only a minute to shut'em down swap modems & install. What does it take to get a US Robotics modem running in Slackware?

As you mentioned /dev/ttyHCF, this is interesting, I did notice when in mandrake in the dialoge GUI ppp setup it recognized the modem only under /dev/modem, I don't know how to set it up under /dev/ttyHCF, please explain before I install the us robotics modem, this may be what I'm missing.

should I uninstall these drivers, then attempt to ./configure, make, makeinstall?

Last edited by Viper; 10-12-2003 at 04:36 PM.
 
Old 10-12-2003, 08:20 PM   #8
shepper
Member
 
Registered: Mar 2003
Location: Dry, Dusty and Conservative
Distribution: OpenBSD, Debian Wheezy/Jessie
Posts: 449

Rep: Reputation: 33
Look in your /dev file with the command "ls -al /dev | less". Use the cursor keys to get to /dev/modem. If the conexant driver is installed you should see that /dev/modem is linked to the conexant driver. Usually the linux driver installers scan for the device and if they do not find it do not install it. If that is the case then /dev/modem will be linked to a /devttyS* port. The other thing the linux driver installers do is write to your modules.conf file which loads the modem drivers on demand. Use "less /etc/modules.conf" to look at the file.

The other thing to do is to check the US robotics modem. US robotics did make some software based modems.

What was the output of the lspci command?
 
Old 10-12-2003, 10:16 PM   #9
Viper
Member
 
Registered: Jul 2002
Location: Kalispell, Montana
Distribution: Slackware Linux "ONLY"
Posts: 168

Original Poster
Rep: Reputation: 30
it is like these directorys do not even exist, ther is nothing there, it shows ?? lines and a blank black screen...
 
Old 10-12-2003, 11:02 PM   #10
shepper
Member
 
Registered: Mar 2003
Location: Dry, Dusty and Conservative
Distribution: OpenBSD, Debian Wheezy/Jessie
Posts: 449

Rep: Reputation: 33
The /dev files have to exist. It is OK for your modules.conf to be empty. An empty modules.conf file means the modem drivers were not installed probably because they were for the wrong modem card.

You really need to post either the output of your lspci command or the chipset on the modem cards if you want to get anywhere with this. (your first post said LUCENT) but you tried to install a CONEXAMT HCF driver. You can not use a Conexant driver for a Lucent modem.

You can try the US robotics modem but not all US robotics modems are hardware modems and if your US robotic modem is a software modem you would be better sticking with the Lucent modem for which there is a free, well supported, self compiling and installing driver.

Last edited by shepper; 10-12-2003 at 11:04 PM.
 
Old 10-13-2003, 01:11 AM   #11
Viper
Member
 
Registered: Jul 2002
Location: Kalispell, Montana
Distribution: Slackware Linux "ONLY"
Posts: 168

Original Poster
Rep: Reputation: 30
Sorry about the confusion, I just was frusterated and didn't realize that I did that, ( mentioned other modems ) I pulled the card and double checked, is what I did was found out when I had mandrake, I found out it is indeed the HSF modem, I do have the drivers for that, but appears that they are mandrake specific before I shortened the name it ended mdk.i586.tar.gz, I shortened the name and turned it into modem.i586.tgz. So today I downloaded the source code files on this computer and emailed them to my work so I can burn that onto cd tomorrow, Slackware doesn't like my floppy disks for some reason. also I mistakenly thought that the lspci output was supposed to be the output of the either the
"ls -al /dev | less" or the "less /etc/modules.conf" command
anyway I just thought I'd just now try the "lspci" command and I won't retype it all, but this is 8th line down:
00:11.0 Communication Controller: Rockwell International HSF 56k Data/Fax/VoiceModem (rev 01)

I also found out that my us robotics modem doesn't have much hope, seems by model number to be another software modem and looks to be totally unsupported, it's also an oldie, even has jumpers on it, I am a certified hardware tech, so that's no problem, actually sometimes easier to deal with in a windows world.

I tried to rebuild these drivers but it said I needed isapnptools, so I emailed those also thinking that I may still need them for the source code, if I must go that route.

Would you recommend that I uninstall the mandrake drivers and then build my own from source, then install those drivers? I think this makes sense because like you said, it should then be optimized for my system. unless alybody already has the precompiled drivers they could email me at: bsurfin@hotmail.com

I really don't care if I need to use the crippled drivers for now, for the HSF modem, since in december I'm getting DSL, my router keeps it alive and Slackware just loves my Linksys network card, that is as easy to setup as it gets...

Last edited by Viper; 10-13-2003 at 01:38 AM.
 
Old 10-13-2003, 10:50 AM   #12
shepper
Member
 
Registered: Mar 2003
Location: Dry, Dusty and Conservative
Distribution: OpenBSD, Debian Wheezy/Jessie
Posts: 449

Rep: Reputation: 33
It would be neat to get the 56K driver. If I remember correctly It was OK to redistribute the driver as long as it was not altered.

There was a problem with some conexant modems reporting themselves incorrectly with the lspci command. I can not remember if some hsf modems reported themselves as hcf modems but really needed the hsf driver or vice vesa. If the HCF driver worked in mandrake that is probably the one to try first..

I helped a friend setup a conexant modem and he has the drivers on floppy. I won't be able to get to them until tonight and then could email them them to you. If you are in a hurry you might post to see if someone who has them sitting on their HD can email them to you. There are some security issues with opening email attachments which I will leave for you to decide.

The link below is is basically a set of install instructions for conexant modems

Previous posts on Conexant Modem in Slackware
 
Old 10-13-2003, 11:24 PM   #13
Viper
Member
 
Registered: Jul 2002
Location: Kalispell, Montana
Distribution: Slackware Linux "ONLY"
Posts: 168

Original Poster
Rep: Reputation: 30
I'm not in that big of a hurry, that would be great, thanks, and I'll try the link, thanks again...
 
Old 10-14-2003, 01:45 AM   #14
Viper
Member
 
Registered: Jul 2002
Location: Kalispell, Montana
Distribution: Slackware Linux "ONLY"
Posts: 168

Original Poster
Rep: Reputation: 30
I installed the crippled source driver with make install, and I got the modem to dial up, connect, but then I get error: Timeout expired while waiting for the pppd interface to come up!

How can I uninstall this driver, it doesn't come up with KPackage ?
 
Old 10-14-2003, 01:55 AM   #15
shepper
Member
 
Registered: Mar 2003
Location: Dry, Dusty and Conservative
Distribution: OpenBSD, Debian Wheezy/Jessie
Posts: 449

Rep: Reputation: 33
You also need to run hsfconfig if it is an hsf modem and I think hcfpciconfig if it is an hcf modem.. It should be in the install instructions in the build directory. My friend is out of town. I can't get the 56k driver just yet.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
External dialup modem philipjm Linux - Newbie 3 04-02-2005 10:57 AM
Dialup Modem rinku Linux - Newbie 2 03-11-2005 05:10 PM
Dialup modem detection. sixth_sense Linux - Networking 1 04-24-2004 08:56 AM
how to configure my lan to dialup on demand with squid?? TAAN Linux - Networking 0 12-10-2003 05:21 AM
Route dialup modem packets back through dialup instead of default route cable modem jogress Linux - Networking 1 10-21-2003 04:48 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:13 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration