Gutsy Wireless Encryption BMCWL5 Driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
knetworkmanager (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: knetworkmanager
Using Feisty:
Ndiswrapper version 1.47 (compiled from source)
BCMWL5.INF was used to install (this is the Broadcom driver for the Dell Inspiron 9100 series Wireless)
Kernel 2.6.20-16-generic
Driver worked without issues.
Using Gutsy: (did the Adept Manager Version Upgrade)
Ndiswrapper version 1.47 (compiled from source)
BCMWL5.INF was used to install (this is the Broadcom driver for the Dell Inspiron 9100 series Wireless)
Kernal 2.6.22-14 generic.
Driver works fine with Open WiFi, but will not connect to any network using Encryption. I have set my home WAP to WEP, WPA, WPA2 and all iterations thereof.
Relevant section of var/log/syslog:
Oct 19 20:04:20 mylaptop NetworkManager: <debug> [1192838660.327823] nm_device_
Oct 19 20:04:20 mylaptop NetworkManager: <info> User Switch: /org/freedeskto
Oct 19 20:04:20 mylaptop NetworkManager: <info> Deactivating device wlan0.
Oct 19 20:04:20 mylaptop NetworkManager: <WARN> nm_device_
Oct 19 20:04:20 mylaptop dhcdbd: message_handler: message handler not found under /com/redhat/
Oct 19 20:04:20 mylaptop NetworkManager: <info> Device wlan0 activation scheduled...
Oct 19 20:04:20 mylaptop NetworkManager: <info> Deactivating device eth0.
Oct 19 20:04:20 mylaptop dhclient: There is already a pid file /var/run/
Oct 19 20:04:20 mylaptop dhclient: killed old client process, removed PID file
Oct 19 20:04:20 mylaptop dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67
Oct 19 20:04:20 mylaptop avahi-daemon[6408]: Withdrawing address record for 192.168.1.100 on eth0.
Oct 19 20:04:20 mylaptop avahi-daemon[6408]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.100.
Oct 19 20:04:20 mylaptop avahi-daemon[6408]: Interface eth0.IPv4 no longer relevant for mDNS.
Oct 19 20:04:21 mylaptop avahi-daemon[6408]: Withdrawing address record for fe80::20f:
Oct 19 20:04:21 mylaptop NetworkManager: <info> Activation (wlan0) started...
Oct 19 20:04:21 mylaptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 19 20:04:21 mylaptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 19 20:04:21 mylaptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 19 20:04:21 mylaptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 19 20:04:21 mylaptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 19 20:04:21 mylaptop NetworkManager: <info> Activation (wlan0/wireless): access point 'My_WAP' is encrypted, and a key exists. No new key needed.
Oct 19 20:04:22 mylaptop NetworkManager: <info> supplicant_
Oct 19 20:04:22 mylaptop NetworkManager: <info> supplicant_
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was 'OK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> supplicant_init() - connect to device ctrl socket (1/10).
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was 'OK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was '0'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 4c65736c69655f5
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was 'OK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was 'OK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was 'OK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was 'OK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was 'OK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 pairwise TKIP'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was 'OK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 group TKIP'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was 'OK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Oct 19 20:04:22 mylaptop NetworkManager: <info> SUP: response was 'OK'
Oct 19 20:04:22 mylaptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 19 20:05:22 mylaptop NetworkManager: <info> Activation (wlan0/wireless): association took too long (>60s), failing activation.
Oct 19 20:05:22 mylaptop NetworkManager: <info> Activation (wlan0) failure scheduled...
Oct 19 20:05:22 mylaptop NetworkManager: <info> Activation (wlan0) failed for access point (My_WAP)
Oct 19 20:05:22 mylaptop NetworkManager: <info> Activation (wlan0) failed.
Oct 19 20:05:22 mylaptop NetworkManager: <info> Deactivating device wlan0.
Oct 19 20:05:22 mylaptop NetworkManager: <info> SUP: sending command 'DISABLE_NETWORK 0'
Is this symptom still reproducible in 8.10?
(BTW, using a self-compiled component in the critical path generally invalidates a bug.)