SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I recently installed Slack 10.1 on a machine that has a pci modem (not a winmodem). I compiled a 2.6.10 kernel, and now kppp cannot access the modem. udev sets it up as /dev/tts/44 with a symlink to /dev/ttyS44, neither of which are available as devices in kppp. Minicom can access the modem on either of these nodes, and if I make a /dev/modem symlink to /dev/tts/44, minicom can access that as well, but when I try to access it from kppp I get an error message stating that the modem is busy. Just for laughs I tried this as root, to see if there was some issue with permissions I was missing, but I got the same error. Any suggestions?
I think that would be a symlink to a symlink, wouldn't it? I dug around some more and concluded that I made a mistake, that the modem is attached to /dev/tts/4, with a symlink of /dev/ttyS4, but that doesn't work in kppp either, it gives the error message: unable to open modem. I emailed the manufacturer of the modem (Actiontec Internal PCI Call Waiting modem, v.90), and asked if there was a compatibility problem with the 2.6 kernel. Here is the reply:
That might be possible. The modem was discontinued a couple of years ago
and no new firmwares or drivers have been written since that time.
It is quite possible it is not compatible with the 2.6 kernel as no testing
was done on that version of LINUX
So I'm going to try a new modem, and see if that changes anythin. I will post again with the results.
Well, I tried another modem, but unfortunately the one I chose is not compatible with my motherboard under Linux. I will spare you all the gorey details of how I discovered this, but both modems, the old one (Actiontec) and the new one (Stratitec model IC56A) are baced on Lucent chipsets that do not work with the Tyan 1662 dual Pentium Pro motherboard. So I'm going to go shopping for another modem.
I finally got the Actiontec modem working. It actually turned out to be on /dev/tts/14 (I have no idea why, it was /dev/ttyS4 with the 2.4 kernel) so I made a /dev/modem symlink to it, and it worked. There is a script in /etc/udev/scripts called make_extra_nodes.sh where you can put the command:
ln -s /dev/tts/14 /dev/modem
(substitute the appropriate node for your setup) and have the modem link made automatically at boot.