Most of the startup scripts are in the /etc/rc.d dir. If you load
that driver from rc.local in that dir, you might not get network
because I believe that's the last one that's run upon bootup. Perhaps
I'm wrong and it doesn't matter. If you notice that it matters,
you'll see rc.modules in that same dir. Edit that one instead. You'll
see most of your kernel modules are loaded from there. Maybe your
card is already in there.
How I figured out which to load for my
NIC was to run rc.hotplug, then check the output with 'dmesg | less'
then found the appropriate module in /etc/rc.d/rc.modules and deleted
# sign in front of it. Also, Slackware will look for
/etc/rc.d/rc.netdevice (chmod 700 or 755) with one line to
load the module for your NIC. Maybe add a #!/bin/sh to the top if
you'd like and make it two lines.
Those are all scripts in that
directory and viewable with more, most, less; and editable with pico
or vi, or whatever you care to use for a text editor.
The only advantage to rc.netdevice instead of loading it from
rc.modules is manageability. If you ever need to refer to the module,
you don't have to scroll through rc.modules, you can just view