Bug 438438
| Summary: | rtl8180 keeps timing out | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew Pegram <deltafox1229> | ||||||||
| Component: | kernel | Assignee: | John W. Linville <linville> | ||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 9 | CC: | dcbw | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2009-03-17 17:23:32 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Andrew Pegram
2008-03-20 21:18:51 UTC
Let me know what logs I should post, as I have no idea where to look (other than /var/log/messages, and I saw nothing out of the ordinary there) Please attach the contents of /var/log/messages anyway, just in case we can see something interesting. If possible, perhaps you can attach a wireshark capture taken from another station that shows the time when you disconnect? Created attachment 298914 [details]
/var/log/messages exerpt
Also, when I type ifup wlan0, it gives me this:
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; No such file or directory.
Determining IP information for wlan0... Done
How would I get a wireshark capture?
The "Set Encode" message is (sadly) normal -- please ignore it. Please attach the output of running "iwconfig wlan0 scan". Also, would you mind attaching the output of runnign "ps aux"? Let's hold-off on the wireshark capture for the moment. Created attachment 298921 [details]
First output is while it was disconnected, Second is while connected
Just to keep you posted, kernel-2.6.24.3-50.fc8 still has this problem. There is a patch in the builds here which may address this issue: http://koji.fedoraproject.org/koji/buildinfo?buildID=46311 When the build completes, could you give that a try? Does it help? Thanks! should I install the debug version, or just the regular? The non-debug version is fine. nope, same problem. Although I have noticed something odd: No matter how physically close I get to the router, NM always reports the signal strength in the range of 22%-27%, and the network speed is usually reported as 1 MB/s. I have rarely seen values outside that range. I don't know if that helps, but... there it is. This problem still exists in as of 2.6.25.3-18 in Fedora 9. Should I refile the bug under Fedora 9 I'm not sure of any specific fix, but it might be wortwhile for you to try a later build: http://koji.fedoraproject.org/koji/buildinfo?buildID=50951 Can you recreate this issue with those kernels? Same problem with 2.6.25.4-39.fc9.i686. Although, before, the NM applet would always register two bars, no matter what. Now, it seems to randomly switch between one, two, and three bars. I don't know if that means anything, but there it is. Is this still an issue in -108 or later? Still an issue in -108. I just downloaded the new 2.6.26 kernel, so I will keep you posted. Created attachment 319687 [details]
0002-rtl8180-normalize-quality-measurment-for-100-point.patch
Normalize quality values to 100-point scale.
I don't have a good theory on why this would help, but without this patch the driver can report quality levels like "133/100" -- that might be confusing NM and/or wpa_supplicant? Well, I think it is worth a try -- want to build a kernel w/ this patch applied and give it a shot? I have never compiled a kernel before, but I'd like to give it a try. What do I need? FWIW, the patch from comment 16 never really worked... :-( I've been using this device with the equivalent of a rawhide kernel lately, and it seems to work alright for me. Are you still seeing problems with recent kernels? If so, what is the latest kernel you have tried? Closed due to lack of response. Please reopen if/when the requested information becomes available...thanks! |