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 just moved to kernel 2.6.7 under Slack 10.0. Now, I'm using the same drivers for my winmodem that I used under 2.4 (ltmodem). The installation goes smoothly and everything works. However, when I reboot the computer and try to connect to the internet via kppp it says that the /dev/modem link doesn't exist (the driver installation creates one and points it to /dev/ttyLT0). So basically, I gotta reinstall the driver to get my Internet up. Where's the problem?
I found out that the modules do load correctly (I see them in lsmod). Now, when kppp complains about the missing /dev/modem file, I found out that the file that it suppose the point to doesnt exist either (/dev/ttyLT0, created during installation)
And yeah, I do have to reinstall, since /dev/ttyLT0 is nowehere to be found.
Ok, here's what I found late last night. when I modprobe lt_serial, it creates the dev ttLTM0. Which according to what I read is what udev does. When a module is loaded, it creates the node for the device and names it what it feels it should be called. So I went into /etc/udev/rules.d and edited the udev_rules file(can't remember the exact name, I'm at work on a Win box right now) at the end I added KERNEL="$udevroot/ttLTM0" SYMLINK="$udevroot/modem" Again that variable $udevroot is probably not the exact name, but look at the udev rules above it to see what the exact variable name is. When udev creates the ttLTM0 node after the modprobe, it will slide through these rules and create the symlink modem to that node. You should then be able to use whatever ppp dialer you want. That's a halfway solution basically. You just have to modprobe the driver, wait like a second or two and then dial in. I guess the issue is with hotplugging. It doesn't recognize the device and so doesn't create the node at boot time. I think that's the issue. Workarounds could be installing of the drivers at boot, or creation of the node by the extra node script in /etc/udev/scripts. I feel there is a more elegant solution possibly, but I don't know what it is, yet.