Problems associating with RTL8188CE

Problems associating with RTL8188CE

[Seth Forshee]

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

I'm seeing a lot of problems associating with APs when using a Toshiba
NB505 with RTL8188CE wireless. The situation seems to have improved
quite a bit when I moved from 3.0 to 3.2-rc2, but I still see a good
number of failed associations. This card doesn't seem to like my Linksys
E2000 router in particular; I rarely see a successful association with
this router.

I'm attaching logs from the kernel and wpa_supplicant from some failed
associations with the E2000 along with the wpa_supplicant configuration
I used. I loaded rtl8192ce with debug=3, but if more verbosity or any
other information is needed, please let me know.

Thanks,
Seth

[-- Attachment #2: wpa-supplicant.log --]
[-- Type: text/plain, Size: 28672 bytes --]

Initializing interface 'wlan0' conf 'wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'wpa_supplicant.conf' -> '/home/sforshee/wpa_supplicant.conf'
Reading configuration file '/home/sforshee/wpa_supplicant.conf'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=6):
     4b 61 69 6c 69 61                                 Kailia          
scan_ssid=1 (0x1)
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=22): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='Kailia'
WEXT: cfg80211-based driver detected
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 7c:4f:b5:c7:a5:53
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_key: alg=0 key_idx=4 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): bb 15 a1 23 32 80 50 ef 91 fb cc 63 e2 40 66 22
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
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=16
State: DISCONNECTED -> SCANNING
Scan SSID - hexdump_ascii(len=6):
     4b 61 69 6c 69 61                                 Kailia          
Starting AP scan for specific SSID(s)
Scan requested (ret=0) - scan timeout 5 seconds
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Received 3662 bytes of scan results (8 BSSes)
BSS: Start scan result update 1
BSS: Add new id 0 BSSID c0:c1:c0:01:e8:1c SSID 'Kailia'
BSS: Add new id 1 BSSID 00:25:3c:2d:1b:09 SSID '2WIRE639'
BSS: Add new id 2 BSSID 02:24:8c:65:b8:09 SSID 'Piria'
BSS: Add new id 3 BSSID 00:24:56:a0:d1:e9 SSID '2WIRE576'
BSS: Add new id 4 BSSID 00:24:8c:65:b8:08 SSID 'Nisyros'
BSS: Add new id 5 BSSID 00:1d:5a:7c:63:51 SSID '2WIRE788'
BSS: Add new id 6 BSSID 90:84:0d:de:96:01 SSID 'R-network'
BSS: Add new id 7 BSSID 00:14:d1:ca:8e:58 SSID ''
New scan results available
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: c0:c1:c0:01:e8:1c ssid='Kailia' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   selected based on RSN IE
   selected WPA AP c0:c1:c0:01:e8:1c ssid='Kailia'
Trying to associate with c0:c1:c0:01:e8:1c (SSID='Kailia' freq=2412 MHz)
FT: Stored MDIE and FTIE from (Re)Association Response - hexdump(len=0):
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 0c 00
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
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
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b1a len=16
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=22
Authentication with c0:c1:c0:01:e8:1c timed out.
Added BSSID c0:c1:c0:01:e8:1c into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Scan results did not fit - trying larger buffer (8192 bytes)
Received 6429 bytes of scan results (14 BSSes)
BSS: Start scan result update 2
BSS: Add new id 8 BSSID 98:fc:11:74:62:f2 SSID 'CSJHC'
BSS: Add new id 9 BSSID 00:1f:33:df:ce:2a SSID 'BandP'
BSS: Add new id 10 BSSID 00:02:6f:6b:ce:e6 SSID '09b239332'
BSS: Add new id 11 BSSID 00:1d:5a:70:8d:59 SSID '2WIRE868'
BSS: Add new id 12 BSSID 98:2c:be:20:f1:89 SSID '2WIRE065'
BSS: Add new id 13 BSSID 96:84:0d:de:96:01 SSID 'R-guest'
New scan results available
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:25:3c:2d:1b:09 ssid='2WIRE639' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
1: 00:24:8c:65:b8:08 ssid='Nisyros' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
2: 02:24:8c:65:b8:09 ssid='Piria' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
3: 00:24:56:a0:d1:e9 ssid='2WIRE576' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
4: 98:fc:11:74:62:f2 ssid='CSJHC' wpa_ie_len=28 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
5: 90:84:0d:de:96:01 ssid='R-network' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
6: 00:1f:33:df:ce:2a ssid='BandP' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
7: 00:02:6f:6b:ce:e6 ssid='09b239332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
8: c0:c1:c0:01:e8:1c ssid='Kailia' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   selected based on RSN IE
   selected WPA AP c0:c1:c0:01:e8:1c ssid='Kailia'
Trying to associate with c0:c1:c0:01:e8:1c (SSID='Kailia' freq=2412 MHz)
FT: Stored MDIE and FTIE from (Re)Association Response - hexdump(len=0):
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 0c 00
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
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
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b1a len=16
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=22
Authentication with c0:c1:c0:01:e8:1c timed out.
BSSID c0:c1:c0:01:e8:1c blacklist count incremented to 2
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Scan SSID - hexdump_ascii(len=6):
     4b 61 69 6c 69 61                                 Kailia          
Starting AP scan for specific SSID(s)
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Scan results did not fit - trying larger buffer (8192 bytes)
Received 5757 bytes of scan results (13 BSSes)
BSS: Start scan result update 3
BSS: Add new id 14 BSSID 00:1d:5a:e2:55:d9 SSID '2WIRE172'
BSS: Add new id 15 BSSID 00:21:7c:7a:27:91 SSID '2WIRE933'
New scan results available
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS: attr type=0x1041 len=1
WPS: attr type=0x103b len=1
WPS: attr type=0x1047 len=16
WPS: attr type=0x1021 len=12
WPS: attr type=0x1023 len=13
WPS: attr type=0x1024 len=7
WPS: attr type=0x1042 len=2
WPS: attr type=0x1054 len=8
WPS: attr type=0x1011 len=13
WPS: attr type=0x1008 len=2
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS: attr type=0x1041 len=1
WPS: attr type=0x103b len=1
WPS: attr type=0x1047 len=16
WPS: attr type=0x1021 len=12
WPS: attr type=0x1023 len=13
WPS: attr type=0x1024 len=7
WPS: attr type=0x1042 len=2
WPS: attr type=0x1054 len=8
WPS: attr type=0x1011 len=13
WPS: attr type=0x1008 len=2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 98:fc:11:74:62:f2 ssid='CSJHC' wpa_ie_len=28 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
1: 00:1f:33:df:ce:2a ssid='BandP' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
2: 00:02:6f:6b:ce:e6 ssid='09b239332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
3: 02:24:8c:65:b8:09 ssid='Piria' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
4: 00:24:56:a0:d1:e9 ssid='2WIRE576' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
5: 00:24:8c:65:b8:08 ssid='Nisyros' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
6: 00:1d:5a:70:8d:59 ssid='2WIRE868' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
7: 00:1d:5a:e2:55:d9 ssid='2WIRE172' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
8: 00:21:7c:7a:27:91 ssid='2WIRE933' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
9: 90:84:0d:de:96:01 ssid='R-network' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
10: 98:2c:be:20:f1:89 ssid='2WIRE065' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
11: 96:84:0d:de:96:01 ssid='R-guest' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
12: 00:14:d1:ca:8e:58 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID not known
Try to find non-WPA AP
0: 98:fc:11:74:62:f2 ssid='CSJHC' wpa_ie_len=28 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
1: 00:1f:33:df:ce:2a ssid='BandP' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
2: 00:02:6f:6b:ce:e6 ssid='09b239332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
3: 02:24:8c:65:b8:09 ssid='Piria' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
4: 00:24:56:a0:d1:e9 ssid='2WIRE576' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
5: 00:24:8c:65:b8:08 ssid='Nisyros' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
6: 00:1d:5a:70:8d:59 ssid='2WIRE868' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
7: 00:1d:5a:e2:55:d9 ssid='2WIRE172' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
8: 00:21:7c:7a:27:91 ssid='2WIRE933' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
9: 90:84:0d:de:96:01 ssid='R-network' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
10: 98:2c:be:20:f1:89 ssid='2WIRE065' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
11: 96:84:0d:de:96:01 ssid='R-guest' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID mismatch
12: 00:14:d1:ca:8e:58 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID not known
No APs found - clear blacklist and try again
Removed BSSID c0:c1:c0:01:e8:1c from blacklist (clear)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 98:fc:11:74:62:f2 ssid='CSJHC' wpa_ie_len=28 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
1: 00:1f:33:df:ce:2a ssid='BandP' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
2: 00:02:6f:6b:ce:e6 ssid='09b239332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
3: 02:24:8c:65:b8:09 ssid='Piria' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
4: 00:24:56:a0:d1:e9 ssid='2WIRE576' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
5: 00:24:8c:65:b8:08 ssid='Nisyros' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
6: 00:1d:5a:70:8d:59 ssid='2WIRE868' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
7: 00:1d:5a:e2:55:d9 ssid='2WIRE172' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
8: 00:21:7c:7a:27:91 ssid='2WIRE933' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
9: 90:84:0d:de:96:01 ssid='R-network' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
10: 98:2c:be:20:f1:89 ssid='2WIRE065' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
11: 96:84:0d:de:96:01 ssid='R-guest' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
12: 00:14:d1:ca:8e:58 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID not known
Try to find non-WPA AP
0: 98:fc:11:74:62:f2 ssid='CSJHC' wpa_ie_len=28 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
1: 00:1f:33:df:ce:2a ssid='BandP' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
2: 00:02:6f:6b:ce:e6 ssid='09b239332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
3: 02:24:8c:65:b8:09 ssid='Piria' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
4: 00:24:56:a0:d1:e9 ssid='2WIRE576' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
5: 00:24:8c:65:b8:08 ssid='Nisyros' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
6: 00:1d:5a:70:8d:59 ssid='2WIRE868' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
7: 00:1d:5a:e2:55:d9 ssid='2WIRE172' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
8: 00:21:7c:7a:27:91 ssid='2WIRE933' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
9: 90:84:0d:de:96:01 ssid='R-network' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
10: 98:2c:be:20:f1:89 ssid='2WIRE065' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
11: 96:84:0d:de:96:01 ssid='R-guest' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID mismatch
12: 00:14:d1:ca:8e:58 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID not known
No suitable network found
Setting scan request: 5 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Scan results did not fit - trying larger buffer (8192 bytes)
Received 5323 bytes of scan results (12 BSSes)
BSS: Start scan result update 4
BSS: Expire BSS 1 due to no match in scan
BSS: Remove id 1 BSSID 00:25:3c:2d:1b:09 SSID '2WIRE639'
BSS: Expire BSS 5 due to no match in scan
BSS: Remove id 5 BSSID 00:1d:5a:7c:63:51 SSID '2WIRE788'
New scan results available
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 02:24:8c:65:b8:09 ssid='Piria' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
1: 00:24:8c:65:b8:08 ssid='Nisyros' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
2: 00:1d:5a:e2:55:d9 ssid='2WIRE172' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
3: 00:24:56:a0:d1:e9 ssid='2WIRE576' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
4: 90:84:0d:de:96:01 ssid='R-network' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
5: 00:1d:5a:70:8d:59 ssid='2WIRE868' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
6: 00:02:6f:6b:ce:e6 ssid='09b239332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
7: 00:21:7c:7a:27:91 ssid='2WIRE933' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
8: c0:c1:c0:01:e8:1c ssid='Kailia' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   selected based on RSN IE
   selected WPA AP c0:c1:c0:01:e8:1c ssid='Kailia'
Trying to associate with c0:c1:c0:01:e8:1c (SSID='Kailia' freq=2412 MHz)
FT: Stored MDIE and FTIE from (Re)Association Response - hexdump(len=0):
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 0c 00
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
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
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b1a len=16
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=22
Authentication with c0:c1:c0:01:e8:1c timed out.
Added BSSID c0:c1:c0:01:e8:1c into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Scan SSID - hexdump_ascii(len=6):
     4b 61 69 6c 69 61                                 Kailia          
Starting AP scan for specific SSID(s)
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Scan results did not fit - trying larger buffer (8192 bytes)
Received 5185 bytes of scan results (12 BSSes)
BSS: Start scan result update 5
BSS: Add new id 16 BSSID 00:25:3c:2d:1b:09 SSID '2WIRE639'
BSS: Expire BSS 8 due to no match in scan
BSS: Remove id 8 BSSID 98:fc:11:74:62:f2 SSID 'CSJHC'
BSS: Expire BSS 9 due to no match in scan
BSS: Remove id 9 BSSID 00:1f:33:df:ce:2a SSID 'BandP'
New scan results available
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 02:24:8c:65:b8:09 ssid='Piria' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
1: 00:24:8c:65:b8:08 ssid='Nisyros' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
2: 90:84:0d:de:96:01 ssid='R-network' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
3: 00:1d:5a:70:8d:59 ssid='2WIRE868' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
4: 00:02:6f:6b:ce:e6 ssid='09b239332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
5: 00:1d:5a:e2:55:d9 ssid='2WIRE172' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
6: 00:21:7c:7a:27:91 ssid='2WIRE933' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
7: c0:c1:c0:01:e8:1c ssid='Kailia' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   selected based on RSN IE
   selected WPA AP c0:c1:c0:01:e8:1c ssid='Kailia'
Trying to associate with c0:c1:c0:01:e8:1c (SSID='Kailia' freq=2412 MHz)
FT: Stored MDIE and FTIE from (Re)Association Response - hexdump(len=0):
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 0c 00
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
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
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b1a len=16
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=22
Authentication with c0:c1:c0:01:e8:1c timed out.
BSSID c0:c1:c0:01:e8:1c blacklist count incremented to 2
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=16
Scan results did not fit - trying larger buffer (8192 bytes)
Received 6028 bytes of scan results (14 BSSes)
BSS: Start scan result update 6
BSS: Add new id 17 BSSID 00:1d:5a:7c:63:51 SSID '2WIRE788'
New scan results available
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 02:24:8c:65:b8:09 ssid='Piria' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
1: 00:24:8c:65:b8:08 ssid='Nisyros' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
2: 90:84:0d:de:96:01 ssid='R-network' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
3: 00:1d:5a:70:8d:59 ssid='2WIRE868' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
4: 00:02:6f:6b:ce:e6 ssid='09b239332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
5: 00:1d:5a:e2:55:d9 ssid='2WIRE172' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
6: 00:21:7c:7a:27:91 ssid='2WIRE933' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
7: 00:25:3c:2d:1b:09 ssid='2WIRE639' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
8: c0:c1:c0:01:e8:1c ssid='Kailia' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - blacklisted
9: 00:24:56:a0:d1:e9 ssid='2WIRE576' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
10: 00:1d:5a:7c:63:51 ssid='2WIRE788' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
11: 98:2c:be:20:f1:89 ssid='2WIRE065' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
12: 00:14:d1:ca:8e:58 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID not known
13: 96:84:0d:de:96:01 ssid='R-guest' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 02:24:8c:65:b8:09 ssid='Piria' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
1: 00:24:8c:65:b8:08 ssid='Nisyros' wpa_ie_len=0 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
2: 90:84:0d:de:96:01 ssid='R-network' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
3: 00:1d:5a:70:8d:59 ssid='2WIRE868' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
4: 00:02:6f:6b:ce:e6 ssid='09b239332' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
5: 00:1d:5a:e2:55:d9 ssid='2WIRE172' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
6: 00:21:7c:7a:27:91 ssid='2WIRE933' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
7: 00:25:3c:2d:1b:09 ssid='2WIRE639' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
8: c0:c1:c0:01:e8:1c ssid='Kailia' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - blacklisted
9: 00:24:56:a0:d1:e9 ssid='2WIRE576' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
   skip - SSID mismatch
10: 00:1d:5a:7c:63:51 ssid='2WIRE788' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
11: 98:2c:be:20:f1:89 ssid='2WIRE065' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
12: 00:14:d1:ca:8e:58 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID not known
13: 96:84:0d:de:96:01 ssid='R-guest' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID mismatch
No APs found - clear blacklist and try again
Removed BSSID c0:c1:c0:01:e8:1c from blacklist (clear)
Selecting BSS from priority group 0
Try to find WPA-enabled AP

[-- Attachment #3: dmesg.log --]
[-- Type: text/plain, Size: 16047 bytes --]

Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.904322] cfg80211: Calling CRDA to update world regulatory domain
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.932587] cfg80211: World regulatory domain updated:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.936510] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.940574] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.944608] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.948602] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.952533] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.956189] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.969504] rtl8192ce 0000:07:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.972820] rtl8192ce 0000:07:00.0: setting latency timer to 64
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.989838] rtlwifi:_rtl_init_hw_ht_capab():<0-0> 1T1R
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.993372] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5360.996464] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.000213] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.003857] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.007517] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.011409] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.016258] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.021505] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.026713] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.032082] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.037470] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.042979] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.048530] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.054266] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.059972] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.065798] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.071714] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.077903] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.084091] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.091445] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.098092] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.104631] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.111276] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.118075] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.124764] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.131602] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.138441] cfg80211: Disabling freq 2484 MHz as custom regd has no rule that fits a 20 MHz wide channel
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.145891] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.150945] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.157645] rtlwifi: wireless switch is on
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.165004] cfg80211: Calling CRDA for country: EC
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.194684] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.199637] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204386] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204398] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204406] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204415] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204422] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204430] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204437] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204445] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204452] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204460] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204467] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204475] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204482] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204491] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204497] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204506] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204512] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204521] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204528] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204536] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204543] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204551] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204558] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204566] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204572] cfg80211: Disabling freq 2484 MHz
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204583] cfg80211: Regulatory domain changed to country: EC
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204588] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204596] cfg80211:     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204603] cfg80211:     (5170000 KHz - 5250000 KHz @ 20000 KHz), (300 mBi, 1700 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204611] cfg80211:     (5250000 KHz - 5330000 KHz @ 20000 KHz), (300 mBi, 2300 mBm)
Nov 18 16:23:38 ubuntu-NB505 kernel: [ 5361.204619] cfg80211:     (5735000 KHz - 5835000 KHz @ 20000 KHz), (300 mBi, 3000 mBm)
Nov 18 16:23:43 ubuntu-NB505 kernel: [ 5365.985224] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin
Nov 18 16:23:43 ubuntu-NB505 kernel: [ 5365.989357] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(49), Signature(0x88c1),Size(32)
Nov 18 16:23:43 ubuntu-NB505 kernel: [ 5366.320052] rtlwifi:rtl_pci_start():<0-0> OK
Nov 18 16:23:43 ubuntu-NB505 kernel: [ 5366.335029] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 18 16:23:43 ubuntu-NB505 kernel: [ 5366.424070] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic disable
Nov 18 16:23:43 ubuntu-NB505 kernel: [ 5366.481833] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic enable
Nov 18 16:23:43 ubuntu-NB505 kernel: [ 5366.490556] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin
Nov 18 16:23:43 ubuntu-NB505 kernel: [ 5366.496684] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(49), Signature(0x88c1),Size(32)
Nov 18 16:23:45 ubuntu-NB505 kernel: [ 5367.690674] wlan0: direct probe to c0:c1:c0:01:e8:1c (try 1/3)
Nov 18 16:23:45 ubuntu-NB505 kernel: [ 5367.706420] wlan0: direct probe responded
Nov 18 16:23:45 ubuntu-NB505 kernel: [ 5367.724064] wlan0: authenticate with c0:c1:c0:01:e8:1c (try 1)
Nov 18 16:23:45 ubuntu-NB505 kernel: [ 5367.724093] rtlwifi:rtl_pci_tx():<200-1> MAC80211_LINKING
Nov 18 16:23:45 ubuntu-NB505 kernel: [ 5367.788092] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic disable
Nov 18 16:23:45 ubuntu-NB505 kernel: [ 5367.924090] wlan0: authenticate with c0:c1:c0:01:e8:1c (try 2)
Nov 18 16:23:45 ubuntu-NB505 kernel: [ 5368.124091] wlan0: authenticate with c0:c1:c0:01:e8:1c (try 3)
Nov 18 16:23:45 ubuntu-NB505 kernel: [ 5368.324086] wlan0: authentication with c0:c1:c0:01:e8:1c timed out
Nov 18 16:23:55 ubuntu-NB505 kernel: [ 5377.692058] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic enable
Nov 18 16:23:55 ubuntu-NB505 kernel: [ 5377.698428] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin
Nov 18 16:23:55 ubuntu-NB505 kernel: [ 5377.702379] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(49), Signature(0x88c1),Size(32)
Nov 18 16:23:56 ubuntu-NB505 kernel: [ 5378.894976] wlan0: authenticate with c0:c1:c0:01:e8:1c (try 1)
Nov 18 16:23:56 ubuntu-NB505 kernel: [ 5378.895011] rtlwifi:rtl_pci_tx():<200-1> MAC80211_LINKING
Nov 18 16:23:56 ubuntu-NB505 kernel: [ 5378.992092] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic disable
Nov 18 16:23:56 ubuntu-NB505 kernel: [ 5379.092069] wlan0: authenticate with c0:c1:c0:01:e8:1c (try 2)
Nov 18 16:23:56 ubuntu-NB505 kernel: [ 5379.292089] wlan0: authenticate with c0:c1:c0:01:e8:1c (try 3)
Nov 18 16:23:56 ubuntu-NB505 kernel: [ 5379.496078] wlan0: authentication with c0:c1:c0:01:e8:1c timed out
Nov 18 16:24:06 ubuntu-NB505 kernel: [ 5388.897510] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic enable
Nov 18 16:24:06 ubuntu-NB505 kernel: [ 5388.905087] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin
Nov 18 16:24:06 ubuntu-NB505 kernel: [ 5388.910213] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(49), Signature(0x88c1),Size(32)
Nov 18 16:24:07 ubuntu-NB505 kernel: [ 5390.200085] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic disable
Nov 18 16:24:12 ubuntu-NB505 kernel: [ 5395.108685] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic enable
Nov 18 16:24:12 ubuntu-NB505 kernel: [ 5395.117237] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin
Nov 18 16:24:12 ubuntu-NB505 kernel: [ 5395.124784] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(49), Signature(0x88c1),Size(32)
Nov 18 16:24:13 ubuntu-NB505 kernel: [ 5396.318437] wlan0: authenticate with c0:c1:c0:01:e8:1c (try 1)
Nov 18 16:24:13 ubuntu-NB505 kernel: [ 5396.322251] rtlwifi:rtl_pci_tx():<200-1> MAC80211_LINKING
Nov 18 16:24:13 ubuntu-NB505 kernel: [ 5396.416083] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic disable
Nov 18 16:24:14 ubuntu-NB505 kernel: [ 5396.524076] wlan0: authenticate with c0:c1:c0:01:e8:1c (try 2)
Nov 18 16:24:14 ubuntu-NB505 kernel: [ 5396.724078] wlan0: authenticate with c0:c1:c0:01:e8:1c (try 3)
Nov 18 16:24:14 ubuntu-NB505 kernel: [ 5396.928077] wlan0: authentication with c0:c1:c0:01:e8:1c timed out
Nov 18 16:24:23 ubuntu-NB505 kernel: [ 5406.328680] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic enable
Nov 18 16:24:23 ubuntu-NB505 kernel: [ 5406.331206] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin
Nov 18 16:24:23 ubuntu-NB505 kernel: [ 5406.331219] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(49), Signature(0x88c1),Size(32)
Nov 18 16:24:25 ubuntu-NB505 kernel: [ 5407.519229] wlan0: direct probe to c0:c1:c0:01:e8:1c (try 1/3)
Nov 18 16:24:25 ubuntu-NB505 kernel: [ 5407.616070] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic disable
Nov 18 16:24:25 ubuntu-NB505 kernel: [ 5407.720073] wlan0: direct probe to c0:c1:c0:01:e8:1c (try 2/3)
Nov 18 16:24:25 ubuntu-NB505 kernel: [ 5407.924075] wlan0: direct probe to c0:c1:c0:01:e8:1c (try 3/3)
Nov 18 16:24:25 ubuntu-NB505 kernel: [ 5408.124099] wlan0: direct probe to c0:c1:c0:01:e8:1c timed out
Nov 18 16:24:35 ubuntu-NB505 kernel: [ 5417.520334] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic enable
Nov 18 16:24:35 ubuntu-NB505 kernel: [ 5417.522861] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin
Nov 18 16:24:35 ubuntu-NB505 kernel: [ 5417.522875] rtl8192c_common:rtl92c_download_fw():<0-0> Firmware Version(49), Signature(0x88c1),Size(32)
Nov 18 16:24:36 ubuntu-NB505 kernel: [ 5418.710601] wlan0: direct probe to c0:c1:c0:01:e8:1c (try 1/3)
Nov 18 16:24:36 ubuntu-NB505 kernel: [ 5418.808042] rtl8192ce:_rtl92ce_phy_set_rf_power_state():<0-0> IPS Set eRf nic disable
Nov 18 16:24:36 ubuntu-NB505 kernel: [ 5418.908061] wlan0: direct probe to c0:c1:c0:01:e8:1c (try 2/3)
Nov 18 16:24:36 ubuntu-NB505 kernel: [ 5419.108090] wlan0: direct probe to c0:c1:c0:01:e8:1c (try 3/3)
Nov 18 16:24:36 ubuntu-NB505 kernel: [ 5419.312085] wlan0: direct probe to c0:c1:c0:01:e8:1c timed out

[-- Attachment #4: wpa_supplicant.conf --]
[-- Type: text/plain, Size: 73 bytes --]

network={
	ssid="Kailia"
	scan_ssid=1
	key_mgmt=WPA-PSK
	psk=[omitted]
}

Re: Problems associating with RTL8188CE

[Larry Finger]

On 11/18/2011 04:54 PM, Seth Forshee wrote:
> I'm seeing a lot of problems associating with APs when using a Toshiba
> NB505 with RTL8188CE wireless. The situation seems to have improved
> quite a bit when I moved from 3.0 to 3.2-rc2, but I still see a good
> number of failed associations. This card doesn't seem to like my Linksys
> E2000 router in particular; I rarely see a successful association with
> this router.
>
> I'm attaching logs from the kernel and wpa_supplicant from some failed
> associations with the E2000 along with the wpa_supplicant configuration
> I used. I loaded rtl8192ce with debug=3, but if more verbosity or any
> other information is needed, please let me know.

Would it be possible for you to have a separate computer log the transaction 
between the AP with ESSID 'Kailia' and the RTL8188CE using wireshark or Kismet? 
Chaoming may see something in the logs that I do not, but the request for 
authentication is timing out. With wireshark, we can see what is actually on the 
air.

Larry

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Sat, Nov 19, 2011 at 11:25:44PM -0600, Larry Finger wrote:
> On 11/18/2011 04:54 PM, Seth Forshee wrote:
> >I'm seeing a lot of problems associating with APs when using a Toshiba
> >NB505 with RTL8188CE wireless. The situation seems to have improved
> >quite a bit when I moved from 3.0 to 3.2-rc2, but I still see a good
> >number of failed associations. This card doesn't seem to like my Linksys
> >E2000 router in particular; I rarely see a successful association with
> >this router.
> >
> >I'm attaching logs from the kernel and wpa_supplicant from some failed
> >associations with the E2000 along with the wpa_supplicant configuration
> >I used. I loaded rtl8192ce with debug=3, but if more verbosity or any
> >other information is needed, please let me know.
> 
> Would it be possible for you to have a separate computer log the
> transaction between the AP with ESSID 'Kailia' and the RTL8188CE
> using wireshark or Kismet? Chaoming may see something in the logs
> that I do not, but the request for authentication is timing out.
> With wireshark, we can see what is actually on the air.

I've uploaded the capture along with the logs to
http://people.canonical.com/~sforshee/rtl8188ce/.

Thanks,
Seth

Re: Problems associating with RTL8188CE

[Larry Finger]

On 11/21/2011 12:13 PM, Seth Forshee wrote:
>
> I've uploaded the capture along with the logs to
> http://people.canonical.com/~sforshee/rtl8188ce/.

Unfortunately, I do not have permission to access the pcap file. The other two 
are OK, but not the one of interest.

Larry

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Mon, Nov 21, 2011 at 12:34:52PM -0600, Larry Finger wrote:
> On 11/21/2011 12:13 PM, Seth Forshee wrote:
> >
> >I've uploaded the capture along with the logs to
> >http://people.canonical.com/~sforshee/rtl8188ce/.
> 
> Unfortunately, I do not have permission to access the pcap file. The
> other two are OK, but not the one of interest.

Sorry about that, didn't notice the lack of permissions. Fixed now.

Re: Problems associating with RTL8188CE

[Larry Finger]

On 11/21/2011 12:56 PM, Seth Forshee wrote:
> On Mon, Nov 21, 2011 at 12:34:52PM -0600, Larry Finger wrote:
>> On 11/21/2011 12:13 PM, Seth Forshee wrote:
>>>
>>> I've uploaded the capture along with the logs to
>>> http://people.canonical.com/~sforshee/rtl8188ce/.
>>
>> Unfortunately, I do not have permission to access the pcap file. The
>> other two are OK, but not the one of interest.
>
> Sorry about that, didn't notice the lack of permissions. Fixed now.

I got it now. I would like one other piece of information - what is the MAC 
address of your RTL8188CE device? It is not found in any of the dmesg logs that 
I have.

Larry

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Mon, Nov 21, 2011 at 08:01:50PM -0600, Larry Finger wrote:
> On 11/21/2011 12:56 PM, Seth Forshee wrote:
> >On Mon, Nov 21, 2011 at 12:34:52PM -0600, Larry Finger wrote:
> >>On 11/21/2011 12:13 PM, Seth Forshee wrote:
> >>>
> >>>I've uploaded the capture along with the logs to
> >>>http://people.canonical.com/~sforshee/rtl8188ce/.
> >>
> >>Unfortunately, I do not have permission to access the pcap file. The
> >>other two are OK, but not the one of interest.
> >
> >Sorry about that, didn't notice the lack of permissions. Fixed now.
> 
> I got it now. I would like one other piece of information - what is
> the MAC address of your RTL8188CE device? It is not found in any of
> the dmesg logs that I have.

7c:4f:b5:c7:a5:53

Thanks for taking a look.

Seth

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Mon, Nov 21, 2011 at 08:20:08PM -0600, Seth Forshee wrote:
> On Mon, Nov 21, 2011 at 08:01:50PM -0600, Larry Finger wrote:
> > On 11/21/2011 12:56 PM, Seth Forshee wrote:
> > >On Mon, Nov 21, 2011 at 12:34:52PM -0600, Larry Finger wrote:
> > >>On 11/21/2011 12:13 PM, Seth Forshee wrote:
> > >>>
> > >>>I've uploaded the capture along with the logs to
> > >>>http://people.canonical.com/~sforshee/rtl8188ce/.
> > >>
> > >>Unfortunately, I do not have permission to access the pcap file. The
> > >>other two are OK, but not the one of interest.
> > >
> > >Sorry about that, didn't notice the lack of permissions. Fixed now.
> > 
> > I got it now. I would like one other piece of information - what is
> > the MAC address of your RTL8188CE device? It is not found in any of
> > the dmesg logs that I have.
> 
> 7c:4f:b5:c7:a5:53
> 
> Thanks for taking a look.

Hi Larry,

Just wondering if you've gotten a chance to take a look at the trace
yet.

Thanks,
Seth

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Mon, Nov 21, 2011 at 08:20:08PM -0600, Seth Forshee wrote:
> On Mon, Nov 21, 2011 at 08:01:50PM -0600, Larry Finger wrote:
> > On 11/21/2011 12:56 PM, Seth Forshee wrote:
> > >On Mon, Nov 21, 2011 at 12:34:52PM -0600, Larry Finger wrote:
> > >>On 11/21/2011 12:13 PM, Seth Forshee wrote:
> > >>>
> > >>>I've uploaded the capture along with the logs to
> > >>>http://people.canonical.com/~sforshee/rtl8188ce/.
> > >>
> > >>Unfortunately, I do not have permission to access the pcap file. The
> > >>other two are OK, but not the one of interest.
> > >
> > >Sorry about that, didn't notice the lack of permissions. Fixed now.
> > 
> > I got it now. I would like one other piece of information - what is
> > the MAC address of your RTL8188CE device? It is not found in any of
> > the dmesg logs that I have.
> 
> 7c:4f:b5:c7:a5:53

Larry,

I've been trying to look into this myself over the last couple of days,
but I'm still trying to learn all of this 802.11 stuff. I've kind of hit
the limit of what knowledge I've acquired so far, so I'd appreciate it
if you could look at my findings and offer suggestions.

What I'm doing is running wpa_supplicant manually to try and initiate a
connection while monitoring the traffic with wireshark on a separate
machine.  What I'm seeing is that when the rtl8192ce device sends a
probe request or authentication request, the majority of the time the AP
sends a response but the adapter fails to ack the response (I don't see
the ack in the wireshark capture, and the AP resends the probe response
several times). The logs show timeouts that correspond to the types of
responses that aren't being acked. It's as if the adapter doesn't see
the responses at all.

I have another AP that the rtl8192ce doesn't have any problems
associating with, so I also captured a trace with wireshark when
associating to that AP. I didn't see much that differed except that the
probe response frame with the problematic AP is about 350 bytes longer
(due to additional information elements).

Something else that I noticed is that with the problematic AP, inactive
power save seems to kick in shortly afer sending the
probe/authentication requests. I wondered if this might be behind the
issues, but loading the module with ips=0 makes no difference.

Any suggestions on what might be going wrong or next steps for
debugging?

Thanks,
Seth

Re: Problems associating with RTL8188CE

[Larry Finger]

On 12/13/2011 01:42 PM, Seth Forshee wrote:
> I have another AP that the rtl8192ce doesn't have any problems
> associating with, so I also captured a trace with wireshark when
> associating to that AP. I didn't see much that differed except that the
> probe response frame with the problematic AP is about 350 bytes longer
> (due to additional information elements).

The extra IE entries must be the clue.

> Something else that I noticed is that with the problematic AP, inactive
> power save seems to kick in shortly afer sending the
> probe/authentication requests. I wondered if this might be behind the
> issues, but loading the module with ips=0 makes no difference.
>
> Any suggestions on what might be going wrong or next steps for
> debugging?

With ips=0, all power save should be eliminated. Please take the two capture 
files, and filter all but the probe and probe response frames. I'll try to find 
some time to analyze them.

Larry

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Tue, Dec 13, 2011 at 02:41:02PM -0600, Larry Finger wrote:
> On 12/13/2011 01:42 PM, Seth Forshee wrote:
> >I have another AP that the rtl8192ce doesn't have any problems
> >associating with, so I also captured a trace with wireshark when
> >associating to that AP. I didn't see much that differed except that the
> >probe response frame with the problematic AP is about 350 bytes longer
> >(due to additional information elements).
> 
> The extra IE entries must be the clue.
> 
> >Something else that I noticed is that with the problematic AP, inactive
> >power save seems to kick in shortly afer sending the
> >probe/authentication requests. I wondered if this might be behind the
> >issues, but loading the module with ips=0 makes no difference.
> >
> >Any suggestions on what might be going wrong or next steps for
> >debugging?
> 
> With ips=0, all power save should be eliminated. Please take the two
> capture files, and filter all but the probe and probe response
> frames. I'll try to find some time to analyze them.

The capture files are available at:

http://people.canonical.com/~sforshee/rtl8188ce/

Thanks,
Seth

Re: Problems associating with RTL8188CE

[Larry Finger]

Seth,

On 12/13/2011 03:26 PM, Seth Forshee wrote:
>
> The capture files are available at:
>
> http://people.canonical.com/~sforshee/rtl8188ce/

The major difference is that the "bad" AP implements 802.11n HT40 technology, 
but the "good" one does not.

There was a period when rtl8192ce and rtl8192cu had a bug that prevented them 
from associating with 802.11n APs, but that was fixed a long time ago. I can 
communicate with my Netgear WNDR3300 AP that implements full 802.11 capabilities.

What kernel are you running? If you implement the bleeding-edge compat-wireless 
release, does that help.

Larry

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Tue, Dec 13, 2011 at 10:57:42PM -0600, Larry Finger wrote:
> Seth,
> 
> On 12/13/2011 03:26 PM, Seth Forshee wrote:
> >
> >The capture files are available at:
> >
> >http://people.canonical.com/~sforshee/rtl8188ce/
> 
> The major difference is that the "bad" AP implements 802.11n HT40
> technology, but the "good" one does not.
> 
> There was a period when rtl8192ce and rtl8192cu had a bug that
> prevented them from associating with 802.11n APs, but that was fixed
> a long time ago. I can communicate with my Netgear WNDR3300 AP that
> implements full 802.11 capabilities.
> 
> What kernel are you running? If you implement the bleeding-edge
> compat-wireless release, does that help.

I'm running 3.2-rc5 currently. The results are the same with
bleeding-edge compat-wireless.

Seth

Re: Problems associating with RTL8188CE

[Larry Finger]

On 12/14/2011 10:23 AM, Seth Forshee wrote:
>
> I'm running 3.2-rc5 currently. The results are the same with
> bleeding-edge compat-wireless.

I'm running 3.2-rc5 from wireless-testing, but I should test the one from 
mainline. I'll also retest an RTL8188CE with my 802.11n AP.

What model is that Cisco AP? Perhaps Realsil has one in their lab. I do not have 
access to any Cisco hardware.

Larry

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Wed, Dec 14, 2011 at 10:39:44AM -0600, Larry Finger wrote:
> On 12/14/2011 10:23 AM, Seth Forshee wrote:
> >
> >I'm running 3.2-rc5 currently. The results are the same with
> >bleeding-edge compat-wireless.
> 
> I'm running 3.2-rc5 from wireless-testing, but I should test the one
> from mainline. I'll also retest an RTL8188CE with my 802.11n AP.
> 
> What model is that Cisco AP? Perhaps Realsil has one in their lab. I
> do not have access to any Cisco hardware.

It's a Linksys E2000.

Re: Problems associating with RTL8188CE

[Larry Finger]

On 12/14/2011 10:49 AM, Seth Forshee wrote:
> On Wed, Dec 14, 2011 at 10:39:44AM -0600, Larry Finger wrote:
>> On 12/14/2011 10:23 AM, Seth Forshee wrote:
>>>
>>> I'm running 3.2-rc5 currently. The results are the same with
>>> bleeding-edge compat-wireless.
>>
>> I'm running 3.2-rc5 from wireless-testing, but I should test the one
>> from mainline. I'll also retest an RTL8188CE with my 802.11n AP.
>>
>> What model is that Cisco AP? Perhaps Realsil has one in their lab. I
>> do not have access to any Cisco hardware.
>
> It's a Linksys E2000.

If matters come to worse, I can buy a used E2000 for $30 on E-bay.

Larry

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Wed, Dec 14, 2011 at 10:58:09AM -0600, Larry Finger wrote:
> On 12/14/2011 10:49 AM, Seth Forshee wrote:
> >On Wed, Dec 14, 2011 at 10:39:44AM -0600, Larry Finger wrote:
> >>On 12/14/2011 10:23 AM, Seth Forshee wrote:
> >>>
> >>>I'm running 3.2-rc5 currently. The results are the same with
> >>>bleeding-edge compat-wireless.
> >>
> >>I'm running 3.2-rc5 from wireless-testing, but I should test the one
> >>from mainline. I'll also retest an RTL8188CE with my 802.11n AP.
> >>
> >>What model is that Cisco AP? Perhaps Realsil has one in their lab. I
> >>do not have access to any Cisco hardware.
> >
> >It's a Linksys E2000.
> 
> If matters come to worse, I can buy a used E2000 for $30 on E-bay.

If there's anything you'd like me to try, don't hesitate to ask. I'm
trying to come up to speed on debugging wireless problems anyway, so I'd
value the experience.

Thanks,
Seth

Re: Problems associating with RTL8188CE

[Larry Finger]

On 12/14/2011 11:12 AM, Seth Forshee wrote:
>
> If there's anything you'd like me to try, don't hesitate to ask. I'm
> trying to come up to speed on debugging wireless problems anyway, so I'd
> value the experience.

I have not had a chance to reboot so that I can install the RTL8188CE. In 
addition, I'm building a fresh copy of mainline 3.2-rc5 for a separate test. 
I'll let you know what happens.

Larry

Re: Problems associating with RTL8188CE

[Larry Finger]

Seth,

As expected, my RTL8188SE came right up.

The lspci -nnv details for my card are

06:00.0 0280: 10ec:8176 (rev 01)
         Subsystem: 10ec:8176
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- 
<MAbort- >SERR- <PERR- INTx-
         Latency: 0, Cache Line Size: 64 bytes
         Interrupt: pin A routed to IRQ 21
         Region 0: I/O ports at 4000 [size=256]
         Region 2: Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
         Capabilities: <access denied>
         Kernel driver in use: rtl8192ce

Does yours also have 10ec:8176 as the PCI ID?

Larry

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Wed, Dec 14, 2011 at 11:43:17AM -0600, Larry Finger wrote:
> Seth,
> 
> As expected, my RTL8188SE came right up.
> 
> The lspci -nnv details for my card are
> 
> 06:00.0 0280: 10ec:8176 (rev 01)
>         Subsystem: 10ec:8176
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B- DisINTx-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 0, Cache Line Size: 64 bytes
>         Interrupt: pin A routed to IRQ 21
>         Region 0: I/O ports at 4000 [size=256]
>         Region 2: Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
>         Capabilities: <access denied>
>         Kernel driver in use: rtl8192ce
> 
> Does yours also have 10ec:8176 as the PCI ID?

Yes.

07:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
	Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8184]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 17
	Region 0: I/O ports at 2000 [size=256]
	Region 2: Memory at f0100000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: rtl8192ce
	Kernel modules: rtl8192ce

Re: Problems associating with RTL8188CE

[Tim Gardner]

On 12/14/2011 09:49 AM, Seth Forshee wrote:
> On Wed, Dec 14, 2011 at 10:39:44AM -0600, Larry Finger wrote:
>> On 12/14/2011 10:23 AM, Seth Forshee wrote:
>>>
>>> I'm running 3.2-rc5 currently. The results are the same with
>>> bleeding-edge compat-wireless.
>>
>> I'm running 3.2-rc5 from wireless-testing, but I should test the one
>> from mainline. I'll also retest an RTL8188CE with my 802.11n AP.
>>
>> What model is that Cisco AP? Perhaps Realsil has one in their lab. I
>> do not have access to any Cisco hardware.
>
> It's a Linksys E2000.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

I ordered a refurb Linksys E3000. Should be here Friday. My Lenovo x120e 
has the identical adapter. It seems to work pretty well except that it 
won't show up the WNDR3300 11N SSID in the list. I've tested thusly:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/902557/comments/52

rtg
-- 
Tim Gardner tim.gardner@canonical.com

Re: Problems associating with RTL8188CE

[Larry Finger]

On 12/14/2011 03:52 PM, Tim Gardner wrote:
> On 12/14/2011 09:49 AM, Seth Forshee wrote:
>> On Wed, Dec 14, 2011 at 10:39:44AM -0600, Larry Finger wrote:
>>> On 12/14/2011 10:23 AM, Seth Forshee wrote:
>>>>
>>>> I'm running 3.2-rc5 currently. The results are the same with
>>>> bleeding-edge compat-wireless.
>>>
>>> I'm running 3.2-rc5 from wireless-testing, but I should test the one
>>> from mainline. I'll also retest an RTL8188CE with my 802.11n AP.
>>>
>>> What model is that Cisco AP? Perhaps Realsil has one in their lab. I
>>> do not have access to any Cisco hardware.
>>
>> It's a Linksys E2000.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> I ordered a refurb Linksys E3000. Should be here Friday. My Lenovo x120e has the
> identical adapter. It seems to work pretty well except that it won't show up the
> WNDR3300 11N SSID in the list. I've tested thusly:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/902557/comments/52

Something is funny. My AP is an WNDR3300 and it works perfectly in 802.11n mode 
with kernels from both mainline and wireless-testing.

I think trying a Live CD might be in order. I'm downloading 
http://cdimage.ubuntu.com/daily-live/current/precise-desktop-amd64.iso.

If this is not the correct one, please send the better link.

Larry


Larry

Re: Problems associating with RTL8188CE

[Larry Finger]

Tim,

I did the live test with the Dec. 14 build of 12.04 (64 bit). It connected with 
my WNDR3300 with no difficulty. I tested all 4 modes supported by the AP. All 
worked.

I assume that an installation would work the same as the live version, but that 
is easy for you to test.

Larry

Re: Problems associating with RTL8188CE

[Tim Gardner]

On 12/14/2011 05:50 PM, Larry Finger wrote:
> Tim,
>
> I did the live test with the Dec. 14 build of 12.04 (64 bit). It
> connected with my WNDR3300 with no difficulty. I tested all 4 modes
> supported by the AP. All worked.
>
> I assume that an installation would work the same as the live version,
> but that is easy for you to test.
>
> Larry
>

Here are the 3 modes I was able to successfully test on my WNDR3300 as 
an open AP:

* Up to 270Mbps at 2.4Ghz
   11N Channel:	03/2.422Ghz
   in this mode only the 11N SSID is beaconed.
   iperf: 11.2 Mbps average over 120 seconds, high of 26.2 Mbps, low of 6.71

* Up to 270Mbps at 5Ghz & 54Mbps at 2.4Ghz
   11N Channel: 36 / 5.180Ghz
   11G Channel: auto
   in this mode only the G beacon can be seen (which makes sense)
   iperf: 14.3 Mbps average over 120 seconds, high of 28.5 Mbps, low of 8.97

* Up to 130Mbps at 2.4Ghz
   11N Channel:	03/2.422Ghz
   in this mode only the 11N SSID is beaconed.
   iperf: 16.0 Mbps average over 120 seconds, high of 28.9 Mbps, low of 7.44

This mode would not acquire a beacon using the rtl8192ce:

* Up to 130Mbps at 5Ghz & 54Mbps at 2.4Ghz
   11N Channel: 36 / 5.180Ghz
   11G Channel: auto
   in this mode no beacon can be seen.

I verified using a MacBook Air under OS/X that the N SSID was appearing 
on the 5 Ghz channel, but couldn't see the G beacon. Maybe its a bug in 
the WNDR3300.

rtg
-- 
Tim Gardner tim.gardner@canonical.com

Re: Problems associating with RTL8188CE

[Larry Finger]

On 12/15/2011 12:41 PM, Tim Gardner wrote:
> On 12/14/2011 05:50 PM, Larry Finger wrote:
>> Tim,
>>
>> I did the live test with the Dec. 14 build of 12.04 (64 bit). It
>> connected with my WNDR3300 with no difficulty. I tested all 4 modes
>> supported by the AP. All worked.
>>
>> I assume that an installation would work the same as the live version,
>> but that is easy for you to test.
>>
>> Larry
>>
>
> Here are the 3 modes I was able to successfully test on my WNDR3300 as an open AP:
>
> * Up to 270Mbps at 2.4Ghz
> 11N Channel: 03/2.422Ghz
> in this mode only the 11N SSID is beaconed.
> iperf: 11.2 Mbps average over 120 seconds, high of 26.2 Mbps, low of 6.71
>
> * Up to 270Mbps at 5Ghz & 54Mbps at 2.4Ghz
> 11N Channel: 36 / 5.180Ghz
> 11G Channel: auto
> in this mode only the G beacon can be seen (which makes sense)
> iperf: 14.3 Mbps average over 120 seconds, high of 28.5 Mbps, low of 8.97
>
> * Up to 130Mbps at 2.4Ghz
> 11N Channel: 03/2.422Ghz
> in this mode only the 11N SSID is beaconed.
> iperf: 16.0 Mbps average over 120 seconds, high of 28.9 Mbps, low of 7.44
>
> This mode would not acquire a beacon using the rtl8192ce:
>
> * Up to 130Mbps at 5Ghz & 54Mbps at 2.4Ghz
> 11N Channel: 36 / 5.180Ghz
> 11G Channel: auto
> in this mode no beacon can be seen.
>
> I verified using a MacBook Air under OS/X that the N SSID was appearing on the 5
> Ghz channel, but couldn't see the G beacon. Maybe its a bug in the WNDR3300.

I had never used the "auto" channel setting before. When I set my AP to the same 
configuration as yours (130/54 and 36/auto), it sent the 802.11n beacon in the 
2.4GHz channel. The 11G SSID was not seen; however, I could connect to the AP on 
channel 1. When I switched to 11G channel 1, rather than auto, then I saw the 
11G SSID in the beacon. I then tested the 5G band using a Dell DW1450 (p54usb) 
dual-band device. The 11N SSID was present on channel 36 using auto or channel 1.

There may be a bug in the WNDR3300 firmware. Sometimes when I switched from 
channel 1 to auto for the 2G band, that band would beacon the 11G SSID, and 
other times, it would beacon the 11N SSID. I have not determined a pattern. The 
11N SSID is always shown on the selected 5G channel. I could, however, connect 
the RTL8188CE to whatever SSID the AP was sending on the 2.4GHz band.

Curiouser and curiouser,

Larry

Re: Problems associating with RTL8188CE

[Tim Gardner]

On 12/15/2011 12:50 PM, Larry Finger wrote:
> On 12/15/2011 12:41 PM, Tim Gardner wrote:
>> On 12/14/2011 05:50 PM, Larry Finger wrote:
>>> Tim,
>>>
>>> I did the live test with the Dec. 14 build of 12.04 (64 bit). It
>>> connected with my WNDR3300 with no difficulty. I tested all 4 modes
>>> supported by the AP. All worked.
>>>
>>> I assume that an installation would work the same as the live version,
>>> but that is easy for you to test.
>>>
>>> Larry
>>>
>>
>> Here are the 3 modes I was able to successfully test on my WNDR3300 as
>> an open AP:
>>
>> * Up to 270Mbps at 2.4Ghz
>> 11N Channel: 03/2.422Ghz
>> in this mode only the 11N SSID is beaconed.
>> iperf: 11.2 Mbps average over 120 seconds, high of 26.2 Mbps, low of 6.71
>>
>> * Up to 270Mbps at 5Ghz & 54Mbps at 2.4Ghz
>> 11N Channel: 36 / 5.180Ghz
>> 11G Channel: auto
>> in this mode only the G beacon can be seen (which makes sense)
>> iperf: 14.3 Mbps average over 120 seconds, high of 28.5 Mbps, low of 8.97
>>
>> * Up to 130Mbps at 2.4Ghz
>> 11N Channel: 03/2.422Ghz
>> in this mode only the 11N SSID is beaconed.
>> iperf: 16.0 Mbps average over 120 seconds, high of 28.9 Mbps, low of 7.44
>>
>> This mode would not acquire a beacon using the rtl8192ce:
>>
>> * Up to 130Mbps at 5Ghz & 54Mbps at 2.4Ghz
>> 11N Channel: 36 / 5.180Ghz
>> 11G Channel: auto
>> in this mode no beacon can be seen.
>>
>> I verified using a MacBook Air under OS/X that the N SSID was
>> appearing on the 5
>> Ghz channel, but couldn't see the G beacon. Maybe its a bug in the
>> WNDR3300.
>
> I had never used the "auto" channel setting before. When I set my AP to
> the same configuration as yours (130/54 and 36/auto), it sent the
> 802.11n beacon in the 2.4GHz channel. The 11G SSID was not seen;
> however, I could connect to the AP on channel 1. When I switched to 11G
> channel 1, rather than auto, then I saw the 11G SSID in the beacon. I
> then tested the 5G band using a Dell DW1450 (p54usb) dual-band device.
> The 11N SSID was present on channel 36 using auto or channel 1.
>
> There may be a bug in the WNDR3300 firmware. Sometimes when I switched
> from channel 1 to auto for the 2G band, that band would beacon the 11G
> SSID, and other times, it would beacon the 11N SSID. I have not
> determined a pattern. The 11N SSID is always shown on the selected 5G
> channel. I could, however, connect the RTL8188CE to whatever SSID the AP
> was sending on the 2.4GHz band.
>
> Curiouser and curiouser,
>
> Larry

Yep - specifying a _fixed_ channel for 'Up to 130Mbps at 5Ghz & 54Mbps 
at 2.4Ghz' allowed a connection using the G beacon. I have not verified 
using a 5Ghz capable adapter that its also beaconing on channel 36.

rtg
-- 
Tim Gardner tim.gardner@canonical.com

Re: Problems associating with RTL8188CE

[Larry Finger]

On 12/16/2011 10:53 AM, Tim Gardner wrote:
>
> Yep - specifying a _fixed_ channel for 'Up to 130Mbps at 5Ghz & 54Mbps at
> 2.4Ghz' allowed a connection using the G beacon. I have not verified using a
> 5Ghz capable adapter that its also beaconing on channel 36.

Do you want to report this to Netgear, or should I?

Larry

Re: Problems associating with RTL8188CE

[Tim Gardner]

On 12/16/2011 10:06 AM, Larry Finger wrote:
> On 12/16/2011 10:53 AM, Tim Gardner wrote:
>>
>> Yep - specifying a _fixed_ channel for 'Up to 130Mbps at 5Ghz & 54Mbps at
>> 2.4Ghz' allowed a connection using the G beacon. I have not verified
>> using a
>> 5Ghz capable adapter that its also beaconing on channel 36.
>
> Do you want to report this to Netgear, or should I?
>
> Larry
>

Please, be my guest :) I'll go back to working on Intel wifi issues.

rtg
-- 
Tim Gardner tim.gardner@canonical.com

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Wed, Dec 14, 2011 at 11:58:04AM -0600, Seth Forshee wrote:
> On Wed, Dec 14, 2011 at 11:43:17AM -0600, Larry Finger wrote:
> > Seth,
> > 
> > As expected, my RTL8188SE came right up.
> > 
> > The lspci -nnv details for my card are
> > 
> > 06:00.0 0280: 10ec:8176 (rev 01)
> >         Subsystem: 10ec:8176
> >         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR+ FastB2B- DisINTx-
> >         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> >         Latency: 0, Cache Line Size: 64 bytes
> >         Interrupt: pin A routed to IRQ 21
> >         Region 0: I/O ports at 4000 [size=256]
> >         Region 2: Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
> >         Capabilities: <access denied>
> >         Kernel driver in use: rtl8192ce
> > 
> > Does yours also have 10ec:8176 as the PCI ID?
> 
> Yes.
> 
> 07:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
> 	Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8184]
> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> 	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> 	Latency: 0, Cache Line Size: 32 bytes
> 	Interrupt: pin A routed to IRQ 17
> 	Region 0: I/O ports at 2000 [size=256]
> 	Region 2: Memory at f0100000 (64-bit, non-prefetchable) [size=16K]
> 	Capabilities: <access denied>
> 	Kernel driver in use: rtl8192ce
> 	Kernel modules: rtl8192ce

Sorry for the long silence on this, I was busy with some other things.
But I've been playing with it again this week and uncovered some new
information regarding the failures.

I noticed the other day that the rtl8188ce was no longer having trouble
associating with this AP. After playing around in the router settings I
discovered that it works fine so long as the router isn't on channel 1.
So then I configured my other router to use channel 1, and then I
started seeing problems with that router as well.

I also tried the rtl8192ce driver from Realtek's website, and I'm having
better luck with that driver.

Seth

Re: Problems associating with RTL8188CE

[Larry Finger]

On 01/26/2012 03:33 PM, Seth Forshee wrote:
> Sorry for the long silence on this, I was busy with some other things.
> But I've been playing with it again this week and uncovered some new
> information regarding the failures.
>
> I noticed the other day that the rtl8188ce was no longer having trouble
> associating with this AP. After playing around in the router settings I
> discovered that it works fine so long as the router isn't on channel 1.
> So then I configured my other router to use channel 1, and then I
> started seeing problems with that router as well.
>
> I also tried the rtl8192ce driver from Realtek's website, and I'm having
> better luck with that driver.

Seth,

Are those AP's 802.11n devices that allow HT features on channel 1? I do not 
know if we support that or not. On my 802.11n device, it automatically switches 
to channel 3 when I enable HT, and that works.

I can connect to an 802.11g AP on channel 1 with no trouble.

Larry

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Thu, Jan 26, 2012 at 05:50:39PM -0600, Larry Finger wrote:
> On 01/26/2012 03:33 PM, Seth Forshee wrote:
> >Sorry for the long silence on this, I was busy with some other things.
> >But I've been playing with it again this week and uncovered some new
> >information regarding the failures.
> >
> >I noticed the other day that the rtl8188ce was no longer having trouble
> >associating with this AP. After playing around in the router settings I
> >discovered that it works fine so long as the router isn't on channel 1.
> >So then I configured my other router to use channel 1, and then I
> >started seeing problems with that router as well.
> >
> >I also tried the rtl8192ce driver from Realtek's website, and I'm having
> >better luck with that driver.
> 
> Seth,
> 
> Are those AP's 802.11n devices that allow HT features on channel 1?
> I do not know if we support that or not. On my 802.11n device, it
> automatically switches to channel 3 when I enable HT, and that
> works.
> 
> I can connect to an 802.11g AP on channel 1 with no trouble.

Whether or not HT is enabled makes no difference. One is an older
802.11g router, and on the other I see the same problems with or without
HT enabled.

Seth

Re: Problems associating with RTL8188CE

[Seth Forshee]

On Thu, Jan 26, 2012 at 09:06:23PM -0600, Seth Forshee wrote:
> On Thu, Jan 26, 2012 at 05:50:39PM -0600, Larry Finger wrote:
> > On 01/26/2012 03:33 PM, Seth Forshee wrote:
> > >Sorry for the long silence on this, I was busy with some other things.
> > >But I've been playing with it again this week and uncovered some new
> > >information regarding the failures.
> > >
> > >I noticed the other day that the rtl8188ce was no longer having trouble
> > >associating with this AP. After playing around in the router settings I
> > >discovered that it works fine so long as the router isn't on channel 1.
> > >So then I configured my other router to use channel 1, and then I
> > >started seeing problems with that router as well.
> > >
> > >I also tried the rtl8192ce driver from Realtek's website, and I'm having
> > >better luck with that driver.
> > 
> > Seth,
> > 
> > Are those AP's 802.11n devices that allow HT features on channel 1?
> > I do not know if we support that or not. On my 802.11n device, it
> > automatically switches to channel 3 when I enable HT, and that
> > works.
> > 
> > I can connect to an 802.11g AP on channel 1 with no trouble.
> 
> Whether or not HT is enabled makes no difference. One is an older
> 802.11g router, and on the other I see the same problems with or without
> HT enabled.

I decided to remove the card from the netbook and test it in another
machine, and it worked flawlessly. A different card in the netbook works
fine as well.

But then after reinstalling the rtl8188ce in the netbook I'm not seeing
any problems associating. None at all. So perhaps the issue was
mechanical in nature.

I'll keep testing it for a while to see if the problems resurface, but
for now everything seems fine. Thanks for your help.

Seth

Re: Problems associating with RTL8188CE

[Larry Finger]

On 01/27/2012 11:05 AM, Seth Forshee wrote:
>
> I decided to remove the card from the netbook and test it in another
> machine, and it worked flawlessly. A different card in the netbook works
> fine as well.
>
> But then after reinstalling the rtl8188ce in the netbook I'm not seeing
> any problems associating. None at all. So perhaps the issue was
> mechanical in nature.
>
> I'll keep testing it for a while to see if the problems resurface, but
> for now everything seems fine. Thanks for your help.

Thanks for the update. At least a mechanical problem would explain why I could 
not reproduce your problem.

Larry