LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   /dev/modem dissapearing after reboot. (http://www.linuxquestions.org/questions/slackware-14/dev-modem-dissapearing-after-reboot-213160/)

naijin 08-03-2004 11:56 PM

/dev/modem dissapearing after reboot.
 
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?

Cedrik 08-04-2004 03:00 AM

Did you try add /sbin/modprobe lt_serial in /etc/rc.modules ?

Also, try to copy the alias and modules parameter from /etc/modules.conf to /etc/modprobe.conf

adz 08-04-2004 07:02 AM

Do you really have to reinstall the driver or just recreate the modem symlink?

naijin 08-04-2004 09:35 AM

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.

maxheadroom 08-04-2004 11:52 AM

I'm having the same issue too. /dev/modem and /dev/ttyLT0 vanish after reboot. The modules load fine(per dmesg). Is there some udev trick or something?

adz 08-05-2004 09:13 AM

How about if you just try a MAKEDEV ttyLT0 as root from the /dev directory. What does that do?

naijin 08-05-2004 11:53 AM

command not found :(

maxheadroom 08-05-2004 12:06 PM

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.

adz 08-05-2004 07:13 PM

You should be able to add the module to /etc/modules, then. That should blindly load it at boot time.

Quote:

command not found
Try a ./MAKEDEV, then.

naijin 08-06-2004 10:18 AM

My both /etc/modules.conf and /etc/modprobe.conf have the same stuff inside them.

alias /dev/modem lt_serial
alias char-major-62 lt_serial
alias /dev/tts/LT0 lt_serial

So, what exactly should I add here? :scratch:

adz 08-06-2004 08:46 PM

No, just /etc/modules with no extension. In there, just add the name of the modules as you would to the modprobe command.

afreitascs 08-07-2004 01:41 PM

#chmod -x /etc/rc.d/rc.udev

:) ;)


All times are GMT -5. The time now is 03:30 AM.