On all but the most 'standard' distros, the average 536ep driver installation is not able to properly install the startup scripts needed to set up the driver after reboot.
There are a number of ways around this, most of which are a different means to the same end. Here's the way I do it: in my /etc/rc.local file, I have the following lines:
Code:
KERNEL=`uname -r`
if [ -e /lib/modules/$KERNEL/kernel/drivers/char/Intel536.ko ]; then
modprobe Intel536
ln -s /dev/536ep0 /dev/modem
mknod /dev/ppp c 108 0
fi
Though you could have this in almost any one of your init scripts. What it does, is:
1 - checks if the 536ep module exists in lib/modules
2 - if it does, insert it, then create the /dev/modem symlink to it's device node, and finally create the /dev/ppp node required for the pppd to function.
I'm not sure what init system Mepis uses (either SystemV or BSD style or what..) but this idea should work for pretty much any linux.
Looks like you would need to adjust the path within /lib/modules, as yours is in /misc, whereas mine is in /char.
Also, if your /dev/modem and /dev/ppp nodes are already there, you can omit that part.
NOTE: 'insmod' is for 2.4 kernels, while 'modprobe' is for 2.6 kernels.
Intel536ep modem lost on reboot
Problem Solved
