I was able 'hack the staging drivers for rt2870 and get the linksys WUSB54GC working in a 2.6.30-r5,r6,r7 kernel, however when I tried to use the drivers that were "SUPPOSED" to work in the 2.6.31 kernel (rt2800usb) this did NOT work. i.e. in looking through gentoo-sources I found 'finally' that 1737:0077 device was identified in the rt2800usb section of wireless drives. However.. when I compiled this an iwconfig DID yield the device, but it would not work. The ONLY way I've been able to get my wireless to work is to 'hack' the .h file as described in the URL above (http://forums.gentoo.org/viewtopic-t-774956-highlight-imbiea.html) in the section where I (imbiea) use the instructions from the previous poster. rt2800usb Reproducible: Always Steps to Reproduce: 1. vi /usr/src/linux-2.6.30-gentoo-r6/drivers/staging/rt3070/rt2870.h 2. add in a section for 1737:0077 and make modules && make modules_install 3. tried using rt2800 drivers in 2.6.31-r3, (which have 1737:0077 , but could not get it to work.
My hack though.. I couldn't get wpa to work.
Created attachment 208146 [details, diff] rtx200 patch Can you try this patch against a clean gentoo-sources-2.6.31-r3
I will try the patch either late tonight or early tomorrow. And report back findings.
ok, sorry my apologies. I'm a bit ignorant here.. :-( first question is that the diff file has: "linux-2.6.31.4/drivers/net/wireless/rt2x00/rt2800usb.c " So do I need repoint my /usr/src/linux symlink to a 2.6.31-r4 directory? and secondly. Where do I run the patch from? i.e. cd /usr/src/linux then patch -p1 < rt200.patch? Can you tell I don't do much (err any ) patching? :-) Please feel free to put in any other verbose information that might help me out.
OK, I tried this, please let me know if this sounds right: from my current /usr/src/linux (sym linked to 2.6.31-r3 make distclean patch -p1 < /root/work/rtx200.patch then just do my make menuconfig as usual, and don't use my hacked version of the drivers... Trying this now..
(In reply to comment #5) > OK, I tried this, please let me know if this sounds right: > > from my current /usr/src/linux (sym linked to 2.6.31-r3 > > make distclean > > patch -p1 < /root/work/rtx200.patch > > then just do my make menuconfig as usual, and don't use my hacked version of > the drivers... > > Trying this now.. > You can try using a more sophisticated patch tool, like quilt. For example, check this out: emerge quilt #installs quilt cd /usr/src/linux make mrproper #clear everything (or just download the sources again to be sure) cp /root/work/rtx200.patch . #copy the patch to the Linux directory quilt import rtx200.patch #import the patch to quilt quilt push #apply it If quilt applies the patch successfully, then you just run 'make menuconfig' etc. as normal.
Sorry Houston, but it's a no go. I tried the patch both with quilt, and with simply patch. Both were done with a new download, (not distclean) and the results were the same on both: after loading the mods: Module Size Used by rt2800usb 31504 0 rt2x00usb 8476 1 rt2800usb rt2x00lib 24144 2 rt2800usb,rt2x00usb crc_ccitt 1596 1 rt2800usb I didn't get ANYTHING (at least not a wireless interface) to show up with an iwconfig my lsusb did show however: Bus 002 Device 001: ID 1d6b:0001 Bus 003 Device 001: ID 1d6b:0001 Bus 004 Device 001: ID 1d6b:0001 Bus 001 Device 008: ID 1737:0077 Bus 001 Device 006: ID 413c:2002 Dell Computer Corp. SK-8125 Keyboard Bus 001 Device 007: ID 0461:4d89 Primax Electronics, Ltd Bus 001 Device 005: ID 413c:1002 Dell Computer Corp. Keyboard Hub Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Prior to the patch I did get an iwconfig to yield an interface, but I could do nothing with it.
ok, can you give the latest git-sources in portage a try?
(In reply to comment #8) > ok, can you give the latest git-sources in portage a try? > Can do, I'll try tomorrow night, and report back.
(In reply to comment #8) > ok, can you give the latest git-sources in portage a try? > OK, I tried linux-2.6.32-rc6-git3 and got the same results as 2.6.31-r3 unpatched. Being that the device does show up, i.e. I can see it with an iwconfig, and lsusb does reveal it's there (however still unidentified (Bus 001 Device 007: ID 1737:0077 -- but no product definition) However I'm unable to actually configure it with iwconfig. i.e. I can't iwconfig wlan1 essid "my essid" and get it to work. Only thus far with my hack I've been able to. Is this maybe a firmware problem with the product on my end? Not maybe a kernel bug? Confused what to try next. Again, 1737:0077 is supposed to be supported in the kernel, but ... it doesn't work for me?
Could we have a copy of your dmesg?
Created attachment 209800 [details] 2.6.31-r3 with 'hacked' modules - showing up as ra0
Created attachment 209802 [details] latest git config with wireless showing up as wlan1
(In reply to comment #13) > Created an attachment (id=209802) [details] > latest git config with wireless showing up as wlan1 > oh, both on the same system, even though one drive shows up as sd and one shows up as hd devices... I didn't do libata or something correctly...
I understand the holidays were upon us, but I've not seen progress in a while. I spec mostly Cisco gear for my clients and couldn't figure out what =I= was doing wrong when I found this bug.
Yes, agreed. Nothing new here. I've provided dmesg information, but nothing new here. I'm still only able to get this card working with my hacked sources, of which don't provide the ability for WPA.
I really think it's time to bring this issue upstream. I'm not familiar with the necessary steps to take to fully support a network wireless device. Post in the linux-staging mailing list and ask them: a) Is Neddy's patch actually valid? Why is your device not supported, and is it just a one line deal to get it to fully function? b) Ask them for some basic guidelines on fixing your problem.
I do not think anyone upstream will fix the issues soon... This issue has been existing for quite a while for some chips... Anyway Ralink still releases open source drivers for rt2870 etc that can be used instead of the staging one... See bug #228553
(In reply to comment #18) > I do not think anyone upstream will fix the issues soon... This issue has been > existing for quite a while for some chips... > Anyway Ralink still releases open source drivers for rt2870 etc that can be > used instead of the staging one... > See bug #228553 > I'll have to check ,but last I looked, they didn't have anything new supporting that USB ID.
Well actually they still do not have that entry in the supported USBs, but there is no problem to add it as supported in the common/rtusb_dev_id.c sources and see if it will work (you can make that change in the rt2870usb-2.3.0.0-unified.patch mentioned in bug #228553). So if it works ok with wpa_supplicant we may really think of adding more USB IDs to that patch so other users could test too...
(In reply to comment #20) > Well actually they still do not have that entry in the supported USBs, but > there is no problem to add it as supported in the common/rtusb_dev_id.c sources > and see if it will work (you can make that change in the > rt2870usb-2.3.0.0-unified.patch mentioned in bug #228553). > So if it works ok with wpa_supplicant we may really think of adding more USB > IDs to that patch so other users could test too... > I actually am inquiring upstream about this. you can download the latest drivers as part of their latest git sources (http://rt2x00.serialmonkey.com/wiki/index.php?title=Rt2x00_GIT_instructions) in which 1737:0077 is part of their devices in Rt2x00.. but also listed in their staging in rt2780.h also! However it (for me) does not work in their latest git sources (2.3.32 kernel) As I've stated it actually does work PERFECT in my 2.6.31 r3 kernel as part of the staging devices (INCLUDING WEP and WPA (initially I said I could not get wpa_suppicant to work, but it does work when I specify wpa_supplicant_ra0="-Dwext" in my conf.d/net) However... it doesn't work quite at nice when I hack the staging drivers in 2.6.31-r6 (the pretty green LED light doesn't light up.. but everything else works) So.. I've inquired with Mark Wallis upstream with serialmonkey... as .. as far as I'm concerned the driver works great for me! But I have to hack my 2870.h file everytime... Not the best long term solution.. :-)
Can you test with the Ralink drivers from the manufacturer of the card? I have you used these in the past with success on another card. http://www.ralinktech.com/support.php?s=2
(In reply to comment #22) > Can you test with the Ralink drivers from the manufacturer of the card? > > I have you used these in the past with success on another card. > > http://www.ralinktech.com/support.php?s=2 > Yes, I've tried the ralink drivers... hmmm. I DO wonder though... maybe this could be a firmware issue? when hack my files, I actually... don't have any firmware in /lib... however I did recently try the rt2x00 drivers, with what I 'think' is the correct firmware (/lib/firmware/rt2870.bin (from ralink) but I still get the same problem... I've also tried (I'll try again.. using this firmware with the latest drivers from ralink... ) an iwconfig does yield seeing the card, but I can't configure a darn thing)
