Comment 1 for bug 347711

This is an Intrepid reinstall (it was working fine before but HDD had some errors), have the same problem, but noticed something

I don't remember having installed any special patches, but on my previous Intrepid setup my interface was named eth0, now it's named eth2. Also something weird when comparing output of mii-tool, and eththool

=> ifconfig

eth2 Link encap:Ethernet HWaddr 00:1c:c0:a7:b3:37
          inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: 2002:be9b:d58c:0:21c:c0ff:fea7:b337/64 Scope:Global
          inet6 addr: fe80::21c:c0ff:fea7:b337/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:14671268 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10328468 errors:0 dropped:46 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2911705282 (2.9 GB) TX bytes:897510370 (897.5 MB)
          Interrupt:220 Base address:0x2000

=> mii-tool
eth2: negotiated 1000baseT-HD flow-control, link ok

Says 1000-HD

=> ethtool eth2
Settings for eth2:
        Supported ports: [ TP MII ]
        Supported link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
        Link detected: yes

Says 1000FD, no way to force 1000FD on mii-tool and I don't know which is right.