Davicom Tulip 'net card in Etch

Red Knuckles · 12-19-2006, 07:48 PM

I am very new to Debian, just installed Etch yesterday. I have the Davicom Tulip Ethernet Card. It uses one of 2 drivers tulip and dmfe. Debian loads tulip by default which doesn't work. To fix manually you run:

#rmmod tulip
#rmmod dmfe
#modprobe dmfe

And you have a net connection. How do I make this permenant in Debian? I've tried adding 'dmfe' to /etc/modules, adding blacklist 'tulip' to '/etc/modprobe.d/blacklist' and '/etc/hotplug/blacklist', and adding this script to '/etc/rcS.d/S40networking':

ifdown eth0
rmmod dmfe
rmmod tulip
modprobe dmfe
ifup eth0

but I still have no net connection when I reboot untill I do the manual fix. How to correct?

Dutch Master · 12-19-2006, 08:09 PM

Simple, put the script in /etc/rc2.d That's how I got my Linksys wireless NIC working in Etch

Red Knuckles · 12-19-2006, 08:29 PM

Quote:

Originally Posted by Dutch Master

Simple, put the script in /etc/rc2.d That's how I got my Linksys wireless NIC working in Etch

/etc/rc2.d is a directory. Do I create a new file or add script to existing file?

Dutch Master · 12-19-2006, 09:10 PM

I presume you have the script in your home-dir somewhere. Make sure it's executable and change it's extension to .sh. (chmod +x </path/to/script> ) Start a rootconsole and create a symlink from /etc/rc2.d (that is, inside that directory) to your script:

Code:

ln -s /path/to/script/scriptname.sh /etc/rc2.d/Sxx<scriptname.sh>

Let me explain the command:

ln -s: this calls the program to create a link, the -s option designates a symbolic link
/path/to/script/scriptname.sh: the full path, starting at /, to your script
/etc/rc2.d/Sxx<scriptname.sh>: the /etc/rc2.d part should be self-explanatory, the S designates a startup script, the xx is a 2 digit number to determine when in the bootsequence the script is called and <scriptname.sh> is of course the name of your script.

Make sure you don't choose the xx number too low. I'd suggest to take 99, as only then you're sure all dependencies for executing the script are available.

PS: if you'd enter the /etc/rc2.d dir and do ls -l you'll see all scripts there are actually symlinks to other directories

Red Knuckles · 12-19-2006, 09:19 PM

Quote:

Originally Posted by Dutch Master

I presume you have the script in your home-dir somewhere. Make sure it's executable and change it's extension to .sh. (chmod +x </path/to/script> ) Start a rootconsole and create a symlink from /etc/rc2.d (that is, inside that directory) to your script:

Code:

ln -s /path/to/script/scriptname.sh /etc/rc2.d/Sxx<scriptname.sh>

Let me explain the command:

ln -s: this calls the program to create a link, the -s option designates a symbolic link
/path/to/script/scriptname.sh: the full path, starting at /, to your script
/etc/rc2.d/Sxx<scriptname.sh>: the /etc/rc2.d part should be self-explanatory, the S designates a startup script, the xx is a 2 digit number to determine when in the bootsequence the script is called and <scriptname.sh> is of course the name of your script.

Make sure you don't choose the xx number too low. I'd suggest to take 99, as only then you're sure all dependencies for executing the script are available.

PS: if you'd enter the /etc/rc2.d dir and do ls -l you'll see all scripts there are actually symlinks to other directories

I don't know yet how to create an executable script. The script is something I copied and pasted. How to?

Dutch Master · 12-19-2006, 10:08 PM

Open a console (as a regular user) and go to the directory where the script is stored using the cd command. I presume you have it somewhere in you home-dir, if not: copy it to your home-dir for security reasons. Then copy and execute this command:

Code:

chmod +x </path/to/script>

where <path/to/script> can be just the scriptname if you are in the same directory. To clarify for yourself that it's an executable script you can change the extension to .sh (if not done already) It doesn't matter for Linux, it's smart enough to figure out without extensions what's executable and what not ;-)

edit: I figured out that maybe you don't know how to write a script. Use this:

Code:

#! /bin/sh

# making the Davicom Tulip Ethernet Card work
ifdown eth0
rmmod dmfe
rmmod tulip
modprobe dmfe
ifup eth0

exit 0

Save this as tulip_eth.txt in your home-dir and proceed as described before.

Red Knuckles · 12-19-2006, 10:42 PM

Quote:

Originally Posted by Dutch Master

Open a console (as a regular user) and go to the directory where the script is stored using the cd command. I presume you have it somewhere in you home-dir, if not: copy it to your home-dir for security reasons. Then copy and execute this command:

Code:

chmod +x </path/to/script>

where <path/to/script> can be just the scriptname if you are in the same directory. To clarify for yourself that it's an executable script you can change the extension to .sh (if not done already) It doesn't matter for Linux, it's smart enough to figure out without extensions what's executable and what not ;-)

edit: I figured out that maybe you don't know how to write a script. Use this:

Code:

#! /bin/sh

# making the Davicom Tulip Ethernet Card work
ifdown eth0
rmmod dmfe
rmmod tulip
modprobe dmfe
ifup eth0

exit 0

Save this as tulip_eth.txt in your home-dir and proceed as described before.

Dutch Master, thanks for the help. For what it's worth the fact that I ask a question in a forum doesn't mean I stop trying to find the answer myself. I had my Sam's Fedora 4 manual out trying to teach myself how to write and executable script and was getting close when I got your last post.

I also discovered that for some reason [I probably had a detail wrong] following your instructions was creation a symbolic link in /etc/rc2.d but when I nanoed that file it was empty. So I just put the script in that file and it worked.

Now I'm going to review how to write a simple executable script. And the detail of the commands I entered and what did and didn't work. Thanks again.

For me to learn how to write and use simple scripts is a big newbie step. Now it's time!