Bug 754481
| Summary: | Wifi signal losses every 30-45mn with RT3090 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dan <Danzisso> | ||||||||||
| Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 16 | CC: | acc-bugz-redhat, bbfuller, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, next.little.owl, sgruszka | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-07-12 09:42:51 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
Dan
2011-11-16 16:19:28 UTC
Do you connect to wpa hotspots? Using the same wifi chip (rt3090), this laptop here most of the time doesn't want to connect, but repeatedly asks for the WPA key: http://forums.fedoraforum.org/showthread.php?t=273086 Sometimes a connection is successfully established by NetworkManager, but that's only sporadic. The rt3090 seems to be handled by these modules: $ lsmod | grep rt2 rt2800pci 9507 0 rt2800lib 39527 1 rt2800pci crc_ccitt 1557 1 rt2800lib rt2x00pci 5768 1 rt2800pci rt2x00lib 46254 3 rt2800pci,rt2800lib,rt2x00pci mac80211 251806 3 rt2800lib,rt2x00pci,rt2x00lib cfg80211 151125 2 rt2x00lib,mac80211 eeprom_93cx6 1647 1 rt2800pci Maybe somebody could tell, which log files to look at and what to test in order to find the reason for this strange behaviour. (In reply to comment #1) > Do you connect to wpa hotspots? > > Using the same wifi chip (rt3090), this laptop here most of the time doesn't > want to connect, but repeatedly asks for the WPA key: > > http://forums.fedoraforum.org/showthread.php?t=273086 > > Sometimes a connection is successfully established by NetworkManager, but > that's only sporadic. > > The rt3090 seems to be handled by these modules: > > $ lsmod | grep rt2 > rt2800pci 9507 0 > rt2800lib 39527 1 rt2800pci > crc_ccitt 1557 1 rt2800lib > rt2x00pci 5768 1 rt2800pci > rt2x00lib 46254 3 rt2800pci,rt2800lib,rt2x00pci > mac80211 251806 3 rt2800lib,rt2x00pci,rt2x00lib > cfg80211 151125 2 rt2x00lib,mac80211 > eeprom_93cx6 1647 1 rt2800pci > > Maybe somebody could tell, which log files to look at and what to test in order > to find the reason for this strange behaviour. Yes, these are WPA networks. Need additional info? Created attachment 537054 [details] RPM from RussianFedora This is where this RPM comes from: http://koji.russianfedora.ru/koji/buildinfo?buildID=73 Created attachment 537055 [details] kmod-RPM from RussianFedora This one is from: http://koji.russianfedora.ru/koji/buildinfo?buildID=750 (built on my machine against the latest kernel) Created attachment 537056 [details] Second kmod-RPM from RussianFedora This one is from: http://koji.russianfedora.ru/koji/buildinfo?buildID=750 (built on my machine against the latest kernel) Created attachment 537057 [details] akmod-RPM from RussianFedora This one is from: http://koji.russianfedora.ru/koji/buildinfo?buildID=750 (built on my machine against the latest kernel) The above attachments (four RPMs) provide an alternative driver for RT3090 chipset. Feel free to test those on your 64bit-machine. (In reply to comment #7) > The above attachments (four RPMs) provide an alternative driver for RT3090 > chipset. Feel free to test those on your 64bit-machine. What shall I install? akmod is enough, right? Plus it will prevent me from having to run a kmod rebuild on every kernel update. In addition to that, will I have to disable some kernel modules to avoid conflicts? You will have to install all 4 of them (don't know why they splitted this into 4 rpms in RussianFedora). You should first try it without blacklisting any other kernel moduls. Reboot and get the output of "lsmod | grep rt2", "lspci -k" and "iwconfig". It _might_ conflict with these modules: rt2800pci rt2800lib rt2x00pci rt2x00lib It shouldn't do that, but if it does, try blacklisting them in /etc/modprobe.d/blacklist.conf and reboot. Then check again with "lspci -k" and "iwconfig". Maybe it even works without those kmod*-packages, but you will need at least both the rt3090- and the akmod-package. And if loading rt3090 and blacklisting those rt28*-modules lets your wlan-device vanish from "iwconfig": remember that you can simply uninstall the rpms and unblacklist all the rt28* modules. This will bring you back to the initial state. If that is the case, we will have to look for a different solution. By the way, I suspect, "64bit" is the problem. In FedoraForum I talked to two people who's rt3090 worked brilliantly on i686 installations. So in the end, a final solution could be found in those rt28** modules - but I'm not in to that. So, this is how the new driver works:
# yum -y install kmod-rt3090-3.1.2-1.fc16.x86_64-2.4.0.4-3.fc16.8.R.x86_64.rpm rt3090-2.4.0.4-1.fc16.noarch.rpm
# echo "blacklist rt2800pci" >> /etc/modprobe.d/blacklist.conf
After a reboot, your wifi connections should work properly, and you will get:
$ lsmod | grep rt2
$ lsmod | grep rt3
rt3090sta 816145 1
$ lspci -k
(...)
43:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
Subsystem: Hewlett-Packard Company Device 1453
Kernel driver in use: rt2860
Kernel modules: rt3090sta, rt2800pci
(...)
So your new driver will be called "rt2860", even though the module's name is "rt3090sta". Please report back, if it works for you.
We have to make in kernel driver work ... There are some pending radio chip programming fixes which should address this issue on rt2x00, you can try compat-wirless-next packages from http://people.redhat.com/sgruszka/compat_wireless.html to see if this fix the problem. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. This will be fixed in 3.4 release, I'm going to backport proper rt2x00 changes to 3.3. Actually no, I will rather wait since fedora will start using 3.4 kernel I'll put this in POST state so it's easier to spot when we rebase to 3.4. Should be relatively soon, as 3.4-rc7 is supposed to be the last rc before the final 3.4 release. Are we going to have kernel 3.4 for Fedora 16 and 17 or do we have to wait for FC18? (In reply to comment #20) > Are we going to have kernel 3.4 for Fedora 16 and 17 or do we have to wait for > FC18? Yes. F16 and F17 will be rebased around the time 3.4.1 is released. We already have kernel 3.4 on F-16 and F-17. I'm closing this bug, if issue still happen please reopen it. |