Your message dated Tue, 1 Nov 2011 03:02:30 +0100
with message-id <[email protected]>
and subject line [ipw3945 bugs]
has caused the Debian Bug report #459678,
regarding network-manager can't connect to my wireless network, it's dropped
whet trying to associate with router (timed out).
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
459678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459678
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.6.5-3
Severity: grave
Justification: renders package unusable
network-manager can't connect to my wireless network, it's dropped whet trying
to associate with router (timed out). my network without any
encryption and router allow connect from MAC address. when i tried to 'iwconfig
eth2 essid "my_net"' and then 'dhclient eth2' - network works
perfectly.
Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection
(rev 02)
dive:/home/dive# lsmod | grep 3945
ipw3945 192740 1
ieee80211 31656 1 ipw3945
firmware_class 9504 2 pcmcia,ipw3945
some log's info:
dive:/home/dive# NetworkManager --no-daemon
NetworkManager: <info> starting...
NetworkManager: <info> New VPN service 'openvpn'
(org.freedesktop.NetworkManager.openvpn).
NetworkManager: <info> New VPN service 'vpnc'
(org.freedesktop.NetworkManager.vpnc).
NetworkManager: <info> Found radio killswitch
/org/freedesktop/Hal/devices/ipw_wlan_switch
NetworkManager: <info> eth2: Device is fully-supported using driver 'ipw3945'.
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to
start
NetworkManager: <info> nm_device_init(): device's worker thread started,
continuing.
NetworkManager: <info> Now managing wireless (802.11) device 'eth2'.
NetworkManager: <info> Deactivating device eth2.
NetworkManager: <info> eth1: Device is fully-supported using driver 'sky2'.
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to
start
NetworkManager: <info> nm_device_init(): device's worker thread started,
continuing.
NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth1'.
NetworkManager: <info> Deactivating device eth1.
NetworkManager: <info> Updating allowed wireless network lists.
NetworkManager: <info> Wireless now enabled by radio killswitch
NetworkManager: <info> SWITCH: no current connection, found better connection
'eth2'.
NetworkManager: <info> Will activate connection 'eth2/divenet'.
NetworkManager: <info> Device eth2 activation scheduled...
NetworkManager: <info> Activation (eth2) started...
NetworkManager: <info> Activation (eth2) Stage 1 of 5 (Device Prepare)
scheduled...
NetworkManager: <info> Activation (eth2) Stage 1 of 5 (Device Prepare)
started...
NetworkManager: <info> Activation (eth2) Stage 2 of 5 (Device Configure)
scheduled...
NetworkManager: <info> Activation (eth2) Stage 1 of 5 (Device Prepare)
complete.
NetworkManager: <info> Activation (eth2) Stage 2 of 5 (Device Configure)
starting...
NetworkManager: <info> Activation (eth2/wireless): access point 'divenet' is
unencrypted, no key needed.
NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth2
wext /var/run/wpa_supplicant '
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
NetworkManager: <info> SUP: response was '0'
NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 646976656e6574'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Trying to associate with 00:13:49:e1:f4:4c (SSID='divenet' freq=2432 MHz)
NetworkManager: <info> SUP: response was 'OK'
NetworkManager: <info> Activation (eth2) Stage 2 of 5 (Device Configure)
complete.
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:49:e1:f4:4c (SSID='divenet' freq=2432 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:49:e1:f4:4c (SSID='divenet' freq=2432 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:49:e1:f4:4c (SSID='divenet' freq=2432 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:49:e1:f4:4c (SSID='divenet' freq=2432 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:49:e1:f4:4c (SSID='divenet' freq=2432 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:49:e1:f4:4c (SSID='divenet' freq=2432 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:49:e1:f4:4c (SSID='divenet' freq=2432 MHz)
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:49:e1:f4:4c (SSID='divenet' freq=2432 MHz)
NetworkManager: <WARN> nm_signal_handler(): Caught signal 2, shutting down
normally.
NetworkManager: <info> Caught terminiation signal
NetworkManager: <debug> [1199756624.895513] nm_print_open_socks(): Open Sockets
List:
NetworkManager: <debug> [1199756624.895578] nm_print_open_socks(): Open Sockets
List Done.
NetworkManager: <info> Deactivating device eth2.
NetworkManager: <info> Activation (eth2): cancelling...
NetworkManager: <info> Activation (eth2) cancellation handler scheduled...
NetworkManager: <info> Activation (eth2): waiting for device to cancel
activation.
NetworkManager: <info> Activation (eth2) cancellation handled.
NetworkManager: <info> Activation (eth2): cancelled.
CTRL-EVENT-TERMINATING - signal 15 received
sendmsg(CTRL_IFACE monitor): No such file or directory
NetworkManager: <info> Deactivating device eth1.
dive:/home/dive# dhclient eth2
There is already a pid file /var/run/dhclient.pid with pid 4170
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth2/00:19:d2:31:15:ca
Sending on LPF/eth2/00:19:d2:31:15:ca
Sending on Socket/fallback
DHCPREQUEST on eth2 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.35 -- renewal in 116066 seconds.
dive:/home/dive# tail -n0 -f /var/log/syslog > /tmp/syslog
....
Jan 8 05:11:29 dive NetworkManager: <info> Activation (eth2) started...
Jan 8 05:11:29 dive NetworkManager: <info> Activation (eth2) Stage 1 of 5
(Device Prepare) scheduled...
Jan 8 05:11:29 dive NetworkManager: <info> Activation (eth2) Stage 1 of 5
(Device Prepare) started...
Jan 8 05:11:29 dive NetworkManager: <info> Activation (eth2) Stage 2 of 5
(Device Configure) scheduled...
Jan 8 05:11:29 dive NetworkManager: <info> Activation (eth2) Stage 1 of 5
(Device Prepare) complete.
Jan 8 05:11:29 dive NetworkManager: <info> Activation (eth2) Stage 2 of 5
(Device Configure) starting...
Jan 8 05:11:29 dive NetworkManager: <info> Activation (eth2/wireless): access
point 'divenet' is unencrypted, no key needed.
Jan 8 05:11:30 dive NetworkManager: <info> SUP: sending command
'INTERFACE_ADD eth2^I^Iwext^I/var/run/wpa_supplicant^I'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: response was 'OK'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: response was 'OK'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: response was '0'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: sending command 'SET_NETWORK
0 ssid 646976656e6574'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: response was 'OK'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: sending command 'SET_NETWORK
0 key_mgmt NONE'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: response was 'OK'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: sending command
'ENABLE_NETWORK 0'
Jan 8 05:11:30 dive NetworkManager: <info> SUP: response was 'OK'
Jan 8 05:11:30 dive NetworkManager: <info> Activation (eth2) Stage 2 of 5
(Device Configure) complete.
....
and then silent... without any message and without connect.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages network-manager depends on:
ii adduser 3.105 add and remove users and groups
ii dbus 1.1.2-1 simple interprocess messaging syst
ii dhcdbd 3.0-1 D-Bus interface to the ISC DHCP cl
ii hal 0.5.10-5 Hardware Abstraction Layer
ii ifupdown 0.6.8 high level tools to configure netw
ii iproute 20071016-2 Professional tools to control the
ii iputils-arping 3:20071127-1 Tool to send ICMP echo requests to
ii libc6 2.7-5 GNU C Library: Shared libraries
ii libdbus-1-3 1.1.2-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.74-1 simple interprocess messaging syst
ii libgcrypt11 1.4.0-2 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.14.3-1 The GLib library of C routines
ii libgpg-error0 1.4-2 library for common error values an
ii libhal1 0.5.10-5 Hardware Abstraction Layer - share
ii libiw29 29~pre22-1 Wireless tools - library
ii libnl1-pre6 1.0~pre6-5 Library for dealing with netlink s
ii libnm-util0 0.6.5-3 network management framework (shar
ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip
ii wpasupplicant 0.6.0-4 Client support for WPA and WPA2 (I
Versions of packages network-manager recommends:
ii network-manager-gnome 0.6.5-3 network management framework (GNOM
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi
The ipw3945 kernel module no longer exists, as it has been replaced by
iwl3945/ iwlagn/ iwl-legacy which is implemented in completely
different ways. Closing this bug as it got no ping response in over a
month and given that two iwl-legacy users on iwl3945 hardware can't
reproduce this issue with recent kernels (3.0/ 3.1).
Regards
Stefan Lippers-Hollmann
--- End Message ---
