[hardy] Network Manager can't deal with ndiswrapper's wifi interface

Bug #208196 reported by Stefano Marinelli
4
Affects Status Importance Assigned to Milestone
ndiswrapper (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Hardy updated on AMD64. My ndiswrapper wlan0 interface is seen by network-manager and I can see the list of the available wifi networks but it can't connect to any.
Doing a manual configuration, things work.

Revision history for this message
Alexander Sack (asac) wrote :

please attach the _complete_ /var/log/syslog taken _after_ a failed connect attempt.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Stefano Marinelli (draga-dragas-it) wrote :
Download full text (4.8 KiB)

Thank you for replying.
Here's the syslog extract as the complete syslog would also include the manual connection attempt:

Mar 28 21:12:10 dragasacer dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Mar 28 21:12:10 dragasacer NetworkManager: <debug> [1206735130.883083] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'dragas_wl'
Mar 28 21:12:10 dragasacer NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / dragas_wl
Mar 28 21:12:10 dragasacer NetworkManager: <info> Deactivating device wlan0.
Mar 28 21:12:10 dragasacer NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Mar 28 21:12:10 dragasacer NetworkManager: <info> Device wlan0 activation scheduled...
Mar 28 21:12:10 dragasacer NetworkManager: <info> Activation (wlan0) started...
Mar 28 21:12:10 dragasacer NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 28 21:12:10 dragasacer NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 28 21:12:10 dragasacer NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 28 21:12:10 dragasacer NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 28 21:12:10 dragasacer NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 28 21:12:10 dragasacer NetworkManager: <info> Activation (wlan0/wireless): access point 'dragas_wl' is encrypted, but NO valid key exists. New key needed.
Mar 28 21:12:10 dragasacer NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'dragas_wl'.
Mar 28 21:12:10 dragasacer NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar 28 21:12:25 dragasacer NetworkManager: <info> Activation (wlan0) New wireless user key for network 'dragas_wl' received.
Mar 28 21:12:25 dragasacer NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 28 21:12:25 dragasacer NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 28 21:12:25 dragasacer NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 28 21:12:25 dragasacer NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 28 21:12:25 dragasacer NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 28 21:12:25 dragasacer NetworkManager: <info> Activation (wlan0/wireless): access point 'dragas_wl' is encrypted, and a key exists. No new key needed.
Mar 28 21:12:26 dragasacer NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Mar 28 21:12:27 dragasacer NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Mar 28 21:12:27 dragasacer kernel: [ 97.625862] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Mar 28 21:12:27 dragasacer kernel: [ 97.676506] NET: Registered protocol family 17
Mar 28 21:12:27 dragasacer NetworkManager: <...

Read more...

Revision history for this message
Alexander Sack (asac) wrote :

network manager has a high bar for drivers. ndiswrapper needs to be fixed.

Revision history for this message
Jayson Rowe (jayson.rowe) wrote :

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ndiswrapper (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.