I am not sure if it is a hardware problem or a module problem.

Puppy 2.0 is installed and I try to use "Connect to Internet by cable ethernet interface":

It finds two modules: ee100 and eepro100 for both Ethernet connectors.
Clicking on eth0 & Test eth0 it says 'Unable to connect to the network'
After several tries it finds:
'Puppy was able to find an alive network'

Auto DHCP fails always!!!
Static IP does not work either, except that I can ping the own IP address.
The Ethernet socket has a green LED, which flashes in a rhythm of 1 second (regardless if I ping or not). I have no idea what that means.

The log file shows:

eepro100.c:v1.09j-t 9/29/99 Donald Becker %url deleted%
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <%deleted%> and others
PCI: Found IRQ 5 for device 0000:01:0e.0
eth0: OEM i82557/i82558 10/100 Ethernet, 00:02:B6:34:27:B0, IRQ 5.
Board assembly ffffff-255, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
Secondary interface chip i82555.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0xd0a6c714).
PCI: Found IRQ 9 for device 0000:01:0f.0
eth1: OEM i82557/i82558 10/100 Ethernet, 00:02:B6:34:27:AF, IRQ 9.
Board assembly ffffff-255, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
Secondary interface chip i82555.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0xd0a6c714).
lp0: using parport0 (interrupt-driven).
lp0: console ready
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation

lsmod shows that both modules e100 and eepro100 are loaded.

Question:
is e100 and/or eepro100 the right driver?



Any idea?


bye

Ronald

Elmit, check to see if there is a file named "/etc/dhcpc/dhcpcd.pid". If there is, delete it and try again.

Using a new cable to another hub helped, ...

I did not think on that, since I used temporary the cable of the VoIP phone (same network, but different hub)

Does your PC have more than one network card?

If it does, I have found that puppy gets confused and won't
let you access the net. I removed one card and puppy worked just
fine.

I hope this helps