Hello, I just installed Redhat 9 onto my system (more questions to come). It has an Asus p4s8x motherboard. I was having the problem where I couldn't install my NIC until someone told me to just run insmod sis900. No problem, it now sees my nic, but now I try to activate my network and it errors out saying something to the effect that the device is busy. I forgot to write down the exact message and I'm in no position to retry at the moment. Anywho, suggestions? Is there an update somewhere I need to pick up, or what?

"I try to activate my network". Give us the commands you used to do this. Was it "ifconfig eth0" or something like that? To set up the network, use "redhat-config-network" for a gui version or "setup", then "Network configuration", for a text-based one. "it errors out saying something to the effect that the device is busy". Please give error message. By the way, you should be able to just enter this line (below) in your /etc/modules.conf file to activate your network driver, rather than manually inserting the module (insmod): alias eth0 sis900 (changing eth0 to whichever interface you are using)

Ok, first I used the gui network setup. When I click the activate button, it pops up a window saying "SIOCSIFFLAGS: Device or resource busy" I later tried ifconfig to set the ip, and got the same message. I can, however, ping my own ip, but attempts to ping other computers tell me "Network is unreachable"

It sounds like you have no routes, except to your IP address. What is your subnet mask, 255.255.255.255? And what ip addresses are you trying to ping? Are they within your current subnet mask? Do you have a default route set up? Do you have any other routes defined? It sounds like to me that you just have a screwy network setup. You might want to give a little information on your settings.

I setup my ip as 192.168.0.9. My gateway is on 192.168.0.1. Subnet is 255.255.255.0. 192.168.0.1 is also a dhcp server, but when I try to set up my system to pull from the dhcp, it still says "Device or resource busy", but it takes longer (I assume it's searching for the dhcp server and timing out) I have had it working under windows with these same parameters, so I know it's not the network. In fact, it's running right now under win2k (I'm dual booting) with no problems. What are these routes of which you speak? Should one not be created by default encompasing my subnet or something? And why, if my ip is in the 192.168.0.x range, would it tell me any other ip on that range is unaccessable?

If your ip address is 192.168.0.9 and your subnet mask is 255.255.255.0, then you should be able to ping 192.168.0.x, assuming you don't have a firewall holding you back. Disable the firewall if it's running. Run "ntsysv" (or "setup", then "System services") or "redhat-config-services" for a gui version, and disable (uncheck) ipchains and iptables, then reboot (or enter "service daemon stop" for temporary disabling). "Network is unreachable" is typically a routing problem, making me guess that you didn't have a route to those ip addresses and that your subnet mask was 255.255.255.255. Enter "route" at a command prompt to see the routing table. Maybe you have a device/resource conflict, and Windows is overriding (or ignoring) it. Enter "cat /proc/pci" at a command prompt. Is your network card conflicting with any other devices (IRQ, I/O)?

There seem to be no conflicts. I think the reason I got the Network unreachable message is on account I can't bring the network up ("ifconfig eth0 up" gives me that blasted busy message) However, when I had it set for DHCP, first I tried bringing it up while plugged into the network, which gave me the busy message, and second I tried after unplugging my computer from the network, and got a message telling me it couldn't reach the dhcp and that my cable was unplugged, so I'm sure it must be doing SOMETHING. Incidentally, I've been using the network setup gui for most of this.