Darn, something must have gone wrong after all then. Funny, I didn't get any error messages during the build process.
"Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.
Many thanks, the help is much appreciated.
entering lsmod | grep rt5 got a result:
But when I typed iwlist wlan0 scan, I gotCode:rt5370sta 801203 0
and iwconfig gave meCode:wlan0 interface doesn't support scanning
Now... it's possible I'm way off track & trying to use the wrong device with this driver. lsusb lists it as a PLANEX GW-USMicroN which I'm sure is a Ralink chipset. I've been using it for years on an old Mac laptop with Ralink's OSX driver & it works fine. Just no joy this time around, unfortunately.Code:lo no wireless extensions. eth0 no wireless extensions.
Entirely possible. Let's have a look at:Now... it's possible I'm way off track & trying to use the wrong device with this driver. lsusb lists it as a PLANEX GW-USMicroN which I'm sure is a Ralink chipset.We need to see details, please.Code:lsusb
"Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.
Here we go:
Device 005 being the dongle I'm trying to shoehorn into this system. Maybe time to get a newer device...Code:Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 003: ID 0566:3107 Monterey International Corp. Bus 001 Device 004: ID 046d:c069 Logitech, Inc. Bus 001 Device 005: ID 2019:ed14 PLANEX GW-USMicroN
Hello guys, i have searched very much about this device, i have written a howto on my blog, you can check if you want.
http://wp.mindless.gr/2012/02/instal...ebian-squeeze/
hope this helps someone
Your blog says you have:minamitek has this:Bus 001 Device 003: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapterrt5370sta does not claim this device.ID 2019:ed14 PLANEX GW-USMicroN
Googling your device suggests several (possibly conflicting) ways to get this going. Let's try rt5370sta first. Please go to the files you extracted as a part of compiling the driver. Open common/rtusb_dev_id.c with any text editor; gedit or nano, for example. Scroll down to the section below and add the highlighted text. Punctuation, brackets, spacing, etc. are crucial. Type carefully and proofread twice. After the changes are made, be sure to save and close the text editor.Now we must recompile:Code:#ifdef RT5370 {USB_DEVICE(0x148F,0x5370)}, /* Ralink 5370 */ {USB_DEVICE(0x2019,0xED14)}, /* PLANEX */ {USB_DEVICE(0x148F,0x5372)}, /* Ralink 5370 */ {USB_DEVICE(0x13D3,0x3365)}, /* Azurewave */ {USB_DEVICE(0x13D3,0x3329)}, /* Azurewave */ #endif // RT5370 //Any improvement?Code:cd Desktop/RT3070etc. <--or wherever you extracted the files sudo su modprobe -r rt5370sta make clean make make install modprobe rt5370sta exit
"Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.
You are right chili555, i didnt notice the device id, just posted here trying to help people with the same problem with me, and the subject says that this thread is for the same module as mine.
HTH
Bookmarks