I recently purchased a new laptop with an Intel IWL4965 card, the iwlwifi drivers work well except I seem to lose my connection after around an hour of use. For the heck of it I tried connecting with NM stopped and just ran wpa_supplicant and my connection remained stable. I then ran NetworkManager --no-daemon and got this error after about 30-40 minutes and my connection dropped ~ 5 minutes later:
*** stack smashing detected ***: /sbin/wpa_supplicant terminated NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '��ӷ��ӷ NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Connection refused NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '��ӷ��ӷ NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '��ӷ��ӷ NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected The strange thing is that NM thinks I am still associated... When I click on nm-applet and tell it to connect back to my AP it connects fine and this is the output: ed NetworkManager: <debug> [1189480089.333758] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'junkyard' NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / junkyard NetworkManager: <info> Deactivating device wlan0. NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '��ӷ��ӷ NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected NetworkManager: <info> SUP: sending command 'DISABLE_NETWORK 0' NetworkManager: <info> SUP: response was '��ӷ��ӷ NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): supplicant_cleanup: supplicant error for 'DISABLE_NETWORK 0'. Response: '��ӷ��ӷ NetworkManager: <WARN> supplicant_cleanup(): supplicant_cleanup - couldn't disable network in supplicant_cleanup NetworkManager: <info> SUP: sending command 'AP_SCAN 0' NetworkManager: <info> SUP: response was '��ӷ��ӷ NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): supplicant_cleanup: supplicant error for 'AP_SCAN 0'. Response: '��ӷ��ӷ NetworkManager: <WARN> supplicant_cleanup(): supplicant_cleanup - couldn't set AP_SCAN 0 NetworkManager: <info> SUP: sending command 'TERMINATE' NetworkManager: <info> SUP: response was '��ӷ��ӷ NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): supplicant_cleanup: supplicant error for 'TERMINATE'. Response: '��ӷ��ӷ NetworkManager: <WARN> supplicant_cleanup(): supplicant_cleanup - couldn't terminate wpasupplicant cleanly. NetworkManager: <info> Device wlan0 activation scheduled... NetworkManager: <info> Activation (wlan0) started... NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... There is an open bug report for this issue on intel's bughost at http://bughost.org/bugzilla/show_bug.cgi?id=1360 but I am beginning to wonder if this might be a NM (or possibly a Gutsy specific issue?) I am running Ubuntu 7.10 (Gutsy) with Network Manager 6.5 with a IWL4965 wireless NIC on a Lenovo T61. This list had been quiet for a few days so I figured it was time to drop a message ;-) Thanks! _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
