Description of problem:
After booting Fedora-8-Live-X86_64, wireless cards based on the Ralink rt61
chipset are recognized, but all attempts to make a connection fail
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot from Fedora-8-Live-X86_64 DVD, modprobe shows rt61pci is loaded, and the
rt61pci-firmware package is preinstalled on live media
2. Attempt to select a network using NetworkManager -> tries to connect but
cannot get a IP address
3. Install to hdd
5. Try with NetWorkManager again -> same
6. Disable nm-applet and NetworkManager services
8. Try setting up wlan0 using system-config-network with static IP, static ESSID
-> appears to connect, but can't ping router, can only ping itself
9. Try using iwconfig and ifconfig to manually bring the deveice up and
configure -> same
10. Download legacy rt61-cvs-daily driver from
http://rt2x00.serialmonkey.com/wiki/index.php/Downloads, compile and install
11. setup wlan0 with system-config-network -> working wireless
No working wireless
wireless card associates with access piont and can ping the access point
Tested on simple network with no encryption: D-Link DWL-g510 to Netcomm NB9W router.
I think that this bug belongs to kernel (due to the wireless component) and
not to an R language module. I am changing the component accordingly. :-)
Please try these kernels (lots of rt2x00 updates):
Do these work any better for you?
How do I install alternative (126.96.36.199-49) kernel, kernel-devel and
kerel-headers alongside without overwriting the stable kernel (188.8.131.52-42)?
sorry about the component mess, my first bug :)
Running 184.108.40.206-49 now (it got pushed to updates), rt61pci is still broken.
The nasty thing is that that its appears to be working fine. i.e. you can scan
for networks and 'associate' with them. iwconfig then shows a valid SSID and
access point MAC, as well as a valid Link Quality, but no data is ever
transferred and the access point cannot be pinged.
Please attach the output of running 'dmesg', 'ifconfig wlan0', and 'iwconfig
Created attachment 259021 [details]
Created attachment 259031 [details]
Created attachment 259041 [details]
My wireless network details:
client distance: 6m
client: Dlink DWL-G510 Rev C2 (Ralink RT61)
typical link quality: 60 to 70%
encryption: open / none
access point: Netcomm NB9W C09_R10
Works well with legacy rt61 drivers from serialmonkey, but no luck with these
Might I ask you to try a few earlier .fc8 kernels, to see if any of them are
more stable w.r.t. wireless?
Which kernels work better?
Have you had a chance to attempt the earlier kernels as stated in comment #10?
Yes, I have tried about 5 other kernels from Koji, as well as ubuntu (2.6.22).
The problem in in the upstream srivers and there lack of backward compatibility
w.r.t older versions of the Devicescape wireless stack (it is developed against
2.6.24, where as f8 is 2.6.23). Leave this bug for now. We will see how things
go when 2.4.24 is released next month. Thanks to everyone vor helping
By the way, the enhanced legacy drivers (CVS) for rt61 are stable and work well,
so peorple with Ralink rt61 cards are not really without wireless, but just have
to compile a driver.
Bohan, just FYI -- the stack in Fedora kernels comes from the wireless-2.6
tree (i.e. it is later than 2.6.23, current with upstream). So if it is
broken now it will continue to be so.
What is the latest Fedora kernel you have tried? There have been some
rt61-specific fixes merged fairly recently.
I have just compiled a vanilla 2.6.24 kernel, copying over the Fedora 2.6.23
.config, and rt61pci is working!!!
I changed preemption to Preemptible Kernel（Low-latency desktop), enable 'Ralink
wireless drivers' in the network drivers section then compiled, rebooted and
wireless started working.
This is great news for F9!
Any chance 2.6.24 will be backported as an update for F8? (The rt2x00 srivers
require the latest ieee80211 stack, found only in 2.6.24 mainline)
Please review comment 14 -- the wireless code in 2.6.24 is much older than
what is already in the F8 kernels.
Please try these kernels:
If they continue to fail, please include new dmesg output as well
as /var/log/messages and the output of 'lspci -n'. Thanks!
Closing on basis of above message. Please reopen if the problem persists with