HOWTO: Native rt2860, rt2870 & rt3070 wireless drivers for Fedora

[ogetbilo]

The rt2860 and rt2870 chipsets from Ralink is used in many wireless USB cards

Update on November, 2011: The device drivers in newer stock kernels fully support rtxxx0 devices for which I once prepared the RPM files below. Hence from Fedora 16 onwards, I am dropping my support on these RPMS; the RPMs will not be shipped by RPMFusion.

Ralink provides native linux drivers on their website:
http://www.ralinktech.com/support.php?s=2
but they don't compile against Fedora kernels. The Fedora kernel devs backported some features from kernel 2.6.27 down to 2.6.25 and 2.6.26 and this breaks the driver code for these kernel versions.
The following howto is for installing patched drivers that work with current Fedora kernels.

Rpmfusion is dribble/livna/freshrpms repositories merged together and will not cause conflicts with them.
Having made that clear, let me explain two different ways of installing the kernel module from rpmfusion.

Note: rt2860 users: Replace every rt2870 you see below with rt2860 and you'll be fine.

Note: rt2870 users: If your card does not work with the rt2870 driver, please try the rt3070 one. It may (or may not) support your card.

Note: rt3070 users: Replace every rt2870 you see below with rt3070 and you'll be fine

1. If you want to add the rpmfusion repo to your repo's:
If you have the livna repository enabled, doing a yum update will automatically install the rpmfusion repo. For all other cases you can visit
this link (http://lists.rpmfusion.org/pipermail/rpmfusion-developers/2008-September/001362.html), which explains how to add the rpmfusion repository. In short do (one line)

rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

After this run a

yum install rt2870

and the rt2870 driver will be installed for the latest kernel.

2. If you don't want to add the rpmfusion repo to your repo's (MORE ADVANCED):


EITHER:

A- Browse through rpmfusion repository (http://download1.rpmfusion.org/free/fedora/updates) and grab your rpm files
You need 3 files:
rt2870-<version>.noarch.rpm
kmod-rt2870-<version>.<your_arch>.rpm
kmod-rt2870-<kernel-version>-<version>-<your_arch>.rpm

Install them altogether because they'll depend on each other

rpm -ivh *rt2870*.rpm

OR:

B- Download the source RPM's and compile them yourself.
Go to rpmfusion-testing's SRPM directory (http://download1.rpmfusion.org/free/fedora/updates/9/SRPMS/). You should download 2 src.rpm's:
rt2870-<version>.src.rpm
rt2870-kmod-<version>.src.rpm
Make sure you have a RPM BUILD environment. This page (http://www.city-fan.org/tips/CreateRPMBuildEnvironment) explains how to create one.
You can then build your rpm's via (don't do this as root!)

rpmbuild --rebuild rt2870-<version>.src.rpm
rpmbuild --rebuild rt2870-kmod-<version>.src.rpm --define "kernels $(uname -r)" --target $(uname -m)

Now you will have 2 RPM's in your ~/rpmbuild/RPMS directory.
One will be under arch the other will be in your own arch.
So these command will install them. As root:

cd /home/<user_name>/rpmbuild/RPMS/
rpm -ivh */*rt2870*.rpm

Here,
<user_name> is the user who ran the above rpmbuild commands.

[pmurphy]

Excellent post ogetbilo.

However for those of us using a Linksys WUSB100, you need to add one line to the header include/rt2870.h

within (line 85) #define RT2870_USB_DEVICES

This I guess defines what USB devices are supported in manufacturer ID/device ID pairs.

add the line

{USB_DEVICE{0x1737,0x0070)}, \

to the list of devices. Then patch, run make and install as previously stated.

Hopefully this helps, it did work with mine, your results may vary.

[hotdog]

Good stuff, it works perfectly with the rt2860sta internal wireless in my Eee PC 901 too.

In fact (on my system at least) you can simplify the installation procedure slightly, the make install script takes care of putting the RT28xxSTA.dat file in /etc/Wireless/RT28xx/ and I didn't need to create an alias in /etc/modprobe.d to get the module loaded at boot either. Basically all I had to do was download the driver source, unpack it, apply the patch, change the WPA options in os/linux/config.mk, make, make install and reboot.

[hotdog]

Update: the new kernel (2.6.26.3-29.fc9) causes the Ralink driver to fail to build, details here (http://forums.fedoraforum.org/showthread.php?p=1081377). We need an updated patch which replaces instances of 'dev->nd_net' with 'dev_net(dev)', at least for builds against 2.6.26 kernels.

[ogetbilo]

Thanks folks.

pmurphy,
I'll add that line to the patch.

hotdog,
I am going to write a more general patch that will cover all the kernel versions 2.6.24,2.6.25,2.6.26 . I will post the patch in this thread in a few days. Other than this, I will also try to build a kmod or akmod package, and post it on rpmfusion/livna so it will be less hassle for people.

Edit: I just realized that the change you mentioned ('dev->nd_net' with 'dev_net(dev)') is already there in the code in the rt2870 driver against 2.6.26 kernels and above. No need to add another patch for this (at least for rt2870).

[dutc2006]

I have fedora 9 with a linksys WUSB100 and when I patch the file os/linux/sta_ioctl.c it fails all 12 hunks, what might have i done wrong or what more info might help you help me...Thanks!

[ogetbilo]

Did you download the correct file? There is other drivers on that page. Make sure you get the right one.
By the way, I submitted a kmod package to rpmfusion for rt2870. It should be in rpmfusion testing repos soon.
Sorry for the late reply.

Edit: I see that they updated the driver tarball. The patch is probably not necessary anymore. I will check it out tomorrow and update the howto.

Edit2: I updated the HOWTO. Now things will be a lot easier for both rt2860 and rt2870 users.

[ogetbilo]

UPDATE (Oct 22nd, 2008): Well, we got some positive feedback and released the new drivers at rpmfusion. So this post does not mean much anymore.

Hello everyone. Do you want to help rpmfusion?
Ralink released a new rt2860 driver on their webpage and we need testers for it.
We -at rpmfusion- don't own any hardware with this chipset hence we cannot test it ourselves. If these RPM's work (or don't work) please let me know. It will be greatly appreciated, not only by us but also by other rt2860 users.
Step 0:
Please uninstall/remove the rt2860 drivers you have (if you have any). To check if you have any drivers installed in the kernel-modules tree of the kernel that you are currently using, do a

du -a /lib/modules/`uname -r`|grep 2860

If nothing comes up, you are good :)

Step 1a:
The rt2860 driver RPM's for 2.6.26.5-45.fc9.i686 and 2.6.26.5-45.fc9.x86_64 kernels can be found at
http://oget.fedorapeople.org/rt2860/

You will need 3 RPMs:
kmod-rt2860-1.8.0.0-0.fc9.<your_arch>.rpm
kmod-rt2860-2.6.26.5-45.fc9.<your_arch>-1.8.0.0-0.fc9.<your_arch>.rpm
rt2860-1.8.0.0-0.fc9.noarch.rpm
where <your_arch> is either i686/x86_64.

(Step 1b:
If you don't have a i686 or a x86_64 computer; or if you don't have the 2.6.26.5-45 kernel installed you can build your own RPM's from the 2 SRPM's on the same page: http://oget.fedorapeople.org/rt2860/

To build your RPM's you have to use

rpmbuild --rebuild rt2860*.src.rpm --define "kernels $(uname -r)" --target $(uname -m)


rt2860-1.8.0.0-0.fc9.src.rpm will produce 1 no arch RPM
rt2860-kmod-1.8.0.0-0.fc9.src.rpm will produce 1 arch-specific RPM. )


Step 2:
Please install the all the RPM's you have (or created) simultaneously (with "rpm -ivh --nodeps") and test out the driver.

After installing the RPM's you can plugin your card. If you see lights going on on your card that probably means it works. You can also check (as root)

lsmod |grep 2860

to see whether the module (most likely: rt2860sta) is loaded or not.
----


If you don't know and don't want to know how to build your own RPM's you can send a message to me with your kernel version and architecture so I can build the specific RPM's for you.

Thank you!

[bgsmith]

I built the source files on FC8 but from some reason do not get a kmod-rt2860-1.8.0.0-0.fc8.x86_64.rpm from the rpmbuild process. Will these source files build on FC8?

Thanks

Brad

[ogetbilo]

WARNING: This message is outdated due to a change in a previous message. Please don't take this into account.

They should build on FC8.

rpmbuild --rebuild rt2860-1.8.0.0-0.fc9.src.rpm --define "kernels $(uname -r)" --target $(uname -m)

will build a rt2860-1.8.0.0-0.fc8.noarch.rpm and put it in /home/<your_username>/rpmbuild/RPMS/noarch/
whereas

rpmbuild --rebuild rt2860-kmod-1.8.0.0-0.fc9.src.rpm --define "kernels $(uname -r)" --target $(uname -m)

will build two rpm's:
kmod-rt2860-1.8.0.0-0.fc8.x86_64.rpm
kmod-rt2860-<kernel_version>.fc8.x86_64-1.8.0.0-0.fc8.x86_64.rpm
and put them into /home/<your_username>/rpmbuild/RPMS/x86_64/

Did you build them as root (I would certainly not recommend it)? But if you did you will have the RPM's built in /usr/src/redhat/RPMS/noarch and /usr/src/redhat/RPMS/x86_64 instead.

Thank you for trying this driver :)

PS: If you are totally lost, tell me your kernel version (uname -r), I will build the RPM's for you.

[bgsmith]

Thanks for the reply when I execute

[bgsmith@pico rt2]$ rpmbuild --rebuild rt2860-kmod-1.8.0.0-0.fc9.src.rpm --define "kernels $(uname -r)" --target $(uname -m)


I get the following (trimmed) output:


.
.
.

Processing files: kmod-rt2860-2.6.26.3-14.fc8-1.8.0.0-0.fc8
Provides: kernel-modules-for-kernel = 2.6.26.3-14.fc8 rt2860-kmod = 1.8.0.0-0.fc8
Requires(interp): /bin/sh /bin/sh
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(VersionedDependencies) <= 3.0.3-1
Requires(post): /bin/sh /sbin/depmod
Requires(postun): /bin/sh /sbin/depmod
Requires: kernel-x86_64 = 2.6.26.3-14.fc8 rt2860-kmod-common >= 1.8.0.0
Processing files: rt2860-kmod-debuginfo-1.8.0.0-0.fc8
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/rt2860-kmod-1.8.0.0-0.fc8-root-bgsmith
Wrote: /home/bgsmith/rpmbuild/RPMS/x86_64/kmod-rt2860-2.6.26.3-14.fc8-1.8.0.0-0.fc8.x86_64.rpm
Wrote: /home/bgsmith/rpmbuild/RPMS/x86_64/rt2860-kmod-debuginfo-1.8.0.0-0.fc8.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.46602
+
.

I admit that I do not do much with rpmbuild but this tells me two rpms were built, one of which is debug information. I cannot find kmod-rt2860-1.8.0.0-0.fc8.x86_64.rpm.

So it appears that for some reason one of the two expected RPMs is not generated. I suspect it is operator (me) error.

Thanks for the help.

Brad

[ogetbilo]

Brad, it's my bad sorry. We usually build the kmod's in a different and slightly more complicated way. I tried to find an easy way of building them for regular users and I seem to be failed.

You can force install the two RPM's


rpm -ivh --force --nodeps ~/rpmbuild/RPMS/x86_64/kmod-rt2860-2.6.26.3-14.fc8-1.8.0.0-0.fc8.x86_64.rpm ~/rpmbuild/RPMS/noarch/rt2860-1.8.0.0-0.fc8.noarch.rpm


Don't worry. The kmod-rt2860 package was just an empty common package which actually does not do anything other than sorting the dependencies.

After you're done testing you can uninstall the RPM's with

rpm -e kmod-rt2860-2.6.26.3-14.fc8 rt2860-1.8.0.0-0.fc8

I will try to find a better solution for other people.

Sorry again,
Orcan

[bgsmith]

Orcan -

Ok. Thanks for the information and update. The rpms install just fine. I was worried that I was missing something with only 2 rpms and not 3.

I will let you know how it goes. I am trying to get an FC 8 workstation to work in a new location that only has wireless so I picked up an Edimax card that uses this rt2860 chip.

Brad

[ogetbilo]

OK great. As far as I can tell these drivers will work only with NetworkManager. I am still improving the RPM but some feedback would be really helpful.

Thanks a lot!

[nicubunu]

Trying to build it on latest Rawhide (2.6.27-0.392.rc8.git7.fc10.i686) I get "error: Bad exit status from /var/tmp/rpm-tmp.PxEtLe *%prep)"

note: I see rpmfusion devel stuck at 352, otherwise I would try the binary from there.

[nicubunu]

OK, I am stupid... of course I can build the src.rpm from the rpmfusion repository... it builds and installs. However, I have to investigate further: I can see the APs, but I can't log in (WPA Personal)

[ogetbilo]

nicubunu,
Thanks for trying to help.
Did you try to build the RPM from the SRPMS that are in the rpmfusion's testing repo right now? Those are the old drivers. The SRPM that I made is for the newer rt2860 driver, which supposedly has to work more efficient.

Note that to build my RPM you will still need kmodtool from rpmfusion (or livna).

I don't have the rawhide kernel but I will install it and build the RPM's for you (and other people).

ps: It looks like there is a newer kernel in rawhide now. I will do the RPMS for that one.

[nicubunu]

Your sources (fc9) refused to compile on my rawhide ("error: Bad exit status from /var/tmp/rpm-tmp.PxEtLe *%prep)") so I used a src.rpm from here: http://download1.rpmfusion.org/free/fedora/development/

[ogetbilo]

Oh, can you put the full error message?

[sathish_odiga]

i got the ans

[ogetbilo]

Hi sathish. These driver files are for Fedora only. If you follow the instructions you can install the drivers for the latets Fedora kernel. Sorry, I can't help with other distros directly. But I am attaching two complete patches (the first one is for Fedora) you should apply to build the drivers. By the way, the 2.6.22 kernel should not require the patches. It should work directly.

Note that because the first patch fixes the issues with backporting a new kernel feature from newer kernel into Fedora kernel, it may not work for other distros. If it fails, try the second patch.

Patch1: http://6mata.com:8014/rt2870/rt2870-complete-fedora.patch.tar.bz2
Patch2: http://6mata.com:8014/rt2870/rt2870-complete.patch.tar.bz2

To apply patches, extract them where you extracted the 1.4.0.0 driver files and do a:

patch -p1 < rt2870-complete-fedora.patch

or

patch -p1 < rt2870-complete.patch

[bgsmith]

I note that in the rpmfusion repository there is an akmod-rt2860-1.8.0.fc9.1.x86_64.rpm available. Is using akmod viable with the rt2860 drivers?

I ask because updating the kernel on a wireless system is multistep now. It would be nice to use akmod to automatically build the driver to the new kernel like akmod can do for the nvidia driver.

These drivers work very well with my Edimax EW-7728In card on an x86_64 system.

Thanks

Brad

[ogetbilo]

I note that in the rpmfusion repository there is an akmod-rt2860-1.8.0.fc9.1.x86_64.rpm available. Is using akmod viable with the rt2860 drivers?

I ask because updating the kernel on a wireless system is multistep now. It would be nice to use akmod to automatically build the driver to the new kernel like akmod can do for the nvidia driver.

These drivers work very well with my Edimax EW-7728In card on an x86_64 system.

Thanks

Brad
Yes, the akmod is derived from the same SRPM I put on the last page (with a minor improvement). The rt2860 driver at rpmfusion is now updated to 1.8.0. You can use either the kmod or the akmod, whichever you want.

Also note that, these rt2860/rt2870 kmods and akmods will not be needed as soon as their code gets into the mainstream kernel, which is planned to happen in kernel-2.6.29 (still 3-4 months).

[vinic]

How do I go about getting a working rt2860 driver for Fedora 10? I'm about to just say screw it and clean-install FC9.

[vinic]

An update: shortly after my previous post I was able to get the rt2860 drivers from RPMfusion and everything was working great. However, once kernel 2.6.27.5-94 hit, it's no longer working. I'll keep messing around and report back if I make any headway. Any input would be appreciated.

[ogetbilo]

vinic,
Rawhide experiences frequent kernel updates. It's hard to keep up the kmods synchronized all the time and it requires a significant amount of manpower. Therefore a decision was made to build kmods for rawhide only once a week. You can either make your own kmod (or akmod) or you should wait a little more.

[Kasper-pA-]

Using the current drivers (via yum install) on FC9, latest kernel. I cannot connect when using AES, I can when using TKIP... if I select Both (tkip and aes) it will not connect, i have to have it as TKIP only... any thoughts, or is it my system :)


rt2860, fc9 x86_64

kmod-rt2860-2.6.26.5-45.fc9.x86_64-1.8.0.0-1.fc9.1.x86_64
rt2860-1.8.0.0-1.fc9.noarch
kmod-rt2860-2.6.27.5-37.fc9.x86_64-1.8.0.0-1.fc9.6.x86_64
kmod-rt2860-2.6.26.6-79.fc9.x86_64-1.8.0.0-1.fc9.2.x86_64
kmod-rt2860-1.8.0.0-1.fc9.6.x86_64

kernel 2.6.27.5-37.fc9.x86_64

Kasp

[ogetbilo]

Kasper-pA- ,
That might be a driver problem. You may need to contact the author:
http://www.ralinktech.com/ralink/Home/Support/Linux.html

[Huntsman191]

Quick question, i have a Buffla WLI-UC-G300N which i think runs off the rt2870 driver. I just installed Fedora 10, installed RPM fusion, and the rt2870 driver, however, i cant seem to be able to find it listed anywhere on Fedora, under any wireless command or GUI. Any ideas how i could get this working?

[ogetbilo]

Quick question, i have a Buffla WLI-UC-G300N which i think runs off the rt2870 driver. I just installed Fedora 10, installed RPM fusion, and the rt2870 driver, however, i cant seem to be able to find it listed anywhere on Fedora, under any wireless command or GUI. Any ideas how i could get this working?

We can add the device ID to the driver header so that when you plugin the device, the kernel recognizes it and assigns the rt2870sta driver to your device. Are you sure that your device is rt2870? Post the lsusb or lspci -nv output depending on what kind of hardware you have.

Google shows 0 results for "Buffla WLI-UC-G300N". Is there a typo?

Edit: I found a Buffalo WLI-UC-G300N with vendor/device ID: 0x0411,0x00e8
If you can confirm this via your lspci -nv or lsusb output I'll add it to the rpmfusions kmod.

[shayh]

I have a Sweek wl303 udb dongle. according to their site:
Chipset: Ralink RT2870 + RT2820

I successfully installed via yum rt2870 on f10, however no interface is created, iwconfig comes out empty.
from lsusb:
Bus 001 Device 008: ID 177f:0302
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

from /var/log/messages:
Feb 4 09:56:50 shayh-l kernel: usb 1-7: new high speed USB device using ehci_hcd and address 8
Feb 4 09:56:50 shayh-l kernel: usb 1-7: configuration #1 chosen from 1 choice
Feb 4 09:56:50 shayh-l kernel: usb 1-7: New USB device found, idVendor=177f, idProduct=0302
Feb 4 09:56:50 shayh-l kernel: usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 4 09:56:50 shayh-l kernel: usb 1-7: Product: 802.11 n WLAN
Feb 4 09:56:50 shayh-l kernel: usb 1-7: Manufacturer: Ralink
Feb 4 09:56:50 shayh-l kernel: usb 1-7: SerialNumber: 1.0

please help, thank
shay

[ogetbilo]

Could you provide the device name properly? "Sweek wl303 udb dongle" doesn't give me any search results. And a link to this website please.

What you can do is, you can add the vendorID and productID to the include/rt2870.h file and compile the driver yourself afterwards. If your wireless card works that way we will add it to the kmod.

If this sounds too complicated, tell me you kernel version and I'll try to build a custom kmod for you. But I'll be busy until the weekend. You will need to wait.

[shayh]

thaks for the swift reply,
the devices site is:
http://www.sweex.com/producten.php?sectie&item=65&artikel=921

As specified before the detailes are idVendor=177f, idProduct=0302
I'm using latest i686 kernel for F10.

I'll try building myself and tell you what happen.
update:downloaded the source for the driver and added the line:
{USB_DEVICE(0x177f,0x0302)}, /* Sweex */ \
to 2008_0925_RT2870_Linux_STA_v1.4.0.0/include/rt2870.h
compiled and now everything works grate.

thanks
shay

[ogetbilo]

great. I will add this device to the header file. please allow some time for the updated kmod to land on the repos.

Edit: I built the new packages.
For F-10 and rawhide: kmod-rt2870-1.4.0.0-7 and above will have Sweex LW303 support
For F-9: kmod-rt2870-1.4.0.0-5 and above will have Sweex LW303 support

[bricktop41]

I am new to linux my wireless does not work in linux but it works in windows I need a comprehensive list of the packages I need to make it work. I don't quite understand how every thing in linux works so some basic tutorials would help. Also I must do this offline by downloading the files in windows, rebooting, and installing into linux
Here is the hardware info .

04:00.0 Network controller [0280]: RaLink Device [1814:0781]


Lsmod=

Module Size Used by
vfat 12672 1
fat 42784 1 vfat
fuse 49436 2
i915 53380 2
drm 158260 3 i915
sco 12932 2
bridge 43668 0
stp 6148 1 bridge
bnep 14848 2
l2cap 21504 3 bnep
bluetooth 48608 5 sco,bnep,l2cap
sunrpc 155924 3
ip6t_REJECT 7296 2
nf_conntrack_ipv6 15864 2
ip6table_filter 6400 1
ip6_tables 14736 1 ip6table_filter
ipv6 230132 24 ip6t_REJECT,nf_conntrack_ipv6
cpufreq_ondemand 9996 1
acpi_cpufreq 12172 1
dm_multipath 17164 0
uinput 10624 0
snd_hda_intel 351124 3
snd_seq_dummy 6660 0
snd_seq_oss 30364 0
snd_seq_midi_event 9600 1 snd_seq_oss
snd_seq 48576 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 10124 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 42496 0
snd_mixer_oss 16896 1 snd_pcm_oss
i2c_i801 12048 0
snd_pcm 65924 2 snd_hda_intel,snd_pcm_oss
usb_storage 82440 1
i2c_core 21396 2 drm,i2c_i801
pcspkr 6272 0
sdhci_pci 10624 0
sdhci 17540 1 sdhci_pci
jmb38x_ms 12292 0
snd_timer 22024 2 snd_seq,snd_pcm
joydev 12736 0
snd_page_alloc 11016 2 snd_hda_intel,snd_pcm
r8169 32132 0
mmc_core 43676 1 sdhci
snd_hwdep 10500 1 snd_hda_intel
memstick 12060 1 jmb38x_ms
snd 50616 16 snd_hda_intel,snd_seq_dummy,snd_seq_oss,snd_seq,sn d_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd _timer,snd_hwdep
mii 8192 1 r8169
soundcore 9416 1 snd
video 20244 0
wmi 9768 0
output 6528 1 video


distro

2.6.27.5-117.fc10.i686


I do understand that this is a learning curve, however the quicker I get full function on the linux side I can learn this OS faster by not switching between 2 systems

[ogetbilo]

bricktop41,

After enabling the RPMFusion free repository, doing a
yum install rt2860
as root will make your wireless card work.

Details are given in the first post of this thread. Let me know if there's anything you don't understand.

[IrishBouzouki]

The probability of getting help with your problem would have tripled if you just wrote to this thread in the first place:
http://www.fedoraforum.org/forum/showthread.php?t=197413

There. Sorry about that. It might help if this thread were not titled "HOWTO: Native rt2860 and rt2870 wireless drivers for Fedora 8 and 9" specifically the 8 and 9 part - which makes my particular problem seem not relevant to the thread. Although I suppose it should be obvious to an expert, I am hardly that.

RPMFusion does not replace Fedora packages. This is a general policy. Keeping it enabled will not magically pull packages from RPMFusion to your system.

Thanks for pointing that out. I will try to set that up then so the package will update. It will be a good learning experience for how to add a third party repository which is probably something I should know how to do.

Forgive please what must seem like anality. I simply lack the expertise to deal with some mess being created on my machine and really really really need to keep my machine working, so I am overly conservative (well, for someone who runs Fedora that is).

There have been many reports about failing WPA connections with rt2860/rt2870 drivers. Unfortunately, we don't have a fix for this. Can't you use WEP instead?

WEP would not be practical for me, if needed I will use the hardline connection instead until (when/if) WPA becomes a functional option.

But are you saying WPA never works with these drivers? Or to put it another way, is there anyone here who has managed to get the drivers to work with WPA?

I'd suggest you to rpeort to issue to Ralink: http://www.ralinktech.com/ralink/Home/Support/Linux.html

The sourceforge project seems to be in transformation, but I have singed up for the user group at rt2x00.serialmonkey.com and will see if they can provide some assistance.




At any rate, thank you for your work on the drivers, and for your help to me. And again I am sorry for posting on another thread and being another pain in the butt n00b.

[ogetbilo]

There. Sorry about that. It might help if this thread were not titled "HOWTO: Native rt2860 and rt2870 wireless drivers for Fedora 8 and 9" specifically the 8 and 9 part - which makes my particular problem seem not relevant to the thread. Although I suppose it should be obvious to an expert, I am hardly that.


Yes, the title needs a change. I'll bug the forum admins for that. Sorry for the confusion.


Thanks for pointing that out. I will try to set that up then so the package will update. It will be a good learning experience for how to add a third party repository which is probably something I should know how to do.

Forgive please what must seem like anality. I simply lack the expertise to deal with some mess being created on my machine and really really really need to keep my machine working, so I am overly conservative (well, for someone who runs Fedora that is).


Rarely, a package gets dropped from Fedora because of patent issues. Then RPMFusion may take that RPM over. But this is very infrequent and it is probably the only way that you'll get an RPM from RPMFusion (if you don't install anything from RPMFusion manually).


WEP would not be practical for me, if needed I will use the hardline connection instead until (when/if) WPA becomes a functional option.

But are you saying WPA never works with these drivers? Or to put it another way, is there anyone here who has managed to get the drivers to work with WPA?

The sourceforge project seems to be in transformation, but I have singed up for the user group at rt2x00.serialmonkey.com and will see if they can provide some assistance.



Please let me know if you get WPA working so I can update the RPM's accordingly. Here I found pages from users of other distros who claim to have a working WPA with rt2870:

http://ubuntuforums.org/showthread.php?t=694026
http://wiki.archlinux.org/index.php/Rt2870



At any rate, thank you for your work on the drivers, and for your help to me. And again I am sorry for posting on another thread and being another pain in the butt n00b.

It's okay. Just make a forum search with the number of the chipset whenever you get a new hardware. This forum is large and may provide you invaluable information.

[IrishBouzouki]

Please let me know if you get WPA working so I can update the RPM's accordingly. Here I found pages from users of other distros who claim to have a working WPA with rt2870:

http://ubuntuforums.org/showthread.php?t=694026
http://wiki.archlinux.org/index.php/Rt2870

Just fyi I attempted the RT2870STA.dat file edits as recommended in the archlinux article (albeit per my own configuration obviously, and with careful referring back and forth to my router settings page). I only edited the parameters mentioned in the linked article. I had a moment of hope as the settings which were in the dat file did not correspond at all to the ones in my network (or my set up in Network Manager) at first. However after editing and a system restart there was no change in system behaviour. I don't know much about this but it seems that Network Manager is the app that is attempting to make the connection through the driver and that it is ignoring the settings in the dat file and using its own instead, which may have a problem with this setup.

That would mean I have the good fortune to be using the perfect storm of fc10, rt2870, wpa, and network-manager!?!

Anyway, short word is that the dat file editing approach in the archlinux link did not change any system behaviour.


I also went ahead and added the RPMFusion repository for an update source so if there should be a fix eventually I will get it.


FURTHER INVESTIGATION:

I noted that the only security options which the Network Manager applet GUI will permit me to apply are "None" and "WPA & WPA2 Personal". There are other options in the pull-down but choosing them disables the "Apply" button.
So I tried "None" and re-configured my router, just to test as doing it kicked everything else off my network.
Upon system restart the device did indeed connect properly and in fact I am posting this EDIT over the Wireless connection using (I presume) the RPMFusion drivers.

This just confirms what you stated re the WPA. But it also indicates there is not a separate additional issue.

[ogetbilo]

Hi ogetbilo

I actually already have the kmod installed:

(code)
[root@tychobrahe ~]# yum install kmod-rt2860
Loaded plugins: refresh-packagekit
Setting up Install Process
Parsing package install arguments
Package kmod-rt2860-1.8.0.0-3.fc10.5.i686 already installed and latest version
Nothing to do
[root@tychobrahe ~]#
(end code)

Its not responding to any iwconfig commands.
Perhaps my module is botch up somewhere?

Is the card recognized at all? Do a:
lsmod|grep rt2860

Also, do you get any error messages in system.log when you remove/reload the driver.

To remove/reload the driver:
rmmod rt2860sta
modprobe rt2860sta

To see the system log afterwards:
dmesg

[Gustav4.]

Hi ogetbilo

Thanks for your reply, but I had just this evening removed the module andtried to reinstalled it as described in the post you mentioned, but now I have more questions than before. Here is what a reinstall terminal session looks like:



root@tychobrahe ~]# yum install kmod-rt2860
Loaded plugins: refresh-packagekit
Setting up Install Process
...

Dependencies Resolved

================================================== ================================================== ==========================================
Package Arch Version Repository Size
================================================== ================================================== ==========================================
Installing:
kmod-rt2860 i686 1.8.0.0-3.fc10.5 rpmfusion-free-updates 5.0 k
Installing for dependencies:
kmod-rt2860-2.6.27.21-170.2.56.fc10.i686 i686 1.8.0.0-3.fc10.5 rpmfusion-free-updates 219 k
rt2860 noarch 1.8.0.0-2.fc10 rpmfusion-free-updates 12 k

Transaction Summary
================================================== ================================================== ==========================================
Install 3 Package(s)
Update 0 Package(s)
Remove 0 Package(s)


and now nothing shows up after running an lsmod command looking for rt2860:


[root@tychobrahe ~]# lsmod | grep rt
iTCO_vendor_support 6916 1 iTCO_wdt
[root@tychobrahe ~]# lsmod | grep 2860
[root@tychobrahe ~]#


So what was installed, and why can't i find the module? Should I try to remove the module and start again?

Cheers!

[ogetbilo]

Gustav4.
Are you sure that your wireless has rt2860 chipset?

If after installing the kmod-rt2860 and rebooting your computer, the lsmod outputs does not display rt2860sta, then that means that the driver will not support you card.

However that may not be the end of the story. If you can tell me the brand of your wireless card, I can try to do something. Is it onboard, PCI, USB? etc.

[asphodeli]

Just fyi I attempted the RT2870STA.dat file edits as recommended in the archlinux article (albeit per my own configuration obviously, and with careful referring back and forth to my router settings page). I only edited the parameters mentioned in the linked article. I had a moment of hope as the settings which were in the dat file did not correspond at all to the ones in my network (or my set up in Network Manager) at first. However after editing and a system restart there was no change in system behaviour. I don't know much about this but it seems that Network Manager is the app that is attempting to make the connection through the driver and that it is ignoring the settings in the dat file and using its own instead, which may have a problem with this setup.

That would mean I have the good fortune to be using the perfect storm of fc10, rt2870, wpa, and network-manager!?!

Also I am wondering if my particular choice of WPA (not WPA2) and TKIP (not AES) is somehow related?

Anyway, short word is that the dat file editing approach in the archlinux link did not change any system behaviour.


I also went ahead and added the RPMFusion repository for an update source so if there should be a fix eventually I will get it.


FURTHER INVESTIGATION:

I noted that the only security options which the Network Manager applet GUI will permit me to apply are "None" and "WPA & WPA2 Personal". There are other options in the pull-down but choosing them disables the "Apply" button.
So I tried "None" and re-configured my router, just to test as doing it kicked everything else off my network.
Upon system restart the device did indeed connect properly and in fact I am posting this EDIT over the Wireless connection using (I presume) the RPMFusion drivers.

This just confirms what you stated re the WPA. But it also indicates there is not a separate additional issue.

I have almost the same config as yours (fc10 on an Eee Box B202), and I am unable to get Network Manager to connect - there's no option for "None", and it doesn't seem to connect at all if I use the selected option of "WPA & WPA2 Personal"

[Gustav4.]

[gustav@tychobrahe ~]$ lspci | grep Network
0c:00.0 Network controller: RaLink RT2860
[gustav@tychobrahe ~]$ lsmod | grep 2860
[gustav@tychobrahe ~]$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

pan0 no wireless extensions.

virbr0 no wireless extensions.

[gustav@tychobrahe ~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1B:38:D0:50:38
inet addr:192.168.1.37 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:38ff:fed0:5038/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2195 errors:0 dropped:0 overruns:0 frame:0
TX packets:2364 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:996453 (973.0 KiB) TX bytes:340649 (332.6 KiB)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2388 (2.3 KiB) TX bytes:2388 (2.3 KiB)

virbr0 Link encap:Ethernet HWaddr EE:4F:B7:15:12:C1
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::ec4f:b7ff:fe15:12c1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:4586 (4.4 KiB)

[gustav@tychobrahe ~]$


And the card is an Intel ProSetWireless: Here's some code:

// Mandatory settings
// ----------------------------------------------------------------------
FamilyCode = 9.22
PFilesOffset = "Intel\Wireless"
EFData = "Intel� PROSet/Wireless", Alpha, "11.1.1.0"


a full readout from the Network Controller on my box:


0c:00.0 Network controller: RaLink RT2860
Subsystem: RaLink Device 2790
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 10
Region 0: Memory at f8200000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Count=1/32 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSVoil-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSVoil-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSVoil-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Kernel modules: rt2860sta


I hope this helps.

cheers!

[ogetbilo]

In the last output, "Kernel modules: rt2860sta" indicates that the rt2860sta driver (which comes with the kmod) is assigned to your card. That's good. It is weird that the module does not load automatically.

Let's do this.
- Make sure lsmod|grep rt2860 shows nothing
- Look at the dmesg output
- Do a modprobe rt2860sta
- Look at the dmesg output again. What is added to the end? Is there an error message?

[tomy88]

I installed the drivers and kmod rpmfusion the others and work for me, but when choosing my network and set the password, which makes me have to make an authentication of the network and not connect, as if to put the password wrong.

[ogetbilo]

tomy88,
Could you be a little more verbose?
What Fedora version? What kernel version? kmod version? Using NetworkManager or not? Where do you put the password?

There is also a new version of the driver in the testing repos, did you try that?

[Gustav4.]

Hi ogetbilo

Hope you had a fine weekend.

Heres what a terminal session looks like with the commands you suggested:

[gustav@tychobrahe ~]$ lsmod | grep rt2860
[gustav@tychobrahe ~]$ dmesg
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.27.21-170.2.56.fc10.i686.PAE (mockbuild@xenbuilder2.fedora.redhat.com) (gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC) ) #1 SMP Mon Mar 23 23:24:26 EDT 2009

(...)

CPU0 attaching NULL sched-domain.
CPU1 attaching NULL sched-domain.
CPU0 attaching sched-domain:
domain 0: span 0-1 level MC
groups: 0 1
CPU1 attaching sched-domain:
domain 0: span 0-1 level MC
groups: 1 0
ACPI: EC: GPE storm detected, transactions will use polling mode
ACPI: EC: missing confirmations, switch off interrupt mode.
[gustav@tychobrahe ~]$ su -
Password:
[root@tychobrahe ~]# modprobe rt2860sta
FATAL: Could not open '/lib/modules/2.6.27.21-170.2.56.fc10.i686.PAE/kernel/drivers/net/wireless/rt2860sta.ko': No such file or directory
[root@tychobrahe ~]# dmesg
(...)
CPU0 attaching NULL sched-domain.
CPU1 attaching NULL sched-domain.
CPU0 attaching sched-domain:
domain 0: span 0-1 level MC
groups: 0 1
CPU1 attaching sched-domain:
domain 0: span 0-1 level MC
groups: 1 0
ACPI: EC: GPE storm detected, transactions will use polling mode
ACPI: EC: missing confirmations, switch off interrupt mode.
[root@tychobrahe ~]#


So, its obvious that the fatal error has something to it, but there is no error message in the dmesg output. It is baffling, isn't ? As I mentioned before, I removed the RT2860sta driver(s?) that I had installed previously, and then reinstalled the rpmfusion driver. Now, its as if there ins't any thing matching the RT2860 driver on my system.

But again:
[root@tychobrahe ~]# yum install kmod-rt2860
Loaded plugins: refresh-packagekit
Setting up Install Process
Parsing package install arguments
Package kmod-rt2860-1.8.0.0-3.fc10.5.i686 already installed and latest version
Nothing to do
[root@tychobrahe ~]#

So where is it?

[ogetbilo]

Gustav.4, there you go. The problem is you got a PAE kernel installed and you are trying to load a nonPAE kmod. That won't work. First, are you using the PAE kernel intentionally? I don't have much knowledge about PAE, but I'll tell you two ways of solving your issue.

Step 1:
Remove all the rt2860 stuff from your computer. You can use something like
rpm -e `rpm -qa|grep rt2860`

Step 2 (harder way):
Normally, when you install a PAE kernel, I would expect yum to download the PAE kmods for that. But that doesn't happen for you, and I don't know why. So let's go and download you PAE kmods from rpmfusion:
http://download1.rpmfusion.org/free/fedora/updates/10/i386/

and install them manually. Then things should work.

Step 2 (easier way):
yum install akmod-rt2860
Reboot
Done!

akmods carry the source code for your module. Whenever you boot your computer, the akmod software will check if the modules are built for the kernel that you are booting to. If they are not present (i.e. if that is a new kernel), it will build and install your rt2860 kmods for you automatically.

This way you never have to worry about this problem anymore.

Come back and tell me about your victory :)

[asphodeli]

Well, I didn't expect Ralink to update their drivers with my e-mail to them regarding the 2.1.0.0 driver causing problems in Fedora 10 (Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=36934!"), but the latest 2.1.1.0 drivers on their website compile fine on 2.6.27.21-170.2.56.fc10.i686, and it works just fine with NetworkManager and my home wireless config (WPA/WPA2 Personal with TKIP+AES). I haven't tested it out extensively, though.

[ogetbilo]

I think multiple people sent emails. We even invited them to rpmfusion bugzilla, where we have extensive reports from different people.

I built the new kmods last Sunday. They are in the testing repo now.

[Gustav4.]

Amazing!!! (what's a PAE?)

Now this is getting a little off topic but it could be import to others regarding the installation of driver modules...
These PAE kernels came to light after a couple of upgrades. Really, I never thought about them, but it one was on the top of the list when I boot my box. I really didn't know what they were... I'm not sure that I need them, and I am impelled to removed them, and start this process with the regular x86 kernel. I noticed that there were two kernels that could be booted - identical in name exept for the PAE suffix.

Here's what my boot directory looks like:

[gustav@tychobrahe ~]$ ls /boot
config-2.6.27.12-170.2.5.fc10.i686 initrd-2.6.27.12-170.2.5.fc10.i686.PAE.img System.map-2.6.27.21-170.2.56.fc10.i686.PAE
config-2.6.27.12-170.2.5.fc10.i686.PAE initrd-2.6.27.21-170.2.56.fc10.i686.img vmlinuz-2.6.27.12-170.2.5.fc10.i686
config-2.6.27.21-170.2.56.fc10.i686 initrd-2.6.27.21-170.2.56.fc10.i686.PAE.img vmlinuz-2.6.27.12-170.2.5.fc10.i686.PAE
config-2.6.27.21-170.2.56.fc10.i686.PAE lost+found vmlinuz-2.6.27.21-170.2.56.fc10.i686
efi System.map-2.6.27.12-170.2.5.fc10.i686 vmlinuz-2.6.27.21-170.2.56.fc10.i686.PAE
grub System.map-2.6.27.12-170.2.5.fc10.i686.PAE
initrd-2.6.27.12-170.2.5.fc10.i686.img System.map-2.6.27.21-170.2.56.fc10.i686
[gustav@tychobrahe ~]$



Now, ogetbilo, should I remove the akmod-rt2860 and just ditch the PAE kernel, and start fresh with a non PAE kernel? I have no idea what ramifications the PAE kernel will have on any updates, or selection of packages.

The module worked after booting and running a modprobe command, but I was still have trouble trying to establish a connection to my wireless network, though all appeared as it should. But what a joy to see "Wireless" show up in the Network Manager.

Cheers!

[ogetbilo]

From the release notes I see that:
"kernel-PAE, for use in 32-bit x86 systems with > 4GB of RAM, or with CPUs that have a 'NX (No eXecute)' feature. This kernel support both uniprocessor and multi-processor systems. "

I don't know if this applies to you. You can safely remove it if you think it is not useful for your system.

Either way, you don't need to remove the akmod-rt2860. akmods are happy with any kernel flavor you use.

[Gustav4.]

Hi ogetbilo

I've decide to ditch the PAE jobbers since I really don't think they're suited to my box. How they got there is a little mystery which I don't care to solve. But for some feed back on the akmod-rt2860:

Running lsmod didn't find it, but after modprobe, lsmod found the module. So did "ifconfig ra0" and so did the Network Manager. The wireless radio sensor finds the networks of my neighbours, too. Mine is hidden, and I am asked if I should join the hidden network by typing in the name.

Once this is done, my network shows up with the others in the area.

However, when I write in the WEP key, the configuration window waits a long while before asking for the key again. It never gets accepted, confirmed, nor implemented.

All manipulations using iwconfig are completely ignored, and have no effect on the settings, though AP reports my AirPort Express box' mac address, but sometimes this changes to "no affilated address" or something like that.

So, I got the module up and running, but I can't make it connect, likely because the key doesn't get enabled.

thanks a ton, for your time and your fine work!

gustav4.

[ogetbilo]

Hi, I'm glad you got the hardware detected finally.

When I put in my WEP password on NetworkManager, my rt2870 works with no problems. I don't own a rt2860 though. Maybe other people here can share their experience.

Also, I read that if
cat /proc/cpuinfo |grep pae
shows something on your computer, then the PAE kernel might be better for you.

[Gustav4.]

Bingo

I am now posting this reply wirelessly. Tons of thanks to you ogetbilo!

I was working on my Mac when I noticed that the AirPort icon was greyed out on it. It's a frequent problem where the units falls off on all connections. I unplugged the unit and fives seconds later plugged it back in. Checked that the network was up on the Mac, and then booted my laptop. It was amazing.

By the way regarding the PAE kernel and the output from cpu:

[gustav@tychobrahe ~]$ cat /proc/cpuinfo | grep pae
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
[gustav@tychobrahe ~]$

Apparently there are flags labelled as pae, and nothing else. But would a flag constitute a need for a pae kernel?

Thanks again!

Best Regards
Gustav

[Jon Briggs]

Gustav.4, there you go. The problem is you got a PAE kernel installed and you are trying to load a nonPAE kmod. That won't work. First, are you using the PAE kernel intentionally? I don't have much knowledge about PAE, but I'll tell you two ways of solving your issue.

Step 1:
Remove all the rt2860 stuff from your computer. You can use something like
rpm -e `rpm -qa|grep rt2860`

Step 2 (harder way):
Normally, when you install a PAE kernel, I would expect yum to download the PAE kmods for that. But that doesn't happen for you, and I don't know why. So let's go and download you PAE kmods from rpmfusion:
http://download1.rpmfusion.org/free/fedora/updates/10/i386/

and install them manually. Then things should work.

Step 2 (easier way):
yum install akmod-rt2860
Reboot
Done!

akmods carry the source code for your module. Whenever you boot your computer, the akmod software will check if the modules are built for the kernel that you are booting to. If they are not present (i.e. if that is a new kernel), it will build and install your rt2860 kmods for you automatically.

This way you never have to worry about this problem anymore.

Come back and tell me about your victory :)

I have done step 2 but the wireless card still does not show in knetwork manager, any ideas?

[ogetbilo]

Jon, give me the outputs of
rpm -qa |grep kernel
rpm -qa |grep 2860
uname -r
lsmod |grep 2860
lspci |grep 2860

[Jon Briggs]

Here is the output of those commands:-

[root@EPCPRTBL sam]# rpm -qa | grep kernel
kernel-headers-2.6.27.21-170.2.56.fc10.i386
kernel-devel-2.6.27.21-170.2.56.fc10.i686
kernel-firmware-2.6.27.5-117.fc10.noarch
kerneloops-0.12-1.fc10.i386
kernel-2.6.27.5-117.fc10.i686
[root@EPCPRTBL sam]# rpm -qa | grep 2860
rt2860-1.8.0.0-2.fc10.noarch
akmod-rt2860-1.8.0.0-3.fc10.i686
[root@EPCPRTBL sam]# uname -r
2.6.27.5-117.fc10.i686
[root@EPCPRTBL sam]# lsmod | grep 2860
[root@EPCPRTBL sam]# lspci | grep 2860

So what do you think ?

[ogetbilo]

Your kernel and kernel-devel packages have different versions. Therefore the akmod cannot find the correct header files for the kernel that you are running.

So either upgrade the kernel, or downgrade kernel-devel so that their versions are equal.

[Jon Briggs]

I ran:-

yum upgrade kernel

And it upgraded to the same kernel as my kernel-devel. On reboot it showed 2 different kernels in grub so i chose the later one i uypgraded too, it took a while to boot and when it did my wireless stil wasn't in knetwork manager and if i run:-

rpm -qa | grep kernel

It lists two kernels the correct one i upgraded too and the old one as well.

What do i ned to do? Thanks for the help btw.

EDIT: ahh i rebooted again and the wireless is there! thanks! Altho how do i change grub so it only lists the correct kernel?

[ogetbilo]

It doesn't hurt to keep an old version of a kernel in case something goes wrong with the new one. Afaik, Fedora keeps two versions of kernel install by default. So, whenever there is a new kernel update, your older kernel will get uninstalled by yum.

If you are impatient, you can uninstall it using
rpm -e kernel-<oldversion> kernel-devel-<oldversion>
But as I said, you really don't need to do this.

[Jon Briggs]

yeah i guess i can live with it. I know its cheeky but could you point me ibn the right forection for getting bluetooth working?

Thanks for all the help btw.

[ogetbilo]

Wrong person to ask. Sorry, I have zero experience with bluetooth.

[IrishBouzouki]

I think multiple people sent emails. We even invited them to rpmfusion bugzilla, where we have extensive reports from different people.

I built the new kmods last Sunday. They are in the testing repo now.

Are the new ralink drivers pushed out of testing yet?
How can I verify that I have RPMFusion as an automatic update source (so it will show up in the update system GUI like the other stuff)? I followed the steps here but want to ascertain it 'took' correctly.

Many, many thanks especially if your new build and the new Ralink drivers solves the WPA2/AES issues.

[chipmunk]

Hi

I have read this thread through several times. I'm a noob to Linux but so tired of Vista that I want to scream.

I have a HP Pavilion Desktop PC that has a Ralink RT2860 wireless card. After tons of frustration with Ubuntu 9.04 I decided to install Fedora. So far I like it a lot better, but I can't get online wirelessly :(

My wifi connection is WPA2 protected. I followed the instructions at the beginning of the thread and installed rpmfusion, so now I can see my wireless card and my home network... Yay for the noob.

When I try to connect, it asks me for my password which i enter, but then the status on the top right goes round and round like it's trying to connect, then pops up and asks me for the passphrase again. when I click the "show password" box, my password shows up not as I entered it but as a bunch of numbers.

I can connect fine using a wired connection and have installed all updates. What do I need to do to make my wireless connection work?

Thanks for all your help! The community is awesome.!

[SgtBower]

When I try to connect, it asks me for my password which i enter, but then the status on the top right goes round and round like it's trying to connect, then pops up and asks me for the passphrase again. when I click the "show password" box, my password shows up not as I entered it but as a bunch of numbers.



This is normal behavior. Your password is being converted into hexadecimal and is being shown to you as the router sees it.

I'm not an old hand at this, but I went through almost the exact same thing trying to get my 2860 working.

First off, turn off the encryption on your router and try to join it. Once you get a connection, then start worrying about the security settings.

If I remember right, the Ralink implimentation has some problems with WPA Enterprise keys. You might try checking the wireless settings in the router to make sure you're on WPA Personal (1 or 2).

It seems like I remember something about AES or TKIP encryption being problematic too. You might just try playing with those two settings.

Ogetbilo can probably give you a bit of further guidance.

[chipmunk]

SgtBower,

Thanks for the reply. I'm pretty sure I have WPA2 Personal, since I'm the one who set up the router. Unfortunately disabling the encryption is not an option for me. How would I play around with the AES and TKIP encryption in my Fedora admin, I don't see those options anywhere.

thanks again

[SgtBower]

You have to crawl before you can walk. Testing without the encryption would only expose you for a minute or two if you were slow. If it makes you nervous, unplug your other computers while you do it.

TKIP and AES are selected in the wireless networking section of the router. The same place where you configure your Encryption.

[ogetbilo]

Are the new ralink drivers pushed out of testing yet?
How can I verify that I have RPMFusion as an automatic update source (so it will show up in the update system GUI like the other stuff)? I followed the steps here but want to ascertain it 'took' correctly.

Many, many thanks especially if your new build and the new Ralink drivers solves the WPA2/AES issues.


EDIT (May 14th): Uh oh, it looks like the kmod updates are waiting for kernel-2.6.29 to go to stable. Well, you can try akmods instead via
rt2860 users:
yum --enablerepo rpmfusion-free-updates-testing install akmod-rt2860
rt2870 users:
yum --enablerepo rpmfusion-free-updates-testing install akmod-rt2870

Afterwards, just reboot your computer and your kmod will be built and installed and loaded for you automatically.

[chipmunk]

You have to crawl before you can walk. Testing without the encryption would only expose you for a minute or two if you were slow. If it makes you nervous, unplug your other computers while you do it.

TKIP and AES are selected in the wireless networking section of the router. The same place where you configure your Encryption.

Thanks again. It's not a matter of being nervous, it's that I can't disable it. I set it up but don't have the control now to disable it, not easily anyway. It's a matter of access.

I set it at TKIP when I configured the router.

I need to figure out how to make the wireless work on my Fedora system without first disabling the WPA encryption. I hope it's possible somehow because I can't stay on the wired connection, I need to be wireless :(

[IrishBouzouki]

Thanks again. It's not a matter of being nervous, it's that I can't disable it. I set it up but don't have the control now to disable it, not easily anyway. It's a matter of access.

I set it at TKIP when I configured the router.

I need to figure out how to make the wireless work on my Fedora system without first disabling the WPA encryption. I hope it's possible somehow because I can't stay on the wired connection, I need to be wireless :(

I am in the same boat, although I am able to disable my wireless security to verify the drivers function without it (and have).

I am not 100% sure, but I believe that the Ralink drivers currently in the kmods described in this thread still have an issue with WPA or WPA2, even Personal. I get the same behaviour with repeated password requests and no login - until I disable all the network security (I believe you can also just set your router for WEP and then, after that or it will not let you, set your network manager connection to WEP - the problem has been stated to be specific to WPA/WPA2).

The good news is there are rumblings that the new version of the Ralink drivers which was released in April has corrected this problem, at least one person has reported success on WPA using the new ones. So when they get out of testing in the RPMFusion repo (see posts above - kmods waiting for kernel version) there is hope that WPA will work.

That is, if I understand everything correctly, probably should not be answering something that I really know nothing about so take with a grain of salt so to speak...

[chipmunk]

I am in the same boat, although I am able to disable my wireless security to verify the drivers function without it (and have).

I am not 100% sure, but I believe that the Ralink drivers currently in the kmods described in this thread still have an issue with WPA or WPA2, even Personal. I get the same behaviour with repeated password requests and no login - until I disable all the network security (I believe you can also just set your router for WEP and then, after that or it will not let you, set your network manager connection to WEP - the problem has been stated to be specific to WPA/WPA2).

The good news is there are rumblings that the new version of the Ralink drivers which was released in April has corrected this problem, at least one person has reported success on WPA using the new ones. So when they get out of testing in the RPMFusion repo (see posts above - kmods waiting for kernel version) there is hope that WPA will work.

That is, if I understand everything correctly, probably should not be answering something that I really know nothing about so take with a grain of salt so to speak...


Thanks for the info, I guess I'll wait for the new drivers then. Definitely can't switch any encryption settings on the router now, so I'll just have to wait. It definitely seems then that it's an issue with Ralink cards with WPA encryption. If anyone has had any success I would love to know how.

Will keep an eye on this thread and post if anything changes on my end.

Thanks all for your help

[SgtBower]

I use WPA2 with AES with no problems. WPA was problematic originally, but the latest few driver and Network Manager releases seem to have fixed the problems.

[ogetbilo]

Uhm, I explained in post #70 how to install the driver from testing. It is the same driver that is going to be pushed to stable if no one reports bugs.

Putting the packages to testing will not magically make them bugfree. I mean, the whole point of testing is for folks to test the drivers and report problems.

Especially for the rt2860 driver, since I (as the rpm maintainer) do not own the hardware, just waiting for the driver to get pushed to stable is not much helpful for locating possible problems.

[chipmunk]

Uhm, I explained in post #70 how to install the driver from testing. It is the same driver that is going to be pushed to stable if no one reports bugs.

Putting the packages to testing will not magically make them bugfree. I mean, the whole point of testing is for folks to test the drivers and report problems.

Especially for the rt2860 driver, since I (as the rpm maintainer) do not own the hardware, just waiting for the driver to get pushed to stable is not much helpful for locating possible problems.


I actually tried to install those drivers from testing as instructed in your post but with no success, they could not be found. I kept running into errors of no package found. I'm not at that computer now but in the morning I will retry and post the errors I get here. My apologies for not posting the error before, I saw you had edited your post and assumed that's why I was getting the error. I'm new to this whole Linux thing and trying to learn, so I'll try to be more precise in future :(

[ogetbilo]

I actually tried to install those drivers from testing as instructed in your post but with no success, they could not be found. I kept running into errors of no package found. I'm not at that computer now but in the morning I will retry and post the errors I get here. My apologies for not posting the error before, I saw you had edited your post and assumed that's why I was getting the error. I'm new to this whole Linux thing and trying to learn, so I'll try to be more precise in future :(

Sorry, if you don't have the akmod installed already, "yum update" won't work. Instead one has to use "yum install". I re-edited post#70 accordingly. Please retry. :)

[chipmunk]

Sorry, if you don't have the akmod installed already, "yum update" won't work. Instead one has to use "yum install". I re-edited post#70 accordingly. Please retry. :)

Ah, I see. I will retry tomorrow and post my results. Thank you much for your assistance :)

[IrishBouzouki]

Uhm, I explained in post #70 how to install the driver from testing. It is the same driver that is going to be pushed to stable if no one reports bugs. Putting the packages to testing will not magically make them bugfree. I mean, the whole point of testing is for folks to test the drivers and report problems. ... just waiting for the driver to get pushed to stable is not much helpful for locating possible problems.


EDIT (May 14th): Uh oh, it looks like the kmod updates are waiting for kernel-2.6.29 to go to stable. Well, you can try akmods instead via
rt2860 users:
yum --enablerepo rpmfusion-free-updates-testing install akmod-rt2860
rt2870 users:
yum --enablerepo rpmfusion-free-updates-testing install akmod-rt2870
Afterwards, just reboot your computer and your kmod will be built and installed and loaded for you automatically.

Well, I tried, here is what I get, what do I need to do about it...

(my common files are 2.1.0.0.-1 and my other two kmod files - tracking metapackage and kernel module itself - are 2.1.0.0-2)

yum --enablerepo rpmfusion-free-updates-testing install akmod-rt2870
Loaded plugins: refresh-packagekit
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package akmod-rt2870.x86_64 0:2.1.1.0-1.fc10 set to be updated
--> Processing Dependency: rt2870-kmod-common >= 2.1.1.0 for package: akmod-rt2870
--> Processing Dependency: akmods for package: akmod-rt2870
--> Processing Dependency: kmodtool for package: akmod-rt2870
--> Running transaction check
---> Package akmod-rt2870.x86_64 0:2.1.1.0-1.fc10 set to be updated
--> Processing Dependency: rt2870-kmod-common >= 2.1.1.0 for package: akmod-rt2870
---> Package akmods.noarch 0:0.3.3-2.fc10 set to be updated
---> Package kmodtool.noarch 0:1-15.fc10 set to be updated
--> Finished Dependency Resolution
akmod-rt2870-2.1.1.0-1.fc10.x86_64 from rpmfusion-free-updates-testing has depsolving problems
--> Missing Dependency: rt2870-kmod-common >= 2.1.1.0 is needed by package akmod-rt2870-2.1.1.0-1.fc10.x86_64 (rpmfusion-free-updates-testing)
Error: Missing Dependency: rt2870-kmod-common >= 2.1.1.0 is needed by package akmod-rt2870-2.1.1.0-1.fc10.x86_64 (rpmfusion-free-updates-testing)

yum --enablerepo rpmfusion-free-updates-testing update rt2870-kmod-common
Loaded plugins: refresh-packagekit
Setting up Update Process
No Packages marked for Update

I have a Linksys WUSB600N (rt2870) on a WPA2-Personal/AES WiFi-N dual-band network. Happy to help test as soon as I can get some help overcoming the above issue(s).

I use WPA2 with AES with no problems. WPA was problematic originally, but the latest few driver and Network Manager releases seem to have fixed the problems.

I will add that I am fully updated to the Network Manager version in the main Fedora repos, and to the version in the main (non-testing) RPMFusion repos, and have the described problem... NetMan continually asks for the passphrase and fails to log on. I also have a Fedora laptop with an integrated bc43 card which can log on to the network with no trouble so I know I have the network setup okay just an issue with the rt2870 stuff, at least the version currently on my machine.

NetworkManager Applet 0.7.1

[john-murphy@localhost ~]$ rpm -qa |grep kernel
kernel-2.6.27.21-170.2.56.fc10.x86_64
kernel-devel-2.6.27.15-170.2.24.fc10.x86_64
kernel-devel-2.6.27.21-170.2.56.fc10.x86_64
kernel-devel-2.6.27.19-170.2.35.fc10.x86_64
kernel-headers-2.6.27.21-170.2.56.fc10.x86_64
kernel-2.6.27.19-170.2.35.fc10.x86_64
kernel-2.6.27.15-170.2.24.fc10.x86_64
kernel-firmware-2.6.27.21-170.2.56.fc10.noarch
kerneloops-0.12-2.fc10.x86_64
[john-murphy@localhost ~]$ rpm -qa |grep 2870
kmod-rt2870-2.1.0.0-2.fc10.x86_64
rt2870-2.1.0.0-1.fc10.noarch
kmod-rt2870-2.6.27.21-170.2.56.fc10.x86_64-2.1.0.0-2.fc10.x86_64
[john-murphy@localhost ~]$ uname -r
2.6.27.21-170.2.56.fc10.x86_64
[john-murphy@localhost ~]$ lsmod |grep 2870
rt2870sta 473800 1
[john-murphy@localhost ~]$ lspci |grep 2870
[john-murphy@localhost ~]$ lsusb |grep 2870

[ogetbilo]

IrishBouzouki,
Thanks for reporting this. It looks like the common package for rt2870 is missing from the repos. It is there for rt2860. I don't know how that happened. I just (re)built it now. It needs to be signed and pushed to mirrors (to testing repo). This process usually takes 1-2 days. I will let you know when they are ready.

EDIT: Okay, it is signed and pushed to the main repo. Please allow a couple hours for the mirrors to repopulate and try again. Thanks again for reporting this. Otherwise, we were going to have a broken rt2870 driver when F-11 is final.

[IrishBouzouki]

Okay it was there and I completed the installation...
[root@localhost ~]# yum --enablerepo rpmfusion-free-updates-testing install akmod-rt2870
Loaded plugins: refresh-packagekit
rpmfusion-free-updates-testing | 2.8 kB 00:00
rpmfusion-free-updates-testing/primary_db | 49 kB 00:00
rpmfusion-nonfree-updates | 2.8 kB 00:00
fedora | 2.8 kB 00:00
rpmfusion-free-updates | 2.8 kB 00:00
rpmfusion-free | 2.7 kB 00:00
rpmfusion-nonfree | 2.7 kB 00:00
updates | 3.0 kB 00:00
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package akmod-rt2870.x86_64 0:2.1.1.0-1.fc10 set to be updated
--> Processing Dependency: rt2870-kmod-common >= 2.1.1.0 for package: akmod-rt2870
--> Processing Dependency: akmods for package: akmod-rt2870
--> Processing Dependency: kmodtool for package: akmod-rt2870
--> Running transaction check
---> Package akmods.noarch 0:0.3.3-2.fc10 set to be updated
---> Package kmodtool.noarch 0:1-15.fc10 set to be updated
---> Package rt2870.noarch 0:2.1.1.0-1.fc10 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================== ==============================
Package Arch Version Repository Size
================================================== ==============================
Installing:
akmod-rt2870 x86_64 2.1.1.0-1.fc10 rpmfusion-free-updates-testing 660 k
Installing for dependencies:
akmods noarch 0.3.3-2.fc10 rpmfusion-free 14 k
kmodtool noarch 1-15.fc10 rpmfusion-free-updates 11 k
Updating for dependencies:
rt2870 noarch 2.1.1.0-1.fc10 rpmfusion-free-updates-testing 16 k

Transaction Summary
================================================== ==============================
Install 3 Package(s)
Update 1 Package(s)
Remove 0 Package(s)

Total download size: 702 k
Is this ok [y/N]: y
Downloading Packages:
(1/4): kmodtool-1-15.fc10.noarch.rpm | 11 kB 00:00
(2/4): akmods-0.3.3-2.fc10.noarch.rpm | 14 kB 00:00
(3/4): rt2870-2.1.1.0-1.fc10.noarch.rpm | 16 kB 00:00
(4/4): akmod-rt2870-2.1.1.0-1.fc10.x86_64.rpm | 660 kB 00:07
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 84 kB/s | 702 kB 00:08
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : kmodtool 1/5
Installing : akmods 2/5
Installing : akmod-rt2870 3/5
Updating : rt2870 4/5
Cleanup : rt2870 5/5

Installed:
akmod-rt2870.x86_64 0:2.1.1.0-1.fc10

Dependency Installed:
akmods.noarch 0:0.3.3-2.fc10 kmodtool.noarch 0:1-15.fc10

Dependency Updated:
rt2870.noarch 0:2.1.1.0-1.fc10

Complete!

Then I rebooted my machine (it took a veeeeery long time coming up), and the ralink device failed to connect to the WiFi network, asking me for the passphrase, which I entered, and this was repeated two more times before I gave up.
Now... I had originally installed the non-testing kmods and I expect they may still be there. Could this be conflicting with the testing akmods?
Also, I do have my wired connection hooked up at the same time. It seems unlikely, but could there be an issue with this in Network Manager somehow causing a conflict?

Most important though, what debugging information can I provide to help solve this, and get my wireless connection running on my desktop machine?

Here is, I think (not sure), the tail end of dmesg output on boot...
-->RTUSBVenderReset
<--RTUSBVenderReset
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
1. Phy Mode = 5
2. Phy Mode = 5
3. Phy Mode = 5
MCS Set = ff ff 00 00 01
<==== rt28xx_init, Status=0
0x1300 = 00064300
mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining
sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 389
ra0: no IPv6 routers present
fuse init (API version 7.9)
SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 389
==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1)
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 389
Terminate the task(RtmpMlmeTask) with pid(2991)!
Terminate the task(RtmpCmdQTask) with pid(2992)!
Terminate the task(RtmpTimerTask) with pid(2990)!
---> RTMPFreeTxRxRingMemory
<--- RTMPFreeTxRxRingMemory
usbcore: deregistering interface driver rt2870
rtusb_disconnect: unregister usbnet usb-0000:00:1d.7-1
RtmpOSNetDevDetach(): RtmpOSNetDeviceDetach(), dev->name=ra0!
RTUSB disconnect successfully
<--- rtusb exit
rtusb init --->

And here (pretty sure, not 100%) is what was added to dmesg by rmmod and modprobe...
<-- RTMPAllocAdapterBlock, Status=0
usbcore: registered new interface driver rt2870
<-- RTMPAllocTxRxRingMemory, Status=0
-->RTUSBVenderReset
<--RTUSBVenderReset
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
1. Phy Mode = 5
2. Phy Mode = 5
3. Phy Mode = 5
MCS Set = ff ff 00 00 01
<==== rt28xx_init, Status=0
0x1300 = 00064300

[IrishBouzouki]

Hot dang it works!

I am not sure exactly what...

1. I performed the edits of the RT2870STA file as described in the archlinux link you provided. I kind of doubt that actually did anything however. But best to mention it.
2. I deleted my Natwork Manager wireless connection from before applying the akmods, and created a brand new one (with the same settings mind you).

Doing it in this order, when I re-enabled my wireless I got the 2nd green light on Net-Man almost immediately and knew from there it would work. Sure enough, and no conflict with the hardline running at the same time near as I can tell.

This is with Wireless N, WPA2 Personal, AES.

I would still be happy to include any info you like.

Here is what I think is the tail end of dmesg with it working?...
<-- RTMPAllocAdapterBlock, Status=0
usbcore: registered new interface driver rt2870
<-- RTMPAllocTxRxRingMemory, Status=0
-->RTUSBVenderReset
<--RTUSBVenderReset
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
1. Phy Mode = 5
2. Phy Mode = 5
3. Phy Mode = 5
MCS Set = ff ff 00 00 01
<==== rt28xx_init, Status=0
0x1300 = 00064300
ra0: no IPv6 routers present
Bulk In Failed. Status=-71, BIIdx=0x6, BIRIdx=0x6, actual_length= 0x0
===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 389
===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 389
==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1)
===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 192
==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1)
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 192
===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 192
Bulk In Failed. Status=-71, BIIdx=0x6, BIRIdx=0x6, actual_length= 0x0
===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 192
===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 192
sky2 eth0: Link is down.
===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 192

[IrishBouzouki]

Now that I have this working, I imagine I want to uninstall the non-functioning kmod non-testing version? Or is that essentially already done by having the more recent akmods? How can I tell?

If I wait for the new kernel push (which is maybe with F11?) and the new kmod version hits out of the repos what will happen with both installed at that time?

(I imagine I want eventually to drop the testing repo and go with the stable repo versions)

[ogetbilo]

I'm glad it is now working for you. I guess that kernel-2.6.29 for F-10 will be pushed around at the same time F-11 is released.
During your bootup, the akmod software compiled (built) and installed the kmod for your kernel version. It might have removed the previous kmods. Even if it does not, the previous kmods shouldn't cause harm. It's up to you if you want to uninstall them. They don't occupy much space.

You can opt to go with akmod for future kernel and Fedora releases. The only difference will be, when you are booting into a new kernel, the kmod will be rebuilt and you will have to wait a little. But it will happen only once per kernel upgrade. The kmods, on the other hand, are prebuilt, so there won't be any lag with them during booting. Their disadvantage is, sometimes when a new kernel is pushed to Fedora, the respective kmods are not pushed simultaneously to rpmfusion repos. We are doing our best to make the gap as small as pooible, but with the framework we have, the kmod upgrade mechanism cannot be made perfect. Our kmod folks are in touch with mirror management folks to produce a better solution for synchronization. I hope that we can get this straightened soon.

[dacia]

Hi there

I installed FC10 on my eeepc 1000 because I want to get rid of recompiling the rt2860 driver each kernel update.

What I have now, is worse then before:
When the machine wakes up after suspend mode, the rt2860 driver failed:
May 16 17:50:54 media kernel: !!! RT2860 Initialized fail !!!
May 16 17:50:54 media kernel: RX DESC f5e81000 size = 2048
May 16 17:50:54 media kernel: <-- RTMPAllocTxRxRingMemory, Status=0
May 16 17:50:54 media kernel: ERROR!!! BBP read R0=0xffffffff fail

I tried Ralinks driver and the rpmfusion module.
With Ralinks 1.8.xx and 2.1.xx driver it will not work at all.
With rpmfusion modules it will work some time, then the machine crashes.

To see if this is a driver/suspend problem, I removed the driver before suspend mode (rmmod) and tired to insert it aferward (modprobe), but got the same result.


Any idea ?


lspci

01:00.0 Network controller: RaLink RT2860
Subsystem: RaLink Device 2790
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 19
Region 0: [virtual] Memory at fbef0000 (32-bit, non-prefetchable) [disabled] [size=64K]


uname -a

Linux this.is.a.computer 2.6.27.21-170.2.56.fc10.i686 #1 SMP Mon Mar 23 23:37:54 EDT 2009 i686 i686 i386 GNU/Linux



rpm -qa | grep 2860
kmod-rt2860-1.8.0.0-3.fc10.5.i686
rt2860-1.8.0.0-2.fc10.noarch
kmod-rt2860-2.6.27.21-170.2.56.fc10.i686-1.8.0.0-3.fc10.5.i686

[ogetbilo]

Did you try playing with the sample suspend.sh script we put in the rt2860-<version>.fc10.noarch.rpm?

I heard that this script may not be necessary on kernel 2.6.29 and after. I don't know much about this subject since suspend never works for me in Fedora anyway (with or without wireless).

[krutoileshii]

Ok, after installing the F11 preview couldn't get the driver (v 2.xxx from ralink to connect to WPA or WPA2) so i got a copy of the RT2860STA.dat file form the previous version(1.8) and replaced the one from the 2xx version. restarted the module and everything works like a charm.

[ogetbilo]

If you have time, could you figure out what option that is missing in 2.xx RT2860STA.dat but is present in 1.8 RT2860STA.dat made the driver work?

Then we can write a patch and send it to ralink so that it gets fixed by their next release.

[TomasPT]

very good boys.

its working fine.

ogetbilo thank you very much. very nice job indeed

[johnv2]

I tried installing the drivers downloaded from ralinktech.com manually but ran into a problem when I couldn't ping anything (including the wireless AP) after connecting to the wireless network via DHCP.

So, I thought I must have done something wrong and then tried using the rpmfusion rpm's but ran into the same problem. I can connect to the network via DHCP, however I'm unable to ping my default gw (192.168.1.1).

Everything looks in order. Module is loaded, I get my IP, DNS servers, etc. I disabled iptables so that couldn't be the culprit, however I still get nothing.

Using tcpdump I can see the icmp echo requests to the wireless AP and UDP requests to DNS servers, but nothing is replying.

My wireless card is an airlink-awll6070 and the wireless AP is a linksys wrt300n. Any help or suggestions would be appreciated!

[ogetbilo]

I tried installing the drivers downloaded from ralinktech.com manually but ran into a problem when I couldn't ping anything (including the wireless AP) after connecting to the wireless network via DHCP.

So, I thought I must have done something wrong and then tried using the rpmfusion rpm's but ran into the same problem. I can connect to the network via DHCP, however I'm unable to ping my default gw (192.168.1.1).

Everything looks in order. Module is loaded, I get my IP, DNS servers, etc. I disabled iptables so that couldn't be the culprit, however I still get nothing.

Using tcpdump I can see the icmp echo requests to the wireless AP and UDP requests to DNS servers, but nothing is replying.

My wireless card is an airlink-awll6070 and the wireless AP is a linksys wrt300n. Any help or suggestions would be appreciated!

This looks like a configuration issue, rather than a driver issue. What IP address does the router give you? Can you ping the same router via ethernet?

[alexiy]

Hi,

I have compiled the rt2870 driver from ralink site. Networkmanager works just fine even with WPA2.

[royor]

bricktop41,

After enabling the RPMFusion free repository, doing a
yum install rt2860
as root will make your wireless card work.

Details are given in the first post of this thread. Let me know if there's anything you don't understand.


Hello,
I have installed all the releveant rt2860 rpms from rpmfusion
on FC11 (or F11, as many prefer to call it).

wpa_supplicant is unable to associate with the AP.

I am using the same files:

/etc/wpa_supplicant/wpa_supplicant.conf
/etc/sysconfig/wpa_supplicant

as I had in fc7, which was working just fine using
the rt2860 driver I had downloaded directly from
the ralinktech.com web site.

So, I thought I would try to do the same with F11.

In order to load the driver I build from the ralink web site,
I had to first boot into single user mode, and take these steps:
1. rmmod rt2860sta
2. cd'd to the dir path /lib/mpdules/......./extras/rt2860
3. mv rt2860sta.ko rt2860sta.ko.sav
4. cp /lib/modules/......wireless/rt2860sta.ko /lib/mpdules/......./extras/rt2860
5. init 5

So, to make a long story short, the driver loaded, no problems there. But still wpa_supplicant is unable to associate with my AP.

It is not clear what is causing the problem. Is it wpa_supplicant itself? Is it the driver?
If it is the driver why does it work in fc7 ???

Hope someone can help!!!

Best regards,

Royor

[royor]

UPDATE (Oct 22nd, 2008): Well, we got some positive feedback and released the new drivers at rpmfusion. So this post does not mean much anymore.

Hello everyone. Do you want to help rpmfusion?
Ralink released a new rt2860 driver on their webpage and we need testers for it.
We -at rpmfusion- don't own any hardware with this chipset hence we cannot test it ourselves. If these RPM's work (or don't work) please let me know. It will be greatly appreciated, not only by us but also by other rt2860 users.
Step 0:
Please uninstall/remove the rt2860 drivers you have (if you have any). To check if you have any drivers installed in the kernel-modules tree of the kernel that you are currently using, do a

du -a /lib/modules/`uname -r`|grep 2860

If nothing comes up, you are good :)

Step 1a:
The rt2860 driver RPM's for 2.6.26.5-45.fc9.i686 and 2.6.26.5-45.fc9.x86_64 kernels can be found at
http://oget.fedorapeople.org/rt2860/

You will need 3 RPMs:
kmod-rt2860-1.8.0.0-0.fc9.<your_arch>.rpm
kmod-rt2860-2.6.26.5-45.fc9.<your_arch>-1.8.0.0-0.fc9.<your_arch>.rpm
rt2860-1.8.0.0-0.fc9.noarch.rpm
where <your_arch> is either i686/x86_64.

(Step 1b:
If you don't have a i686 or a x86_64 computer; or if you don't have the 2.6.26.5-45 kernel installed you can build your own RPM's from the 2 SRPM's on the same page: http://oget.fedorapeople.org/rt2860/

To build your RPM's you have to use

rpmbuild --rebuild rt2860*.src.rpm --define "kernels $(uname -r)" --target $(uname -m)


rt2860-1.8.0.0-0.fc9.src.rpm will produce 1 no arch RPM
rt2860-kmod-1.8.0.0-0.fc9.src.rpm will produce 1 arch-specific RPM. )


Step 2:
Please install the all the RPM's you have (or created) simultaneously (with "rpm -ivh --nodeps") and test out the driver.

After installing the RPM's you can plugin your card. If you see lights going on on your card that probably means it works. You can also check (as root)

lsmod |grep 2860

to see whether the module (most likely: rt2860sta) is loaded or not.
----


If you don't know and don't want to know how to build your own RPM's you can send a message to me with your kernel version and architecture so I can build the specific RPM's for you.

Thank you!


I downloaded and installed the rpms you list from rpmfusion
into my F11 installation.
I rebooted
lsmod | grep rt2860 shows the driver to be loaded just fine

But wpa_supplicant is NOT able to associate with the AP.

Before migrating to F11, i was on F7, where I had compiled
and used the driver I had downloaded directly from ralinktech.com. There, all worked well. I was able to
associate with the AP and get on the net.

In F11, I brought in the same

/etc/wpa_supplicant/wpa_supplicant.conf and
/etc/sysconfig/wpa_supplicant

which I had used in FC7.

I rebooted.

Still wpa_supplicant is unable to associate!!!

Someone please tell me HOW can I get past this point I am stuck in???

Cheers,

Royor.

[phil_hays]

AKA: WUSB54G version 3


I've tried several different methods of getting this wireless USB adapter to work:

ndiswrapper (which gives an error message about a missing symbol MmGetSystemRoutineAddress)

I followed the suggestions in topic. Result, not recognized.

Downloaded the source from ralink (2009_0521_RT2870_Linux_STA_V2.1.2.0.tgz), and modified the source to add in this device (os/linux/usb_main_dev.c, add line

{USB_DEVICE(0x1737,0x0077)}, /* Linksys WUSB54GC-CA */

Now the device powers up, and I get a flashing green light, and this in dmesg

rtusb init --->


=== pAd = f8f01000, size = 470408 ===

<-- RTMPAllocAdapterBlock, Status=0
usbcore: registered new interface driver rt2870
<-- RTMPAllocTxRxRingMemory, Status=0
-->RTUSBVenderReset
<--RTUSBVenderReset
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
1. Phy Mode = 5
2. Phy Mode = 5
RTMPSetPhyMode: channel is out of range, use first channel=1
3. Phy Mode = 9
MCS Set = ff 00 00 00 01
<==== rt28xx_init, Status=0
0x1300 = 00064300


I can see ra0 in System>administration=>network

The status in "Inactive".

ra0 knows of no access points (I have security off on the access point, and I'm in an apartment building).


I'm a newbie at drivers.


Any suggestions?
Phil Hays

[a53r]

AKA: WUSB54G version 3


I've tried several different methods of getting this wireless USB adapter to work:

ndiswrapper (which gives an error message about a missing symbol MmGetSystemRoutineAddress)

I followed the suggestions in topic. Result, not recognized.

Downloaded the source from ralink (2009_0521_RT2870_Linux_STA_V2.1.2.0.tgz), and modified the source to add in this device (os/linux/usb_main_dev.c, add line

{USB_DEVICE(0x1737,0x0077)}, /* Linksys WUSB54GC-CA */

Now the device powers up, and I get a flashing green light, and this in dmesg


I can see ra0 in System>administration=>network

The status in "Inactive".

ra0 knows of no access points (I have security off on the access point, and I'm in an apartment building).


I'm a newbie at drivers.


Any suggestions?
Phil Hays

Phil,

I think, I can help you.
I have the Hawking wireless Dish adapter (HWDN2) and I observed the similar problem.

Repeat the same steps that you have done and additionally change the following two lines in the os/linux/config.mk file from:

# Support Wpa_Supplicant
HAS_WPA_SUPPLICANT=n
# Support Native WpaSupplicant for Network Maganger
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n

to

# Support Wpa_Supplicant
HAS_WPA_SUPPLICANT=y
# Support Native WpaSupplicant for Network Maganger
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y

I hope it will help.
Let me know the result by posting on this forum; I am curious.

[phil_hays]

Thanks for the suggestion, but these were already was set to y, y.

http://forums.fedoraforum.org//forum/images/smilies/frown.gif


#ifdef WPA_SUPPLICANT_SUPPORT
# Support Wpa_Supplicant
HAS_WPA_SUPPLICANT=y
#endif // WPA_SUPPLICANT_SUPPORT //

#ifdef NATIVE_WPA_SUPPLICANT_SUPPORT
# Support Native WpaSupplicant for Network Maganger
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
#endif // NATIVE_WPA_SUPPLICANT_SUPPORT //

[ogetbilo]

Folks, if you install the rt2860/rt2870/rt3070 rpm from rpmfusion, then boot your computer with the device plugged in and see that the module has been loaded, then my job as the packager is done. The rest in about your own custom configuration.

There are many ways of handling the configuration. For NetworkManager, there are tons of documentation out there. There is also the configuration file

/etc/Wireless/RT2870STA/RT2870STA.dat etc.

that you can use to configure your connection. I doubt that I can help more than this.

phil_hays, let me know if you manage to get things working with your device. I can add the vendor/device ID (0x1737,0x0077) to the rpmfusion's RPM file so people with your hardware don't have to compile things manually.

edit: phil_hays, could it be that your card is actually an rt3070, but not rt2870?

[phil_hays]

phil_hays, let me know if you manage to get things working with your device. I can add the vendor/device ID (0x1737,0x0077) to the rpmfusion's RPM file so people with your hardware don't have to compile things manually.


I'll be happy to let you know, but right now I'm stuck. I'll be happy to try modifying the code in the RPMs if it is different than the code on the manufacturer's website. I'm not used to using RPMs. I assume I can extract a source RPM to a directory, edit files as needed, and then repack to a RPM, however I don't have any idea exactly what commands and options are needed to do this, especially the repacking into a RPM .

rpm2cpio and cpio do the unpacking (I think), the source code modification isn't hard, but how do I pack stuff into a RPM correctly?



edit: phil_hays, could it be that your card is actually an rt3070, but not rt2870?


CD that came with card has:



rt2870.inf
rt2870.sys



Which might not support only the obvious chip. Is there a script for identifying the chip? Or should I just try the driver for the 3070?


Phil

[ogetbilo]

You want to setup an rpm environment. Don't do these things as root. There are bunch of RPM howtos you can refer to. For instance I found
http://www.g-loaded.eu/2006/04/05/how-to-build-rpm-packages-on-fedora/

This one is written for FC-5 but still looks valid to me. I'm sure there is a howto in this forum too.

After you setup your rpm environment you can populate it with any SRPM (src.rpm) file you find. You can download the rt2870-kmod SRPM and install it into your rpm environment via (not as root again!):

rpm -ivh rt2870-kmod*.src.rpm


Then you will see the source files and patches that I use for this RPM in ~/rpmbuild/SOURCE and the SPEC file will be in ~/rpmbuild/SPEC. You can produce RPMs from SPEC files with


rpmbuild -ba rt2870-kmod.spec



Do you know how to make patches?

Suppose you are in a directory which has only two subdirectories:
code.original
code.new
Then you can create a patch file with

diff -rupN code.original code.new > my_diff.patch


For instance, you can apply this patch into the code.original directory. Go into that directory and do

patch -p1 < ../my_diff.patch


Now the directories code.original and code.new will be identical.

You can use patches inside SPEC files!


As for the chipset: Those files don't tell much. The rt3070 driver code from ralink refers to rt3070 as rt2870. Confusing indeed. Do you have a manual that comes with technical specs?

I checked the rt3070 driver. That one doesn't have your vendor/device ID either. It has to be added by hand, or by a patch.

[demonon]

Hello,

I have a rt2870 chipset and am unable to install the drivers.
I get this error message:

[behzad@localhost ~]$ rpm -ivh *rt2870*.rpm
warning: kmod-rt2870-2.1.2.0-2.fc11.x86_64.rpm: Header V3 RSA/SHA256 signature:NOKEY, key ID 8fcff4da
error: Failed dependencies:
kernel-uname-r = 2.6.29.6-217.2.8.fc11.x86_64 is needed by kmod-rt2870-2.6.29.6-217.2.8.fc11.x86_64-2.1.2.0-2.fc11.x86_64

As you might have noticed I use Fedora 11 x64 version.
I just installed Fedora a few hours ago and I have not read through all pages of this thread yet.

I just downloaded the three files as stated in the first post and did rpm -ivh *rt2870*.rpm
I also cannot install the driver using the rt3070 driver.

I hope this problem can get solved soon!

Regards,

-demonon.

[hotdog]

Hi, looks like you've got a mismatch between the kmod and kernel versions. I take it you've doing this by method 2 in the first post?

I'd strongly recommend setting up the rpmfusion repository if you haven't already (useful for other things too) and installing the akmod (and its dependancies) using yum or PackageKit. That will automatically take care of things, all you need to do it 'yum install akmod-rt2870'.

[demonon]

This time I double checked the version and found out one file was wrong.
I tried the command again and this is what I got:

[behzad@localhost ~]$ rpm -ivh *rt2870*.rpm
warning: kmod-rt2870-2.1.2.0-2.fc11.x86_64.rpm: Header V3 RSA/SHA256 signature:NOKEY, key ID 8fcff4da
error: Failed dependencies:
kernel-uname-r = 2.6.29.6-217.2.8.fc11.x86_64 is needed by kmod-rt2870-2.6.29.6-217.2.8.fc11.x86_64-2.1.2.0-2.fc11.x86_64


BTW, I can't setup the repository because I cannot connect to the internet with that PC.
I could try moving the PC to my router so a Ethernet cable, but I rather not.

[hotdog]

OK, well the error message is still about the kernel version not matching the version the kmod rpm has been built for. Which kernel version are you actually running? ('uname -r' will tell you if you're not sure). You'll need to install the the kmod versions that match your current kernel, the ones you're trying to install are for kernel 2.6.29.6-217.2.8.fc11.x86_64.

Once you've got the right versions of the kernel packages and your internet connection up and running I'd still go ahead and setup rpmfusion and install the akmod, the akmod will then handle kernel/kmod version matching automatically for you from then on.

[demonon]

I am running kernel version 2.6.29.4-167.fc11.x86_64

The problem I am facing now is there are no rt2870 for my kernel.

BTW, I added you on MSN

[hotdog]

In that case you'll need to download a more up to date kernel rpm (ideally 2.6.29.6-217.2.8.fc11.x86_64 since you've already got the kmods for that) and manually install it first, before you install the rt2870 drivers.

Setting up a machine from a fresh install can be a pain if the official distribution is missing network drivers you need. This is one of the reasons I own a 10 metre ethernet cable so that following an new installation I can temporarily use a wired connection to my router until I have the wireless sorted out...

[demonon]

So there is no other option, is there?

[hotdog]

If hooking up a wired connection to your router (temporarily, to update the kernel at least, setup rpmfusion and install the akmod) is really inconvenient, then yes, the next simplest solution is the manual kernel update followed by the manual kmod installation.

It shouldn't be too big a deal, you've obviously already downloaded the rt2870 rpms and transferred them onto the target machine somehow, upgrading the kernel is just a case of downloading and transferring one more rpm, in this case from your local Fedora download mirror. Once you're got your internet connection running you'll want to install all the available updates anyway.

[demonon]

I think I just will make some time so I can temporary move my PC closer my router.

Thanks for all your help!

Regards,

-demonon.

[WillB]

I am about 2 steps shy of punching a baby seal.

I have the WUSB600N adapter, everything I have read says that I need the rt2870. I did the yum install with the repository included. Everything seemed fine, dependencies added and all.

Reboot, nothing new with wireless.

Read a bit more (tried above again for the hell of it) still no change.

System recognized it "automagically" as:
usb 1-3: new high speed USB device using ehci_hcd and address 2
usb 1-3: New USB device found, idVendor=1737, idProduct=0079
usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-3: Product: Linksys WUSB600N Wireless-N USB Network Adapter with Dual-Band ver. 2
usb 1-3: Manufacturer: Linksys
usb 1-3: configuration #1 chosen from 1 choice

Still nothing shown as a connectible option.

Working with Fedora 11
Kernel 2.6.30.8-64.fc11.i586


Save the seals, help me out. I know just enough about linux to nuke my own system.



EDITED

------------------------------------------------

Bueller?... Bueller?...

[ViperSBT]

Man, I was really hoping that I would be able to answer my question reading through this thread. Although I found lots of similarity I could not get any of the resolutions to cure my particular problem. I am sure I missed something. I am running a new install of Fedora 10 (MythDora) and am using a Ralink card based on the 2860 chipset. I originally tried compiling and getting the driver to work from scratch before I found the YUM resource that has been discussed here.

I currently get the card recognized and when I go to the Wireless Assistant in KDE it is showing me the available networks. My network is WPA-personal encrypted and I can not get it to connect with the passphrase. It tries for about 20 seconds and the says Connect Failed. I have tried turning off the security and get the same thing.

Here is the output of some of the various commands that I have seen requested to resolve this issue:
# lsmod | grep rt2860
rt2860sta 465592 1

# dmesg
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Intel ICH 0000:00:02.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
intel8x0_measure_ac97_clock: measured 50483 usecs
intel8x0: clocking to 48000
EXT3 FS on dm-0, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 2097144k swap on /dev/mapper/VolGroup00-LogVol02. Priority:-1 extents:1 across:2097144k
IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
firmware: requesting intel-ucode/0f-02-09
firmware: requesting intel-ucode/0f-02-09
microcode: CPU0 updated from revision 0x14 to 0x2e, date = 08112004
microcode: CPU1 updated from revision 0x14 to 0x2e, date = 08112004
p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available
ip6_tables: (C) 2000-2006 Netfilter Core Team
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RX DESC f600c000 size = 2048
<-- RTMPAllocTxRxRingMemory, Status=0
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
1. Phy Mode = 5
2. Phy Mode = 5
3. Phy Mode = 9
RTMPSetPhyMode: channel is out of range, use first channel=1
MCS Set = ff ff 00 00 01
<==== rt28xx_init, Status=0
0x1300 = 00064300
eth0: Media Link On 100mbps full-duplex
agpgart-sis 0000:00:00.0: AGP 3.5 bridge
agpgart-sis 0000:00:00.0: putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart-sis 0000:00:00.0: SiS delay workaround: giving bridge time to recover
agpgart-sis 0000:00:00.0: putting AGP V3 device at 0000:01:00.0 into 8x mode
[drm] Setting GART location based on new memory map
[drm] Loading R200 Microcode
[drm] writeback test succeeded in 1 usecs
audit(1254971142.643:20290): auid=4294967295 ses=4294967295 op=remove rule key=(null) list=2 res=1
audit(1254971142.643:20291): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1
fuse init (API version 7.9)
==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=6)
==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=6)

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0D:87:38:32:4C
inet addr:192.168.0.98 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:64338 errors:0 dropped:0 overruns:0 frame:0
TX packets:7826 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5341497 (5.0 MiB) TX bytes:869431 (849.0 KiB)
Interrupt:19 Base address:0xc400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:270 errors:0 dropped:0 overruns:0 frame:0
TX packets:270 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:14188 (13.8 KiB) TX bytes:14188 (13.8 KiB)

ra0 Link encap:Ethernet HWaddr 00:08:54:8A:1B:70
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:191127 errors:0 dropped:0 overruns:0 frame:0
TX packets:212611 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36172096 (34.4 MiB) TX bytes:0 (0.0 b)
Interrupt:16

# rpm -qa |grep kernel
kernel-devel-2.6.27.35-170.2.94.fc10.i686
kernel-2.6.27.9-159.fc10.i686
kernel-doc-2.6.27.35-170.2.94.fc10.noarch
kernel-headers-2.6.27.35-170.2.94.fc10.i386
kerneloops-0.12-2.fc10.i386
kernel-PAEdebug-2.6.27.35-170.2.94.fc10.i686
kernel-debug-devel-2.6.27.35-170.2.94.fc10.i686
kernel-PAE-2.6.27.35-170.2.94.fc10.i686
kernel-debug-2.6.27.35-170.2.94.fc10.i686
kernel-2.6.27.35-170.2.94.fc10.i686
kernel-firmware-2.6.27.35-170.2.94.fc10.noarch
kernel-PAEdebug-devel-2.6.27.35-170.2.94.fc10.i686
kernel-PAE-devel-2.6.27.35-170.2.94.fc10.i686

# rpm -qa |grep 2860
rt2860-2.1.2.0-2.fc10.noarch
kmod-rt2860-2.6.27.35-170.2.94.fc10.i686-2.1.2.0-2.fc10.2.i686
kmod-rt2860-2.1.2.0-2.fc10.2.i686

# uname -r
2.6.27.35-170.2.94.fc10.i686

# lsmod |grep 2860
rt2860sta 465592 1

# lspci |grep 2860
[root@localhost]#

I am more than happy to provide any additional details that may help resolve this issue. I am not a complete NOOB with Linux, but this is my first attempt at getting Wireless running under Linux.

[foooooo]

i can get the command "iwlist ra0 scanning" work, and I can get a ipv6 address, but not a ipv4 address. so when I try to bring up the ra0 device with command " ifup ra0" the device is not trying to commute a ipv4 address to the router, the "ifconfig " shows

ra0 Link encap:Ethernet HWaddr 00:1E:E5:E6:6F:7B
inet6 addr: fe80::21e:e5ff:fee6:6f7b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1553 errors:0 dropped:0 overruns:0 frame:0
TX packets:6298 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:176281 (172.1 KiB) TX bytes:503920 (492.1 KiB)

no inet address here, any ideas?

[foooooo]

my situation the card failed is because of the virtual box, the installation of virtualbox messed up all the usbfs links, so the hal wont know what the driver associated with the device. see the post
http://blogs.gnome.org/dcbw/2009/10/14/public-service-announcement-virtualbox-3-hal-and-networkmanager/
and
https://bugzilla.redhat.com/show_bug.cgi?id=474584

Hope this help others to resolve the issue.

BEst

[jonrpick]

Hi...

I'm trying to get my Linksys WUSB100 working on F10.

I've tried installing the rt2870 drivers via Yum. The download and installation completed fine, with no errors. But I still do not have a wireless connection listed in Network Manager. No errors... it's just as if nothing is there.

lsusb:


[pickens@localhost ~]$ lsusb
Bus 001 Device 007: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI
Bus 001 Device 006: ID 0bda:0151 Realtek Semiconductor Corp. Mass Stroage Device
Bus 001 Device 005: ID 1737:0078 Linksys
Bus 001 Device 004: ID 03f0:3e17 Hewlett-Packard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
Bus 002 Device 002: ID 04ca:002f Lite-On Technology Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[pickens@localhost ~]$



iwconfig:


[pickens@localhost ~]$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

pan0 no wireless extensions.

[pickens@localhost ~]$




I appear to be missing something here...

[foooooo]

you might need a different driver rather than rt2870.

[jonrpick]

you might need a different driver rather than rt2870.

I tried a 3070, I believe it was... whatever was mention in the 1st post. Same results.

[foooooo]

have you try to modify the header file of the rt3070, so they can recognize your device, I think you need to put the device id in that file /os/linux/usb_main_dev.c , add one line for your device. something like this,
{USB_DEVICE(0x7392,0x7717)},
{USB_DEVICE(0x1737,0x0070)}, /* Linksys WUSB100 */
{USB_DEVICE(0x1737,0x0071)}, /* Linksys WUSB600N */
{USB_DEVICE(0x0411,0x00e8)}, /* Buffalo WLI-UC-G300N*/
{USB_DEVICE(0x050d,0x815c)}, /* Belkin F5D8053 */
I found the code offered on the ralink website can not work on fedora 11 , at least for me(now version 2.2.0,), so you probably need to download the code rpm from rpm fusion, and recompile it. if the device id is in the souce code, the kernel will try to load it some how, and I think the rt3070 is the driver .

Best,

[jonrpick]

have you try to modify the header file of the rt3070, so they can recognize your device, I think you need to put the device id in that file /os/linux/usb_main_dev.c , add one line for your device. something like this,
{USB_DEVICE(0x7392,0x7717)},
{USB_DEVICE(0x1737,0x0070)}, /* Linksys WUSB100 */
{USB_DEVICE(0x1737,0x0071)}, /* Linksys WUSB600N */
{USB_DEVICE(0x0411,0x00e8)}, /* Buffalo WLI-UC-G300N*/
{USB_DEVICE(0x050d,0x815c)}, /* Belkin F5D8053 */
I found the code offered on the ralink website can not work on fedora 11 , at least for me(now version 2.2.0,), so you probably need to download the code rpm from rpm fusion, and recompile it. if the device id is in the souce code, the kernel will try to load it some how, and I think the rt3070 is the driver .

Best,

Should I first remove any rt**** drivers that are installed and start from scratch? How can I see which drivers are actually "loaded"?

[foooooo]

lsmod
will show what driver has been loaded,
rmmod
will remove that module

[jonrpick]

lsmod
will show what driver has been loaded,
rmmod
will remove that module

I don't see the rt2870 driver loading at all:


Module Size Used by
fuse 49436 2
sco 12932 2
bridge 43796 0
stp 6148 1 bridge
bnep 14848 2
l2cap 21504 3 bnep
bluetooth 48736 5 sco,bnep,l2cap
sunrpc 156436 3
ip6t_REJECT 7296 2
nf_conntrack_ipv6 15864 2
ip6table_filter 6400 1
ip6_tables 14736 1 ip6table_filter
ipv6 230388 28 ip6t_REJECT,nf_conntrack_ipv6
cpufreq_ondemand 9996 2
acpi_cpufreq 12172 0
dm_multipath 17292 0
uinput 10624 0
snd_hda_intel 354324 5
snd_seq_dummy 6660 0
snd_seq_oss 30364 0
snd_seq_midi_event 9600 1 snd_seq_oss
snd_seq 48576 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 10124 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 42624 0
snd_mixer_oss 16896 1 snd_pcm_oss
snd_pcm 65924 3 snd_hda_intel,snd_pcm_oss
snd_timer 22024 2 snd_seq,snd_pcm
snd_page_alloc 11144 2 snd_hda_intel,snd_pcm
ata_generic 8452 0
snd_hwdep 10628 1 snd_hda_intel
firewire_ohci 22916 0
firewire_core 35616 1 firewire_ohci
crc_itu_t 5760 1 firewire_core
snd 50616 19 snd_hda_intel,snd_seq_dummy,snd_seq_oss,snd_seq,sn d_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd _timer,snd_hwdep
usb_storage 86792 0
pata_acpi 7680 0
forcedeth 51600 0
pcspkr 6272 0
usblp 14592 0
pata_amd 13316 0
serio_raw 8836 0
soundcore 9416 1 snd
nvidia 7225464 36
i2c_core 21396 1 nvidia
wmi 9768 0


Edit:

I removed all rt**** using Yum. Then reinstalled rt2870, rebooted and got the exact same thing. So, it's not loading the module. How can I make it load the module?


Also:


[root@localhost pickens]# modprobe rt2870
FATAL: Module rt2870 not found.
[root@localhost pickens]#

[foooooo]

should use
modprobe rt2870sta
but you should use the 3070 driver.

[jonrpick]

should use
modprobe rt2870sta
but you should use the 3070 driver.

I tried that:


[root@localhost pickens]# modprobe rt2870sta
FATAL: Module rt2870sta not found.
[root@localhost pickens]#


I installed the rt3070 drivers...


[root@localhost pickens]# modprobe rt3070sta
FATAL: Module rt3070sta not found.
[root@localhost pickens]#

[foooooo]

use
rpm -qa|grep 2870
or
rpm -qa|grep 3070
to see what rpm are installed, then if you installed only src rpm, you should use the rpmbuild to build the rpm for kmod-rpm that was what I did, i guess you only installed the source code rpm, but have not build it yet. before you build add your device id to the c file under os/linux. I think the rpm you get from rpmfusion by default need rebuilt on your machine.
if that was the issue.

[jonrpick]

use
rpm -qa|grep 2870



[root@localhost pickens]# rpm -qa|grep 2870
rt2870-2.1.2.0-2.fc10.noarch
kmod-rt2870-2.6.27.37-170.2.104.fc10.i686-2.1.2.0-2.fc10.3.i686
kmod-rt2870-2.1.2.0-2.fc10.3.i686
[root@localhost pickens]#




or
rpm -qa|grep 3070



[root@localhost pickens]# rpm -qa|grep 3070
rt3070-2.1.1.0-2.fc10.noarch
kmod-rt3070-2.1.1.0-2.fc10.3.i686
kmod-rt3070-2.6.27.37-170.2.104.fc10.i686-2.1.1.0-2.fc10.3.i686
[root@localhost pickens]#


So, both are installed...




to see what rpm are installed, then if you installed only src rpm, you should use the rpmbuild to build the rpm for kmod-rpm that was what I did, i guess you only installed the source code rpm, but have not build it yet. before you build add your device id to the c file under os/linux. I think the rpm you get from rpmfusion by default need rebuilt on your machine.
if that was the issue.

Ok, I missed something then... How do I build it?

[foooooo]

you can follow the instruction on the first post to use rpmbuild to build the driver, I am afraid the souce code they compiled for you as the rpm package, may not include your device id, so try to do a
modprobe rt2870sta or modprobe rt3070sta, then use
service NetworkManager restart to restart the networkmanager service, then use
dmesg to see what the log says.

[foooooo]

you can follow the instruction on the first post to use rpmbuild to build the driver, I am afraid the souce code they compiled for you as the rpm package, may not include your device id, so try to do a
modprobe rt2870sta or modprobe rt3070sta, then use
service NetworkManager restart to restart the networkmanager service, then use
dmesg to see what the log says.

[jonrpick]

I had errors and more errors trying to rebuild the RPM.

I'm giving up. I'm trying to locate an older USB 802.11G adapter to use. I *had*, but can't find one that used an rt2500 driver. It was great.

I'm limited since I don't have an available PCI slot--only a PCI Express slot. Such is the price for choosing a "slim" form factor PC.

At this point, the WUSB100 is back in the packaging with the receipt on top, awaiting it's return trip to Micro Center. :(

[jonrpick]

As a follow-up, I exchanged the Linksys adapter for this:

http://www.microcenter.com/single_product_results.phtml?product_id=0305660

I just installed the rt73usb-firmware package via Yum, plugged in the adapter, restarted, and I'm online.

:)

normally, I would've seen the rt2870 issue through till the end, but I have limited time lately, and a serious need to have less cords in my new, small space.

Thanks for all the help though. :)

[ogetbilo]

Sorry folks, I've been really busy recently. jonrpick I see that you returned your rt2870 card. But the solution was simple: Just add your device id to the header file as indicated above and rebuild the rpm.

I will add your device id to rpmfusion's kmod rpm in the next round of updates.

[mtheory]

ogetbilo - would you mind adding my device ID to the header file? I got it to work by that method but it would be nice not to have to recompile.

Hawking HWDN2 REV-E: 0x0E66,0x0015

Thank you kindly! :)

[ogetbilo]

ogetbilo - would you mind adding my device ID to the header file? I got it to work by that method but it would be nice not to have to recompile.

Hawking HWDN2 REV-E: 0x0E66,0x0015

Thank you kindly! :)

Sure. Which one? 2860, 2870 or 3070?

[mtheory]

Apologies. I got it working with the 2870...

Thanks again!

[oakwcj]

I have an Msi Wind U210 with the Ralink rt3090 wireless adaptor. I downloaded the driver from the Ralink website and it appears to be close to the rt2860. I installed the kmod-rt2860 driver. It shows up in lsmod, but there is no reference to it in dmesg. Ihaven't yet tried to compile the driver. I see tha Mandriva has an rpm for the card. Is there any work going on at RPMFusion for the rt3090? TIA

[ogetbilo]

oakwci, it would be nice to have an RPM for 3090 too, but I have so little time and so many RPM's to take care of both in Fedora and RPMFusion.

Would you like to make an RPM for rt3090 and submit it to RPMFusion? You would probably need to use very similar patches that we use for rt2870 etc

If not, I will take this to my list. But I can't promise a time.

Edit: Apologies. I got it working with the 2870...

Thanks again!

I added support for your device on kmods in F-10 and later. They will be available with the next roll of updates (new updates usually spend 2 weeks in testing).

[oakwcj]

oakwci, it would be nice to have an RPM for 3090 too, but I have so little time and so many RPM's to take care of both in Fedora and RPMFusion.

Would you like to make an RPM for rt3090 and submit it to RPMFusion? You would probably need to use very similar patches that we use for rt2870 etc

If not, I will take this to my list. But I can't promise a time.

I completely understand that there are so many drivers and so little time. I have read [on Thorsten's kernel log blog] that the rt3090 is supposed to be included in the .32 kernel release, but it isn't in the staging directory in the most recent Fedora kernel. It is based on the rt2860, so if you could tell me where to find the patches you use, I would be willing to give it a shot, although I fear it may be beyond my abilities. Unfortunately, Thorsten also says that the Ralink drivers are a mess, so I doubt that I could be successful when actual developers have problems cleaning up the code.

I did try to compile the driver, but it failed with various syntax errors. No surprise there.

[ogetbilo]

Here you go, the SPEC file and the patches: http://cvs.rpmfusion.org/viewvc/rpms/rt2860-kmod/devel/?root=free

The other drivers (rt2870,rt3070) have almost identical patches. You can find those by just changing the URL.

Currently there are 3 types of drivers:
- Ralink's drivers: Yes they are messy. For instance, they don't officially support 2.6.31 kernel. I had to patch the source to get that working. This is what the kmod-rtxxx0 packages are made of, with the patches given in the above link.
- Staging drivers: Less messy, but not much. They are forked from the ralink's driver, but afaik (this may be wrong information) these are not being actively maintained, so theye may have less functionality than Ralink's drivers.
- Serialmonkey drivers: Clean and true kernel modules. These are incomplete and currently being written, but rather slowly. We were expecting them to be done last year around this time, but it still did not happen. When they come out, they will replace the above 2 sets.

Thorsten packaged the staging kmods recently. So from my understanding, kernel staging folks took the ralink's 3090 drivers into staging for 2.6.32.

[Shtirlicas]

Hi,

missing support for Sweex USB WiFi Adapters in rt2870sta driver:
Model: LW313, Chipset: RT2770, ID: 177F:0313
Model: LW303, Chipset: RT2870, ID: 177F:0302

[Dandapani]

Just installed F12 on my Asus EEE 1000 and followed these directions. Perfection! Thanks!

[ogetbilo]

Hi,

missing support for Sweex USB WiFi Adapters in rt2870sta driver:
Model: LW313, Chipset: RT2770, ID: 177F:0313
Model: LW303, Chipset: RT2870, ID: 177F:0302

177F:0302 was already there. I added 177F:0313 and also bunch of other devices.

[cripto]

well, in F10 it get to work thanks tou your efforts ogetbilo, as i said before
Now im in Fedora 12 and its not workeing altough it is seen in network manager.
My pen is a wusb 600N. From linksys/cisco.
i get this in dmesg:

usb 2-1: new high speed USB device using ehci_hcd and address 5
usb 2-1: New USB device found, idVendor=1737, idProduct=0071
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: Dual-Band Wireless-N USB Network Adapter
usb 2-1: Manufacturer: Cisco-Linksys LLC
usb 2-1: configuration #1 chosen from 1 choice
phy3: Selected rate control algorithm 'minstrel'
Registered led device: rt2800usb-phy3::radio
Registered led device: rt2800usb-phy3::assoc
Registered led device: rt2800usb-phy3::quality
rt2800usb 2-1:1.0: firmware: requesting rt2870.bin
cfg80211: Calling CRDA for country: PT
cfg80211: Current regulatory domain intersected:
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
phy3 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
rt2800usb 2-1:1.0: firmware: requesting rt2870.bin
phy3 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.


Failed to request firmware??
any idea? thanks
this error was after doing: yum install rt2870. Before i dont know but it didnt work. Just showed up
orrectly at network manager

[ogetbilo]

Hmm, that dmesg message belongs to the incomplete driver rt2870usb that is shipped with the kernel. I don't know why they are shipping an incomplete driver with kernel. But we are expecting this driver to be complete soon, by 2.6.32 perhaps. Afterwards, we will not need these kmods anymore.

Meanwhile, I guess what happened to you was, you plugged in the device before you did "yum install rt2870" so the incomplete rt2800usb module is loaded. Then, even after installing the rt2870 kmod package, the rt2870sta module is not loaded because there is already the incomplete rt2870usb module loaded for your device. What you can do is, you can remove your usb card, making sure you have installed rt2870 kmod, then you reboot your computer. Next time rt2870sta driver should be loaded instead, and you card will work.

If you don't want to reboot, just remove your usb card, then do rmmod rt2870usb; modprobe rt2870sta and this will load the correct module. Then you can plug your card back in.

If the situation persists on some other day (you can check which driver is loaded by lsmod |grep rt2), then you will need to blacklist the incomplete driver with something like
echo blacklist rt2870usb > /etc/modprobe.d/blacklist.rt2870usb
as root, although I don't expect this to happen. In case you have to do this, remember to remove this blacklist file when there is a kernel update to see if the newer kernel's rt2870usb module is working.

Edit: If the rt2870usb driver keeps loading, please let me know so that I add the blacklist file to the rt2870 package.

[cripto]

Hmm, that dmesg message belongs to the incomplete driver rt2870usb that is shipped with the kernel. I don't know why they are shipping an incomplete driver with kernel. But we are expecting this driver to be complete soon, by 2.6.32 perhaps. Afterwards, we will not need these kmods anymore.

Meanwhile, I guess what happened to you was, you plugged in the device before you did "yum install rt2870" so the incomplete rt2800usb module is loaded. Then, even after installing the rt2870 kmod package, the rt2870sta module is not loaded because there is already the incomplete rt2870usb module loaded for your device. What you can do is, you can remove your usb card, making sure you have installed rt2870 kmod, then you reboot your computer. Next time rt2870sta driver should be loaded instead, and you card will work.

If you don't want to reboot, just remove your usb card, then do rmmod rt2870usb; modprobe rt2870sta and this will load the correct module. Then you can plug your card back in.

If the situation persists on some other day (you can check which driver is loaded by lsmod |grep rt2), then you will need to blacklist the incomplete driver with something like
echo blacklist rt2870usb > /etc/modprobe.d/blacklist.rt2870usb
as root, although I don't expect this to happen. In case you have to do this, remember to remove this blacklist file when there is a kernel update to see if the newer kernel's rt2870usb module is working.

Edit: If the rt2870usb driver keeps loading, please let me know so that I add the blacklist file to the rt2870 package.

Thanks Obilo,
im gonna try the solution you provided.
I suppose i have to follow all those steps to install it again..
Im gonna try your rrmod 2870.

what i tried before was to yum remove 2870 and then install it again.
the same situation happened: it is detected correctly at network manager as a
Dual-Band Wireless-N USB Network Adapter but it cant find any network
and seems to be invisile at iwconfig and ifconfig.

this noon ill try it and post here my achievements. All people with F12 will have this
issue?
thank you very much

[IrishBouzouki]

having some trouble with setting this up again this time under fc12.x86_64 (2.6.31.6)

removed my WUSB600N from the plug before installing the OS (did not replace it until after installing the rpmfusion stuff as described in the following)

got the 3 files from rpmfusion...
rt2870-2.1.2.0-2.fc12.noarch.rpm
kmod-rt2870-2.1.2.0-6.fc12.x86_64.rpm
kmod-rt2870-2.6.31.6-145.fc12.x86_64-2.1.2.0-6.fc12.x86_64.rpm

did the install then shut down the machine
with machine off plugged the WUSB600N into the plug
brought up the system, configured a new wireless connection per the correct settings

did not "find the device", did not connect and no LED activity on the device (off)

re-booted

still does not light up the LED or connect but I do notice the device appears under the hardware listing

(NOTE - did not apply any of the changes I used on fc10 - see posts around #80 on this thread - but not even getting that far as the device does not even come on to ask for a passphrase - and maybe those changes for WPA2 are no longer required?)

here is a dmesg bit...

usb 2-1: new high speed USB device using ehci_hcd and address 2
usb 2-1: New USB device found, idVendor=1737, idProduct=0071
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: Dual-Band Wireless-N USB Network Adapter
usb 2-1: Manufacturer: Cisco-Linksys LLC
usb 2-1: configuration #1 chosen from 1 choice

and a little further down

Registered led device: rt2800usb-phy0::radio
Registered led device: rt2800usb-phy0::assoc
Registered led device: rt2800usb-phy0::quality
usbcore: registered new interface driver rt2800usb
alloc irq_desc for 22 on node 0
alloc kstat_irqs on node 0
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: setting latency timer to 64
rtusb init --->
usbcore: registered new interface driver rt2870

here is a bit from lsusb...

Bus 002 Device 002: ID 1737:0071 Linksys

and the lsmod bit grep'd

rt2870sta 484456 0

and just so you can be sure the rpm -qa bit grep'd

kmod-rt2870-2.1.2.0-6.fc12.x86_64
kmod-rt2870-2.6.31.6-145.fc12.x86_64-2.1.2.0-6.fc12.x86_64
rt2870-2.1.2.0-2.fc12.noarch

let me know if you have any ideas or if I can provide any other info

thanks.

[ogetbilo]

IrishBouzouki, read post 141 for a workaround. I guess I am gonna add the blacklist file to the kmod package.

[charactermatter]

I have been trying to figure out how to get my wireless to work on my eee pc901 with an RaLink 27** wireless card. I tried it on a fresh install of F12 and, for whatever reason, I couldn't get it to work. I tried it with F-11 and with F-10 and couldn't get it to work there either. I had F-10 on a year or so ago and I don't remember having any trouble. Will the instructions on page one of this thread still work with the latest kernel in F-12? In F-11? Right now I have a fresh install of F-11 LXDE installed. I yum updated everything. So, before I go in and screw things up too bad, if I run the yum install rt27* with the rpm fusion repo enabled, will I finally get this working? I don't remember having this much trouble before. Do I need to install the akmod? I haven't had to do this type of thing for several years, since F-8 fedora has run pretty smoothly on all of my machines. I may need some remedial training. My question: Do the instructions on page 1 still work, and are there any steps that I need to do that are not there?

[ogetbilo]

charactermatter, the instructions are valid for any Fedora since F-8. Please provide some specific information if something is wrong: dmesg output, lsmod output, kernel version, kmod-rt* version etc. See post 143 for an example feedback.

[charactermatter]

Here is lsmod
[Johneee@Johneee ~]$ lsmod
Module Size Used by
sunrpc 155656 1
ip6t_REJECT 4540 2
nf_conntrack_ipv6 17724 2
ip6table_filter 3156 1
ip6_tables 10968 1 ip6table_filter
ipv6 235712 22 ip6t_REJECT,nf_conntrack_ipv6
cpufreq_ondemand 6348 2
acpi_cpufreq 8864 0
dm_multipath 14048 0
pcspkr 2176 0
i2c_i801 10204 0
uvcvideo 50552 0
videodev 29636 1 uvcvideo
v4l1_compat 12056 2 uvcvideo,videodev
iTCO_wdt 10356 0
iTCO_vendor_support 2760 1 iTCO_wdt
btusb 13552 0
bluetooth 77104 1 btusb
joydev 9244 0
snd_hda_codec_realtek 193548 1
snd_hda_intel 24096 2
snd_hda_codec 59388 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 6724 1 snd_hda_codec
snd_pcm 63000 2 snd_hda_intel,snd_hda_codec
snd_timer 17780 1 snd_pcm
atl1e 31920 0
snd 50292 10 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec, snd_hwdep,snd_pcm,snd_timer
soundcore 5484 1 snd
snd_page_alloc 7720 2 snd_hda_intel,snd_pcm
eeepc_laptop 11220 0
rfkill 8936 3 eeepc_laptop
hwmon 2576 1 eeepc_laptop
ata_generic 4296 0
pata_acpi 3656 0
i915 154168 2
drm 167600 2 i915
i2c_algo_bit 4796 1 i915
video 18704 1 i915
output 2448 1 video
i2c_core 24992 4 i2c_i801,i915,drm,i2c_algo_bit

Here is a partial dmesg I had to shorten it to post it
[Johneee@Johneee ~]$ dmesg
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.30.9-99.fc11.i586 (mockbuild@x86-5.fedora.phx.redhat.com) (gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) ) #1 SMP Tue Nov 17 21:10:57 EST 2009
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
....(deleted sections)....
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
Fixed MDIO Bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf7eb7c00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.30.9-99.fc11.i586 ehci_hcd
usb usb1: SerialNumber: 0000:00:1d.7
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000d480
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.30.9-99.fc11.i586 uhci_hcd
usb usb2: SerialNumber: 0000:00:1d.0
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d800
usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: UHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.30.9-99.fc11.i586 uhci_hcd
usb usb3: SerialNumber: 0000:00:1d.1
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000d880
usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: UHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.30.9-99.fc11.i586 uhci_hcd
usb usb4: SerialNumber: 0000:00:1d.2
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1d.3: setting latency timer to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000dc00
usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: UHCI Host Controller
usb usb5: Manufacturer: Linux 2.6.30.9-99.fc11.i586 uhci_hcd
usb usb5: SerialNumber: 0000:00:1d.3
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
rtc_cmos 00:03: RTC can wake from S4
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, 114 bytes nvram, hpet irqs
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
nf_conntrack version 0.5.0 (16250 buckets, 65000 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
Using IPI No-Shortcut mode
PM: Resume from disk failed.
registered taskstats version 1
Magic number: 5:147:276
tty tty13: hash matches
Initalizing network drop monitor service
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input5
ata2.00: CFA: ASUS-PHISON SSD, TST2.04U, max UDMA/66
ata2.00: 7880544 sectors, multi 0: LBA
ata2.01: CFA: ASUS-PHISON SSD, TST2.04P, max UDMA/66
ata2.01: 31522176 sectors, multi 0: LBA
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/66
scsi 1:0:0:0: Direct-Access ATA ASUS-PHISON SSD TST2 PQ: 0 ANSI: 5
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] 7880544 512-byte hardware sectors: (4.03 GB/3.75 GiB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 <<5>scsi 1:0:1:0: Direct-Access ATA ASUS-PHISON SSD TST2 PQ: 0 ANSI: 5
sd 1:0:1:0: Attached scsi generic sg1 type 0
sda5 > sda3 sda4
sd 1:0:1:0: [sdb] 31522176 512-byte hardware sectors: (16.1 GB/15.0 GiB)
sd 1:0:1:0: [sdb] Write Protect is off
sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sdb:<5>sd 1:0:0:0: [sda] Attached SCSI disk
sdb1
sd 1:0:1:0: [sdb] Attached SCSI disk
...(deleted section)...

usb 5-1: Product: BT-253
usb 5-1: Manufacturer: Broadcom Corp
usb 5-1: SerialNumber: 0015AFF68A40
usb 5-1: configuration #1 chosen from 1 choice
EXT4-fs: barriers enabled
kjournald2 starting: pid 74, dev dm-0:8, commit interval 5 seconds
EXT4-fs: delayed allocation enabled
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
EXT4-fs: mounted filesystem dm-0 with ordered data mode
type=1404 audit(1259838959.510:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
...(deleted section)...
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: Generic Bluetooth USB driver ver 0.5
usbcore: registered new interface driver btusb
intel_rng: FWH not detected
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)


I ran yum install rt2860...so what is next?
[Johneee@Johneee ~]$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

[Johneee@Johneee ~]$

[charactermatter]

IrishBouzouki, I think we are experiencing the same thing. The kernel doesn't seem to load the module for the wireless card. I don't know enough about it to know why, but I know what you're experiencing. I am going through the same thing. The driver installs, but the device does not seem to be present. netiher system-config-network, nor network manager seem to be able to access the device. I hope someone can help us out...

[ogetbilo]

hey guys. post 141 gives the reason why the correct driver is not being loaded for the device and how to work around it until I rebuild the package. What is not clear about it?

[charactermatter]

Well, I hope it works for Irish. For me, the card is not a USB, it's an internal in my eee-pc 901. I can't (easily) unplug it. I can load another OS, and wait for Fedora to catch up. I don't understand why I had the same problem when I did the retro, and tried to load F10, and F11. Right now I am trying to get it to work on F11 LXDE. I see now that F12 LXDE is out. Am I forgetting a command to load the kernel module: modprobe or IFUP? I feel like it's something simpler than what I have been going through. Are you pretty sure this is what is happening with mine as well? Will I be waiting days, weeks, or months for the fix? I would happily run F10 or F11 if the wifi would work. I don't need to be on the cuting edge.

[ogetbilo]

charactermatter,
In post 141, there is a workaround. It tells you how to blacklist a module. You just need to blacklist the "bad" kernel module.
If you are using rt2860, the bad module is possibly rt2x00pci. You can find the other possibly bad modules by
rpm -ql kernel| grep rt2
If you want to make sure you can blacklist all of those modules.

Now I am managing 3 kernel modules: rt2860, rt2870, rt3070. I only have the hardware for rt2870 so I can't make tests for other ones. I need to go to look into the kernel code to see what I need to blacklist for each of the above kmod packages. I have a very limited time for Fedora these days. Just FYI, other than these kmods, I also have to deal with ~100 packages and their bugs. I am trying to reach everywhere but I can't do fixes rightaway sometimes. From the moment I wake up until I go to sleep, I sometimes don't even have time to eat lunch or dinner. This issue was reported only 5 days ago and I already outlined a workaround for it. Please be patient.

If you want to help, please find out for me which module(s) need to be blacklisted for rt2860.

[charactermatter]

My post wasn't meant as a "hurry-up" and I do appreciate your efforts in the forum. Please don't misunderstand. I meant only that I will seek other options if the timeline is going to be long. I know how to be happy with somethig that's free...Would I be able to deprecate my kernel, and then just not update until there are fixes available? What about going back to the earlier F-? I could also live with that, as I have been running Fedora since Fedora Core 1 and still have lots of copies of everything. I am eager to get something other than the xandros back on my eee so I can run IP tables....I'll give the work-around a go and see if I can manage it. I am just a linux-peon. Everything I know I have learned from trial and error or from the forums and books. If I get something to work, I rarely really understand why. :) Thanks for the help.

[IrishBouzouki]

hey guys. post 141 gives the reason why the correct driver is not being loaded for the device and how to work around it until I rebuild the package. What is not clear about it?
Hmm, that dmesg message belongs to the incomplete driver rt2870usb that is shipped with the kernel. I don't know why they are shipping an incomplete driver with kernel. But we are expecting this driver to be complete soon, by 2.6.32 perhaps. Afterwards, we will not need these kmods anymore.
Meanwhile, I guess what happened to you was, you plugged in the device before you did "yum install rt2870" so the incomplete rt2800usb module is loaded. Then, even after installing the rt2870 kmod package, the rt2870sta module is not loaded because there is already the incomplete rt2870usb module loaded for your device. What you can do is, you can remove your usb card, making sure you have installed rt2870 kmod, then you reboot your computer. Next time rt2870sta driver should be loaded instead, and you card will work.
If you don't want to reboot, just remove your usb card, then do rmmod rt2870usb; modprobe rt2870sta and this will load the correct module. Then you can plug your card back in.
If the situation persists on some other day (you can check which driver is loaded by lsmod |grep rt2), then you will need to blacklist the incomplete driver with something like
echo blacklist rt2870usb > /etc/modprobe.d/blacklist.rt2870usb
as root, although I don't expect this to happen. In case you have to do this, remember to remove this blacklist file when there is a kernel update to see if the newer kernel's rt2870usb module is working.
Edit: If the rt2870usb driver keeps loading, please let me know so that I add the blacklist file to the rt2870 package.

it is likely I am just too clueless about this to understand... but in answer to your question what is not clear about it is that I have no rt2870usb driver loaded so rmmod rt2870usb as suggested in the workaround post #141 does not seem to make any sense in my case.... so... which drivers that I actually have on my machine (as listed below) do I need to rmmod and which are actually part of the rpmfusion rt2870sta driver package and need to be kept?

$ rpm -ql kernel | grep rt2
/lib/modules/2.6.31.6-145.fc12.x86_64/kernel/drivers/net/wireless/rt2x00
/lib/modules/2.6.31.6-145.fc12.x86_64/kernel/drivers/net/wireless/rt2x00/rt2400pci.ko
/lib/modules/2.6.31.6-145.fc12.x86_64/kernel/drivers/net/wireless/rt2x00/rt2500pci.ko
/lib/modules/2.6.31.6-145.fc12.x86_64/kernel/drivers/net/wireless/rt2x00/rt2500usb.ko
/lib/modules/2.6.31.6-145.fc12.x86_64/kernel/drivers/net/wireless/rt2x00/rt2800usb.ko
/lib/modules/2.6.31.6-145.fc12.x86_64/kernel/drivers/net/wireless/rt2x00/rt2x00lib.ko
/lib/modules/2.6.31.6-145.fc12.x86_64/kernel/drivers/net/wireless/rt2x00/rt2x00pci.ko
/lib/modules/2.6.31.6-145.fc12.x86_64/kernel/drivers/net/wireless/rt2x00/rt2x00usb.ko
/lib/modules/2.6.31.6-145.fc12.x86_64/kernel/drivers/net/wireless/rt2x00/rt61pci.ko
/lib/modules/2.6.31.6-145.fc12.x86_64/kernel/drivers/net/wireless/rt2x00/rt73usb.ko
$ lsmod | grep rt2
rt2870sta 484456 0
rt2800usb 34320 0
rt2x00usb 11088 1 rt2800usb
rt2x00lib 41184 2 rt2800usb,rt2x00usb
input_polldev 4160 1 rt2x00lib
mac80211 181496 2 rt2x00usb,rt2x00lib
cfg80211 87800 2 rt2x00lib,mac80211
crc_ccitt 2096 1 rt2800usb

but, okay, after seeing the kernel driver listing per your suggestion and after doing a bunch of reading on what that info in lsmod means I can try to guess, so here, I unplug my WUSB600N wireless adapter then do the following...
# rmmod rt2800usb
# rmmod rt2x00usb
# rmmod rt2x00lib
# lsmod | grep rt2
rt2870sta 484456 0
...and... after plugging the adapter back in... okay... it friggin worked! WPA2 and everything!

EXCEPT... on a reboot, there were all the 'bad' modules again, and no active wireless!

but the blacklist works and now when I shut down and restart the wireless comes up automatically, here is what I did... unplug the adapter again and then...
# rmmod rt2800usb
# rmmod rt2x00usb
# rmmod rt2x00lib
# lsmod | grep rt2
rt2870sta 484456 0
# gedit /etc/modprobe.d/blacklist.conf
(one could of course use a different editor, I use gedit because I don't have much vim or emacs experience, at least not in the past 5 years or so)

here is what I added to the file...
# Ralink Tech rt2870 USB (WUSB600N) drivers (comment out blacklist after each kernel update to test new kernel drivers!)
blacklist rt2800usb
blacklist rt2x00usb
blacklist rt2x00lib
(the '#' is not the root prompt here -being pedantic- but is the comment specifier for the blacklist file)
...then plug it back in and when I reboot now it still works

so there you go... it was just a matter of not understanding enough about this to realize that all those darn modules were part of the 'bad' module and they all needed to be unloaded even though I had no rt2870usb driver as stated on my system.
that did it, thanks, and @charactermatter you should probably try something like this with whatever changes to driver names are relevant for your configuration - but the core idea I take from this experience is that the rt2870sta (or whichever it is for your card) is the only one that stays (the rest are there in the kernel whether you avoided installing any additional hardware support or not - didn't check rt73usb in my install but there it was in the kernel anyhow). I'd try it with the blacklist stuff without removing your hardware (not sure you might have to blacklist first if it keeps trying to reload the bad drivers, experiment some)

[ogetbilo]

sorry my bad. rt2870usb was just figure of speech. When I said

...something like
echo blacklist rt2870usb > /etc/modprobe.d/blacklist.rt2870usb

that "something like" meant you need to figure out yourself what that actual module name is. In this case it is rt2800usb, which you already figured out. I sent the new packages to testing this morning with rt2800usb blacklisted. They will be in the testing repo possibly tomorrow.

Sorry, I should have been clearer.

[daf1983]

hi there, i've got a similar problem but i think it's even more complicated. i've got a Ralink 2860 PCI card on my eeepc 1000H and everything worked perfectly until yesterday. after yesterday's kernel update, the card is not recognised whatsoever. what's even more astonishing is the fact that the module does not load despite a successful check whether kernel modules exist.:
[teru@netbook ~]$ lsmod |grep rt2
[teru@netbook ~]$
i tried the trick with blacklisting modules but it didn't help. reinstalling the kmods and akmods did not work either. dmesg does not show anything when i do modprobe rt2860sta (the module loads). it does not work on the old kernel either. please, help me.

[ogetbilo]

daf1983, can you post the outputs of

rpm -qa |grep kernel
uname -r
rpm -qa |grep rt2

[daf1983]

rpm -qa|grep kernel

kernel-devel-2.6.31.5-127.fc12.i686
abrt-plugin-kerneloopsreporter-1.0.0-1.fc12.i686
abrt-addon-kerneloops-1.0.0-1.fc12.i686
kernel-headers-2.6.31.6-145.fc12.i686
kernel-2.6.31.6-145.fc12.i686
kernel-firmware-2.6.31.6-145.fc12.noarch
kernel-devel-2.6.31.6-145.fc12.i686
kernel-2.6.31.5-127.fc12.i686

uname -r

2.6.31.6-145.fc12.i686

rpm -qa|grep rt2

kmod-rt2860-2.6.31.6-145.fc12.i686-2.1.2.0-3.fc12.8.i686
kmod-rt2860-2.1.2.0-3.fc12.8.i686
akmod-rt2860-2.1.2.0-3.fc12.6.i686
rt2860-2.1.2.0-2.fc12.noarch
kmod-rt2860-2.6.31.5-127.fc12.i686-2.1.2.0-3.fc12.6.i686

i can see that i've got three kmods installed but the one for the older kernel is a result of building it during boot as i installed only the newest one.

[ogetbilo]

Hmm, I don't know what to say. Everything seems normal. It might be that my kernel-2.6.31 hack is not working. It works for my rt2870 though... (Ralink driver does not support kernel 2.6.31 or higher. I had to hack the source to make things work). Since I don't have the rt2860 device, I can't test any possible hacks myself

Could you try removing all of those rt2860 packages that you reported above and install the staging drivers, i.e.
yum remove rt2860
yum install kmod-staging
then restart and see if it works (the staging kmod also contains a rt2860 driver.)

charactermatter, could you try this too?

[daf1983]

no improvement unfortunately. what's strange is the fact that it used to work with kernel-2.6.31.5-127.fc12.i686 but it doesn't work with this kernel any longer. maybe it's not a matter of 2.6.31? i checked what packages were also updated when the driver ceased to work:


Dec 01 22:25:46 Updated: abrt-libs-1.0.0-1.fc12.i686
Dec 01 22:25:51 Updated: abrt-1.0.0-1.fc12.i686
Dec 01 22:25:52 Updated: libuuid-2.16-10.3.fc12.i686
Dec 01 22:25:53 Updated: libblkid-2.16-10.3.fc12.i686
Dec 01 22:25:55 Updated: 1:cups-libs-1.4.2-7.fc12.i686
Dec 01 22:25:57 Updated: file-libs-5.03-12.fc12.i686
Dec 01 22:25:58 Updated: telepathy-gabble-0.8.8-1.fc12.i686
Dec 01 22:25:59 Updated: abrt-plugin-bugzilla-1.0.0-1.fc12.i686
Dec 01 22:26:00 Updated: abrt-addon-ccpp-1.0.0-1.fc12.i686
Dec 01 22:26:01 Updated: abrt-plugin-logger-1.0.0-1.fc12.i686
Dec 01 22:26:03 Updated: abrt-addon-python-1.0.0-1.fc12.i686
Dec 01 22:26:03 Updated: abrt-plugin-sqlite3-1.0.0-1.fc12.i686
Dec 01 22:26:04 Updated: gstreamer-tools-0.10.25.1-1.fc12.i686
Dec 01 22:26:08 Updated: gstreamer-0.10.25.1-1.fc12.i686
Dec 01 22:26:11 Updated: gstreamer-plugins-base-0.10.25.1-1.fc12.i686
Dec 01 22:26:13 Updated: empathy-libs-2.28.1.2-1.fc12.i686
Dec 01 22:26:13 Updated: grubby-7.0.9-1.fc12.i686
Dec 01 22:26:15 Updated: abrt-plugin-kerneloopsreporter-1.0.0-1.fc12.i686
Dec 01 22:26:16 Updated: abrt-addon-kerneloops-1.0.0-1.fc12.i686
Dec 01 22:26:18 Updated: fuse-libs-2.8.1-3.fc12.i686
Dec 01 22:26:20 Updated: mojito-0.21.6-1.fc12.i686
Dec 01 22:26:23 Updated: nbtk-1.2.1-1.fc12.i686
Dec 01 22:26:23 Updated: file-5.03-12.fc12.i686
Dec 01 22:26:35 Updated: 1:cups-1.4.2-7.fc12.i686
Dec 01 22:26:36 Updated: tree-1.5.3-1.fc12.i686
Dec 01 22:26:37 Updated: patch-2.6-1.fc12.i686
Dec 01 22:26:38 Updated: abrt-desktop-1.0.0-1.fc12.i686
Dec 01 22:26:45 Updated: papyon-0.4.3-1.fc12.noarch
Dec 01 22:26:46 Updated: telepathy-butterfly-0.5.3-1.fc12.noarch
Dec 01 22:26:49 Updated: kernel-firmware-2.6.31.6-145.fc12.noarch
Dec 01 22:26:55 Updated: kernel-headers-2.6.31.6-145.fc12.i686
Dec 01 22:26:59 Updated: lohit-gujarati-fonts-2.4.4-1.fc12.noarch
Dec 01 22:27:58 Installed: kernel-devel-2.6.31.6-145.fc12.i686
Dec 01 22:27:59 Updated: perf-2.6.31.6-145.fc12.noarch
Dec 01 22:28:24 Updated: empathy-2.28.1.2-1.fc12.i686
Dec 01 22:28:26 Updated: abrt-gui-1.0.0-1.fc12.i686
Dec 01 22:28:27 Updated: coreutils-libs-7.6-7.fc12.i686
Dec 01 22:28:33 Updated: coreutils-7.6-7.fc12.i686
Dec 01 22:30:10 Installed: kernel-2.6.31.6-145.fc12.i686
Dec 01 22:30:14 Updated: util-linux-ng-2.16-10.3.fc12.i686
Dec 01 22:30:15 Updated: fuse-2.8.1-3.fc12.i686


maybe one of these packages is responsible for that. is there any way i could help you? unfortunately, i don't know much about kernel modules.

my friend at forum.fedora.pl has just written that this card on MSI U100Plus works fine for him despite the update. it seems it's gonna be tough.

[duende]

my friend at forum.fedora.pl has just written that this card on MSI U100Plus works fine for him despite the update. it seems it's gonna be tough.

Well, as I said, it does work on MSI Wind U100Plus. I have also checked that the output of the commands
rpm -qa |grep kernel
uname -r
rpm -qa |grep rt2
is exactly the same as in daf's post #157. So it is probably something else. On my computer the module does load:
lsmod | grep rt2
rt2860sta 477264 1

[daf1983]

i've just found a solution! i had to... enable wireless. it was disabled :mad:. i pressed Fn+F2 and it miraculously started to work. i don't know whether i disabled it accidentally or whether it became disabled after the update but it is working fine at the moment. sorry for bothering you. the simplest solutions are indeed the best.

[charactermatter]

I nstalled the "kmod-staging" and my wireless worked on the next reboot. Here's how it went: I was on a crisp fresh install of LXDE F12. I ran 'yum update all'...I added the fusion repo and key. Then I ran 'yum install kmod-staging'... On the next reboot, wireless worked jsut fine. Monday morning, I saw a software update ask to load, a new 'kernel', and also a new 'kmod-staging' was available to update. Like a fool, I let yum update everything it wanted to. I was unable to boot the kernel on the restart. Where did I go wrong?

[fredex]

I'm just now attempting to use the LXDE live on a USB stick. I'm interested in playing with it to see how well it works on the eeepc, especially my 901. I've got a full Gnome F12 installed on the machine, so I would love for this to work from usb.

well, I can't get the rt2860 wireless working either. I installed the akmod for it and rebooted and it's as if I hadn't bothered... no rt2860sta.ko gets generated. there was some error message at boot about not having the packages necessary to build the akmod, but I didn't understand it well enough to determine WHICH packages it needed.

so I removed that and installed the kmods, rebooted, and still no joy. the .ko exists, but it still won't load. modprobe rt2860sta does nothing useful. lspci shows the device. the wireless hardware defaults (in the BIOS settings) to ON, and in fact works fine on my "normal" F12 installation.

Clues, anyone?

[charactermatter]

Fred, you are seeing exactly what I saw. I too am trying different things on the eee 901. I couldn't get the wireless to work until I followed the instructions in an earlier post in this thread from Og. Remove RT2860, then install kmod-staging. Wireless worked perfectly on the reboot. Note here I am running LXDE installed, not from the usb live. I ran Gnome on this computer a year or so ago, and found it to be too much. ( I have yet to find anything that boots faster, runs smoother, or works as flawlessly as the Xandros the eee came with. I have tried many. I need more functionality with it now, though, and I am not so familiar with Deb as I am Fedora...So here I am.) I am trying to understand what "kmod-staging" is. Is it what it sounds like? Pre-release kmods? If I have "kmods-staging" installed am I ok to allow the kernel or kmods to update? What kinds of precautions should I take. As I said in my earlier post, I installed "kmod-staging" and things were great for two days. When a new kernel, and new kmod-staging package were installed on an update. I was unable to boot the kernel. I could have gone in and repaired, but iut was faster to just reinstall. I had nothing on it to worry about losing. Og, what is kmod-staging, and how should I handle updates? Will there be a point when I will remove "kmod-staging?"

[fredex]

well, I can try what you suggest, what have I to lose ? (my sanity is already gone...) I can always re-create the bootable usb, too.

regarding your questions on what is kmod-staging, I have no clue. never heard of it before reading this thread.

While I agree with you that the default Xandros-derivative that came with the 901 is the fastest thing I've seen, I disagree on the "works flawlessly" part. it's flaky as all heck. and as I used it over the course of 4-6 months it became flakier and flakier as time went by.

I finally blew it away (having used dd to save the two SSD contents off to a NAS box first) and installed F10 with, as time went by, custom tweaks, and Quasar8000's updated eeepc kernel. F11 was much better, and I didn't feel the need for his custom kernel, and so far on F12 I don't either.

however, a full gnome system with all the bells and whistles is sometimes rather slow on the 901, so I thought to try lxde in a non-destructive way.

Thanks for the hints, I'll give it a whirl and see where it takes me.

[ogetbilo]

charactermatter,
kmod-staging are modules that are from the staging branch of kernel. In other words, their code is not written in kernel quality. Some staging kmods will get into kernel some day, some will not. rt2860 module that is in the kmod-staging package is basically same with the module from the kmod-rt2860 package, maybe the kmod-staging is a little older and has less functionality. For more information please read post 136.

If your kernel is not booting that is hardly kmod-staging's or kmod-rt2860's fault. As I am not a kernel developer, the best place to report this is http://bugzilla.redhat.com

fredex, on the LXDE box, what does rpm -qa |grep kmod tell you? Also please post the outputs of uname -r and rpm -q kernel-devel

[fredex]

ogetbilo: Before I saw your post I blew away the USB image and re-created it. I then did "yum install kmod-staging", rebooted, and no wireless. I then did "yum install rt2860", rebooted, and no wireless. I then did "yum install kernel-devel", rebooted, and no wireless.

lsmod does not list rt2860.

now, for your questions:

$ rpm -qa | grep kmod
kmod-staging-2.6.31.6-162.fc12.i686-2.6.31.5-2.fc12.7.i686
staging-kmod-addons-2.6.31.5-2.fc12.noarch
kmod-staging-2.6.31.5-2.fc12.7.i686
kmod-rt2860-2.6.31.6-162.fc12.i686-2.1.2.0-3.fc12.9.i686
kmod-rt2860-2.1.2.0-3.fc12.9.i686

$ uname -r
2.6.31.5-127.fc12.i686

$ rpm -q kernel-devel
kernel-devel-2.6.31.6-162.fc12.i686

[leigh123linux]

ogetbilo: Before I saw your post I blew away the USB image and re-created it. I then did "yum install kmod-staging", rebooted, and no wireless. I then did "yum install rt2860", rebooted, and no wireless. I then did "yum install kernel-devel", rebooted, and no wireless.

lsmod does not list rt2860.

now, for your questions:$ rpm -qa | grep kmod
kmod-staging-2.6.31.6-162.fc12.i686-2.6.31.5-2.fc12.7.i686
staging-kmod-addons-2.6.31.5-2.fc12.noarch
kmod-staging-2.6.31.5-2.fc12.7.i686
kmod-rt2860-2.6.31.6-162.fc12.i686-2.1.2.0-3.fc12.9.i686
kmod-rt2860-2.1.2.0-3.fc12.9.i686

$ uname -r
2.6.31.5-127.fc12.i686

$ rpm -q kernel-devel
kernel-devel-2.6.31.6-162.fc12.i686


Try ( the modules needs to match the kernel version )


su
yum update kernel
rebootMake sure you reboot to the new kernel i.e 2.6.31.6-162.fc12.i686

[fredex]

Hmm. I didn't see the conflicting kernel versions before. thanks for pointing that out.

I don't understand how this live cd (on a usb stick) boots,... the grub prompt only offers one item to boot from and it doesn't specify a kernel (at least not by version number). certainly both kernels are installed.

there is no /boot/grub.conf or /boot/grub/menu.lst. I find a grub.conf in:
/usr/lib/anaconda-runtime/boot/grub.conf
and
/mnt/live/efi/boot/grub.conf
but neither of them looks like a "normal" grub.conf.

So, does anyone know how to boot from the live-cd-on-a-usb-stick but from a newer-than-default kernel? t'ain't obvious to me. (seems to me I've been able to install updated kernelsl on a live-cd-on-a-usb-stick installation before, and have the new kernel boot, on F11, for example. but this one appears to be different.)

[leigh123linux]

Hmm. I didn't see the conflicting kernel versions before. thanks for pointing that out.

I don't understand how this live cd (on a usb stick) boots,... the grub prompt only offers one item to boot from and it doesn't specify a kernel (at least not by version number). certainly both kernels are installed.

there is no /boot/grub.conf or /boot/grub/menu.lst. I find a grub.conf in:/usr/lib/anaconda-runtime/boot/grub.conf and/mnt/live/efi/boot/grub.confbut neither of them looks like a "normal" grub.conf.

So, does anyone know how to boot from the live-cd-on-a-usb-stick but from a newer-than-default kernel? t'ain't obvious to me. (seems to me I've been able to install updated kernelsl on a live-cd-on-a-usb-stick installation before, and have the new kernel boot, on F11, for example. but this one appears to be different.)


Try this, it should install the matching kmod for the running kernel


su
yum install kmod-rt2860.$(uname -r)
modprobe rt2860sta

[fredex]

Leigh: thanks for the hint.

unfortunately:

yum install kmod-rt2860.$(uname -r)
No package kmod-rt2860.2.6.31.5-127.fc12.i686 available.
Nothing to do.

and this doesn't look promising either:

# yum list available | grep -y rt2860
akmod-rt2860.i586 2.1.2.0-3.fc12.6 rpmfusion-free
akmod-rt2860.i686 2.1.2.0-3.fc12.6 rpmfusion-free
kmod-rt2860.i586 2.1.2.0-3.fc12.6 rpmfusion-free
kmod-rt2860-2.6.31.5-127.fc12.i686.i586
kmod-rt2860-2.6.31.5-127.fc12.i686.PAE.i686
kmod-rt2860-2.6.31.6-145.fc12.i686.i686
kmod-rt2860-2.6.31.6-145.fc12.i686.PAE.i686
kmod-rt2860-2.6.31.6-162.fc12.i686.PAE.i686
kmod-rt2860-PAE.i686 2.1.2.0-3.fc12.9 rpmfusion-free-updates

[ogetbilo]

Sorry, I don't have much live CD experience. I just use them to install Fedora:)
You can try download and install the rpms manually from
http://download1.rpmfusion.org/free/fedora/releases/12/Everything/i386/os/

[fredex]

thanks for trying!

I had no trouble at all with "normal" F12 live on the usb stick, I installed the 2860 driver without issue. it's weird that the live lxde seems different.

[ogetbilo]

Hi folks. There are updates from Ralink for the rt2870 and rt3070 drivers. But since I will be on vacation for about 3.5 weeks and I won't be around to fix stuff if something goes wrong with the new versions, I will postpone the kmod updates until I get back (mid January). Sorry for the inconvenience.

[charactermatter]

One thing which I discovered when I was trying to get my RT2860 working was this. I downloaded and installed F12 I386 from the Fedora site, or it's mirrors. The version that installed when I ran the CD and installed on My (4) computers was a PAE kernel. On three computers I had no problem getting wireless right after install. My EEE has the RT2860. I knew the PAE was installed, but I expected everything I did with YUM to figure out which versions of anything to install. When I was trying to get the RT2860 to install and work, everything seemed to install OK, but it still didn't work. It was there in the lspci. Short story is this, when I installed the kmod-staging from a terminal, it did not install the correct one for the PAE kernel. I realized this when I took a look at what I had installed (I used Yumex because I like GUI's ... my typing is less than perfect.) I realized there were two kmod-staging versions in the repo and I had the standard installed, not the PAE version. I don't know why this happened, but I wish I would have caught it a few weeks ago. Running yum install kmod-staging will get the standard, not the PAE, even if you have only a PAE installed. I also don't know why F12 installs a PAE by default. That however is of little consequence, since I am a novice / hobbyist and only have a basic understand of the difference. Everything works now, and I love Fedora again.

[whitenight639]

hi,

A fedora update killed my RT2860 card and I havnt been able to get it working since, it really frustrated me, been looking for the RPM packages in the fusion repo but can't find any for my kernel version, my kernel version is 2.6.30.10-105.fc11.i586

As i dont have network conectivity on this box everything has to be put on it via cd or usb and is frustrating.

The other kernel versions i can boot into are also still in the 2.6.30 range so i can't drop back to an older version, as for updating to a newer kernel i wouldnt know how to, and if i did i'd imagine there would be a lot of dependancies that also need downloading.

Am I right in thinking the RPMs can be rebuild for my kernel version? if so how?

thanks

[leigh123linux]

hi,

A fedora update killed my RT2860 card and I havnt been able to get it working since, it really frustrated me, been looking for the RPM packages in the fusion repo but can't find any for my kernel version, my kernel version is 2.6.30.10-105.fc11.i586

As i dont have network conectivity on this box everything has to be put on it via cd or usb and is frustrating.

The other kernel versions i can boot into are also still in the 2.6.30 range so i can't drop back to an older version, as for updating to a newer kernel i wouldnt know how to, and if i did i'd imagine there would be a lot of dependancies that also need downloading.

Am I right in thinking the RPMs can be rebuild for my kernel version? if so how?

thanks


Try reading the end of post #1 .

[cpgcpg]

hi, any support for "RaLink RT3092 Wireless 802.11n 2T/2R PCIe" (lspci) ?

it's an internal minipci card.

[root@dell-f12 ~]# modprobe -v rt3070sta
insmod /lib/modules/2.6.31.9-174.fc12.x86_64/extra/rt3070/rt3070sta.ko
[root@dell-f12 ~]# uname -a
Linux dell-f12 2.6.31.9-174.fc12.x86_64 #1 SMP Mon Dec 21 05:33:33 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux
[root@dell-f12 ~]#


dmesg says this:
rtusb init --->
usbcore: registered new interface driver rt2870

however, it does not look like it's well supported, as network manager does not seem to recognize it.

[root@dell-f12 ~]# lspci -s 0c:00.0 -x
0c:00.0 Network controller: RaLink RT3092 Wireless 802.11n 2T/2R PCIe
00: 14 18 92 30 07 01 10 00 00 00 80 02 10 00 00 00
10: 00 00 ff f1 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 14 18 92 30
30: 00 00 00 00 40 00 00 00 00 00 00 00 05 01 00 00
[root@dell-f12 ~]#


maybe with the new updates after ogetbilo comes back? :)

[Savdnc Systems]

according to 'lspci', i have rt3090.
as i understand i must use rt2860 drivers.
so i did 'yum install rt2860'
nothing works and if i try "ifconfig ra0",
i'm getting this:
ra0: error fetching interface information: Device not found

i can't understand anything. maybe i should compile proper driver but i don't know how.

[Kotau]

I have worked extensively with the latest ra2870 driver from ralink on f12 with 2.6.32 and found that it does not allow wpa_supplicant to connect to an Access Point. If I compile without wpa_supplicant support I am able to connect manually but only at 802.11g. I have the same problem with the rpmfusion module.



uname -r
2.6.32-0.65.rc8.git5.fc13.i686.PAE




/usr/bin/Startwifi
#!/bin/bash
insmod /usr/src/RT2870_LinuxSTA_V2.3.0.0/os/linux/rt2870sta.ko;
ifconfig ra0 up;
iwpriv ra0 set NetworkType=Infra;
iwpriv ra0 set AuthMode=WPA2PSK;
iwpriv ra0 set EncrypType=TKIP;
iwpriv ra0 set SSID="xxxxxx";
iwpriv ra0 set WPAPSK=xxxxxxxxxxxx;
iwpriv ra0 set SSID="xxxxxx";
/sbin/dhclient;




ra0 Ralink STA ESSID:"xxxx" Nickname:"RT2870STA"
Mode:Managed Frequency=2.462 GHz Access Point: 00:1C:F0:F6:08:50
Bit Rate=54 Mb/s
RTS thr:off Fragment thr:off
Encryption key:8E51-B6EA-A9CD-032C-A690-0EC2-D412-66B3 [3]
Link Quality=100/100 Signal level:-56 dBm Noise level:-71 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0




I have a bcm4312 which is able to connect via wpa_supplicant without any problems. The ra2870 works fine in windows at high speed and has worked for me at 802.11n with 2.6.29 kernels.

I am also unable to set the "rate" setting with iwconfig. I get an error message that the setting is not support by the driver.

It would be good if someone from ralink is able to comment here as this thread is the most extensive and well documented on the internet. I am surprised that this issue has gone unnoticed as I would expect them to test with wpa_supplicant before releasing the update.



iwconfig ra0 rate 270M
(no error message but also no effect)

iwconfig ra0 rate N
Error for wireless request "Set Bit Rate" (8B20) :
invalid argument "N".

iwpriv ra0 set rate=270
Interface doesn't accept private ioctl...
set (8BE2): Invalid argument

iwpriv ra0 set rate=N
Interface doesn't accept private ioctl...
set (8BE2): Invalid argument

[northbysouth]

First, thank you for working on and supporting the rt3070.

I have an rt3070 working under Fedora 12. The "mostly"
part is that I have to enable broadcast of the SSID from
my router. Otherwise the rt3070 won't connect. I have
a laptop with an Intel 2200BG and Fedora 12 that works
fine with the SSID broadcast turned off on the router.
So, I suspect it has something to do with the rt3070
driver or the RT3070STA.dat file.

The failure to connect happens with no security or
with WEP (haven't tested the issue with WPA).

iwlist ra0 scanning - sees the network ESSID:"" correctly
when SSID broadcast is turned off

I know that turning off the SSID broadcast is no longer
recommended, but that is how my router was set up.
I just wanted to let others know that there may be an
issue and try it with SSID broadcast turned on if they
are having trouble with a rt3070 based device. And
if the problem is reproducible it should probably be
considered a low priority bug.

[plamphere]

Thanks for all the hard work on these RPMs. Makes life easier for us n00bs...

I've got two devices that I can't get to work, and am not sure how to modify the .c file in the RPMs (or even how to pull down the right RPMs to modify). They are:

Linksys WUSB600N v2 - rt3070 (unlike the 2870 v1). USB ID 1737:0079
Hawking HWUN3 - rt 2870. USB ID 0e66:0013

If anyone can help a n00b get these added to the config file, I'd greatly appreciate it.

Thanks,
-P@

[justforgetme]

Ogetbilo, may I suggest that (at least for the f12 rt2870 case) you add the howto for blacklisting the rtXXXXusb drivers? on the first post of this topic i mean, so that newcomers can easily get done with this issue without needing to read the whole thread?

thanks

[vgivanovic]

I have two issues:

I can't get the rpmfusion RPMs to work at all.
I can't get ra0 (created by compiling the Ralink 3070 sources) to associate successfully.


I'm running Fedora 12 on my Gateway LT3101 netbook (AMD Athlon64 L110, 2GB, 128GB SSD) with a built-in Atheros AR9285 b/g wireless adapter and a Buffalo WLI-UC-GN USB g/n wireless dongle. I'm using NetworkManager.

I can get the Atheros to work poorly (frequent disconnects, low strength compared to the identical hardware running Windows 7), but I can't seem to get the Buffalo USB wireless to work with the most recent F12 kernel: 2.6.31.12-174.2.22.fc12.x86_64.

I have the rpmfusion-{free,non-free,free-updates,non-free-updates} repos enabled, and I've tried 'yum install rt3070' and then rebooting. Neither 'ifconfig' nor 'iwconfig' recognize the device, even after 'modprobe rt3070sta'. I've also tried 'rt2860' and 'rt2870' with the same results.

If I compile and install the Ralink 3070 driver that I downloaded from Ralink, I can get the ra0 device recognized, but it never associates correctly. I used the NetworkManager menu item "Connect to a hidden network..." and filled out the dialog box. The ra0 device doesn't associate correctly and NetworkManager reports in the syslog:

user_connection_updated_cb: assertion `old_connection != NULL' failed
Activation (ra0) starting connection 'HomeWLAN'
(ra0): device state change: 3 -> 4 (reason 0)
Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled...
Activation (ra0) Stage 1 of 5 (Device Prepare) started...
Activation (ra0) Stage 2 of 5 (Device Configure) scheduled...
Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
Activation (ra0) Stage 2 of 5 (Device Configure) starting...
(ra0): device state change: 4 -> 5 (reason 0)
Activation (ra0/wireless): access point 'HomeWLAN' has security, but secrets are required.
(ra0): device state change: 5 -> 6 (reason 0)
Activation (ra0) Stage 2 of 5 (Device Configure) complete.
Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled...
Activation (ra0) Stage 1 of 5 (Device Prepare) started...
(ra0): device state change: 6 -> 4 (reason 0)
Activation (ra0) Stage 2 of 5 (Device Configure) scheduled...
Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
Activation (ra0) Stage 2 of 5 (Device Configure) starting...
(ra0): device state change: 4 -> 5 (reason 0)
Activation (ra0/wireless): connection 'HomeWLAN' has security, and secrets exist. No new secrets needed.
Config: added 'ssid' value 'HomeWLAN'
Config: added 'scan_ssid' value '1'
Config: added 'key_mgmt' value 'WPA-PSK'
Config: added 'psk' value '<omitted>'
Activation (ra0) Stage 2 of 5 (Device Configure) complete.
(ra0): supplicant connection state: scanning -> disconnected
Config: set interface ap_scan to 2
(ra0): supplicant connection state: disconnected -> scanning
(ra0): supplicant connection state: scanning -> associating
ra0: link timed out.
Activation (ra0/wireless): association took too long.
(ra0): device state change: 5 -> 6 (reason 0)
Activation (ra0/wireless): asking for new secrets
(ra0): supplicant connection state: associating -> disconnected
(ra0): device state change: 6 -> 9 (reason 7)
Activation (ra0) failed for access point (HomeWLAN)
Marking connection 'HomeWLAN' invalid.
Activation (ra0) failed.
(ra0): device state change: 9 -> 3 (reason 0)
(ra0): deactivating device (reason: 0).


and then repetitively puts up a dialog asking me for the WPA2-PSK key.

Now, the interesting thing is that I can get the Ralink sources to create an ra0 device and associate if I use the previous F12 kernel: 2.6.31.12-174.2.19.fc12.x86_64.

The Ralink sources I've used are 2009_1110_RT3070_Linux_STA_v2.1.2.0 downloaded from http://www.ralinktech.com/support.php?s=2. (I modified the make files as recommended to support NetworkManager and WPA supplicant, and I created a symbolic link RT2870STA.dat that pointed to RT3070STA.dat.)

So, <whew!> any help would be appreciated. I'd prefer not to have to use the older F12 kernel.

P.S. I've posted my questions in this forum because it seems that others are doing so as well. I'd be happy to move my questions to another more appropriate forum if asked to do so.

[duende]

Vgivanovic, were you able to find a solution? I am having a problem which looks exactly the same as yours (I am using rt2860). Unfortunately, I was using mobile broadband rather than wireless for a while, so I do not have any working kernels any more.

With all the kernels I've got (the latest is 2.6.32.9-70.fc12.i686) I am having the same problem, and the logs look similar. Sometimes, after several tries, logging out and back in again, the wireless would eventually connect, but it really is a pain.

I would be grateful for ideas on what to do about it.

[vgivanovic]

@duende No, I was not able to get my Buffalo dongle to work well all the time.

The best luck I had was with the Fedora 11 kernel 2.6.30.10-105.2.23.fc11.x86_64 on my Fedora 12
system and the 2009_1110_RT3070_Linux_STA_v2.1.2.0 release from the Ralink web site.

I had to modify that release by setting "HAS_WPA_SUPPLICANT=y" and
"HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y" to in os/linux/config.mk, and by adding
"{USB_DEVICE(0x0411,0x015D)}, /* Buffalo WLI-UC-GN*/" as the last entry in the table rtusb_usb_id in os/linux/usb_main_dev.c.

With this compiled, installed and loaded (Oh, I forgot; there is a mismatch between the names of the
directory and dat file in /etc/Wireless and in the driver. Just add links so that any combination
works.) the dongle will associate most of the time and will stay up most of the time. However, it
disassociates frequently and the signal strength is low. Sometimes it refuses to re-associate. It
seemed to work best after a poweroff.

But, with this set up, my built-in Atheros AR9285 (ath9k driver, part of kernel) barely worked at
all: very low signal strength and constant disassociation.

So, now I'm using the latest Fedora 12 kernel 2.6.32.9-70.fc12.x86_64 with the AR9285 (ath9k
driver). This combination seems to work well, but now the RT3070 based Buffalo WLI-UC-GN dongle doesn't work at all: it never associates.

BTW, I tried every combination of drivers from the Ralink web site including the latest (2.3.0.1)
and 2.6.30/2.6.31 kernels I could find. They either don't work, don't compile or don't use a device
whose name I know. Usually the Ralink device is called ra0, but with 2.3.0.1 that device doesn't
exist and I don't know what name works. Setting "alias ra0 rt3070sta" in /etc/modeprobe.d/dist.conf
didn't help.

So, does anyone want to buy a perfectly good (under Windows 7 x64) Buffalo WLI-UC.GN dongle?

[duende]

Thanks for the reply.

At the moment I suspect that Network Manager could be the problem. When I disable network and then enable it again, Network Manager does not show available networks any more (or takes AGES before it does), while iwlist scanning shows networks correctly. Logging in and out sometimes solves the problem.

I remember that my old wireless card (Intersil Prism 2.5) did not work with WPA and Network Manager - I either could not connect or the connection was breaking often, but the card worked perfectly when I was using networking scripts. Perhaps this is something similar. I'm intending to try to use scripts in this case (when I've got time), and see if it helps. Network Manager is a lot more convenient, though.

EDIT: I tried with scripts and it does not help - sometimes I get a connection and sometimes not, the same as with NM.

[Overlord Laharl]

I could use a little help regarding the RT2870sta drivers on Fedora 10.

I have recently bought an Aztech WL552USB WiFi adapter, which, according to what i have found out, makes use of the RT2870 chipset. However, when i plugged the WL552USB into my PC, nothing happened. And checking iwconfig revealed that no new interface was set up: there was only lo, eth0 and pan0.

Thinking that there were no drivers for the RT2870, i downloaded the source from Ralink's website and installed the driver by running the following commands:

make
su -
make install

At this point, the drivers seemingly installed, but there was still no wlan0 or ra0 interface, and i have no idea how to create one as well. Even after running /sbin/insmod/rt2870sta.ko, there is still no interface at all. Because of that, my WiFi stick is still useless and i cannot get online with Fedora (im posting this from within Windows).

Am i misinterpreting the instructions in the readme for Ralink's rt2870sta driver? Can anyone be kind enough to walk me through the installation procedure for Ralink's RT2870sta driver? I dont really want to make use of the rpmfusion drivers for rt2870 for a certain reason.

[ogetbilo]

Hi all, sorry I have been very busy in the past few months and I didn't have much time to keep the drivers in shape. FYI there is the 2.3.0.0 version of rt2860 drivers that is in the rpmfusion's testing repo. They will go to stable if no problems get reported.

There is also a 2.3.0.0 version of the rt2870 driver. However this version is buggy, and it causes occasional freezes. We will stick to the 2.1.2.0 version for the time being.

If there are any problems that you couldn't solve in the last 4-5 months, feel free to bring it up again.


Overlord Laharl,
Can you post here your lsusb output? It might happen that your device is so new that the drivers need to be updated to recognize it. I need to know the busID's etc to make sure.
edit: hmm I see that you are asking for the F-10 driver. F-10 is no longer supported and I don't think I have the resources to make an RPM for you. Can you update to a more recent Fedora?

[Overlord Laharl]

Hi all, sorry I have been very busy in the past few months and I didn't have much time to keep the drivers in shape. FYI there is the 2.3.0.0 version of rt2860 drivers that is in the rpmfusion's testing repo. They will go to stable if no problems get reported.

There is also a 2.3.0.0 version of the rt2870 driver. However this version is buggy, and it causes occasional freezes. We will stick to the 2.1.2.0 version for the time being.

If there are any problems that you couldn't solve in the last 4-5 months, feel free to bring it up again.


Overlord Laharl,
Can you post here your lsusb output? It might happen that your device is so new that the drivers need to be updated to recognize it. I need to know the busID's etc to make sure.
edit: hmm I see that you are asking for the F-10 driver. F-10 is no longer supported and I don't think I have the resources to make an RPM for you. Can you update to a more recent Fedora?

thanks, but it seems that i have managed to solve the problem on my own. Apparently, the rt2870sta driver offered by ralink was not the one i needed for my device but the 3070sta was. But compiling the 3070sta driver made calls to the rt2870sta driver, so i just compiled and installed both drivers, rmmod the rt2870sta driver, modprobe-d the rt3070sta driver and everything is now working.

[duende]

Hi all, sorry I have been very busy in the past few months and I didn't have much time to keep the drivers in shape. FYI there is the 2.3.0.0 version of rt2860 drivers that is in the rpmfusion's testing repo. They will go to stable if no problems get reported.


Many thanks Ogetbilo!

I have installed the driver rt2860 from the testing repo. This seems to have solved my problem.

Thanks again, I really appreciate your efforts!

[MidnightWatcher]

Does the DVD ISO of FC12 have the rt2870 drivers built in? I'm a total noob that this and can't get the driver to install (installed the live CD).

[ogetbilo]

Does the DVD ISO of FC12 have the rt2870 drivers built in? I'm a total noob that this and can't get the driver to install (installed the live CD).

Could you follow the steps given in the first post of the thread? Let me know if you find something confusing. Thanks

[bonedome]

Hello
I got my son an eeepc 1001ha last xmas and after weeks of trying various distros (mandriva, 3 different ubuntu's, fedora12 and puppy) and bodge ups I gave up on having a linux/wireless combo on it.
I then read the rt 2860 driver "might" make it into the 2.6.32 kernel if not deffo the 2.6.33, patience thought I, I then promptly forgot all about it, then stumbled upon this thread http://forums.fedoraforum.org/showthread.php?t=236729 can anyone tell me if the rt2860 driver is built into the 2.6.32 kernel ? if so how can I tell and can I use fedora 13 with an older kernel ?
He would be running fedora from a live usb stick with a small amount of persistence and I just can't be arsed building my own kernel etc.
I also read an interview a good few months ago with one of the top kernel gods who is responsible for kernel modules/drivers and he said he'd almost run out of things to do, well here's one for you.
All in all it seems to me ralink are a total shambles "there ya go Mr Gates one working wireless driver. Linux !, oh yeah totally forgot about them, here's the source code, figure it out yourself" :D

[rafa1981]

thanks, but it seems that i have managed to solve the problem on my own. Apparently, the rt2870sta driver offered by ralink was not the one i needed for my device but the 3070sta was. But compiling the 3070sta driver made calls to the rt2870sta driver, so i just compiled and installed both drivers, rmmod the rt2870sta driver, modprobe-d the rt3070sta driver and everything is now working.

I don't know how did you manage to discover that, but itś worling with the "D-Link System DWA-140 RangeBooster N USB Adapter(rev.B2)" dongle on kernel "2.6.33.3-85.fc13.x86_64
", before that I had everything recognized, but the LED of the dongle wasn't blinking and I wasn't able to scan, same case as you.

The steps I did were:

-Download last rt2870 and 3070 from ralink website.
-Unpack both.
-Edit os/linux/config.mk, and change the "n" for a "y" in the two WPA Supplicant related lines of the rt2870 driver (as usual).
-Blacklist all rt2870 and rt2x00 devices that appeared with a lsmod |grep rt command on etc/modprobe.d/blacklist.conf.
-"make" and "make install" of rt2870.
-"make" and "make install" of rt3070.
-Reboot

Thanks for that, nice find.

[jimmy2975]

Before I buy the card, will the method (mentioned in the first post of this thread) work for the linksys WUSB600N cards on

Linux linuxhome 2.6.32.12-115.fc12.x86_64 #1 SMP Fri Apr 30 19:46:25 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

I plan on getting this USB N adapter and a router that supports N speeds.

Thanks in advance for any comments/suggestions.

Jimmy

[weitjong]

Before I buy the card, will the method (mentioned in the first post of this thread) work for the linksys WUSB600N cards on

Linux linuxhome 2.6.32.12-115.fc12.x86_64 #1 SMP Fri Apr 30 19:46:25 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

I bought this USB adapter together with Linksys WRT610N. It works on my F12 and F13 x86_64 after I install akmod-rt2870 package from RpmFusion. I did not follow exactly the steps in the first post but basically the akmod-rt2870 is achieving the same things:

1. blacklist "built-in" but "broken" kernel module.
2. install rt2870.
3. install the kernel module that is compatible with currently running kernel, i.e. whatever kmod-rt2870-2.6.xx.x-xxx that matches with your running kernel. In fact, the akmods will even build one automatically during boot when the matching kmod-rt2870 is still not yet available in the RpmFusion repo. This may happen sometimes when newer kernel is available in the Fedora repo and RpmFusion lags behind.

In short, all you need is just installing "akmod-rt2870". And run yum update one more time to fetch the matching kmod-rt2870.

[IrishBouzouki]

okay, this may be a netmon problem, but I just did the change from kernel *.12 to *.14 and now, even though my rt2870 usb dongle is lit, there is no network connection shown on the panel applet (and just in case I verified indeed no internet browsing etc).

when I go back to *.12 kernel using grub it comes up just fine.

several months ago when first getting fc12 up and running I followed the steps in this thread, but it has been ages since I have even been on this forum.

an odd note - the panel applet for netmon disappeared altogether under the *.12 kernel during some update a while back, but it still seems to work in that I have network connectivity. just an fyi, don't want to confuse the issue.

anyone else having trouble with the new kernel and rt2870?

anything I can do to provide more info?

EDIT - this problem was, as suggested, simply the lack of the kmod for the new kernel version, now that this new kmod is in the repos it works just fine again with the new kernel on my system. thanks.

[mr xray mind]

I just installed F-13 on my eee 901. I have the Ralink RT2860. The card is in and running fine. It sees both of my wireless networks, but is unable to connect to either one of them One is a verizon broadband wireless connection using WPA-TKIP security. The other is a D-Link wireless router using 128-bit WEP encryption. It's also unable to connect to my D-Link router with the encryption turned off. My installation is still at default from an F13 installation. It sees them but is unable to connect to them. Does anyone have any suggestions for where I should look to for my problem?

---------- Post added at 11:00 AM CDT ---------- Previous post was at 10:36 AM CDT ----------

Addendum: I un-ticked the 'Enable Networking' box from right clicking the icon in the panel. I re-ticked the enable networking box, Then I was able to connect to my unencrypted network. I thought I would try connecting to my encrypted network. It failed again. Then I tried the unencrypted network and failed again. I can not connect to the internet and update my system. I could download from another computer if I knew which packages need the updates Any suggestions?

[justforgetme]

okay, this may be a netmon problem, but I just did the change from kernel *.12 to *.14 and now, even though my rt2870 usb dongle is lit, there is no network connection shown on the panel applet (and just in case I verified indeed no internet browsing etc).

when I go back to *.12 kernel using grub it comes up just fine.

several months ago when first getting fc12 up and running I followed the steps in this thread, but it has been ages since I have even been on this forum.

an odd note - the panel applet for netmon disappeared altogether under the *.12 kernel during some update a while back, but it still seems to work in that I have network connectivity. just an fyi, don't want to confuse the issue.

anyone else having trouble with the new kernel and rt2870?

anything I can do to provide more info?

IrishBouzouki, there are some other people that have the same problem. the problem is not the kernel but the missing kmod-rt**** package the driver needs to work.

there is an open thread on the issue here: http://forums.fedoraforum.org/showthread.php?t=247139

[IrishBouzouki]

IrishBouzouki, there are some other people that have the same problem. the problem is not the kernel but the missing kmod-rt**** package the driver needs to work.

there is an open thread on the issue here: http://forums.fedoraforum.org/showthread.php?t=247139

I guess this is one of those times where having the akmod works better...

[jimmy2975]

THanks for the reply!! So I bought this WUSB600N wireless adapter. THe only way I could find out what driver this might need is from the cd and it had rt2870....so I installed kmod-2870, rt2870 files and when I reboot I do not see the wirless adapter turning on or any SSID showing up. I have also blacklisted blacklist rt2800usb. Here is what I have

uname -a
Linux linuxhome 2.6.32.12-115.fc12.x86_64 #1 SMP Fri Apr 30 19:46:25 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

lsmod |grep rt
rt2870sta 474441 0
exportfs 3504 1 nfsd
parport_pc 21189 0
parport 31685 2 ppdev,parport_pc
You have new mail in /var/spool/mail/root

rpm -qa |grep kmod
kmod-nvidia-195.36.24-1.fc12.2.x86_64
kmodtool-1-18.fc11.noarch
kmod-wl-2.6.32.12-115.fc12.x86_64-5.60.48.36-1.fc12.10.x86_64
kmod-rt2870-2.1.2.0-6.fc12.19.x86_64
kmod-ndiswrapper-2.6.32.11-99.fc12.x86_64-1.54-4.fc12.30.x86_64
kmod-rt3070-2.6.32.12-115.fc12.x86_64-2.1.1.0-3.fc12.27.x86_64
kmod-nvidia-2.6.32.11-99.fc12.x86_64-195.36.15-1.fc12.2.x86_64
libmikmod-3.2.0-9.beta2.fc12.x86_64
kmod-wl-5.60.48.36-1.fc12.10.x86_64
kmod-nvidia-2.6.32.12-115.fc12.x86_64-195.36.24-1.fc12.2.x86_64
kmod-wl-2.6.32.11-99.fc12.x86_64-5.60.48.36-1.fc12.5.x86_64
akmods-0.3.6-3.fc12.noarch
kmod-rt2860-2.3.0.0-1.fc12.x86_64
kmod-rt3070-2.1.1.0-3.fc12.27.x86_64
kmod-rt2860-2.6.32.12-115.fc12.x86_64-2.3.0.0-1.fc12.x86_64
kmod-rt2870-2.6.32.12-115.fc12.x86_64-2.1.2.0-6.fc12.19.x86_64

I don't understand why this is not working. I also tried akmod with no luck. Also any help in getting this to work is much appreciated!!! If I have to start clean that is ok with me.

Thanks
Jimmy

[mr xray mind]

Jimmy, I got this reply in a different, more current thread on these wireless cards. If you go to this bugzilla report and skim through it you will see that there are work arounds, but no fixes yet. https://bugzilla.redhat.com/show_bug.cgi?id=570869 About half way through there is a way to make your own driver, but it will only work till you up your kernel, then you'll have to redo it. My situation is worse, in that I for my computer, the only way I can get online is wifi. If it doesn't work, I have to do all my installs manually.

[jimmy2975]

lsusb | grep Link gives me

Bus 001 Device 004: ID 1737:0079 Linksys

Does anyone with a working adapter post eh device ID? I am trying to figure out if there is some version 2 WUSB600N out there that might be using some other driver other that rt28xx series????

Thanks
Jimmy

[weitjong]

lsusb | grep Link gives me
Bus 001 Device 004: ID 1737:0079 Linksys
Does anyone with a working adapter post eh device ID?

I think you will get better responses if you open a new thread. :) :). Anyway, these are what shown in my PC when the USB adapter is attached.
[weitjong@icecastle ~]$ lsusb |grep Linksys
Bus 001 Device 008: ID 1737:0071 Linksys WUSB600N Dual-Band Wireless-N USB Network Adapter
[weitjong@icecastle ~]$ uname -a
Linux icecastle 2.6.33.5-124.fc13.x86_64 #1 SMP Fri Jun 11 09:38:12 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
[weitjong@icecastle ~]$ lsmod |grep rt...0
rt2870sta 464216 1
[weitjong@icecastle ~]$ rpm -qa |egrep .*kmod-rt |sort
akmod-rt2870-2.1.2.0-6.fc13.5.x86_64
kmod-rt2870-2.6.33.4-95.fc13.x86_64-2.1.2.0-6.fc13.6.x86_64
kmod-rt2870-2.6.33.5-112.fc13.x86_64-2.1.2.0-6.fc13.7.x86_64
kmod-rt2870-2.6.33.5-124.fc13.x86_64-2.1.2.0-6.fc13.5.x86_64
Snippet of /var/log/messages (I have to cut away some formatting to reduce the size of my post as it exceeds the forum limit).
kernel: usb 1-4.1.4: new high speed USB device using ehci_hcd and address 8
kernel: usb 1-4.1.4: New USB device found, idVendor=1737, idProduct=0071
kernel: usb 1-4.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 1-4.1.4: Product: Dual-Band Wireless-N USB Network Adapter
kernel: usb 1-4.1.4: Manufacturer: Cisco-Linksys LLC
kernel: rtusb init --->
kernel:
kernel:
kernel: === pAd = ffffc90011097000, size = 501352 ===
kernel:
kernel: <-- RTMPAllocAdapterBlock, Status=0
kernel: usbcore: registered new interface driver rt2870
NetworkManager[1510]: <info> (ra0): driver does not support SSID scans (scan_capa 0x00).
NetworkManager[1510]: <info> (ra0): new 802.11 WiFi device (driver: 'usb' ifindex: 6)
NetworkManager[1510]: <info> (ra0): exported as /org/freedesktop/NetworkManager/Devices/2
NetworkManager[1510]: <info> (ra0): now managed
NetworkManager[1510]: <info> (ra0): device state change: 1 -> 2 (reason 2)
NetworkManager[1510]: <info> (ra0): bringing up device.
kernel: <-- RTMPAllocTxRxRingMemory, Status=0
kernel: -->RTUSBVenderReset
kernel: <--RTUSBVenderReset
kernel: Key1Str is Invalid key length(0) or Type(0)
kernel: Key2Str is Invalid key length(0) or Type(0)
kernel: Key3Str is Invalid key length(0) or Type(0)
kernel: Key4Str is Invalid key length(0) or Type(0)
kernel: 1. Phy Mode = 5
kernel: 2. Phy Mode = 5
kernel: RTMPSetPhyMode: channel is out of range, use first channel=1
kernel: 3. Phy Mode = 5
kernel: MCS Set = ff ff 00 00 01
kernel: <==== rt28xx_init, Status=0
kernel: 0x1300 = 00064300
NetworkManager[1510]: <info> (ra0): preparing device.
NetworkManager[1510]: <info> (ra0): deactivating device (reason: 2).
NetworkManager[1510]: <info> (ra0): supplicant interface state: starting -> ready
NetworkManager[1510]: <info> (ra0): device state change: 2 -> 3 (reason 42)
avahi-daemon[1521]: Registering new address record for fe80::21e:e5ff:fedf:db8 on ra0.*.
ntpd[1799]: Listen normally on 8 ra0 fe80::21e:e5ff:fedf:db8 UDP 123
NetworkManager[1510]: <info> Activation (ra0) starting connection 'Auto SouthPole_5GHz'
NetworkManager[1510]: <info> (ra0): device state change: 3 -> 4 (reason 0)
NetworkManager[1510]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[1510]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[1510]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[1510]: <info> Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[1510]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[1510]: <info> (ra0): device state change: 4 -> 5 (reason 0)
NetworkManager[1510]: <info> Activation (ra0/wireless): connection 'Auto SouthPole_5GHz' has security, and secrets exist. No new secrets needed.
NetworkManager[1510]: <info> Config: added 'ssid' value 'SouthPole_5GHz'
NetworkManager[1510]: <info> Config: added 'scan_ssid' value '1'
NetworkManager[1510]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
NetworkManager[1510]: <info> Config: added 'psk' value '<omitted>'
NetworkManager[1510]: <info> Config: added 'proto' value 'WPA RSN'
NetworkManager[1510]: <info> Activation (ra0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[1510]: <info> Config: set interface ap_scan to 1
NetworkManager[1510]: <info> (ra0): supplicant connection state: scanning -> disconnected
NetworkManager[1510]: <info> (ra0): supplicant connection state: disconnected -> associating
NetworkManager[1510]: <info> (ra0): supplicant connection state: associating -> associated
kernel: Rcv Wcid(1) AddBAReq
kernel: Start Seq = 00000000
NetworkManager[1510]: <info> (ra0): supplicant connection state: associated -> 4-way handshake
NetworkManager[1510]: <info> (ra0): supplicant connection state: 4-way handshake -> group handshake
NetworkManager[1510]: <info> (ra0): supplicant connection state: group handshake -> completed
NetworkManager[1510]: <info> Activation (ra0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'SouthPole_5GHz'.
NetworkManager[1510]: <info> Activation (ra0) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager[1510]: <info> Activation (ra0) Stage 3 of 5 (IP Configure Start) started...
NetworkManager[1510]: <info> (ra0): device state change: 5 -> 7 (reason 0)
NetworkManager[1510]: <info> Activation (ra0) Beginning DHCPv4 transaction (timeout in 45 seconds)
NetworkManager[1510]: <info> dhclient started with pid 2888
NetworkManager[1510]: <info> Activation (ra0) Stage 3 of 5 (IP Configure Start) complete.
Jun 17 12:36:00 icecastle dhclient[2888]: Internet Systems Consortium DHCP Client 4.1.1-P1
Jun 17 12:36:00 icecastle dhclient[2888]: Copyright 2004-2010 Internet Systems Consortium.
Jun 17 12:36:00 icecastle dhclient[2888]: All rights reserved.
Jun 17 12:36:00 icecastle dhclient[2888]: For info, please visit https://www.isc.org/software/dhcp/
Jun 17 12:36:00 icecastle dhclient[2888]:
Jun 17 12:36:00 icecastle NetworkManager[1510]: <info> (ra0): DHCPv4 state changed nbi -> preinit
Jun 17 12:36:00 icecastle dhclient[2888]: Listening on LPF/ra0/00:1e:e5:df:0d:b8
Jun 17 12:36:00 icecastle dhclient[2888]: Sending on LPF/ra0/00:1e:e5:df:0d:b8
Jun 17 12:36:00 icecastle dhclient[2888]: Sending on Socket/fallback
Jun 17 12:36:01 icecastle dhclient[2888]: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 3
Jun 17 12:36:01 icecastle dhclient[2888]: DHCPOFFER from 192.168.1.1
Jun 17 12:36:01 icecastle dhclient[2888]: DHCPREQUEST on ra0 to 255.255.255.255 port 67
Jun 17 12:36:01 icecastle dhclient[2888]: DHCPACK from 192.168.1.1
Jun 17 12:36:01 icecastle dhclient[2888]: bound to 192.168.1.110 -- renewal in 37260 seconds.
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> (ra0): DHCPv4 state changed preinit -> bound
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> Activation (ra0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> Activation (ra0) Stage 4 of 5 (IP4 Configure Get) started...
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> address 192.168.1.110
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> prefix 24 (255.255.255.0)
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> gateway 192.168.1.1
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> nameserver '192.168.1.1'
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> nameserver '165.21.100.88'
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> nameserver '165.21.83.88'
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> Activation (ra0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> Activation (ra0) Stage 4 of 5 (IP4 Configure Get) complete.
Jun 17 12:36:01 icecastle NetworkManager[1510]: <info> Activation (ra0) Stage 5 of 5 (IP Configure Commit) started...
Jun 17 12:36:01 icecastle avahi-daemon[1521]: Joining mDNS multicast group on interface ra0.IPv4 with address 192.168.1.110.
Jun 17 12:36:01 icecastle avahi-daemon[1521]: New relevant interface ra0.IPv4 for mDNS.
Jun 17 12:36:01 icecastle avahi-daemon[1521]: Registering new address record for 192.168.1.110 on ra0.IPv4.
Jun 17 12:36:02 icecastle ntpd[1799]: Listen normally on 9 ra0 192.168.1.110 UDP 123
Jun 17 12:36:02 icecastle NetworkManager[1510]: <info> Policy set 'System eth0' (eth0) as default for IPv4 routing and DNS.
Jun 17 12:36:02 icecastle NetworkManager[1510]: <info> (ra0): device state change: 7 -> 8 (reason 0)
Jun 17 12:36:02 icecastle NetworkManager[1510]: <info> (ra0): roamed from BSSID 00:21:29:CF:DB:15 (SouthPole_5GHz) to (none) ((none))
Jun 17 12:36:02 icecastle NetworkManager[1510]: <info> Activation (ra0) successful, device activated.
Jun 17 12:36:02 icecastle NetworkManager[1510]: <info> Activation (ra0) Stage 5 of 5 (IP Configure Commit) complete.
From the screenshot you can see the adapter detects both the usual 2.4 GHz as well as 5 GHz radio from my WRT610N wireless router.
19704
And the wireless interface is up together with my wired one.
19705

[jimmy2975]

Thanks for the reply. I will open a new thread.
Jimmy

[IrishBouzouki]

I think you will get better responses if you open a new thread. We are not supposed to ask questions in the "Guides" section :).

I do not believe this is correct. My guess is that the poor guy in charge of the package would rather see all the information here in one place than scattered across multiple threads.

Looking through this thread one can see that it is in fact chock full of questions, and answers, exactly like this one. As are several other similar howto threads (such as the ever-popular nvidia).

---------- Post added at 07:42 AM CDT ---------- Previous post was at 07:35 AM CDT ----------

lsusb | grep Link gives me

Bus 001 Device 004: ID 1737:0079 Linksys

Does anyone with a working adapter post eh device ID? I am trying to figure out if there is some version 2 WUSB600N out there that might be using some other driver other that rt28xx series????

Thanks
Jimmy

See my posts in this thread #143 and #153. I have the exact same device. It shows the command-line details for blacklisting the non-functional kernel stuff and also has the device id's etc.

Might help, might not.

[weitjong]

He is asking a specific information regarding WUSB600N which should get him more replies if he opens a new thread. You are correct about asking the question part. I will edit my post.

---------- Post added at 08:10 PM CDT ---------- Previous post was at 07:43 PM CDT ----------

Jimmy is using F12. In F13, the rt2870 package includes the blacklist configuration file already.
[weitjong@icecastle ~]$ rpm -ql rt2870
/etc/Wireless
/etc/Wireless/RT2870STA
/etc/Wireless/RT2870STA/RT2870STA.dat
/etc/Wireless/RT2870STA/RT2870STACard.dat
/etc/modprobe.d/blacklist-rt2800usb.conf
/usr/share/doc/rt2870-2.1.2.0
/usr/share/doc/rt2870-2.1.2.0/README_STA
/usr/share/doc/rt2870-2.1.2.0/ReleaseNotes
/usr/share/doc/rt2870-2.1.2.0/iwpriv_usage.txt
/usr/share/doc/rt2870-2.1.2.0/sta_ate_iwpriv_usage.txt
/usr/share/doc/rt2870-2.1.2.0/suspend.sh

The F12 version of the rt2870 package should have this blacklist configuration file as well. Also his lsmod output shows the correct rt2870sta being loaded instead of the broken kernel module. So, there may be another problem.

[Moonf4]

I also have the Linksys WUSB600N v 1 adapter and would like to get it working in FC 12. I read somewhere that just updating the firmware from the ralink web site will get it working, but when I download the firmware update, I see a .bin file and no README or instructions. wth?

I have attempted to go through this thread, but that has added more confusion. 14 pages long starting in 2008? Does anyone have a simple and concise way to get this wireless adapter working in FC12?

I attempted the steps in the first page of this thread, but the rpm's I downloaded fail to install due to dependencies. My system is running MythDora 12.23 so I have to be careful what kind of yum updates I run.

Thanks,

[leigh123linux]

I also have the Linksys WUSB600N v 1 adapter and would like to get it working in FC 12. I read somewhere that just updating the firmware from the ralink web site will get it working, but when I download the firmware update, I see a .bin file and no README or instructions. wth?

I have attempted to go through this thread, but that has added more confusion. 14 pages long starting in 2008? Does anyone have a simple and concise way to get this wireless adapter working in FC12?

I attempted the steps in the first page of this thread, but the rpm's I downloaded fail to install due to dependencies. My system is running MythDora 12.23 so I have to be careful what kind of yum updates I run.

Thanks,


Follow post #1 and rebuild the srpms or switch to fedora ;)

[Moonf4]

I am using Fedora. Fedora 12, hence the name MythDora 12.

[Billy_Mays]

Jon, give me the outputs of
rpm -qa |grep kernel
rpm -qa |grep 2860
uname -r
lsmod |grep 2860
lspci |grep 2860[chaos@localhost ~]$ rpm -qa |grep kernel
kernel-PAE-devel-2.6.33.5-124.fc13.i686
abrt-addon-kerneloops-1.1.1-1.fc13.i686
kernel-PAE-2.6.33.5-124.fc13.i686
kernel-devel-2.6.33.5-124.fc13.i686
kernel-headers-2.6.33.5-124.fc13.i686

[chaos@localhost ~]$ rpm -qa |grep 2860
[chaos@localhost ~]$

[chaos@localhost ~]$ uname -r
2.6.33.5-124.fc13.i686.PAE
[chaos@localhost ~]$ lsmod |grep 2860
[chaos@localhost ~]$


i installed akmod-2860 and it would appear it's working. i have my AP showing up in network manager but i can't connect to it.

[Moonf4]

Here is where I am at:

FC 12 (mythdora 12.23) Linksys WUSB600N

[root@lunarshot ~]# uname -r
2.6.32.14-127.fc12.i686

[root@lunarshot ~]# rpm -qa |grep kernel
kernel-2.6.32.11-99.fc12.i686
kernel-firmware-2.6.32.14-127.fc12.noarch
kernel-2.6.32.14-127.fc12.i686

[root@lunarshot ~]# rpm -qa |grep 2870
kmod-rt2870-2.1.2.0-6.fc12.20.i686
kmod-rt2870-2.6.32.14-127.fc12.i686-2.1.2.0-6.fc12.20.i686
rt2870-2.1.2.0-2.fc12.1.noarch

[root@lunarshot ~]# lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 1737:0079 Linksys
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I was going to install akmod-rt2870, but it is saying it needs to install 19 packages.

yum install akmod-rt2870

================================================== ================================================== ==========================
Package Arch Version Repository Size
================================================== ================================================== ==========================
Installing:
akmod-rt2870 i686 2.1.2.0-6.fc12 mythdora 667 k
Installing for dependencies:
akmods noarch 0.3.6-3.fc12 mythdora 16 k
cloog-ppl i686 0.15.7-1.fc12 fedora 81 k
cpp i686 4.4.3-4.fc12 mythdora 3.3 M
elfutils i686 0.147-1.fc12 updates 204 k
elfutils-libs i686 0.147-1.fc12 updates 189 k
fakeroot i686 1.12.2-22.fc12 fedora 71 k
fakeroot-libs i686 1.12.2-22.fc12 fedora 49 k
gcc i686 4.4.3-4.fc12 mythdora 8.1 M
glibc-devel i686 2.11.2-1 updates 955 k
glibc-headers i686 2.11.2-1 updates 591 k
kernel-devel i686 2.6.32.14-127.fc12 updates 6.1 M
kernel-headers i686 2.6.32.14-127.fc12 updates 754 k
kmodtool noarch 1-18.fc11 mythdora 13 k
mpfr i686 2.4.1-5.fc12 mythdora 154 k
ppl i686 0.10.2-10.fc12 fedora 1.1 M
procmail i686 3.22-25.fc12 fedora 152 k
rpm-build i686 4.7.2-1.fc12 mythdora 118 k
rpmdevtools noarch 7.8-1.fc12 mythdora 109 k
Updating for dependencies:
elfutils-libelf i686 0.147-1.fc12 updates 165 k
glibc i686 2.11.2-1 updates 4.2 M
glibc-common i686 2.11.2-1 updates 14 M

Transaction Summary
================================================== ================================================== ==========================
Install 19 Package(s)
Upgrade 3 Package(s)

Trying to figure out if break anything.

[ogetbilo]

Hello
I got my son an eeepc 1001ha last xmas and after weeks of trying various distros (mandriva, 3 different ubuntu's, fedora12 and puppy) and bodge ups I gave up on having a linux/wireless combo on it.
I then read the rt 2860 driver "might" make it into the 2.6.32 kernel if not deffo the 2.6.33, patience thought I, I then promptly forgot all about it, then stumbled upon this thread http://forums.fedoraforum.org/showthread.php?t=236729 can anyone tell me if the rt2860 driver is built into the 2.6.32 kernel ? if so how can I tell and can I use fedora 13 with an older kernel ?
He would be running fedora from a live usb stick with a small amount of persistence and I just can't be arsed building my own kernel etc.
I also read an interview a good few months ago with one of the top kernel gods who is responsible for kernel modules/drivers and he said he'd almost run out of things to do, well here's one for you.
All in all it seems to me ralink are a total shambles "there ya go Mr Gates one working wireless driver. Linux !, oh yeah totally forgot about them, here's the source code, figure it out yourself" :D

Hi, the wireless module that comes with the kernel does not yet support the ralink devices properly. However, if you follow the instructions in thee first post of this thread for rt2860, I expect it to work.

[ogetbilo]

lsusb | grep Link gives me

Bus 001 Device 004: ID 1737:0079 Linksys

Does anyone with a working adapter post eh device ID? I am trying to figure out if there is some version 2 WUSB600N out there that might be using some other driver other that rt28xx series????

Thanks
Jimmy

Hi Jimmy,
1737:0079 Linksys is not supported by any of our kmod packages. I believe that this device is a rt2870. I am building the newest 2.4.0.0 version for rt2870 now. I can add your device to the list to the supported hardware in our kmod-rt2870 module. But I need you to test it before I can push it to the rpmfusion repos.

Are you comfortable with rebuilding SRPMs? That would make my life easier. Otherwise post me the kernel version you are running and I'll try to do something else.

[ogetbilo]

Here is where I am at:

FC 12 (mythdora 12.23) Linksys WUSB600N
[cut]
Bus 001 Device 002: ID 1737:0079 Linksys
[cut]

Trying to figure out if break anything.

Moonf4, please see the above post. Are you ready to be a tester?

[ogetbilo]

I just installed F-13 on my eee 901. I have the Ralink RT2860. The card is in and running fine. It sees both of my wireless networks, but is unable to connect to either one of them One is a verizon broadband wireless connection using WPA-TKIP security. The other is a D-Link wireless router using 128-bit WEP encryption. It's also unable to connect to my D-Link router with the encryption turned off. My installation is still at default from an F13 installation. It sees them but is unable to connect to them. Does anyone have any suggestions for where I should look to for my problem?

---------- Post added at 11:00 AM CDT ---------- Previous post was at 10:36 AM CDT ----------

Addendum: I un-ticked the 'Enable Networking' box from right clicking the icon in the panel. I re-ticked the enable networking box, Then I was able to connect to my unencrypted network. I thought I would try connecting to my encrypted network. It failed again. Then I tried the unencrypted network and failed again. I can not connect to the internet and update my system. I could download from another computer if I knew which packages need the updates Any suggestions?

Hi, did you try the kmod-rt2860 package from rpmfusion? It sounds like you are using the module that comes with the standard Fedora kernel, which doesn't work for the time being. I suggest you to follow the first post of this thread.

[Moonf4]

Sure, I will test. I will need some assistance if I need to compile SRPMS.

Just let me know what you need.

Mike Moon

[ogetbilo]

Alright, since I don't know your experience level with Linux/Fedora, I will give a generic guideline. Let me know if you need me to make any step clearer.

Unfortunately, upon some further investigation, I found that the 1737:0079 Linksys device might be a rt3572, for which we have no kmod yet on rpmfusion. However, the rt2870 driver might work if you follow these instructions, or work only with limited functionality, or not work at al. Note that the rt3572 driver on Ralink's website won't work without a hack (you need to add your device ID 1737:0079 to the list of supported devices). I'll explain the hack if you can't get this working with rt2870 driver. Here we go:

1- First of all, make sure that your system is up to date and you booted into the newest kernel.
2- You need to setup a rpm build tree in your home directory. To do this install the rpmdevtools and rpm-build packages. Then as a regular user (not root), do
$ rpmdev-setuptree
This will setup an rpmbuild tree in your home directory.
3- Download these 2 SRPMs:
http://6mata.com:8014/review/rt2870-kmod-2.4.0.0-0.1.Moon.fc13.src.rpm
http://6mata.com:8014/review/rt2870-2.4.0.0-0.1.Moon.fc13.src.rpm
These have the device IDs added for you device.
4- You will try to build RPMs from the SRPMs next. To do this, go to the directory where you downloaded the SRPMs and build both packages (as regular user)
$ rpmbuild --rebuild rt2870-kmod-2.4.0.0-0.1.Moon.fc13.src.rpm
$ rpmbuild --rebuild rt2870-2.4.0.0-0.1.Moon.fc13.src.rpm
I expect this the fail in your first couple attempts, since you probably don't have all the build dependencies installed. Read the error messages carefully and install the missing packages, and try the above commands again.
5- At the end of the day, you will have your RPMs built in ~/rpmbuild/RPMS/noarch/*.rpm and ~/rpmbuild/RPMS/<your arch>/*.rpm. Install them and see how things go.

[Moonf4]

When I bought this Linksys WUSB600N I was informed it was version 1, but I just checked the microscopic print on the back which says v 2, which I believe is the rt3572 chipset. grrrhhhhh.

[ogetbilo]

I would still try the rt2870 driver that I made above. It might work. For instance, my rt2870 card works with both rt2870 and rt3070 drivers.

[Moonf4]

I have a dependency issue when attempting the build the first rpm. It needs the i386 version, but I have the i686 version on my system. Also, should I create an orcan group?

[mythtv@lunarshot ~]$ rpmbuild --rebuild rt2870-kmod-2.4.0.0-0.1.Moon.fc13.src.rpm
Installing rt2870-kmod-2.4.0.0-0.1.Moon.fc13.src.rpm
warning: user orcan does not exist - using root
warning: group orcan does not exist - using root
warning: user orcan does not exist - using root
warning: group orcan does not exist - using root
warning: user orcan does not exist - using root
warning: group orcan does not exist - using root
warning: user orcan does not exist - using root
warning: group orcan does not exist - using root
warning: user orcan does not exist - using root
warning: group orcan does not exist - using root
warning: user orcan does not exist - using root
warning: group orcan does not exist - using root
warning: user orcan does not exist - using root
warning: group orcan does not exist - using root
warning: user orcan does not exist - using root
warning: group orcan does not exist - using root
error: Failed build dependencies:
buildsys-build-rpmfusion-kerneldevpkgs-current-i386 is needed by rt2870-kmod-2.4.0.0-0.1.Moon.md12.src


[mythtv@lunarshot ~]$ rpm -qa|grep buildsys
buildsys-build-rpmfusion-12-26.i686
buildsys-build-rpmfusion-kerneldevpkgs-current-12-26.i686

[ogetbilo]

Hmm, could you try

rpmbuild --target i686 --rebuild rt2870-kmod-2.4.0.0-0.1.Moon.fc13.src.rpm

Sorry, I haven't built an RPM on a 32bit machine for a while.
No need to create orcan group. You can ignore those messages.

[Moonf4]

These rpm's were created:

Wrote: /home/mythtv/rpmbuild/RPMS/i686/akmod-rt2870-2.4.0.0-0.1.Moon.md12.i686.rpm
Wrote: /home/mythtv/rpmbuild/RPMS/i686/kmod-rt2870-2.4.0.0-0.1.Moon.md12.i686.rpm
Wrote: /home/mythtv/rpmbuild/RPMS/i686/kmod-rt2870-2.6.32.14-127.fc12.i686-2.4.0.0-0.1.Moon.md12.i686.rpm
Wrote: /home/mythtv/rpmbuild/RPMS/i686/kmod-rt2870-PAE-2.4.0.0-0.1.Moon.md12.i686.rpm
Wrote: /home/mythtv/rpmbuild/RPMS/i686/kmod-rt2870-2.6.32.14-127.fc12.i686.PAE-2.4.0.0-0.1.Moon.md12.i686.rpm


Wrote: /home/mythtv/rpmbuild/RPMS/noarch/rt2870-2.4.0.0-0.1.Moon.md12.noarch.rpm

[ogetbilo]

I don't know much about PAE kernels. See what kernel you are running by doing
uname -a
If that shows a PAE kernel install the RPMs that have the PAE in their name. If not, install the other ones.

In either case, you also want to install the noarch RPM, that is at the end of your list above.

Install all RPMs at once. For example, for non-PAE kernel (1 line):
rpm -ivh /home/mythtv/rpmbuild/RPMS/noarch/rt2870-2.4.0.0-0.1.Moon.md12.noarch.rpm /home/mythtv/rpmbuild/RPMS/i686/kmod-rt2870-2.6.32.14-127.fc12.i686-2.4.0.0-0.1.Moon.md12.i686.rpm /home/mythtv/rpmbuild/RPMS/i686/kmod-rt2870-2.4.0.0-0.1.Moon.md12.i686.rpm

By the way, how is the new mythdora? I have an older one installed in a computer that I use rarely.

[jimmy2975]

Hi Jimmy,
1737:0079 Linksys is not supported by any of our kmod packages. I believe that this device is a rt2870. I am building the newest 2.4.0.0 version for rt2870 now. I can add your device to the list to the supported hardware in our kmod-rt2870 module. But I need you to test it before I can push it to the rpmfusion repos.

Are you comfortable with rebuilding SRPMs? That would make my life easier. Otherwise post me the kernel version you are running and I'll try to do something else.

Although I have not built any SRPMs I don't mind doing it and being a tester. I will try to build it later tonight (after work). I am guessing the instructions you have a few threads down still holds? I have F12 64 bit.

BTW : Thanks for your efforts and continued support. I was suspicious the the card I had did not use 2870. Although the CD had 2870 on it.!!!

Thanks
Jimmy

[Moonf4]

The install is looking for rt2870-kmod-common.

[jimmy2975]

Alright, since I don't know your experience level with Linux/Fedora, I will give a generic guideline. Let me know if you need me to make any step clearer.

Unfortunately, upon some further investigation, I found that the 1737:0079 Linksys device might be a rt3572, for which we have no kmod yet on rpmfusion. However, the rt2870 driver might work if you follow these instructions, or work only with limited functionality, or not work at al. Note that the rt3572 driver on Ralink's website won't work without a hack (you need to add your device ID 1737:0079 to the list of supported devices). I'll explain the hack if you can't get this working with rt2870 driver. Here we go:

1- First of all, make sure that your system is up to date and you booted into the newest kernel.
2- You need to setup a rpm build tree in your home directory. To do this install the rpmdevtools and rpm-build packages. Then as a regular user (not root), do
$ rpmdev-setuptree
This will setup an rpmbuild tree in your home directory.
3- Download these 2 SRPMs:
http://6mata.com:8014/review/rt2870-kmod-2.4.0.0-0.1.Moon.fc13.src.rpm
http://6mata.com:8014/review/rt2870-2.4.0.0-0.1.Moon.fc13.src.rpm
These have the device IDs added for you device.
4- You will try to build RPMs from the SRPMs next. To do this, go to the directory where you downloaded the SRPMs and build both packages (as regular user)
$ rpmbuild --rebuild rt2870-kmod-2.4.0.0-0.1.Moon.fc13.src.rpm
$ rpmbuild --rebuild rt2870-2.4.0.0-0.1.Moon.fc13.src.rpm
I expect this the fail in your first couple attempts, since you probably don't have all the build dependencies installed. Read the error messages carefully and install the missing packages, and try the above commands again.
5- At the end of the day, you will have your RPMs built in ~/rpmbuild/RPMS/noarch/*.rpm and ~/rpmbuild/RPMS/<your arch>/*.rpm. Install them and see how things go.

Hi I am using Linux linuxhome 2.6.32.14-127.fc12.x86_64 #1 SMP Fri May 28 04:30:39 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
Can you provide me a link to the respective source rpm so I can try to build?

Thanks
Jimmy

[ogetbilo]

The install is looking for rt2870-kmod-common.

The noarch package (I guess /home/mythtv/rpmbuild/RPMS/noarch/rt2870-2.4.0.0-0.1.Moon.md12.noarch.rpm) should provide that. You can check with
rpm -qp --provides /home/mythtv/rpmbuild/RPMS/noarch/rt2870-2.4.0.0-0.1.Moon.md12.noarch.rpm

Add that to the list of RPMs you are installing. You need to install 3 RPMs at once:
- The noarch one, .e.g. rt2870-2.4.0.0-0.1.Moon.md12.noarch.rpm
- Arch specific that contains the kernel version, e.g. kmod-rt2870-2.6.32.14-127.fc12.i686-2.4.0.0-0.1.Moon.md12.i686.rpm
- Arch specific that doesn't contain the kernel version, e.g. kmod-rt2870-2.4.0.0-0.1.Moon.md12.i686.rpm

[ogetbilo]

Hi I am using Linux linuxhome 2.6.32.14-127.fc12.x86_64 #1 SMP Fri May 28 04:30:39 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
Can you provide me a link to the respective source rpm so I can try to build?

Thanks
Jimmy
Hello, the F-13 SRPM will work on F-12. See the instructions and links in post #219.

[ogetbilo]

Attention advanced rt3070 users:

I made new packages for the newer version of the driver for inclusion in RPMFusion. Since I don't own the hardware, I need this to be tested before I push them to the repository. If you own this hardware, are capable of buliding and installing RPMs manually, and have time to test it, this will be very much appreciated. Here are the SRPMs:

http://6mata.com:8014/review/rt3070-2.3.0.2-0.1.fc13.src.rpm
http://6mata.com:8014/review/rt3070-kmod-2.3.0.2-0.1.fc13.src.rpm

Thank you!

[Moonf4]

Ok, so I installed the 3 rpms and now I see a wireless device, but I am not able to connect or see any wireless networks. Here is some output from iwconfig and dmesg:

[root@lunarshot ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

ra0 Ralink STA ESSID:"11n-AP" Nickname:"RT2870STA"
Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=10/100 Signal level:0 dBm Noise level:0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


RTUSB_VendorRequest failed(-19),TxFlags=0x0, ReqType=IN, Req=0x7, Idx=0x1000,pAd->Flags=0x300a0542
CMDTHREAD_RESET_BULK_IN: Cannot do bulk in because flags(0x300a0542) on !
---> RTMPFreeTxRxRingMemory
<--- RTMPFreeTxRxRingMemory
RTUSB disconnect successfully
usb 1-7: new high speed USB device using ehci_hcd and address 4
usb 1-7: New USB device found, idVendor=1737, idProduct=0079
usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-7: Product: Linksys WUSB600N Wireless-N USB Network Adapter with Dual-Band ver. 2
usb 1-7: Manufacturer: Linksys
usb 1-7: configuration #1 chosen from 1 choice


=== pAd = f82a6000, size = 510456 ===

<-- RTMPAllocTxRxRingMemory, Status=0
<-- RTMPAllocAdapterBlock, Status=0
-->RTUSBVenderReset
<--RTUSBVenderReset
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
1. Phy Mode = 5
2. Phy Mode = 5
RTMPSetPhyMode: channel is out of range, use first channel=1
3. Phy Mode = 5
MCS Set = ff ff 00 00 01
<==== rt28xx_init, Status=0
0x1300 = 00064300
Jun 30 02:23:40 localhost NetworkManager: <info> (ra0): preparing device.
Jun 30 02:23:40 localhost NetworkManager: <info> (ra0): deactivating device (reason: 2).
Jun 30 02:23:41 localhost NetworkManager: <info> (ra0): supplicant interface state: starting -> ready
Jun 30 02:23:41 localhost NetworkManager: <info> (ra0): device state change: 2 -> 3 (reason 42)

[jimmy2975]

I am getting the same iwlist results (built rpms from srpms according to post #219)

ra0 Ralink STA ESSID:"11n-AP" Nickname:"RT2870STA"
Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s
RTS thr:off Fragment thr:off
Link Quality=10/100 Signal level:0 dBm Noise level:0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

However the device lights up and no wireless networks are detected. I tried it both from NM and System>Admin>Network.

Thanks
Jimmy

[ogetbilo]

alright. that really means that you guys need to use the RT3572USB driver from ralink. I'll make some SRPMs for you. The procedure will be the same. Meanwhile you can safely remove the rt2870 RPMs you installed.

[ogetbilo]

Here you go. Before testing these, it might help if you remove the rt2870 stuff.
rpm -qa |grep rt2870
should return nothing. Here are the SRPMs. As I said, the procedure to build and install is the same:
http://6mata.com:8014/review/rt3572-kmod-2.4.0.0-0.1.try.fc13.src.rpm
http://6mata.com:8014/review/rt3572-2.4.0.0-0.1.try.fc13.src.rpm

Please let me know how things go.

[sahilahuja]

It feels really good that you guys are actively working on making usb wifi work :). I got a Linksys WUSB45GC (Usb ID 1737:0077) shipped 2 days back and spent the whole of yesterday (~15 hrs) trying to make it work on F13 and in the process also reinstalled F13 twice :p.

Facing the same issue: It's not detecting any network with RT2870.
Had tried rt3070sta taken directly from ralink's website (http://www.ralinktech.com/support.php?s=2) but that failed to load drivers on plugging in usb.

Will try 2 things now:
a) Modifying rt3070 source rpm posted here to load on 1737:0077
b) Using rt3572

[jimmy2975]

Here you go. Before testing these, it might help if you remove the rt2870 stuff.
rpm -qa |grep rt2870
should return nothing. Here are the SRPMs. As I said, the procedure to build and install is the same:
http://6mata.com:8014/review/rt3572-kmod-2.4.0.0-0.1.try.fc13.src.rpm
http://6mata.com:8014/review/rt3572-2.4.0.0-0.1.try.fc13.src.rpm

Please let me know how things go.

I tried this and and now the device is not recognized. Does this have the v2 device ID (1737:0079) added to it? I deleted the 2870 stuff before building 3572. Should I blacklist anything?

Thanks
Jimmy

[sahilahuja]

Same here -
Removed rt2870, rt3070
Modified rt3572's rt3572-additional-devices-support.patch to contain " +{USB_DEVICE(0x1737,0x0077)}, /* Added by oget */" instead of "+ {USB_DEVICE(0x1737,0x0079)}, /* Added by oget */"

Outcome:
Network manager not able to detect device.

On plugging in usb adapter:
dmesg:
usb 1-1: new high speed USB device using ehci_hcd and address 8
usb 1-1: New USB device found, idVendor=1737, idProduct=0077
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: 802.11 g WLAN
usb 1-1: Manufacturer: Ralink
usb 1-1: SerialNumber: 1.0

=== pAd = fdefa000, size = 511608 ===
<-- RTMPAllocTxRxRingMemory, Status=0
<-- RTMPAllocAdapterBlock, Status=0
/var/log/messages: -> this is different from the output of rt2870 driver (attached)

Jul 2 20:22:27 localhost kernel: usb 1-1: Product: 802.11 g WLAN
Jul 2 20:22:27 localhost kernel: usb 1-1: Manufacturer: Ralink
Jul 2 20:22:27 localhost kernel: usb 1-1: SerialNumber: 1.0
Jul 2 20:22:27 localhost kernel:
Jul 2 20:22:27 localhost kernel:
Jul 2 20:22:27 localhost kernel: === pAd = fdefa000, size = 511608 ===
Jul 2 20:22:27 localhost kernel:
Jul 2 20:22:27 localhost kernel: <-- RTMPAllocTxRxRingMemory, Status=0
Jul 2 20:22:27 localhost kernel: <-- RTMPAllocAdapterBlock, Status=0
Jul 2 20:22:27 localhost NetworkManager[1643]: <warn> /sys/devices/virtual/net/ra0: couldn't determine device driver; ignoring...

modinfo rt3572sta
alias: usb:v0B05p1742d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1737p0077d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0B05p1732d*dc*dsc*dp*ic*isc*ip*


And rt3572sta is listed in lsmod.

[ogetbilo]

I tried this and and now the device is not recognized. Does this have the v2 device ID (1737:0079) added to it? I deleted the 2870 stuff before building 3572. Should I blacklist anything?

Thanks
Jimmy

Yes this kmod has the deviceID added to it. You have to figure out yourself if there is need to blacklist anything. As I don't have the hardware, I can't test stuff.

Look at what lsmod gives you before and after you connect the device after you do a fresh reboot. If you see rt3572sta, then the kmod module is loaded properly.

At least one module, either the kmod one or something else, must load when you plug in the device as we introduced your deviceID to the driver.

[ogetbilo]

Hi sahilahuja, I wish I could help you more. There are many other things to try. There is a RT2870DAT file in /etc/Wireless that has bunch of parameters to play with.

In the spec file, there is a patch and a few sed lines to rename RT2870 to RT3572 (or to RT3070). I put it there to prevent a conflict with the RT2870 driver. Although I don't think it is likely, this might be causing problems. You can remove these and see how things go.

Please let me know if you can get your device working. Thanks.

[jimmy2975]

Yes this kmod has the deviceID added to it. You have to figure out yourself if there is need to blacklist anything. As I don't have the hardware, I can't test stuff.

Look at what lsmod gives you before and after you connect the device after you do a fresh reboot. If you see rt3572sta, then the kmod module is loaded properly.

At least one module, either the kmod one or something else, must load when you plug in the device as we introduced your deviceID to the driver.

lsmod |grep rt* did not return anything.

rpm -qa does not show rt3572.

I did not see any error when installing the rpm. How do I make sure the rpm is installed?

Thanks
Jimmy

[ogetbilo]

If
rpm -qa |grep kmod |grep rt
does not show you anything relevant, then the kmod is not installed properly. Make sure you have installed 3 RPMs:
- 1 noarch
- 1 arch specific with kernel version you are running (check with uname -r)
- 1 arch specific without the kernel version

[jimmy2975]

If
rpm -qa |grep kmod |grep rt
does not show you anything relevant, then the kmod is not installed properly. Make sure you have installed 3 RPMs:
- 1 noarch
- 1 arch specific with kernel version you are running (check with uname -r)
- 1 arch specific without the kernel version

OK. This is what I have

rpm -qa |grep rt3572
kmod-rt3572-2.4.0.0-0.1.try.fc12.x86_64
rt3572-2.4.0.0-0.1.try.fc12.noarch
kmod-rt3572-2.6.32.14-127.fc12.x86_64-2.4.0.0-0.1.try.fc12.x86_64

uname -r
2.6.32.14-127.fc12.x86_64

lsusb -v |grep Linksys
can't get hub descriptor: Operation not permitted
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
cannot read device status, Operation not permitted (1)
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get hub descriptor: Operation not permitted
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
Bus 001 Device 003: ID 1737:0079 Linksys
cannot read device status, Operation not permitted (1)
idVendor 0x1737 Linksys
can't get hub descriptor: Operation not permitted
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)

lsmod |grep rt3572
rt3572sta 500327 0

iwconfig
lo no wireless extensions.

ra0 Ralink STA
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 invalid crypt:0 invalid misc:0

eth0 no wireless extensions.

eth1 no wireless extensions.

vboxnet0 no wireless extensions.


blacklisted the following
blacklist rt2800usb
blacklist rt2x00usb
blacklist rt2x00lib

I just can't seem to find out why the device is not being recognized, unless of course 3572 is not the right driver?

Thanks
Jimmy

[ogetbilo]

I just can't seem to find out why the device is not being recognized, unless of course 3572 is not the right driver?


It is either that or you need to play with the configuration file in /etc/Wireless/ or


lsmod |grep rt3572[/B]
rt3572sta 500327 0


some other driver needs to be blacklisted. Check the lsmod output for something suspicious. e.g.

lsmod | grep rt

The final possibility is my patches break something. You could try building driver from source. Note that you need to add your device ID to the list in the file

2010_06_25_RT3572_Linux_STA_v2.4.0.0/common/rtusb_dev_id.c

If you want to go this way, I recommend uninstalling all the kmod stuff first.

[liedekef]

The final possibility is my patches break something. You could try building driver from source. Note that you need to add your device ID to the list in the file

2010_06_25_RT3572_Linux_STA_v2.4.0.0/common/rtusb_dev_id.c

If you want to go this way, I recommend uninstalling all the kmod stuff first.

Hi, indeed your patch is wrong: it patches the wrong section in the rtusb_dev_id.c file.
For the correct patch (verified and build by me for v2.3, but this patch has been updated for 2.4), I refer to the gentoo bug report which had the same problem:

http://bugs.gentoo.org/attachment.cgi?id=236761

For the whole bug report: http://bugs.gentoo.org/show_bug.cgi?id=228553
This also has some other small fixes for v2.3 which are probably the same as for 2.4:
rt3572usb-2.3.0.0-nodebug.patch (to deactivate debug)
rt3572usb-2.3.0.0-Makefile.patch
rt3572usb-2.3.0.0-config.mk.patch (to enable wpa)
I don't know if all of these are needed, I would refer to the 2870 driver for reference here.
For the config.mk patch, I in fact based myself on the comments found in this ubuntu thread:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/408165/comments/33
(again, I don't know if the changes made are all needed though, I did use this config.mk and it worked ok)

[ogetbilo]

Good catch liedekef. I now patched the correct part of the file. *Sigh* this driver code is so messy.

jimmy2975, sahilahuja's, please try these SRPMs. These have device IDs 0x1737,0x0077 and 0x1737,0x0079 added to them correctly.

http://6mata.com:8014/review/rt3572-kmod-2.4.0.0-0.2.try.fc13.src.rpm
http://6mata.com:8014/review/rt3572-2.4.0.0-0.2.try.fc13.src.rpm

Let's hope that this is the last try. Make sure that the old module is unloaded, and the device is unplugged before you install this kmod.

[sahilahuja]

Thanks for adding 0x1737,0x0077 ! :) (It's for Linksys WUSB54GC ver 3)
Got the same response in /var/log/messages, and Network Manager isn't detecting anything. ("NetworkManager[1646]: <warn> /sys/devices/virtual/net/ra0: couldn't determine device driver; ignoring...")

1) Jul 5 01:41:25 localhost kernel: <-- RTMPAllocTxRxRingMemory, Status=0
2) Jul 5 01:41:25 localhost kernel: <-- RTMPAllocAdapterBlock, Status=0
3) Jul 5 01:41:25 localhost kernel: usbcore: registered new interface driver rt2870
4) Jul 5 01:41:25 localhost NetworkManager[1646]: <warn> /sys/devices/virtual/net/ra0: couldn't determine device driver; ignoring...


Got line 3) when I did "modprobe rt3572sta", and after that line 4 came immediately.

This time all I did was:
su -c 'rpm -e rt3572 kmod-rt3572-2.6.33.5-124.fc13.i686-2.4.0.0-0.1.try.fc13.i686'
rpmdev-setuptree
rpm -Uvh rt3572-*
cd ~/rpmbuild/
rpmbuild -bb --target i686 SPECS/rt3572.spec
rpmbuild -bb --target i686 SPECS/rt3572-kmod.spec
su -c 'rpm -Uvh RPMS/i686/kmod-rt3572-2.6.33.5-124.fc13.i686-2.4.0.0-0.2.try.fc13.i686.rpm RPMS/noarch/rt3572-2.4.0.0-0.2.try.fc13.noarch.rpm'

[liedekef]

3) Jul 5 01:41:25 localhost kernel: usbcore: registered new interface driver rt2870

Got line 3) when I did "modprobe rt3572sta", and after that line 4 came immediately.



If you have installed rt2870, remove it or blacklist it if you want/need to use rt3572sta

[jimmy2975]

The card is not detected with the new src.rpm files (patch applied correctly).
lsmod |grep rt
exportfs 3504 1 nfsd
rt3572sta 500359 0
parport_pc 21189 0
parport 31685 2 ppdev,parport_pc

rpm -qa |grep rt3572
kmod-rt3572-2.4.0.0-0.2.try.fc12.x86_64
kmod-rt3572-2.6.32.14-127.fc12.x86_64-2.4.0.0-0.2.try.fc12.x86_64
rt3572-2.4.0.0-0.2.try.fc12.noarch

How come the patch (with correct device ID ) for rt2870 recognized the device? I am still suspicious that 3572 is not the correct driver for WUSB600N v2. The CD that came with the USB has rt2870 drivers on it. It might not be the same rt2870 that you are taking about, but it might still be 2870 with some changes in it?

Thanks
Jimmy

[liedekef]

rpm -qa |grep rt3572
kmod-rt3572-2.4.0.0-0.2.try.fc12.x86_64
kmod-rt3572-2.6.32.14-127.fc12.x86_64-2.4.0.0-0.2.try.fc12.x86_64
rt3572-2.4.0.0-0.2.try.fc12.noarch
Jimmy

Jimmy,

you should only install the kmod version, the other one does not have any patches applied to it I believe (I don't know if that's intentional or not though ...). Probably the created rpm without the patch has overwritten the other one. Recommendation: remove all the relevant rpm's and install only the correct kmod version.
Btw: I'm using WUSB600N v2 with this driver (not this src rpm, but anyway ...) so it is sure to work.

Franky