Bug 13960
| Summary: | rtl8187 not connect to wifi | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | David Heidelberg (david) |
| Component: | Network | Assignee: | Larry Finger (Larry.Finger) |
| Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
| Severity: | high | CC: | htl10, Larry.Finger, linville, rjw |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.31-rc5 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 13615 | ||
| Attachments: |
dmesg_from_30
dmesg_from_31 Set MSR_LINK_ENEDCA |
||
it worked once with .31, after reboot from .30, second try not worked. Adding dmesg from .31 Created attachment 22668 [details]
dmesg_from_31
[ 105.777403] wlan0: direct probe to AP 00:21:63:e9:83:2b try 1 [ 105.977062] wlan0: direct probe to AP 00:21:63:e9:83:2b try 2 [ 106.176052] wlan0: direct probe to AP 00:21:63:e9:83:2b try 3 [ 106.377239] wlan0: direct probe to AP 00:21:63:e9:83:2b timed out Didn't we put some fixes into wireless-testing to address this type of issue? Do we need to dig those out and redirect them to 2.6.31? Not sure why you're adding me -- its most likely just the driver not transmitting or receiving correctly. Just thought you might have some insight -- didn't we just deal with this in w-t? Looks like those issues were fall-out from some other changes, probably not at play here... okias, could you do a git bisect from 2.6.30 to 2.6.31-rc5 to try to narrow-down the problem? There are a handful of changes in drivers/net/wireless/rtl818x but none of them look immediately obvious as culprits to me. It is most important for the OP to bisect the problem. On v2.6.31-rc6-223-g6c30c53, both my RTL8187 and RTL8187B work perfectly, thus I cannot confirm this problem. What encryption is being used? Mine is using WPA2/TKIP. While testing openSUSE 11.2 Milestone 5, I did see a similar problem. When I unplugged/replugged the RTL8187B, then it worked. Can you unplug your device? If so, does that make it work? Created attachment 22798 [details]
Set MSR_LINK_ENEDCA
This patch fixes the problem on my computer.
This sounds like one of the mysterious problems I reported a while ago, and also seems to be about of the same time frame - I couldn' t switch from compat-wireless to compat-wireless, but had to switch back to as-shipped modules first. Handled-By : Larry Finger <Larry.Finger@lwfinger.net> Patch : http://bugzilla.kernel.org/attachment.cgi?id=22798 |
Created attachment 22667 [details] dmesg_from_30 Working fine with 2.6.30, not working with 2.6.31-rc5 (both - nm and manual connect). It try connect, but it fail. It's not signal problem, AP distance is about 3m.