|
I'm pretty sure Redhat 7.1 has support for the tulip module buit-in; you shouldn't need to compile it separately. were you not able select it in Redhat's network configuration tool?
If not, and you have to compile, here's some general info:
- tulip.o is dependent on pci-scan.o, which means that pci-scan.o must be loaded before tulip.o. The way to make your system aware of this and load modules in the proper order automatically is by running "depmod -a" to update the module dependancy list after installing the modules.
A few more things to check:
-Log in as root, go to the command line or terminal window, and type "lspci" and verify that your NIC is being recognized. Type "cat /proc/interrupts" and make sure your NIC's IRQ isn't conflicting with another device. Type "cat /proc/ioports" and check the address ranges for conflicts. If you have resource conflicts, you
can try rearranging the slot order of your PCI cards.
-If you get a failure on bootup, you may have a resource (IRQ or I/O address) conflict with another device. Try turning off Plug-N-Play support in your BIOS, it can cause conflicts with some cards.
-You can also verify the IRQ/address info by typing "ifconfig". There should be stats for the loopback device (lo) and eth0. "ifconfig -a" will list all devices, active or not; try that as well.
- After doing "depmod -a", try loading the module again. You can also try "modprobe tulip" as opposed to "insmod tulip". After loading the module, type "lsmod" to see if the tulip driver appears in the list of active modules.
-Check that the line "alias eth0 tulip" exists in /etc/modules.conf (it might be /etc/conf.modules instead). If not, add it.
Finally, how are you assigning the NIC's IP? Are you giving it a static address, or does it obtain one via DHCP?
Last edited by DMR; 01-22-2002 at 10:14 PM.
|
NIC Card Help
Please help if you can.
