Are you sure that you havn't hard coded the duplex in a script or
elsewhere? lspci should show you which nic you have in the server.
Simon Buchanan <nmc@orcon.net.nz> 09/27/04 8:40 PM >>>
Here is the output of ethtool... i cant remember what the nic is...:
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: pumbg
Wake-on: d
Doug Griswold wrote:
Try checking with ethtool. Which nic are you using?
Simon Buchanan <nmc@orcon.net.nz> 09/27/04 8:13 PM >>>
Hi There, i have a debian woody box that i am connected to via ssh,
here
is the ifconfig:
eth0 Link encap:Ethernet HWaddr 00:50:FC:XX:XX:XX
inet addr:203.109.xxx.xx Bcast:203.109.xxx.xx
Mask:255.255.255.xxx
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4109 errors:0 dropped:0 overruns:0 frame:0
TX packets:1079 errors:8 dropped:0 overruns:0 carrier:16
collisions:23 txqueuelen:100
RX bytes:809755 (790.7 KiB) TX bytes:169903 (165.9 KiB)
Interrupt:16 Base address:0xa000
When i check the link with mii-tool i get the following response:
box:/etc# mii-tool -v eth0
eth0: 10 Mbit, half duplex, no link
product info: vendor 00:00:00, model 0 rev 0
basic mode: 10 Mbit, half duplex
basic status: no link
capabilities:
advertising:
NO LINK? But im connected to the thing - and its connected to a
100Mbit
hub... Is this a problem with the ethernet card?
Thanks
Simon