Hm, neither of those seemed to work. I also manually installed 8390.o; no diff.
yomama:~# modprobe tulip /lib/modules/2.2.17/net/tulip.o: init_module: Device or resource busy Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.2.17/net/tulip.o: insmod /lib/modules/2.2.17/net/tulip.o failed /lib/modules/2.2.17/net/tulip.o: insmod tulip failed yomama:~# Same behavior with old_tulip (s/tulip/old_tulip/g). Any other ideas? On Fri, 25 Aug 2000, Dan Brosemer wrote: > Try the old_tulip module... might have better luck with that. Also try > using modprobe instead of insmod. modprobe will drag in module dependencies > for you (and some network cards depend on 8390.o -- not sure if tulip does, > though).
