Quote:
Originally Posted by senthil4984
[root@TNPMWAPP network-scripts]# mii-tool
SIOCGMIIPHY on 'eth0' failed: Operation not supported
eth1: negotiated 100baseTx-FD, link ok
eth2: negotiated 100baseTx-FD, link ok
SIOCGMIIPHY on 'eth3' failed: Operation not supported
|
miitool probably isn't compatible with your NIC. It's generally considered deprecated.
Quote:
Originally Posted by senthil4984
[root@TNPMWAPP network-scripts]# ethtool eth0
Settings for eth0:
Supported ports: [ ]
Supported link modes:
Supports auto-negotiation: No
Advertised link modes: Not reported
Advertised auto-negotiation: No
Speed: 10000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: no
|
The highlighed parts are interesting. It seems autonegotiation is not supported (which is so unusual for a copper gigabit NIC that
ethtool is probably wrong), and no link is detected (the last line).
When the link status is "down", an Ethernet NIC should typically report 10 Mbps and half duplex, but your NIC seems locked to 1 Gbps and full duplex. Either there's a distribution-specific setting somewhere that forces a specific speed/duplex setting (which would deactivate auto-negotiation and hence explain "Advertised auto-negotiation: No" and "Auto-negotiation: off"), or there's something wrong with either the hardware or the driver (which would explain "Supports auto-negotiation: No").
What kind of NIC is this, and what's the name of the associated kernel module/driver? For that matter, what Linux distribution and kernel version are you running?
Please post the output from:
Code:
lspci -v
ifconfig -v eth0
uname -mr
