PROBLEM: linux kernel 3.9 rc1 and rtl8187 wireless, unable to connect to any available hotspots.

[Jenya Y]

Even though I am presented with a list of available networks, my system
with the rc1 kernel is not able to connect to any of them.
It stops at the point where it tries to obtain an IP address.

I tried to delete the Profile of my WiFi and recreate it but no luck.

This issue is only with 3.9rc1, it worked fine with 3.6 to 3.8.2.


--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Jenya Y]

Even though I am presented with a list of available networks, my system
with the rc1 kernel is not able to connect to any of them.
It stops at the point where it tries to obtain an IP address.

I tried to delete the Profile of my WiFi and recreate it but no luck.

This issue is only with 3.9rc1, it worked fine with 3.6 to 3.8.2.

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Larry Finger]

Even though I am presented with a list of available networks, my system with the
rc1 kernel is not able to connect to any of them.
It stops at the point where it tries to obtain an IP address.
I tried to delete the Profile of my WiFi and recreate it but no luck.
This issue is only with 3.9rc1, it worked fine with 3.6 to 3.8.2.

I am running 3.9-rc1 from wireless-testing, and both my RTL8187L and RTL8187B
can connect to WEP, WPA1, and WPA2 networks without a problem. At the moment, it
is not convenient for me to boot 3.9-rc1 from mainline, but I should be able to
do that tomorrow.

What kind of encryption are you using, and what is the USB ID for your device as
shown by the lsusb command?

Larry

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Larry Finger]

Larry, thank you for reply.
I set up my router with WPA2 // the USB ID Device 008: ID 0bda:8187 Realtek
Semiconductor Corp. RTL8187 Wireless Adapter.
(I used lsusb in my 3.8.2, I hope it makes no difference, it's the vendor device
id I suppose...)

*Never* drop the Cc to any mailing list unless you are prepared to pay for
private consulting!!

I generated a 64-bit version of Linus's current mainline tree. The results for
carious commands are as follows:

***@linux-cqp5:~/linux-2.6> sudo iwlist wlan1 scan
wlan1 Scan completed :
Cell 01 - Address: C0:3F:0E:BE:2B:44
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=70/70 Signal level=-36 dBm
Encryption key:on
ESSID:"lwfdjf-n"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0000027606801313
Extra: Last beacon: 4ms ago
IE: Unknown: 00086C7766646A662D6E
IE: Unknown: 010882848B962430486C
IE: Unknown: 030103
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown:
2D1A1E181AFFFF000001000000000000000000000000000000000000
IE: Unknown: 3D1603051300000000000000000000000000000000000000
IE: Unknown:
DD790050F204104A00011010440001021041000100103B000103104700103452030A44DB81A930CE71790556FE821021000D4E4554474541522C20496E632E10230008574E44523333303010240008574E4452333330301042000230311054000800060050F204000110110008574E445233333030100800020084
IE: Unknown: DD090010180201F0050000
IE: Unknown:
DD180050F2020101800003A4000027A4000042435E0062322F00
IE: Unknown:
DD1E00904C331E181AFFFF000001000000000000000000000000000000000000
IE: Unknown:
DD1A00904C3403051300000000000000000000000000000000000000

***@linux-cqp5:~/linux-2.6> iwconfig wlan1
wlan1 IEEE 802.11bg ESSID:"lwfdjf-n"
Mode:Managed Frequency:2.422 GHz Access Point: C0:3F:0E:BE:2B:44
Bit Rate=48 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-39 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:49 Missed beacon:0

***@linux-cqp5:~/linux-2.6> ifconfig wlan1
wlan1 Link encap:Ethernet HWaddr 00:1B:2F:A2:07:CA
inet addr:192.168.1.115 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:2fff:fea2:7ca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6137 (5.9 Kb) TX bytes:11066 (10.8 Kb)

***@linux-cqp5:~/linux-2.6> uname -r
3.9.0-rc1-Linus+


***@linux-cqp5:~/linux-2.6> lsusb
Bus 002 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0846:6a00 NetGear, Inc. WG111v2 54 Mbps Wireless [RealTek
RTL8187L]


As you can see, my system connected to a WPA2-encrypted network running 3.9-rc1
from the mainline tree. I do not know what problem you are having, but I cannot
reproduce it. My USB ID is different, but the chip is the same.

Larry

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Larry Finger]

I just recompiled the kernel with CONFIG_USB_DEBUG flag and here is the output
of the same commands you provided me with earlier + output of dmesg (though it's
might be superfluous)

No, it was not. At the end were the lines

[ 19.322729] rtl8187: wireless switch is on
[ 19.322763] usbcore: registered new interface driver rtl8187
[ 19.423269] systemd-udevd[272]: renamed network interface wlan0 to wlp0s29f7u7u3
[ 21.321746] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u7u3: link is not ready

Why are your udev rules renaming wlan0 to that crazy string?

Your ESSID for the AP of "1.618029" is also strange, but that works OK here.

Note that I added the ML to this reply.

Larry

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Jenya Y]

Post by Larry Finger
No, it was not. At the end were the lines
[ 19.322729] rtl8187: wireless switch is on
[ 19.322763] usbcore: registered new interface driver rtl8187
[ 19.423269] systemd-udevd[272]: renamed network interface wlan0 to wlp0s29f7u7u3
[ 21.321746] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u7u3: link is not ready
Why are your udev rules renaming wlan0 to that crazy string?
Your ESSID for the AP of "1.618029" is also strange, but that works OK here.
Note that I added the ML to this reply.
Larry

The ID didn't cause any issues before, neither did the strange names
(courtesy of systemd 197) and they are indeed very strange but as you
have already seen the same setup is working in 3.8.2

Here are relevant dmesg output in 3.8.2 //

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.2-1-jy (***@Y8) (gcc version 4.7.2 (GCC)
) #1 SMP PREEMPT Thu Mar 7 23:37:49 CET 2013
....
[ 17.868726] cfg80211: Calling CRDA to update world regulatory domain
[ 17.991571] cfg80211: World regulatory domain updated:
[ 17.991574] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 17.991576] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[ 17.991578] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[ 17.991580] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300
mBi, 2000 mBm)
[ 17.991582] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[ 17.991583] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300
mBi, 2000 mBm)
[ 18.393371] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 18.393650] ieee80211 phy0: hwaddr 00:15:af:03:b1:88, RTL8187vB
(default) V1 + rtl8225z2, rfkill mask 2
[ 18.404459] rtl8187: Customer ID is 0x00
[ 18.404944] rtl8187: wireless switch is on
[ 18.404970] usbcore: registered new interface driver rtl8187
[ 18.518265] systemd-udevd[326]: renamed network interface wlan0 to
wlp0s29f7u7u3
[ 20.419743] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u7u3: link is not ready
[ 30.480518] wlp0s29f7u7u3: authenticate with 00:13:49:df:22:72
[ 30.515723] wlp0s29f7u7u3: capabilities/regulatory prevented using AP
HT/VHT configuration, downgraded
[ 30.552709] wlp0s29f7u7u3: send auth to 00:13:49:df:22:72 (try 1/3)
[ 30.554577] wlp0s29f7u7u3: authenticated
[ 30.554666] rtl8187 5-7.3:1.0 wlp0s29f7u7u3: disabling HT as WMM/QoS
is not supported by the AP
[ 30.554669] rtl8187 5-7.3:1.0 wlp0s29f7u7u3: disabling VHT as WMM/QoS
is not supported by the AP
[ 30.555028] wlp0s29f7u7u3: associate with 00:13:49:df:22:72 (try 1/3)
[ 30.557461] wlp0s29f7u7u3: RX AssocResp from 00:13:49:df:22:72
(capab=0x411 status=0 aid=1)
[ 30.558206] wlp0s29f7u7u3: associated
[ 30.558237] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s29f7u7u3: link
becomes ready


so is there maybe a quick fix?

I have another idea, I should try out. Maybe I should try to disable
IPv6 in my network settings.

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Larry Finger]

Post by Larry Finger
No, it was not. At the end were the lines
[ 19.322729] rtl8187: wireless switch is on
[ 19.322763] usbcore: registered new interface driver rtl8187
[ 19.423269] systemd-udevd[272]: renamed network interface wlan0 to wlp0s29f7u7u3
[ 21.321746] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u7u3: link is not ready
Why are your udev rules renaming wlan0 to that crazy string?
Your ESSID for the AP of "1.618029" is also strange, but that works OK here.
Note that I added the ML to this reply.
Larry

The ID didn't cause any issues before, neither did the strange names (courtesy
of systemd 197) and they are indeed very strange but as you have already seen
the same setup is working in 3.8.2
Here are relevant dmesg output in 3.8.2 //
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
SMP PREEMPT Thu Mar 7 23:37:49 CET 2013
....
[ 17.868726] cfg80211: Calling CRDA to update world regulatory domain
(max_antenna_gain, max_eirp)
2000 mBm)
2000 mBm)
2000 mBm)
2000 mBm)
2000 mBm)
[ 18.393371] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 18.393650] ieee80211 phy0: hwaddr 00:15:af:03:b1:88, RTL8187vB (default) V1
+ rtl8225z2, rfkill mask 2
[ 18.404459] rtl8187: Customer ID is 0x00
[ 18.404944] rtl8187: wireless switch is on
[ 18.404970] usbcore: registered new interface driver rtl8187
[ 18.518265] systemd-udevd[326]: renamed network interface wlan0 to wlp0s29f7u7u3
[ 20.419743] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u7u3: link is not ready
[ 30.480518] wlp0s29f7u7u3: authenticate with 00:13:49:df:22:72
[ 30.515723] wlp0s29f7u7u3: capabilities/regulatory prevented using AP HT/VHT
configuration, downgraded
[ 30.552709] wlp0s29f7u7u3: send auth to 00:13:49:df:22:72 (try 1/3)
[ 30.554577] wlp0s29f7u7u3: authenticated
[ 30.554666] rtl8187 5-7.3:1.0 wlp0s29f7u7u3: disabling HT as WMM/QoS is not
supported by the AP
[ 30.554669] rtl8187 5-7.3:1.0 wlp0s29f7u7u3: disabling VHT as WMM/QoS is not
supported by the AP
[ 30.555028] wlp0s29f7u7u3: associate with 00:13:49:df:22:72 (try 1/3)
[ 30.557461] wlp0s29f7u7u3: RX AssocResp from 00:13:49:df:22:72 (capab=0x411
status=0 aid=1)
[ 30.558206] wlp0s29f7u7u3: associated
[ 30.558237] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s29f7u7u3: link becomes ready
so is there maybe a quick fix?
I have another idea, I should try out. Maybe I should try to disable IPv6 in my
network settings.

I see that had no effect. You need to bisect between HEAD and v3.8.

Larry


--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Jenya Y]

Post by Larry Finger
I see that had no effect. You need to bisect between HEAD and v3.8.
Larry

Larry, I'm very happy to report that after recompiling the kernel from
git master just a few minutes ago all is working again! Thank you very
much for your patience with my ignorance. (and all kudos to you, friend,
comrade, sister or brother....whoever you are on other end of the wire
who managed to fix this :)

So I'm off bothering Mighty Alan again until the other problem with my
usb hub in the display is solved :) Have to brace myself for another
round of awkward comments, I guess.

Thank you again! I will familiar with bisecting soon enough.

// Jenya



[ 0.000000] Linux version 3.9.0-1-jy-alpha (***@Y8) (gcc version 4.7.2
(GCC) ) #1 SMP PREEMPT Sat Mar 9 02:33:53 CET 2013
.....
[ 18.412863] ieee80211 phy0: hwaddr 00:15:af:03:b1:88, RTL8187vB
(default) V1 + rtl8225z2, rfkill mask 2
[ 18.423761] rtl8187: Customer ID is 0x00
[ 18.424413] rtl8187: wireless switch is on
[ 18.424799] usbcore: registered new interface driver rtl8187
[ 18.466185] systemd-udevd[294]: renamed network interface wlan0 to
wlp0s29f7u7u3
[ 20.361794] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u7u3: link is not ready
[ 23.724490] wlp0s29f7u7u3: authenticate with 00:13:49:df:22:72
[ 23.868638] wlp0s29f7u7u3: send auth to 00:13:49:df:22:72 (try 1/3)
[ 23.871268] wlp0s29f7u7u3: authenticated
[ 23.871402] rtl8187 5-7.3:1.0 wlp0s29f7u7u3: disabling HT as WMM/QoS
is not supported by the AP
[ 23.871407] rtl8187 5-7.3:1.0 wlp0s29f7u7u3: disabling VHT as WMM/QoS
is not supported by the AP
[ 23.872038] wlp0s29f7u7u3: associate with 00:13:49:df:22:72 (try 1/3)
[ 23.874879] wlp0s29f7u7u3: RX AssocResp from 00:13:49:df:22:72
(capab=0x411 status=0 aid=1)
[ 23.875634] wlp0s29f7u7u3: associated
[ 23.875662] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s29f7u7u3: link
becomes ready

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html