FS#29597 - Networkmanager 0.9.4 breaks ipw2200 wireless

Attached to Project: Arch Linux
Opened by Mike Cloaked (mcloaked) - Tuesday, 24 April 2012, 18:53 GMT
Last edited by Ionut Biru (wonder) - Tuesday, 24 April 2012, 21:43 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Dell D610 laptop with previously up to date packages and working wireless fails to start wireless connection on eth1 after update to networkmanager 0.9.4.0-3 - reverting to 0.9.2.0-3 and restarting networkmanager gives a working wireless connection again.

Additional info:
* package version(s)
* config and/or log files etc.

Booting with ipv6.disable=1 also fails to start the wireless connection.

messages log contains:

Apr 24 19:26:33 localhost NetworkManager[865]: keyfile: parsing mdc-guest ...
Apr 24 19:26:33 localhost NetworkManager[865]: keyfile: read connection 'mdc-guest'
Apr 24 19:26:33 localhost NetworkManager[865]: <info> trying to start the modem manager...
Apr 24 19:26:33 localhost NetworkManager[865]: <info> monitoring kernel firmware directory '
/lib/firmware'.
Apr 24 19:26:33 localhost NetworkManager[865]: <info> found WiFi radio killswitch rfkill1 (a
t /sys/devices/pci0000:00/0000:00:1e.0/0000:03:03.0/ieee80211/phy0/rfkill1) (driver (unknown
))
Apr 24 19:26:33 localhost NetworkManager[865]: <info> WiFi enabled by radio killswitch; enab
led by state file
Apr 24 19:26:33 localhost NetworkManager[865]: <info> WWAN enabled by radio killswitch; enab
led by state file
Apr 24 19:26:33 localhost NetworkManager[865]: <info> WiMAX enabled by radio killswitch; ena
bled by state file
Apr 24 19:26:33 localhost NetworkManager[865]: <info> Networking is enabled by state file
Apr 24 19:26:33 localhost NetworkManager[865]: <warn> failed to allocate link cache: (-10) O
peration not supported
Apr 24 19:26:33 localhost NetworkManager[865]: <info> (eth0): carrier is OFF
Apr 24 19:26:33 localhost NetworkManager[865]: <info> (eth0): new Ethernet device (driver: '
tg3' ifindex: 2)
Apr 24 19:26:33 localhost NetworkManager[865]: <info> (eth0): exported as /org/freedesktop/N
etworkManager/Devices/0
Apr 24 19:26:33 localhost NetworkManager[865]: <info> (eth0): now managed
Apr 24 19:26:33 localhost NetworkManager[865]: <info> (eth0): device state change: unmanaged
-> unavailable (reason 'managed') [10 20 2]
Apr 24 19:26:33 localhost NetworkManager[865]: <info> (eth0): bringing up device.
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth0): preparing device.
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth0): deactivating device (reason 'm
anaged') [2]
Apr 24 19:26:34 localhost NetworkManager[865]: <info> Added default wired connection 'Wired
connection 1' for /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/net/eth0
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth1): using nl80211 for WiFi device
control
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth1): new 802.11 WiFi device (driver
: 'ipw2200' ifindex: 3)
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth1): exported as /org/freedesktop/N
etworkManager/Devices/1
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth1): now managed
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth1): device state change: unmanaged
-> unavailable (reason 'managed') [10 20 2]
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth1): bringing up device.
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth1): preparing device.
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth1): deactivating device (reason 'managed') [2]
Apr 24 19:26:34 localhost dbus[664]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
Apr 24 19:26:34 localhost NetworkManager[865]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Apr 24 19:26:34 localhost dbus[664]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Apr 24 19:26:34 localhost NetworkManager[865]: <info> wpa_supplicant started
Apr 24 19:26:34 localhost NetworkManager[865]: <info> (eth1): supplicant interface state: starting -> down
Apr 24 19:26:34 localhost NetworkManager[865]: <warn> Trying to remove a non-existant call id.

The access point is WPA/AES and this machine has always previously connected to it just fine.

Steps to reproduce:

pacman -Syu
this updates to networkmanager 0.9.4.0-3 (and last night to -2 with the same result)
if networkmanager is restarted or the machine is booted then there is no wireless connection.
Downgrade to 0.9.2.0-3 and restarting networkmanager immediately gives a working wireless connection again.
This task depends upon

Closed by  Ionut Biru (wonder)
Tuesday, 24 April 2012, 21:43 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.9.4-0-4
Comment by Giancarlo Bianchi (hermes14) - Tuesday, 24 April 2012, 19:56 GMT
The same here with Broadcom BCM43225 chip on an Acer Aspire 3820G (see https://bbs.archlinux.org/viewtopic.php?pid=1092065), so this bug is not strictly related to ipw2200. My wireless interface is seen as wired and it is not available. Reverting back to 0.9.2 for now.

Here is a relevant excerpt from syslog:
Apr 23 21:03:35 localhost NetworkManager[10841]: <info> (wlan0): driver 'wl' does not support carrier detection.
Apr 23 21:03:35 localhost NetworkManager[10841]: <error> [1335207815.523410] [nm-device-ethernet.c:456] real_update_permanent_hw_address(): (wlan0): unable to read permanent MAC address (error 0)
Apr 23 21:03:35 localhost NetworkManager[10841]: <info> (wlan0): new Ethernet device (driver: 'wl' ifindex: 2)
Apr 23 21:03:35 localhost NetworkManager[10841]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Apr 23 21:03:35 localhost NetworkManager[10841]: <info> (wlan0): now managed
Apr 23 21:03:35 localhost NetworkManager[10841]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 23 21:03:35 localhost NetworkManager[10841]: <info> (wlan0): bringing up device.
Apr 23 21:03:35 localhost NetworkManager[10841]: <warn> (wlan0): couldn't get carrier state: (-1) unknown
Apr 23 21:03:35 localhost NetworkManager[10841]: <info> (wlan0): carrier now OFF (device state 20, deferring action for 4 seconds)
Apr 23 21:03:35 localhost NetworkManager[10841]: <info> (wlan0): preparing device.
Apr 23 21:03:35 localhost NetworkManager[10841]: <info> (wlan0): deactivating device (reason 'managed') [2]
Apr 23 21:03:35 localhost NetworkManager[10841]: <info> Added default wired connection 'Connessione via cavo 2' for /sys/devices/pci0000:00/0000:00:1c.1/0000:05:00.0/net/wlan0
Comment by Ionut Biru (wonder) - Tuesday, 24 April 2012, 20:13 GMT
please check out networkmanager-0.9.4.0-4
Comment by Giancarlo Bianchi (hermes14) - Tuesday, 24 April 2012, 20:33 GMT
It works! I tried 0.9.4.0-{2-3} as well, but they didn't.
As I see in the changelog, wext has been reenabled. I compiled the wl driver using the wext API, while the one included with the kernel should use the cfg80211 API. Strange thing is that with the latter it wouldn't work either. To be more specific, the interface wasn't seen at all. Is it the only change between version 3 and 4 of the package?
Comment by Ionut Biru (wonder) - Tuesday, 24 April 2012, 20:38 GMT
yes, we enabled wext in -4.
Comment by Mike Cloaked (mcloaked) - Tuesday, 24 April 2012, 20:41 GMT
I guess that 0.9.4.0-4 will get into extra before long? I am a relatively new convert to arch from Fedora and I am not familiar with checking out a package (presumably from svn?). As I am still on a learning curve I am happy to wait till it gets to [testing] or [extra].
Comment by Ionut Biru (wonder) - Tuesday, 24 April 2012, 20:42 GMT
is already in extra. Just wait for your mirror to sync or change to a mirror that is already synced.
Comment by Mike Cloaked (mcloaked) - Tuesday, 24 April 2012, 20:47 GMT
Fabulous - thank you.
Comment by Mike Cloaked (mcloaked) - Tuesday, 24 April 2012, 21:39 GMT
OK 0.9.4-0-4 does get my connection working for ipw2200 - though the wireless icon on the panel of the KDE desktop no longer shows the correct signal strength as a set of arcs - (was fine with 0.9.2) however the iwconfig command shows normal data ( I replaced sensitive data with x's ):


eth1 IEEE 802.11bg ESSID:"mdc-guest"
Mode:Managed Frequency:2.422 GHz Access Point: xx:xx:xx:xx:xx:xx
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx Security mode:open
Power Management:off
Link Quality=96/100 Signal level=-29 dBm Noise level=-88 dBm
Rx invalid nwid:0 Rx invalid crypt:2 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

So this for me is a partial fix - maybe the desktop panel display is a separate package issue?
Comment by Ionut Biru (wonder) - Tuesday, 24 April 2012, 21:42 GMT
you should open a different bug.

Loading...