Arch Linux

T-u-N-i-X

Member

From: İstanbul

Registered: 2006-03-14

Posts: 435

Website

Wireless Connection Disconnects Randomly

I have a HP dv2580et laptop computer which has

07:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

in it.. It was working a few days ago. I'm using testing/core/extra/community repositories since the first time I use Arch Linux which is about 2 years.. I downgraded to core/kernel26 (2.6.23.14) and reinstalled iwlwifi but it didn't solve my problem. Same thing happens.. So I started to use testing/kernel26 without having iwlwifi again..

I'm dualbooting with Vista and Windows Upgrade just upgraded the driver for my wireless card. And suddenly Vista started to do the same.. So I suspect the ucode part of the iwlwifi driver might be somehow buggy..

I can't use my wireless card because of these random disconnections.. It's very annoying..

dmesg messages:

wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: authentication with AP 00:c0:49:62:9a:4f timed out
wlan0: authentication frame received from 00:c0:49:62:9a:4f, but not in authenticate state - ignored
wlan0: authentication frame received from 00:c0:49:62:9a:4f, but not in authenticate state - ignored
wlan0: authentication frame received from 00:c0:49:62:9a:4f, but not in authenticate state - ignored
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: RX authentication from 00:c0:49:62:9a:4f (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:c0:49:62:9a:4f
wlan0: RX AssocResp from 00:c0:49:62:9a:4f (capab=0x411 status=0 aid=3)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:c0:49:62:9a:4f)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
wlan0: RX deauthentication from 00:c0:49:62:9a:4f (reason=16)
wlan0: deauthenticated
wlan0: RX deauthentication from 00:c0:49:62:9a:4f (reason=7)
wlan0: RX deauthentication from 00:c0:49:62:9a:4f (reason=7)
wlan0: RX deauthentication from 00:c0:49:62:9a:4f (reason=7)
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: RX authentication from 00:c0:49:62:9a:4f (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:c0:49:62:9a:4f
wlan0: RX ReassocResp from 00:c0:49:62:9a:4f (capab=0x411 status=0 aid=3)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:c0:49:62:9a:4f)
wlan0: deauthenticate(reason=3)
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: RX authentication from 00:c0:49:62:9a:4f (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:c0:49:62:9a:4f
wlan0: RX AssocResp from 00:c0:49:62:9a:4f (capab=0x411 status=0 aid=3)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:c0:49:62:9a:4f)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: disassociate(reason=3)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: RX authentication from 00:c0:49:62:9a:4f (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:c0:49:62:9a:4f
wlan0: RX AssocResp from 00:c0:49:62:9a:4f (capab=0x411 status=0 aid=3)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:c0:49:62:9a:4f)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: deauthenticate(reason=3)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: RX authentication from 00:c0:49:62:9a:4f (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:c0:49:62:9a:4f
wlan0: RX AssocResp from 00:c0:49:62:9a:4f (capab=0x411 status=0 aid=3)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:c0:49:62:9a:4f)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
wlan0: RX deauthentication from 00:c0:49:62:9a:4f (reason=16)
wlan0: deauthenticated
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: authenticate with AP 00:c0:49:62:9a:4f
wlan0: authentication with AP 00:c0:49:62:9a:4f timed out
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present

And these are the /var/log/daemon.log messages:

Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) started...
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0/wireless): access point 'ALPERKANAT' is encrypted, but NO valid key exists.  New key needed.
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) New wireless user key requested for network 'ALPERKANAT'.
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jan 27 20:56:54 penguix NetworkManager: <info>  DHCP daemon state is now 14 (normal exit) for interface wlan0
Jan 27 20:56:54 penguix NetworkManager: <info>  DHCP daemon state is now 11 (unknown) for interface wlan0
Jan 27 20:56:54 penguix NetworkManager: <info>  DHCP daemon state is now 14 (normal exit) for interface wlan0
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) New wireless user key for network 'ALPERKANAT' received.
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0/wireless): access point 'ALPERKANAT' is encrypted, and a key exists.  No new key needed.
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: sending command 'INTERFACE_ADD wlan0               wext    /var/run/wpa_supplicant  '
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: response was 'OK'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: sending command 'AP_SCAN 1'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: response was 'OK'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: sending command 'ADD_NETWORK'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: response was '0'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 ssid 414c5045524b414e4154'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: response was 'OK'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 proto WPA'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: response was 'OK'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: response was 'OK'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 psk <key>'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: response was 'OK'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: sending command 'ENABLE_NETWORK 0'
Jan 27 20:56:54 penguix NetworkManager: <info>  SUP: response was 'OK'
Jan 27 20:56:54 penguix NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jan 27 20:57:00 penguix NetworkManager: <info>  nm_policy_device_change_check:: old_dev has_link? 1
Jan 27 20:57:00 penguix NetworkManager: <info>  Old device 'wlan0' activating, won't change.
Jan 27 20:57:09 penguix NetworkManager: <info>  Deactivating device wlan0.
Jan 27 20:57:09 penguix NetworkManager: <info>  Activation (wlan0): cancelling...
Jan 27 20:57:09 penguix NetworkManager: <info>  Activation (wlan0) cancellation handler scheduled...
Jan 27 20:57:09 penguix NetworkManager: <info>  Activation (wlan0): waiting for device to cancel activation.
Jan 27 20:57:09 penguix NetworkManager: <info>  Activation (wlan0) cancellation handled.
Jan 27 20:57:09 penguix NetworkManager: <info>  Activation (wlan0): cancelled.
Jan 27 20:57:09 penguix NetworkManager: <info>  nm_policy_device_change_check:: !old_dev && !new_dev!!
Jan 27 20:57:17 penguix NetworkManager: <info>  nm_device_set_active_link start
Jan 27 20:57:17 penguix NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link.
Jan 27 20:57:17 penguix NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'.
Jan 27 20:57:17 penguix NetworkManager: <info>  nm_policy_device_change_check:: lets try to switch device!
Jan 27 20:57:17 penguix NetworkManager: <info>  Will activate connection 'eth0'.
Jan 27 20:57:17 penguix NetworkManager: <info>  Device eth0 activation scheduled...
Jan 27 20:57:17 penguix NetworkManager: <info>  Activation (eth0) started...
Jan 27 20:57:17 penguix NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 27 20:57:17 penguix NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jan 27 20:57:17 penguix NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jan 27 20:57:17 penguix NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jan 27 20:57:17 penguix NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jan 27 20:57:17 penguix NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jan 27 20:57:17 penguix NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jan 27 20:57:17 penguix NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jan 27 20:57:17 penguix NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jan 27 20:57:18 penguix NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
Jan 27 20:57:18 penguix dhclient: wmaster0: unknown hardware address type 801
Jan 27 20:57:18 penguix NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth0
Jan 27 20:57:18 penguix NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jan 27 20:57:18 penguix NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth0
Jan 27 20:57:18 penguix dhclient: wmaster0: unknown hardware address type 801
Jan 27 18:57:19 penguix avahi-daemon[13751]: Registering new address record for fe80::216:d3ff:fef0:655b on eth0.*.
Jan 27 20:57:21 penguix dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 27 20:57:22 penguix dhclient: DHCPOFFER from 192.168.1.1
Jan 27 20:57:22 penguix dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 27 20:57:22 penguix dhclient: DHCPACK from 192.168.1.1
Jan 27 20:57:22 penguix NetworkManager: <info>  DHCP daemon state is now 2 (bound) for interface eth0
Jan 27 20:57:22 penguix NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Jan 27 20:57:22 penguix NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Jan 27 20:57:22 penguix NetworkManager: <info>  Retrieved the following IP4 configuration from the DHCP daemon:
Jan 27 20:57:22 penguix NetworkManager: <info>    address 192.168.1.3
Jan 27 20:57:22 penguix NetworkManager: <info>    netmask 255.255.255.0
Jan 27 20:57:22 penguix NetworkManager: <info>    broadcast 192.168.1.255
Jan 27 20:57:22 penguix NetworkManager: <info>    gateway 192.168.1.1
Jan 27 20:57:22 penguix NetworkManager: <info>    nameserver 208.67.222.222
Jan 27 20:57:22 penguix NetworkManager: <info>    nameserver 208.67.220.220
Jan 27 20:57:22 penguix NetworkManager: <info>    nameserver 192.168.1.1
Jan 27 20:57:22 penguix NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jan 27 20:57:22 penguix NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Jan 27 20:57:22 penguix NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Jan 27 20:57:22 penguix dhclient: bound to 192.168.1.3 -- renewal in 37920 seconds.
Jan 27 18:57:22 penguix avahi-daemon[13751]: Withdrawing address record for fe80::216:d3ff:fef0:655b on eth0.
Jan 27 18:57:22 penguix avahi-daemon[13751]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.3.
Jan 27 18:57:22 penguix avahi-daemon[13751]: New relevant interface eth0.IPv4 for mDNS.
Jan 27 18:57:22 penguix avahi-daemon[13751]: Registering new address record for 192.168.1.3 on eth0.IPv4.
Jan 27 18:57:23 penguix avahi-daemon[13751]: Got SIGTERM, quitting.
Jan 27 18:57:23 penguix avahi-daemon[13751]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.3.
Jan 27 20:57:23 penguix avahi-daemon[14223]: Found user 'avahi' (UID 84) and group 'avahi' (GID 84).
Jan 27 20:57:23 penguix avahi-daemon[14223]: Successfully dropped root privileges.
Jan 27 20:57:23 penguix avahi-daemon[14223]: avahi-daemon 0.6.20 starting up.
Jan 27 20:57:23 penguix avahi-daemon[14223]: Successfully called chroot().
Jan 27 18:57:23 penguix avahi-daemon[14223]: Successfully dropped remaining capabilities.
Jan 27 18:57:23 penguix avahi-daemon[14223]: Loading service file /services/sftp-ssh.service.
Jan 27 18:57:23 penguix avahi-daemon[14223]: Loading service file /services/ssh.service.
Jan 27 18:57:23 penguix avahi-daemon[14223]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.3.
Jan 27 18:57:23 penguix avahi-daemon[14223]: New relevant interface eth0.IPv4 for mDNS.
Jan 27 18:57:23 penguix avahi-daemon[14223]: Network interface enumeration completed.
Jan 27 18:57:23 penguix avahi-daemon[14223]: Registering new address record for fe80::216:d3ff:fef0:655b on eth0.*.
Jan 27 18:57:23 penguix avahi-daemon[14223]: Registering new address record for 192.168.1.3 on eth0.IPv4.
Jan 27 18:57:23 penguix avahi-daemon[14223]: Registering HINFO record with values 'I686'/'LINUX'.
Jan 27 20:57:23 penguix NetworkManager: <info>  nm_device_set_active_link start
Jan 27 20:57:23 penguix NetworkManager: <info>  Activation (eth0) Finish handler scheduled.
Jan 27 20:57:23 penguix NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jan 27 20:57:23 penguix NetworkManager: <info>  Activation (eth0) successful, device activated.
Jan 27 18:57:24 penguix avahi-daemon[14223]: Server startup complete. Host name is penguix.local. Local service cookie is 4115023546.
Jan 27 18:57:24 penguix avahi-daemon[14223]: Service "penguix" (/services/ssh.service) successfully established.
Jan 27 18:57:24 penguix avahi-daemon[14223]: Service "SFTP File Transfer on penguix" (/services/sftp-ssh.service) successfully established.

---

Quis custodiet ipsos custodiet?

phunkedelik

Member

Registered: 2008-06-17

Posts: 59

Re: Wireless Connection Disconnects Randomly

im having a similar if not the same problem my card is bcm4328

pyther

Member

Registered: 2008-01-21

Posts: 1,395

Website

Re: Wireless Connection Disconnects Randomly

@phunkedelik in your case it'll be best to post a new thread as this thread is over 7months old and I doubt your using kernel 2.6.23.14
Also are you using network-manager?

---

Website - Blog - arch-home
Arch User since March 2005

kjon

Member

From: Temuco, Chile

Registered: 2008-04-16

Posts: 398

Re: Wireless Connection Disconnects Randomly

Looks an acpi issue. Avoid using networkmanager and try the good n' ol' way of netcfg.

Networkmanager causes connection losing when it's performing its background network scanning. For instance, some atheros cards doesn't like that and collapse 'inso facto'.

Last edited by kjon (2008-09-01 00:43:56)

---

They say that if you play a Win cd backward you hear satanic messages. That's nothing! 'cause if you play it forwards, it installs windows.

pyther

Member

Registered: 2008-01-21

Posts: 1,395

Website

Re: Wireless Connection Disconnects Randomly

@kjon did you even bother to read my post, that issue is over 7 months old! There is a good chance it has been fixed now especially considering how popular the intel wireless card is.

---

Website - Blog - arch-home
Arch User since March 2005

kjon

Member

From: Temuco, Chile

Registered: 2008-04-16

Posts: 398

Re: Wireless Connection Disconnects Randomly

No, I did not. I just read the log files and made my own conclusions. Sorry to bother you.

---

They say that if you play a Win cd backward you hear satanic messages. That's nothing! 'cause if you play it forwards, it installs windows.