On resume, knetworkmanager tries to ifup eth0 without a link

[Michael Blakeley]

Binary package hint: knetworkmanager

This might be a network-manager bug- I'm not sure how the flow of control works, between those two.

Linux mblakele-lt 2.6.22-6-generic #1 SMP Fri Jun 1 00:54:39 GMT 2007 x86_64 GNU/Linux
knetworkmanager/gutsy uptodate 1:0.2~r674918-0ubuntu2
network-manager/gutsy uptodate 0.6.5-0ubuntu2

$ sudo /usr/sbin/ethtool -i eth0
driver: tg3
version: 3.76
firmware-version: 5753m-v3.56
bus-info: 0000:08:00.0
$ sudo /usr/sbin/ethtool eth0
Settings for eth0:
        Supported ports: [ 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: Unknown! (65535)
        Duplex: Unknown! (255)
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: d
        Current message level: 0x000000ff (255)
        Link detected: no

When I resume my laptop (hp nc6400) from suspend-to-RAM, I see knetworkmanager's "connecting" icon (spinning gear) and a mouseover indicates that it's trying to connect on eth0. But eth0 has no link, per the ethtool output above, so the connection eventually falls back to a self-assigned DHCP address.

The previous version of knetworkmanager (or network-manager) didn't do this. It used to recognize that eth0 didn't have a link, and fall back to eth1 (my wifi interface). I'd like to have that behavior back.

[Michael Blakeley (mike+ubuntu)]

Not a duplicate of 90267 precisly, but also fixed in 0.6.5-0ubuntu7.