| 1 |
Juan Fco. Giordana, mused, then expounded: |
| 2 |
> |
| 3 |
> ########### |
| 4 |
> # server1 # |
| 5 |
> ########### |
| 6 |
> |
| 7 |
> ~ # lspci | grep Ethernet |
| 8 |
> 04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet |
| 9 |
> Controller (Copper) (rev 01) |
| 10 |
> 04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet |
| 11 |
> Controller (Copper) (rev 01) |
| 12 |
> |
| 13 |
> |
| 14 |
> ~ # ethtool eth1 |
| 15 |
> Settings for eth1: |
| 16 |
> Supported ports: [ TP ] |
| 17 |
> Supported link modes: 10baseT/Half 10baseT/Full |
| 18 |
> 100baseT/Half 100baseT/Full |
| 19 |
> 1000baseT/Full |
| 20 |
> Supports auto-negotiation: Yes |
| 21 |
> Advertised link modes: 100baseT/Full |
| 22 |
> Advertised auto-negotiation: Yes |
| 23 |
> Speed: Unknown! (65535) |
| 24 |
> Duplex: Unknown! (255) |
| 25 |
> Port: Twisted Pair |
| 26 |
> PHYAD: 1 |
| 27 |
> Transceiver: internal |
| 28 |
> Auto-negotiation: on |
| 29 |
> Supports Wake-on: pumbag |
| 30 |
> Wake-on: g |
| 31 |
> Current message level: 0x00000001 (1) |
| 32 |
> Link detected: no |
| 33 |
> |
| 34 |
> |
| 35 |
|
| 36 |
It doesn't matter what the LED is saying there is no link detected. It |
| 37 |
seems the phy on eth1 is good but the path from the phy to the |
| 38 |
ethernet chip is bad. |
| 39 |
|
| 40 |
> |
| 41 |
> ########### |
| 42 |
> # server2 # |
| 43 |
> ########### |
| 44 |
> |
| 45 |
> ~ # lspci | grep Ethernet |
| 46 |
> 02:0c.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro |
| 47 |
> 100 (rev 0d) |
| 48 |
> 02:0d.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro |
| 49 |
> 100 (rev 0d) |
| 50 |
> |
| 51 |
|
| 52 |
Server two is working, only that should be running the EEPro100 driver, |
| 53 |
not the e1000e driver. |
| 54 |
|
| 55 |
Bob |
| 56 |
-- |
| 57 |
- |
Archives