Suse Network Help.

Interesting... type ifconfig eth0 up and then ifconfig (assuming no errors appear)

Quote:

---

linux#ifconfig eth0 up
eth0: Unknown device

---

Its like it doesn't thinkg theres a NIC there. I don't know, I'm not that good yet with *nix.
I know my NIC is eth0 though cause thats what it says under the NIC card in the Yast Modules

It looks like it may not be detecting it right. What kind of NIC is it? (Manufacturer, model)?

Its an onboard NIC. Nforce 2 chipset for the NIC.

I think I'm gonna search real quick for a different Linux driver and see if that helps

I just don't understand it.

I put a Linksys Fast Ethernet Card in there, started the machine up got to the gui, and it said that it had found new hardware and it named the exact name of the card. I then proceeded to configure it. I gave it a IP of 192.168.1.105 and a mask of 255.255.255.0 and set my router as the gateway. Now of this NIC is eth1, I removed eth0 as a NIC so eth1 is the primary, but I still get the same damn errors. This thing is really frustrating now. I guess I just need to spend a whole day on this.

I was searching through and found some of the following that might be helpful:

http://www.netsys.com/suse-linux-e/2.../msg01848.html
http://home.t-online.de/home/Johanne...rce2linux.html
http://www.linuxtested.com/results/Asus_A7N8X-E.html
http://dnaresearch.com.au/linux_on_abit_nf7s.shtml
http://www.thejemreport.com/communit...=617&view=next

From experience, I've found that SuSE sometimes doesn't like onboard NICs. If you have a spare NIC around there to slip into a PCI slot, try that, and see if you can at least get a dynamic IP.

I've got a couple PC's at work that run SuSE and they don't recognize the onboard intel NICs, I've installed the PCI equivalent NIC into a PCI slot and was able to get a connection.

Hope ya have a spare NIC around...(I know, sounds like the cheap way out, but sometimes my work wants results rather than explanations, so I just thought I'd share my 2 cents) :)

disc0rd, he did try a spare nic (note his last post). The issue, IMHO, is the board itself. From what I've read the kernel (2.4.20 or 2.4.21?) doesn't like nforce based boards. It might be worthwhile for him to upgrade to 2.4.22 and then install the NIC drivers.

Ah crap, I read it too fast, sorry about that..I just get excited helping people :P

I'm going to drink some more coffee and retreat to my hole of a cubicle at work :(

I'll try upgrading then to a newer kernel.

Thanks for all your help.