Intel 536ep Modem

[TheCyberDude]

Where and What do I do to get the Intel 536ep Modem to load drivers automatically.

I can install them mannualy and they work.

Intels script doesnt install correctlly on knoppix.

Thanks.........

[TheCyberDude]

Here's the Solution !

REF: http://www.justlinux.com/nhf/Distribution_Specific/Debian_GNULinux/Debian__Startup_Commands.html

1) Execute this command to find your default runlevel:
cat /etc/inittab | grep initdefault
You should see a line like this:
id:2:initdefault:
That means 2 is your default runleve. This may also be 3, or rarely 4 or 5.
2) Create your rc.local file like this (as root):
touch /etc/init.d/rc.local
chmod 774 /etc/init.d/rc.local
3) Set it to be run at boot time by doing this:
ln -s /etc/init.d/rc.local /etc/rcX.d/S99local
Replace the X with your default runlevel from step one. For example, rc2.d.
4) Edit your /etc/init.d/rc.local scrip


Below is my rc.local ....

# Install Intel Modem Drivers & Set Permissions
chmod a+rw /dev/modem
chmod a+rw /dev/ttyS2
cd /lib/modules/2.4.20-xfs/kernel/drivers/char
insmod -f 536epcore.o
insmod -f 536ep.o

NOTE: ttyS2 is for COM3 - Insert your COM

[TheCyberDude]

UPDATE!!!

# Install Intel Modem Drivers & Set Permissions
su -c "chmod a+rw /dev/Modem"
su -c "chmod a+rw /dev/ttyS2"
cd /lib/modules/2.4.20-xfs/kernel/drivers/char
insmod -f 536epcore.o
insmod -f 536ep.o

Must use su -c to get Root and chmod .

I tried setting 1777 for /dev/modem from an terminal,
but after rebooting - the sticky bit was gone.

The above take's care of the problem.

Good Luck ...

[Loper]

Thanks for taking the time to post the solution to your own problem. I think we all appreciate it when people share in this way. Can this be added to the documentation (if it's not already there)? This is a popular modem.

[garyng]

just curious, why not just add the modules to be loaded to /etc/modules ? Every module in that file would be loaded automatically on boot.

As for the permission setting, I believe /dev/ttyS2 needs to be set only once and /dev/modem is usually just a symbolic link to whatever device(/dev/ttyS2 in this case) and I don't think permission on it really matters.

Also, since this is running under INIT, 'su' may not be needed as INIT is run under root(or can it be configured to run under some other user ID).

[TheCyberDude]

Another update:

You can put : #Install Intel Modem Drivers & Set Permissions
su -c "chmod a+rw /dev/modem"
su -c "chmod a+rw /dev/ttyS2"
cd /lib/modules/2.4.20-xfs/kernel/drivers/char
insmod -f 536epcore.o
insmod -f 536ep.o

in /etc/init.d/bootmisc.sh (Instead of creating an rc.local).

My drivers always load, but I have to go into konsole an su
chmod a+rw /dev/modem.