Then you should maybe remove the line again. Try to write:

/sbin/lsmod

To see what modules are loaded. Try to setup networking with RedHats configuration tool: /usr/sbin/setup

Instead of using the insmod command, try using the modprobe command as root.

# /sbin/modprobe tulip
# /sbin/ifconfig

And after the ifconfig command, see if it gives you another device besides the lo or local loopback

Should look something like this:
Also have you tried running the netconfig command to configure your network ? Its usually pretty reliable and detects what module to use with whatever NIC.

Done. Same error message when I run insmod.

I'm getting the feeling it's not usually this hard.

No go. Though when I run dmesg there are like 10 entries like this at the bottom:

Linux tulip driver version 0.9.15-prell (May 11, 2002)

netconfig takes me to the same interface as /usr/sbin/setup. I can select setup networking and it gives me the option to set up. But it doesn't seem to save the changes because every time I open it, it looks exactly the same as when I started.

The module list with /sbin/lsmod does not show the network module loaded (I'm guessing that's the one I'm looking for), but the running services list at the System Services menu shows an * by network.

I can try to activate the eth0 module in the network configuration utility, but it keeps saying it can't active eth0. And I can't configure a network device. Even though it's supported, it isn't in the drop down list.

It's time to give up, been at this all day. It's a nice OS and has come a long way, but this is nuts. Going to try one last thing. Going to pull the card and reinstall it, then reinstall red hat. If it works, super. If not I'm just going to shelf it until I can go to Linux bootcamp or get a book.

Thanks for all the help, you were super.

It would actually be nice if there was some little hardware howto that told you how to find information about your system, setup, trouble shooting, and so on. It could be called "Nerd - Know Your Hardware".

That would be handy. In this case one can strongly suspect operator error. It's not the os that's the problem, it's my lack of experience. The os is ready and I can improve.

Thanks again.

Can you post your output of /proc/pci ??

cat /proc/pci

But if you see the device in dmesg, it could be some sort of IRQ problem or such. Or it could just be the card itself and chipset. Might could try to get an updated tulip driver ??

90% of networking problems happen at the hardware level. Reinstalled the card, reinstalled RedHat and it found the card and the network all by itself. Picked up a DHCP address and populated the DNS names and everything.

Thought it was strange that I couldn't activate the module on either distro. Unix is the original network language and it's like an OS 101 kind of thing. Plus there wasn't a lot in the support docs, which can mean no one else is having the same problem.

Man, do I feel stupid. Think I'll change user names to avoid perpetual shame.

Linux isn't the future, it's the present.

Thanks again, you guys are super.

Nice, I was going to say recomplie the kernal. That way you can tell what NIC you have and will be used to kernal.
The best way to use linux system is once you set up the system, complie keranl is the final step to do. That way, you can also enable NFS, Netfiletering, so on.

Lint

hmmm... should be that problematic... tried it myself once... but i solved it by eventually move the nic to a different pci-slot.. then it worked like a charm!!