You are not logged in.

#1 2010-06-09 21:40:53

nss_archer
Member
Registered: 2010-06-09
Posts: 7

No wireless connection

Hello everybody.

I've installed Arch64 few days ago. I tried hard to set my wireless connection but i failed.

some times i can connect but with lot of difficulties and when i try to repeat same steps i fail.
i read the wiki about wireless setup many times. wlan0 is detected i can scan networks and associate (some times it fails) when i execute

dhcpcd wlan0

carrier lost issue even i specified channel auto.

the loaded driver is ath9k. i have atheros AR9285

i can connect using lan with eth0 it works great but i can't stay attached to my wire i have a laptop.

Last edited by nss_archer (2010-07-03 12:24:21)

Offline

#2 2010-06-10 16:47:56

nss_archer
Member
Registered: 2010-06-09
Posts: 7

Re: No wireless connection

i forgot to mention that the connection works on ubuntu lucid perfectly

Offline

#3 2010-06-10 18:19:15

frigaut
Member
From: Canberra, Australia
Registered: 2009-05-10
Posts: 215
Website

Re: No wireless connection

The atheros AR9285 is listed as being supported by ath9k, indeed.
What program is handling your network connection, if any? networkmanager, wicd, netcfg?
Do you know if lucid is using ath9k or madwifi?

Also, I'm not sure to understand what is exactly the nature of the problem. You say wlan0 is listed and can scan network, and (sometime) actually associate to them. So what's the issue? The "sometimes"?

Can you dump here the results of "lspci -v", "ifconfig wlan0" and may be "iwlist wlan0 scan"? Did you install wpa_supplicant?


Archer since 03/2009 - AUR packages

Offline

#4 2010-06-10 19:44:55

nss_archer
Member
Registered: 2010-06-09
Posts: 7

Re: No wireless connection

thank u frigaut for ur reply

i didn't install any driver the driver for ath9k comes with the kernel.
i tried to connect using wireless_tools. and networkmanager. both doesn't work.

the problem is that i rarly succeed to esbalish the wireless network.
and sometimes i try about 40 times to succeed and sometimes i never succeed.

when i compare lsmod from arch and lucid i see that they both load:
cfg80211, mac80211, ath9k, ath

but arch loads also: ath9k_hw, ath9k_common.

and when i blacklist these 2 modules udev doesn't load all the rest too. because ath9k in arch depends on these two modules.


dmesg | grep ath

ath9k 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ath9k 0000:02:00.0: setting latency timer to 64
ath: EEPROM regdomain: 0x60
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x60
phy0: Selected rate control algorithm 'ath9k_rate_control'
Registered led device: ath9k-phy0::radio
Registered led device: ath9k-phy0::assoc
Registered led device: ath9k-phy0::tx
Registered led device: ath9k-phy0::rx
ath9k: Two wiphys trying to scan at the same time

lspci | grep -i net

02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

lsmod | grep ath

ath9k                  72278  0 
ath9k_common            2529  1 ath9k
mac80211              182567  2 ath9k,ath9k_common
ath9k_hw              216792  2 ath9k,ath9k_common
ath                     8790  2 ath9k,ath9k_hw
cfg80211              141568  4 ath9k,ath9k_common,mac80211,ath
led_class               2347  1 ath9k

ifconfig -a

eth0      Link encap:Ethernet  HWaddr C8:0A:A9:34:AE:9D  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:27 Base address:0xe000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2100 (2.0 Kb)  TX bytes:2100 (2.0 Kb)

wlan0     Link encap:Ethernet  HWaddr C4:17:FE:5B:1E:D2  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

iwconfig wlan0 essid "ADSL9563"
iwconfig wlan0

wlan0     IEEE 802.11bgn  ESSID:"ADSL9563"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

dhcpcd wlan0

dhcpcd[2462]: version 5.2.5 starting
dhcpcd[2462]: wlan0: waiting for carrier
dhcpcd[2462]: wlan0: carrier acquired
dhcpcd[2462]: wlan0: broadcasting for a lease
dhcpcd[2462]: wlan0: carrier lost
dhcpcd[2462]: timed out

sometimes i can connect and with the same output for iwconfig wlan0.

i don't know if it's the problem:
ath9k: Two wiphys trying to scan at the same time

Last edited by nss_archer (2010-07-05 00:06:46)

Offline

#5 2010-06-10 22:28:49

nss_archer
Member
Registered: 2010-06-09
Posts: 7

Re: No wireless connection

i can connect to the internet now suddenly. i don't know what was the exact problem.i'll wait and see.

Offline

#6 2010-06-28 18:19:53

nss_archer
Member
Registered: 2010-06-09
Posts: 7

Re: No wireless connection

still the same problem

Last edited by nss_archer (2010-07-03 12:24:54)

Offline

#7 2010-07-04 18:05:23

nss_archer
Member
Registered: 2010-06-09
Posts: 7

Re: No wireless connection

dmesg | grep ath

ath9k 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ath9k 0000:02:00.0: setting latency timer to 64
ath: EEPROM regdomain: 0x60
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x60
phy0: Selected rate control algorithm 'ath9k_rate_control'
Registered led device: ath9k-phy0::radio
Registered led device: ath9k-phy0::assoc
Registered led device: ath9k-phy0::tx
Registered led device: ath9k-phy0::rx
ath9k: Two wiphys trying to scan at the same time

i don't know if it's the problem:
ath9k: Two wiphys trying to scan at the same time

Last edited by nss_archer (2010-07-05 00:07:17)

Offline

#8 2010-08-01 16:19:48

deluminathor
Member
From: Poland
Registered: 2008-09-14
Posts: 16

Re: No wireless connection

Hi,
I have a similar problem. My network card is also Atheros AR9285 with ath9k driver and laptop is Sony Vaio VPC-EA1S1E. I tried manual connecting, netcfg and networkmanager. Each of them causes problems although a bit different.

When I try to connect manually

1. First I run:

sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid Drums

2. Then:

sudo wpa_supplicant -c /etc/wpa_supplicant.conf -iwlan0 -d

and the wpa_supplicant log is:

Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=1
ap_scan=1
fast_reauth=1
Priority group 0
   id=0 ssid='Drums'
   id=1 ssid='Hellland'
   id=2 ssid='pindolindolandia'
   id=3 ssid='AGH-WPA'
   id=4 ssid='infiniteloop'
   id=5 ssid='erlang'
   id=6 ssid='VLO WiFi DWO'
Initializing interface (2) 'wlan0'
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 78:dd:08:c7:c4:c2
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): 8f e8 35 d2 a9 e5 54 c6 a0 c6 f2 e6 d7 21 a2 f0
WPS: Build Beacon and Probe Response IEs
WPS:  * Version
WPS:  * Wi-Fi Protected Setup State (0)
WPS:  * Version
WPS:  * Wi-Fi Protected Setup State (0)
WPS:  * Response Type (2)
WPS:  * UUID-E
WPS:  * Manufacturer
WPS:  * Model Name
WPS:  * Model Number
WPS:  * Serial Number
WPS:  * Primary Device Type
WPS:  * Device Name
WPS:  * Config Methods (0)
WPS:  * RF Bands (3)
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b1a len=48
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Failed to get scan results
Failed to get scan results - try scanning again
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
ioctl[SIOCSIWSCAN]: Device or resource busy
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 10 sec 0 usec
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Failed to get scan results
Failed to get scan results - try scanning again
Setting scan request: 1 sec 0 usec
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Received 636 bytes of scan results (1 BSSes)
New scan results available
WPS-AP-AVAILABLE 
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:22:b0:b3:e6:96 ssid='Drums' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   selected based on RSN IE
   selected WPA AP 00:22:b0:b3:e6:96 ssid='Drums'
Trying to associate with 00:22:b0:b3:e6:96 (SSID='Drums' freq=2447 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2 proto 2
WPA: clearing AP WPA IE
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b1a len=21
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Received 1024 bytes of scan results (2 BSSes)
New scan results available
WPS-AP-AVAILABLE 
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:22:b0:b3:e6:96 ssid='Drums' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   selected based on RSN IE
   selected WPA AP 00:22:b0:b3:e6:96 ssid='Drums'
Already associated with the selected AP.
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8c08 len=170
AssocResp IE wireless event - hexdump(len=154): 01 04 82 84 8b 96 32 08 8c 12 98 24 b0 48 60 6c dd 1e 00 90 4c 33 4e 10 1f ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 1a 00 90 4c 34 08 07 07 00 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2d 1a 4e 10 1f ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 3d 16 08 07 03 00 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 18 00 50 f2 02 01 01 00 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:22:b0:b3:e6:96
Association info event
resp_ies - hexdump(len=154): 01 04 82 84 8b 96 32 08 8c 12 98 24 b0 48 60 6c dd 1e 00 90 4c 33 4e 10 1f ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 1a 00 90 4c 34 08 07 07 00 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2d 1a 4e 10 1f ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 3d 16 08 07 03 00 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 18 00 50 f2 02 01 01 00 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:22:b0:b3:e6:96
No keys have been configured - skip key clearing
Associated with 00:22:b0:b3:e6:96
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RX EAPOL from 00:22:b0:b3:e6:96
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=2
  key_info 0x8a (ver=2 keyidx=0 rsvd=0 Pairwise Ack)
  key_length=16 key_data_length=0
  replay_counter - hexdump(len=8): 00 00 00 00 00 00 03 a5
  key_nonce - hexdump(len=32): 18 8d 06 08 76 ed 1d 0d 09 2f b9 e3 73 39 7f c5 f9 b9 62 e3 3b 22 c6 2c 17 94 2c 25 06 5d b4 26
  key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:22:b0:b3:e6:96 (ver=2)
RSN: msg 1/4 key data - hexdump(len=0):
WPA: Renewed SNonce - hexdump(len=32): 6c db 68 2f 3d ea 7c f5 dc 0d d6 26 1c a7 3d e5 46 99 33 28 b7 aa 03 a8 ba 23 22 e4 1f 3b fb 5d
WPA: PTK derivation - A1=78:dd:08:c7:c4:c2 A2=00:22:b0:b3:e6:96
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=48): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:22:b0:b3:e6:96
IEEE 802.1X RX: version=1 type=3 length=151
  EAPOL-Key type=2
  key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
  key_length=16 key_data_length=56
  replay_counter - hexdump(len=8): 00 00 00 00 00 00 03 a6
  key_nonce - hexdump(len=32): 18 8d 06 08 76 ed 1d 0d 09 2f b9 e3 73 39 7f c5 f9 b9 62 e3 3b 22 c6 2c 17 94 2c 25 06 5d b4 26
  key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_mic - hexdump(len=16): 9f 08 64 90 e6 66 6b e2 50 cf 2e 51 2f 85 44 54
RSN: encrypted key data - hexdump(len=56): 71 0c 43 76 4f f3 c8 04 6b c5 3a 1e c6 de 07 00 02 04 43 12 a8 39 b5 cd 81 bc 50 2e 25 4a 0b e6 b7 5b 92 a8 8d f9 97 77 7d 1a be 24 7a ef eb f4 d1 7b e9 9d 22 ac 86 84
WPA: decrypted EAPOL-Key key data - hexdump(len=48): [REMOVED]
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:22:b0:b3:e6:96 (ver=2)
WPA: IE KeyData - hexdump(len=48): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00 dd 16 00 0f ac 01 02 00 3a 91 38 6e ef a3 0d 15 2e 09 9c 7c 20 2a ec 0d dd 00
WPA: Sending EAPOL-Key 4/4
WPA: Installing PTK to the driver.
wpa_driver_wext_set_key: alg=3 key_idx=0 set_tx=1 seq_len=6 key_len=16
EAPOL: External notification - portValid=1
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
RSN: received GTK in pairwise handshake - hexdump(len=18): [REMOVED]
WPA: Group Key - hexdump(len=16): [REMOVED]
WPA: Installing GTK to the driver (keyidx=2 tx=0 len=16).
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=3 key_idx=2 set_tx=0 seq_len=6 key_len=16
WPA: Key negotiation completed with 00:22:b0:b3:e6:96 [PTK=CCMP GTK=CCMP]
Cancelling authentication timeout
State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:22:b0:b3:e6:96 completed (auth) [id=0 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state DISABLED
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
EAPOL authentication completed successfully
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
EAPOL: startWhen --> 0
EAPOL: disable timer tick

So it properly associates with my AP.

dmesg output from this phase looks as follows:

ADDRCONF(NETDEV_UP): wlan0: link is not ready
ath9k: Two wiphys trying to scan at the same time
wlan0: deauthenticating from 00:22:b0:b3:e6:96 by local choice (reason=3)
wlan0: authenticate with 00:22:b0:b3:e6:96 (try 1)
wlan0: authenticated
wlan0: associate with 00:22:b0:b3:e6:96 (try 1)
wlan0: RX AssocResp from 00:22:b0:b3:e6:96 (capab=0x431 status=0 aid=4)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present

3. Then I try to get IP from DHCP and this is where the problems appear. I tried both dhcpcd and dhclient but none of them worked.
dhcpcd

sudo dhcpcd -d wlan0

produces:

dhcpcd[4592]: version 5.2.5 starting
dhcpcd[4592]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd[4592]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd[4592]: wlan0: reading lease `/var/lib/dhcpcd/dhcpcd-wlan0.lease'
dhcpcd[4592]: wlan0: rebinding lease of 192.168.1.190
dhcpcd[4592]: wlan0: sending REQUEST (xid 0x303e338), next in 3.14 seconds
dhcpcd[4592]: wlan0: sending REQUEST (xid 0x303e338), next in 8.18 seconds
dhcpcd[4592]: wlan0: broadcasting for a lease
dhcpcd[4592]: wlan0: sending DISCOVER (xid 0x4283daf5), next in 3.67 seconds
dhcpcd[4592]: wlan0: sending DISCOVER (xid 0x4283daf5), next in 8.48 seconds
dhcpcd[4592]: wlan0: sending DISCOVER (xid 0x4283daf5), next in 15.99 seconds
dhcpcd[4592]: timed out

dhclient

sudo dhclient -d wlan0

produces:

Internet Systems Consortium DHCP Client 4.2.0
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit [url]https://www.isc.org/software/dhcp/[/url]

can't create /var/db/dhclient.leases: No such file or directory                                                                                                                                                                  
Listening on LPF/wlan0/78:dd:08:c7:c4:c2                                                                                                                                                                                         
Sending on   LPF/wlan0/78:dd:08:c7:c4:c2                                                                                                                                                                                         
Sending on   Socket/fallback                                                                                                                                                                                                     
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3                                                                                                                                                                      
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5                                                                                                                                                                      
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14                                                                                                                                                                     
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12                                                                                                                                                                     
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9                                                                                                                                                                      
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12                                                                                                                                                                     
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6                                                                                                                                                                      
No DHCPOFFERS received.                                                                                                                                                                                                          
No working leases in persistent database - sleeping.
When I try to use netcfg

Netcfg usually fails when running:

sudo netcfg Drums

with message:

:: Drums up           [BUSY]
 > DHCP IP lease attempt failed.      [FAIL]

but sometimes (very rarely) it does connect.

When I try to use networkmanager (with knetworkmanager as graphical interface)

1. After reboot or resume (after suspend) networkmanager doesn't connect automatically and the log looks as follows:

Aug  1 12:16:23 svea NetworkManager: <info>  starting...
Aug  1 12:16:23 svea NetworkManager: <info>  Trying to start the modem-manager...
Aug  1 12:16:23 svea NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Aug  1 12:16:23 svea NetworkManager: <info>  Found wlan radio killswitch rfkill0 (at /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/SNY5001:00/rfkill/rfkill0) (driver Sony Notebook Control Driver)
Aug  1 12:16:23 svea NetworkManager: <info>  Found wlan radio killswitch rfkill2 (at /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/ieee80211/phy0/rfkill2) (driver <unknown>)
Aug  1 12:16:23 svea NetworkManager: <info>  WiFi enabled by radio killswitch; enabled by state file
Aug  1 12:16:23 svea NetworkManager: <info>  WWAN enabled by radio killswitch; enabled by state file
Aug  1 12:16:23 svea NetworkManager: <info>  (wlan0): driver supports SSID scans (scan_capa 0x01).
Aug  1 12:16:23 svea NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver: 'ath9k')
Aug  1 12:16:23 svea NetworkManager: <info>  (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0
Aug  1 12:16:23 svea NetworkManager: <info>  (wlan0): now managed
Aug  1 12:16:23 svea NetworkManager: <info>  (wlan0): device state change: 1 -> 2 (reason 2)
Aug  1 12:16:23 svea NetworkManager: <info>  (wlan0): bringing up device.
Aug  1 12:16:23 svea NetworkManager: <info>  (wlan0): preparing device.
Aug  1 12:16:23 svea NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
Aug  1 12:16:23 svea NetworkManager: <info>  (eth0): carrier is OFF
Aug  1 12:16:23 svea NetworkManager: <info>  (eth0): new Ethernet device (driver: 'sky2')
Aug  1 12:16:23 svea NetworkManager: <info>  (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Aug  1 12:16:23 svea NetworkManager: <info>  (eth0): now managed
Aug  1 12:16:23 svea NetworkManager: <info>  (eth0): device state change: 1 -> 2 (reason 2)
Aug  1 12:16:23 svea NetworkManager: <info>  (eth0): preparing device.
Aug  1 12:16:23 svea NetworkManager: <info>  (eth0): deactivating device (reason: 2).
Aug  1 12:16:23 svea NetworkManager: Added default wired connection 'Auto eth0' for /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/net/eth0
Aug  1 12:16:23 svea NetworkManager: <WARN>  default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
Aug  1 12:16:23 svea NetworkManager: <WARN>  user_connection_get_settings_cb(): Couldn't retrieve connection settings: Message did not receive a reply (timeout by message bus).
Aug  1 12:16:23 svea NetworkManager: <info>  (wlan0): supplicant interface state:  starting -> ready
Aug  1 12:16:23 svea NetworkManager: <info>  (wlan0): device state change: 2 -> 3 (reason 42)
Aug  1 12:16:33 svea NetworkManager: <info>  Activation (wlan0) starting connection 'Drums'
Aug  1 12:16:33 svea NetworkManager: <info>  (wlan0): device state change: 3 -> 4 (reason 0)
Aug  1 12:16:33 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug  1 12:16:33 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug  1 12:16:33 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug  1 12:16:33 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug  1 12:16:33 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug  1 12:16:33 svea NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Aug  1 12:16:33 svea NetworkManager: <info>  Activation (wlan0/wireless): access point 'Drums' has security, but secrets are required.
Aug  1 12:16:33 svea NetworkManager: <info>  (wlan0): device state change: 5 -> 6 (reason 0)
Aug  1 12:16:33 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug  1 12:16:38 svea NetworkManager: <WARN>  secrets_update_setting(): Failed to update connection secrets: 1 802-1x
Aug  1 12:16:38 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug  1 12:16:38 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug  1 12:16:38 svea NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
Aug  1 12:16:38 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug  1 12:16:38 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug  1 12:16:38 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug  1 12:16:38 svea NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Aug  1 12:16:38 svea NetworkManager: <info>  Activation (wlan0/wireless): connection 'Drums' has security, and secrets exist.  No new secrets needed.
Aug  1 12:16:38 svea NetworkManager: <info>  Config: added 'ssid' value 'Drums'
Aug  1 12:16:38 svea NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Aug  1 12:16:38 svea NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Aug  1 12:16:38 svea NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Aug  1 12:16:38 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug  1 12:16:38 svea NetworkManager: <info>  Config: set interface ap_scan to 1
Aug  1 12:16:38 svea NetworkManager: <info>  (wlan0): supplicant connection state:  inactive -> scanning
Aug  1 12:16:39 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 12:16:49 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug  1 12:16:49 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 12:16:50 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 12:16:50 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Aug  1 12:16:50 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Aug  1 12:16:50 svea NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake
Aug  1 12:16:50 svea NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
Aug  1 12:16:50 svea NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Drums'.
Aug  1 12:16:50 svea NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Aug  1 12:16:50 svea NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Aug  1 12:16:50 svea NetworkManager: <info>  (wlan0): device state change: 5 -> 7 (reason 0)
Aug  1 12:16:50 svea NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction (timeout in 45 seconds)
Aug  1 12:16:50 svea NetworkManager: <info>  dhcpcd started with pid 4749
Aug  1 12:16:50 svea NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) scheduled...
Aug  1 12:16:50 svea NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Aug  1 12:16:50 svea NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) started...
Aug  1 12:16:50 svea NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete.
Aug  1 12:16:50 svea NetworkManager: <info>  DHCP: device wlan0 state changed (null) -> preinit

2. Then I click my network profile in knetworkmanager again and it successfully connects:

Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): device state change: 7 -> 3 (reason 0)
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): deactivating device (reason: 0).
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) starting connection 'Drums'
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): device state change: 3 -> 4 (reason 0)
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0/wireless): connection 'Drums' has security, and secrets exist.  No new secrets needed.
Aug  1 12:18:27 svea NetworkManager: <info>  Config: added 'ssid' value 'Drums'
Aug  1 12:18:27 svea NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Aug  1 12:18:27 svea NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Aug  1 12:18:27 svea NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug  1 12:18:27 svea NetworkManager: <info>  Config: set interface ap_scan to 1
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> disconnected
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Drums'.
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Aug  1 12:18:27 svea NetworkManager: <info>  (wlan0): device state change: 5 -> 7 (reason 0)
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction (timeout in 45 seconds)
Aug  1 12:18:27 svea NetworkManager: <info>  dhcpcd started with pid 4757
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) scheduled...
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) started...
Aug  1 12:18:27 svea NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete.
Aug  1 12:18:38 svea NetworkManager: <info>  DHCP: device wlan0 state changed preinit -> bound
Aug  1 12:18:38 svea NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Aug  1 12:18:38 svea NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Aug  1 12:18:38 svea NetworkManager: <info>    address 192.168.1.190
Aug  1 12:18:38 svea NetworkManager: <info>    prefix 24 (255.255.255.0)
Aug  1 12:18:38 svea NetworkManager: <info>    gateway 192.168.1.1
Aug  1 12:18:38 svea NetworkManager: <info>    nameserver '212.76.34.49'
Aug  1 12:18:38 svea NetworkManager: <info>    nameserver '212.76.34.50'
Aug  1 12:18:38 svea NetworkManager: <info>    domain name 'home.aster.pl'
Aug  1 12:18:38 svea NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Aug  1 12:18:38 svea NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Aug  1 12:18:38 svea NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Aug  1 12:18:39 svea NetworkManager: <info>  (wlan0): device state change: 7 -> 8 (reason 0)
Aug  1 12:18:39 svea NetworkManager: <info>  Policy set 'Drums' (wlan0) as default for routing and DNS.
Aug  1 12:18:39 svea NetworkManager: <info>  Activation (wlan0) successful, device activated.
Aug  1 12:18:39 svea NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.

3. At this stage WiFi works properly. I tried launching ping every 5 seconds and it worked even one hour (maybe could even longer but I interrupted it).

4. From time to time WiFi reassociates which is observable in log:

Aug  1 12:43:32 svea NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> disconnected
Aug  1 12:43:32 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 12:43:33 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 12:43:33 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Aug  1 12:43:36 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Aug  1 12:43:36 svea NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake
Aug  1 12:43:36 svea NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed

and in dmesg:

wlan0: deauthenticated from 00:22:b0:b3:e6:96 (Reason: 6)
cfg80211: Calling CRDA to update world regulatory domain
wlan0: authenticate with 00:22:b0:b3:e6:96 (try 1)
wlan0: authenticated
wlan0: associate with 00:22:b0:b3:e6:96 (try 1)
wlan0: RX AssocResp from 00:22:b0:b3:e6:96 (capab=0x431 status=0 aid=4)
wlan0: associated

And network still works after a few such reassiciations.

5. If I leave internet connection idle for some time (e.g. browse Web Pages and don't download anything in the backgroud) or run some high-speed transfer (e.g. using NFS over my 802.11n home network) then after a few minutes network stops working. The log looks as follows:

Aug  1 13:32:55 svea NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> disconnected
Aug  1 13:32:56 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 13:32:57 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 13:33:00 svea NetworkManager: <debug> [1280662380.003345] periodic_update(): Roamed from BSSID 00:22:B0:B3:E6:96 (Drums) to (none) ((none))
Aug  1 13:33:07 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug  1 13:33:07 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 13:33:08 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 13:33:08 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated

And dmesg:

wlan0: deauthenticated from 00:22:b0:b3:e6:96 (Reason: 4)
cfg80211: Calling CRDA to update world regulatory domain
wlan0: authenticate with 00:22:b0:b3:e6:96 (try 1)
wlan0: authenticated
wlan0: associate with 00:22:b0:b3:e6:96 (try 1)
wlan0: RX AssocResp from 00:22:b0:b3:e6:96 (capab=0x431 status=0 aid=4)
wlan0: associated

So it looks quite similar to one of those periodical reassociations but now network doesn't work.

6. Now when I try to reconnect (by clicking my network profile in knetworkmanager) it sometimes reconnects and brings my network connection back to work but sometimes doesn't help and networkmanager stucks in a loop where it tries to reconnect but unexpectedly asks me for my WiFi network password (which knows very well as it's saved in a profile), I click OK and after a while it asks again and so on... Log looks as follows:

Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): device state change: 8 -> 3 (reason 11)
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): deactivating device (reason: 11).
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): canceled DHCP transaction, dhcp client pid 4757
Aug  1 13:33:11 svea NetworkManager: <WARN>  nm_dhcp_manager_handle_event(): Received DHCP event from unexpected PID 4757 (expected 0)
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) starting connection 'Drums'
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): device state change: 3 -> 4 (reason 0)
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0/wireless): access point 'Drums' has security, but secrets are required.
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): device state change: 5 -> 6 (reason 0)
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> disconnected
Aug  1 13:33:11 svea NetworkManager: <WARN>  secrets_update_setting(): Failed to update connection secrets: 1 802-1x
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0/wireless): connection 'Drums' has security, and secrets exist.  No new secrets needed.
Aug  1 13:33:11 svea NetworkManager: <info>  Config: added 'ssid' value 'Drums'
Aug  1 13:33:11 svea NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Aug  1 13:33:11 svea NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Aug  1 13:33:11 svea NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Aug  1 13:33:11 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug  1 13:33:11 svea NetworkManager: <info>  Config: set interface ap_scan to 1
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 13:33:11 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Aug  1 13:33:14 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Aug  1 13:33:23 svea NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> disconnected
Aug  1 13:33:23 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 13:33:24 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
Aug  1 13:33:24 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 13:33:24 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 13:33:34 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug  1 13:33:34 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 13:33:35 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 13:33:35 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Aug  1 13:33:37 svea NetworkManager: <info>  Activation (wlan0/wireless): association took too long.
Aug  1 13:33:37 svea NetworkManager: <info>  (wlan0): device state change: 5 -> 6 (reason 0)
Aug  1 13:33:37 svea NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets
Aug  1 13:33:37 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> disconnected
Aug  1 13:33:52 svea NetworkManager: <info>  wlan0: link timed out.
Aug  1 13:34:07 svea NetworkManager: <WARN>  secrets_update_setting(): Failed to update connection secrets: 1 802-1x
Aug  1 13:34:07 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug  1 13:34:07 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug  1 13:34:07 svea NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
Aug  1 13:34:07 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug  1 13:34:07 svea NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug  1 13:34:07 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug  1 13:34:07 svea NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Aug  1 13:34:07 svea NetworkManager: <info>  Activation (wlan0/wireless): connection 'Drums' has security, and secrets exist.  No new secrets needed.
Aug  1 13:34:07 svea NetworkManager: <info>  Config: added 'ssid' value 'Drums'
Aug  1 13:34:07 svea NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Aug  1 13:34:07 svea NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Aug  1 13:34:07 svea NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Aug  1 13:34:07 svea NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug  1 13:34:07 svea NetworkManager: <info>  Config: set interface ap_scan to 1
Aug  1 13:34:07 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 13:34:08 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 13:34:18 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug  1 13:34:18 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 13:34:19 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 13:34:19 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Aug  1 13:34:22 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Aug  1 13:34:31 svea NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> disconnected
Aug  1 13:34:31 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 13:34:32 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
Aug  1 13:34:32 svea NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug  1 13:34:32 svea NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug  1 13:34:32 svea NetworkManager: <info>  Activation (wlan0/wireless): association took too long.
Aug  1 13:34:32 svea NetworkManager: <info>  (wlan0): device state change: 5 -> 6 (reason 0)
Aug  1 13:34:33 svea NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets
Aug  1 13:34:33 svea NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug  1 13:34:48 svea NetworkManager: <info>  wlan0: link timed out.

And dmesg:

wlan0: associate with 00:22:b0:b3:e6:96 (try 1)
wlan0: associate with 00:22:b0:b3:e6:96 (try 2)
wlan0: associate with 00:22:b0:b3:e6:96 (try 3)
wlan0: association with 00:22:b0:b3:e6:96 timed out
ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20100121/evregion-474)
ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.TZ01._TMP] (Node ffff880117c4c960), AE_TIME
Please help

Any ideas how to fix the problem? I think the most strange and most important issue (which may also cause a strange behavior of networknamager) is to make manual connection working.
I've tried to ask uncle Google for help and have read through many forums but didn't find any solution of this very problem.

PS My Arch installation is quite fresh as I've bought this new laptop about a month ago. All my packages are up-to-date (I use stable repos).
PS2 Shouldn't be this topic under Networking, Server, and Protection?

Last edited by deluminathor (2010-08-01 16:56:28)


Order dissolves into chaos and then collapses into a higher form of order. This holds true for galaxies, ecosystems, empires and civilizations. The Universe, society, culture manifests in eternal change, and so should music and art.

Offline

#9 2010-08-01 17:25:31

cesura
Package Maintainer (PM)
From: Tallinn, Estonia
Registered: 2010-01-23
Posts: 1,867

Re: No wireless connection

Did you set your WPA key before trying to connect?
http://wiki.archlinux.org/index.php/WPA … icant.conf

Offline

#10 2010-08-01 17:51:58

deluminathor
Member
From: Poland
Registered: 2008-09-14
Posts: 16

Re: No wireless connection

Yes, actually I copied wpa_supplicant.conf from my old laptop (I filtered out comment lines and other network profiles but mine):

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
network={
        ssid="Drums"
        psk=<some hash generared with wpa_passphrase>
}

Last edited by deluminathor (2010-08-01 17:54:15)


Order dissolves into chaos and then collapses into a higher form of order. This holds true for galaxies, ecosystems, empires and civilizations. The Universe, society, culture manifests in eternal change, and so should music and art.

Offline

#11 2010-08-03 17:46:20

deluminathor
Member
From: Poland
Registered: 2008-09-14
Posts: 16

Re: No wireless connection

Hm, it seems that I've solved the problem and it wasn't actually caused by my laptop but by my router. I upgraded its firmware (I was planning it for some time...) and WiFi on my laptop started to work - both manual connecting as well as networkmanager. I think I messed the router a bit while reconfiguring and it gone mad. Now it works properly.


Order dissolves into chaos and then collapses into a higher form of order. This holds true for galaxies, ecosystems, empires and civilizations. The Universe, society, culture manifests in eternal change, and so should music and art.

Offline

Board footer

Powered by FluxBB