Hi,

I need some help.

I've just upgraded to a brand new PC, and I can't get the new machine to connect to my ASDL router (a Vigor 2600, which works perfectly with my older system).

I'd appreciate any advice on how to get it working; I'll try to give any details that will help, but I still consider myself a bit of a newbie, so forgive me if I miss anything.

The new machine has an ASUS A7N8X-E Deluxe motherboard, which has two built-in network ports. These are being picked up correctly by Suse as eth0 and eth1, and they show up in the hardware scans as expected, but the boot sequence reports "failed" for both of them, and I don't seem to be able to get any response out of either of them.

I tried looking for the reasons for it reporting "failed", but the one log file I found (in Yast) was not very enlightening - it just said "failed"; didn't give any more details.

I did some research, and I'm told this motherboard should work fine with Linux, so I'm sure it's just something wrong in my setup. I just don't know what.


Thanks in advance for any replies.

Try redoing the network configuration stuff, and check that you made sure to specify the correct way of connecting (pppoe? dhcp? static IP address?) If its pppoe check your username and password. (With a router, its typically DHCP though)

Thats really all I can think of. Try "/bin/dmesg" and seeing if you can get any useful error messages out of the boot log. Run ifconfig -a and make sure its really detecting both an eth0 and an eth1. Maybe swap your cable (maybe you have it set up to dhcp on eth0, but the router is plugged into eth1?)

Ah, got distracted... also see if you can try starting the network by hand, that might get you more useful error messages? (if static, run ifconfig eth# up 555.555.555.555 netmask 255.255.255.0 gw 555.555.555.1, or if dhcp, run the dhcp client by hand - typically pump, dhcpcd, dhcpc, or dhcp-client)

Thank you Qzukk for the replies.

I've spent a good portion of today trying to solve this, and I still don't have it working, but I think I have made some progress, though.

I did a bit more digging around the web, and found that the network ports on this mobo do need a driver that isn't included as standard with Suse. So I downloaded it and installed it. So far so good.

Now, when I change the network settings in Yast, the P1 light on the router blinks, which it wasn't doing before... which implies that I have made some sort of progress. It also isn't reporting failure any more on bootup. I still can't get any sort of connection, though - the only thing I can ping is localhost.

Help!

Hi again,

Yes, I'm still fighting with this one.

I have the driver installed, and set it up in Yast for eth0 as far as I can tell correctly.

Now when I boot, I am no longer getting "eth0 Failed". But instead I am getting "Eth0 (DHCP) . . . . . no ip address yet....backgrounding"

I have no idea what this means.... execpt that I still can't connect to anything.

Can anyone explain what I need to do now? :?


This is really getting quite frustrating.

Hi guys,
i'm a linux newbie too and had the same problem with you.
ifup,ifdown,ifconfig or anything else wouldn't renew my lease.
So i tried:

'#ifup eth0 dhcp'

and it worked!!!!I suggest you give it a try too!!!
I'll be waiting for the results...

Try this:

I had a similar problem with having 2 nic's installed on my system. Reconfigure eth0 and eth1 but this time put them on different subnets. For some reason Linux does not like 2 nic's in the same machine on the same subnet.

I had the same problem. Gave up SuSE, and now uses fedora.redhat.com. Worked on first try there...

Funny thing! I just gave up on fedora and now working on SuSE!!!!