Probably the first step is to make sure that your module really isn't
getting loaded. After booting, type "lsmod" (without quotes) at the
command prompt. This will list all currently loaded modules. If tulip
isn't in the list, type "insmod tulip". If you get an error such as
"Device or Resource unavailable or busy", then your module hasn't been
properly made. If you get "Using xx/xx/xx/tulip.o" then the module is now
loaded.
The steps you used to make & install your module should work. The
steps taken to load the module at boottime vary with the distribution
you're using. Also, IIRC ResNET uses DHCP, so if you do get your module
loaded, all you need to do is "dhcpcd eth0" to get connected.
--
Doc Shipley
Network Guy
TARL Labs, UT
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
