[SOLVED] help: eth0 stopped working

nihilo · Last edited by nihilo on Mon Jul 19, 2004 1:21 am; edited 1 time in total

I cannot get dhcpcd or static ip to work. I thought it might be related to windows not releasing its ip, so i bought a router, but it makes no difference.

I've tried setting the appropriate dhcpcd setting in /etc/conf.d/net, but it says there is no response from dhcp server, though it works fine in windows and on my linux laptop (with a much older setup and older kernel, different hardware).

Here is what dhcp should set:

IP: 192.168.2.2
GW: 192.168.2.1
Netmask: 255.255.255.0
Nameserver: 192.168.2.1

I've set these setting by hand, using ifconfig, route, and vi resolv.conf, but it still doesn't work.

Here's the state when I try to do it staticly, which should be the most reliable:

ifconfig:

Shows eth0 UP but not running, with correct MAC address, inet addr: 192.168.2.2, Bcast:192.168.2.255, Mask:255.255.255.0, and it shows RX bytes:0 (none received), TX bytes (346444), and interrupt 20.

route shows the following:
Destination Gateway Genmask ..... Iface
192.168.2.0 * 255.255.255.0 eth0
loopback 192.168.2.1 255.0.0.0 lo
default 192.168.2.1 0.0.0.0 eth0

Can any networking guru suggest what else I might try?

My NIC is eepro100, which used to work fine before upgrading to 2.6.7-r?. I've tried it both as a module, and compiled in. I've also tried older kernels which used to work, and they no longer work, and I've tried livecd, which doesn't work but used to.

I had installed cisco-vpn-client a few days before this broke a week ago, and also openvpn, but have since uninstalled these, but it makes no difference.

When I try to ping things on the internet, I just get "Destination Host Unreachable." I've already spent about 10 hours on this, and have search everywhere I could think of, but have made zero progress. Any help would be greatly appreciated.

Spear · n00b Joined: 08 Mar 2004 Posts: 65

One thing I found was that dhcp would simply refuse to work and give timed out errors when I compiled the kernel with /dev/pts support. A recompile with just /dev sorted that. Be warned though that in my case a static IP would still work fine.

hadfield · Posted: Sat Jul 17, 2004 7:20 am Post subject:

nihilo · Posted: Sat Jul 17, 2004 7:50 pm Post subject:

hadfield · Posted: Sat Jul 17, 2004 8:03 pm Post subject:

megalomani · Tux's lil' helper Joined: 08 Jun 2004 Posts: 77

It's a problem with your network card try

insmod eepro100 options=0x100,0,0x20

if that doesn't work then you might want to change IO with

insmod eepro100=0xe800 irq=10

see

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=378CCAA9.C15025B3%40rahul.net&rnum=1&prev=/groups%3Fq%3Deepro100%2BIO%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3D378CCAA9.C15025B3%2540rahul.net%26rnum%3D1

nihilo · Posted: Sat Jul 17, 2004 8:20 pm Post subject:

nihilo · Posted: Sat Jul 17, 2004 8:34 pm Post subject:

nihilo · Posted: Sun Jul 18, 2004 8:30 am Post subject:

Tried recompiling as module, and insmoding with various options settings, but it makes no difference. Still broken.

megalomani · Tux's lil' helper Joined: 08 Jun 2004 Posts: 77

It's seems that the devoplement of the driver forked a couple of years ago.

e100 is another driver for your network card (called Intel(R) PRO/100+ support in make config) Look at your cards ID to see if it's supported
http://www.intel.com/support/network/adapter/1000/linux/e100.htm

nihilo · Posted: Sun Jul 18, 2004 8:19 pm Post subject:

megalomani · Tux's lil' helper Joined: 08 Jun 2004 Posts: 77

Probably a typo, but your route info is wrong

loopback 192.168.2.1 255.0.0.0 lo

should be

loopback 192.168.2.2 255.0.0.0 lo

nihilo · Posted: Mon Jul 19, 2004 1:18 am Post subject: