Public bug reported:
This on current (as of 2006-09-15) Edgy, and it used to work fine on
Dapper.
I have thinkpad X41 with tg3 wired card and ipw2200 wlan. Network-
Manager applet in gnome sometimes shows that ipw2200 is also wired, and
displays selection between two wired cards. This makes using wireless
networks pretty hard as it does not show which networks are available
and what are their statuses, but this doesn't matter much because
wireless network to connect to cannot be selected anyway... From the
few tests I have it works OK after reboot (meaning, it shows one wired
and one wireless card correctly), and usually (pretty much always) gets
broken (meaning, shows two wired cards) after suspend.
Here is a bit of NetworkManager --no-daemon output when coming back from
suspend and recognizing both cards as wired:
NetworkManager: <information> Waking up from sleep.
NetworkManager: <debug info> [1158314002.466493] nm_hal_device_added (): New
device added (hal udi is '/org/freedesktop/Hal/devices/net_00_16_d3_20_7d_ea').
NetworkManager: <information> eth0: Device is fully-supported using driver
'tg3'.
NetworkManager: <information> nm_device_init(): waiting for device's worker
thread to start
NetworkManager: <information> nm_device_init(): device's worker thread
started, continuing.
NetworkManager: <information> Now managing wired Ethernet (802.3) device
'eth0'.
NetworkManager: <information> Deactivating device eth0.
NetworkManager: <information> Will activate wired connection 'eth0' because
it now has a link.
NetworkManager: <debug info> [1158314002.913971] nm_hal_device_added (): New
device added (hal udi is '/org/freedesktop/Hal/devices/net_00_16_6f_1b_e1_af').
NetworkManager: <information> eth1: Device is fully-supported using driver
'ipw2200'.
NetworkManager: <information> nm_device_init(): waiting for device's worker
thread to start
NetworkManager: <information> nm_device_init(): device's worker thread
started, continuing.
NetworkManager: <information> Now managing wired Ethernet (802.3) device
'eth1'.
NetworkManager: <information> Deactivating device eth1.
NetworkManager: <information> Will activate wired connection 'eth1' because
it now has a link.
NetworkManager: <information> SWITCH: no current connection, found better
connection 'eth1'.
NetworkManager: <information> Will activate connection 'eth1'.
NetworkManager: <information> Device eth1 activation scheduled...
And then it goes and activates eth1. Which is another bug as eth0 [wired
tg3] was connected before suspend, but maybe it is somehow related to
this bug of mixing up wired and wireless cards.
And here is what lspci says about the two cards in case it matters:
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit
Ethernet PCI Express (rev 11)
04:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network
Connection (rev 05)
** Affects: network-manager (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
Sporadically mixes up wireless network as wired
https://launchpad.net/bugs/60545
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
