HOWTO: RT2500, etc. wireless cards

[wieman01]

Hi weiman01.

My laptop is 32-bit before I upgraded to hardy my wireless worked fine.
I post the rest of inf.

Thanks
OK then. Could you point me to the driver that you have used? Just want to check something.

[studentz]

I use the driver shipped by the laptop manufacturer (last version WinXP)
Here is the drive inf

~$ dmesg | grep rt2500
[ 63.403908] ndiswrapper: driver rt2500 (Ralink Technology, Inc.,06/10/2004, 2.02.06.0000) loaded
[ 63.654592] wlan0: ethernet device 00:11:09:0f:1e:ae using NDIS driver: rt2500, version: 0x20001, NDIS version: 0x500, vendor: 'IEEE 802.11g Wireless Card.', 1814:0201.5.conf

[wieman01]

studentz,

Really beats me... :-(

[studentz]

:confused:Hi weiman01

Here is something interesting. I use my old pcmcia network card with a similar chipset Ralink rt2500 and it works. Unfortunately, I cannot use my pcmcia port with my nice sound card. I post all inf.

Other forum suggests to use the serial monkey rt2500 driver and blacklist the alternative driver rt2500pci which comes with the kernel. I tried to blacklist rt2500pci using "echo 'blacklist rt2500pci' | sudo tee -a /etc/modprobe.d/blacklist".This command add the line "blacklist rt2500pci" to blacklist, but when you ask for ndiswrapper -l you still can see the alternative driver, and the wlan0 did not work.

Any suggestions?

Thanks for your time and support.




~$ lspci -nn | grep Network
00:09.0 Network controller [0280]: RaLink RT2500 802.11g Cardbus/mini-PCI [1814:0201] (rev 01)
02:00.0 Network controller [0280]: RaLink RT2500 802.11g Cardbus/mini-PCI [1814:0201] (rev 01)

~$ dmesg | grep rt2500
[ 59.360469] ndiswrapper: driver rt2500 (Ralink Technology, Inc.,06/10/2004, 2.02.06.0000) loaded
[ 59.611257] wlan0: ethernet device 00:11:09:0f:1e:ae using NDIS driver: rt2500, version: 0x20001, NDIS version: 0x500, vendor: 'IEEE 802.11g Wireless Card.', 1814:0201.5.conf
[ 288.764000] wlan1: ethernet device 00:50:18:2e:6a:83 using NDIS driver: rt2500, version: 0x20001, NDIS version: 0x500, vendor: 'IEEE 802.11g Wireless Card.', 1814:0201.5.conf


~$ lshw -C network

*-network
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlan1
version: 01
serial: 00:50:18:2e:6a:83
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+rt2500 driverversion=1.45+Ralink Technology, Inc.,06/ ip=192.168.2.108 latency=64 module=ndiswrapper multicast=yes wireless=IEEE 802.11g


*-network:0
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: 9
bus info: pci@0000:00:09.0
logical name: wlan0
version: 01
serial: 00:11:09:0f:1e:ae
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+rt2500 driverversion=1.45+Ralink Technology, Inc.,06/ latency=64 module=ndiswrapper multicast=yes wireless=IEEE 802.11g
*-network:1
description: Ethernet interface
product: VT6102 [Rhine-II]
vendor: VIA Technologies, Inc.
physical id: 12
bus info: pci@0000:00:12.0
logical name: eth0
version: 74
serial: 00:40:45:27:32:14
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=via-rhine driverversion=1.4.3 latency=64 maxlatency=8 mingnt=3 module=via_rhine multicast=yes


~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:40:45:27:32:14
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:510 errors:0 dropped:0 overruns:0 frame:0
TX packets:243 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:97102 (94.8 KB) TX bytes:36866 (36.0 KB)
Interrupt:18 Base address:0xd400

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:1261 errors:0 dropped:0 overruns:0 frame:0
TX packets:1261 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:178041 (173.8 KB) TX bytes:178041 (173.8 KB)

wlan0 Link encap:Ethernet HWaddr 00:11:09:0f:1e:ae
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:19 Memory:febfe000-fec00000

wlan1 Link encap:Ethernet HWaddr 00:50:18:2e:6a:83
inet addr:192.168.2.108 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::250:18ff:fe2e:6a83/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3090 errors:0 dropped:0 overruns:0 frame:0
TX packets:3047 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2961200 (2.8 MB) TX bytes:421361 (411.4 KB)
Interrupt:16 Memory:24000000-24002000

~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:40:45:27:32:14
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:510 errors:0 dropped:0 overruns:0 frame:0
TX packets:243 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:97102 (94.8 KB) TX bytes:36866 (36.0 KB)
Interrupt:18 Base address:0xd400

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:1261 errors:0 dropped:0 overruns:0 frame:0
TX packets:1261 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:178041 (173.8 KB) TX bytes:178041 (173.8 KB)

wlan0 Link encap:Ethernet HWaddr 00:11:09:0f:1e:ae
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:19 Memory:febfe000-fec00000

wlan1 Link encap:Ethernet HWaddr 00:50:18:2e:6a:83
inet addr:192.168.2.108 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::250:18ff:fe2e:6a83/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3090 errors:0 dropped:0 overruns:0 frame:0
TX packets:3047 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2961200 (2.8 MB) TX bytes:421361 (411.4 KB)
Interrupt:16 Memory:24000000-24002000

~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 No scan results

wlan1 Scan completed :
Cell 01 - Address: 00:18:39:72:57:AD
ESSID:"TEST"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:60/100 Signal level:-57 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

[wieman01]

Serialmonkey's driver is an option, however, it does not work at all with Network Manager. You will have to configure your network from command line.

If you decide to use their driver, then you have to remove 'ndiswrapper' entirely. Just remove it using Synaptics as it will confict with the other driver.

[studentz]

Hi weiman01

My subliminal question was How I can blacklist alternative drive rt2500pci so I only will have rt2500 drive working.

Thanks

[wieman01]

You can just open the blacklist by issuing:
sudo gedit /etc/modprobe.d/blacklist
Then add:
rt2500pci
That should do. Just play around with the blacklist.

[samm71790]

Hello everyone. I am running Hardy 64 with a rt2500pci on a asus m2n-e sli.

The good news is out of the box I could connect to my wpa 1/2 tkip/aes network! I had upgraded from gutsy 64 to hardy. And after messing with wcid and trying to reinstall gnome network manager I messed up everything pretty badly and was getting some HAL initialization error.

Well I now have a fresh install of hardy that I am going to treat very gently now. The problem is that I am maxing out at 30 kb/s on all networking things combined(media streaming from my media server, internet, everything). I know it is not my modem (I'm downloading things at 800 kb/s on my torrent box...)

My router is a wrt54gl with tomato 1.19(most recent i believe) on it.

While I realize I am way ahead of some as far as out of the box working... I really don't want to copy all of my hd movies to my computer and would LOVE to be back up to my wonderful xp wireless speeds.

I am a complete noob on Ubuntu and would love to keep using it as my desktop (i even got all my games working under wine!!!) so please help me find a way around this problem and get it all up to speed... i dont want something this minor to force me back to windows.

let me know what you want me to pull up in terminal if you want to see some settings. Also if the windows driver wrapper is my best bet and i should just follow the guide let me know, but if it is already sortof working that seams possibly counter productive.

[wieman01]

samm71790,

As far as I can tell you are one of the lucky ones as your adapters works out of the box. As for your performance issues, all I can advise is that you try this tutorial and use "ndiswraper" rather than the orginial driver.

Problem is that you are on 64-bit which is a headache for some. You will have to get a copy of the 64-bit XP drivers in order for this tutorial to work. Will that be a problem?

[defenestratos]

I run Hardy 64 and I followed the instructions on my Laptop with integrated RT2500 chip.
Works great until I try to hibernate when it tells me I am attempting to run a 32 bit driver on a 64 bit kernel. You don't need to be Sherlock Holmes to work out what the problem is...Is there a way around this, because on resume I have no wireless even though Wiradar sees the network.

[wieman01]

Have you not deployed the 64-bit version of the driver? Would that solve the problem perhaps?

[defenestratos]

Have you not deployed the 64-bit version of the driver? Would that solve the problem perhaps?

As far as I am aware there is no 64 bit driver for my device. I should have a bit more of a look though. Doesn't Ndswrapper convert 32 to 64 as well?

Actually there is an abundance of them. I followed your how to with the 64 bit windows driver and all works complete with hibernate/suspend.

[Silent Ninja]

As far as I am aware there is no 64 bit driver for my device. I should have a bit more of a look though. Doesn't Ndswrapper convert 32 to 64 as well?

Actually there is an abundance of them. I followed your how to with the 64 bit windows driver and all works complete with hibernate/suspend.

I've an MSI 670 Notebook with a RaLink RT61 card (64bits ubuntu)

I've tried to install the Windows drivers following this tutorial and I've tried a 32bits XP driver, a 64bits Vista driver, they've all installed correctly, but when I reboot the wlan0 device dissapear, so I'm guessing it doesn't work.

Anybody has made a RaLink Wireless card work with 64bits ubuntu?

[wieman01]

As far as I am aware there is no 64 bit driver for my device. I should have a bit more of a look though. Doesn't Ndswrapper convert 32 to 64 as well?

Actually there is an abundance of them. I followed your how to with the 64 bit windows driver and all works complete with hibernate/suspend.
So problem solved? :-)

[defenestratos]

So problem solved? :-)


Problem solved!! Thank you!

[ricardisimo]

I'm assuming everyone else had the same experience I did, and that Hardy has not, in fact, solved the problem. Certainly, the LiveCD has zero connectivity. However, I got an email update from Launchpad saying the following:
Marking this "Fix Released" as Stefan's patch is available in linux-
backports-modules:

linux-backports-modules-2.6.24 (2.6.24-16.14) hardy; urgency=low

[Stefan Bader]

* Added rt2x00 driver from serialmonkey.org
- LP: #134660
Is this true? If so, how do I get a hold of the "fix" before do a fresh install of Hardy - after which install I won't have a connection at all. I realize this is kind of off-topic, and if I were smarter or braver I'd just get ndiswrapper up and running as per Wieman's tutorial. Sadly, I'm a slow-witted coward who's waited two releases for someone else to fix my problems, and would like to know if it's finally been done. Thanks for any help anyone can give.

[The Helpful Hobo]

Can someone help me with which card I have? I've installed ndiswrapper already. I have the card...
Realtek RTL8101E Family PCI-E
Realtek RTL8187B Wireless 802.2.11G

And from this list...
rt2500usb
rt2500pci
rt2500
rt2570
rt73usb
rt73pci
rt73
rt61usb
rt61pci
rt61
rt2x00usb
rt2x00lib

Help would be appreciated. Thanks in advance.

[wieman01]

Can someone help me with which card I have? I've installed ndiswrapper already. I have the card...
Realtek RTL8101E Family PCI-E
Realtek RTL8187B Wireless 802.2.11G

And from this list...
rt2500usb
rt2500pci
rt2500
rt2570
rt73usb
rt73pci
rt73
rt61usb
rt61pci
rt61
rt2x00usb
rt2x00lib

Help would be appreciated. Thanks in advance.
Good question. Since this is a Realtek wireless adapter, I have no clue really. But you can run this & post the results:
sudo lshw -C network
The last line ought to tell you which driver is being used.

[tragicglee]

I have a D-Link g122 USB adapter, rev b1 (rt2570/rt2500usb). To some extent, this works out of the box on Gutsy (speed/stability are non-existent, network-manager goes nuts, and then there's the whole 'ew, no WPA2' thing). I managed to get things working flawlessly using the ndiswrapper method and manual configuration in the past and was using that for months without an issue, until two days ago. I booted into WinXP for a bit, and my adapter's refused to work with ndiswrapper since. This has happened in the past but it's usually resolved with 2-3 reboots. I've seen a few others with the same problem in the past, all using USB adapters, all running into it after using Windows.

wlan1's listed in ifconfig but it's not associating with my AP, and the LEDs aren't lighting up. I'm relatively sure that the hardware's fine b/c, while it's not working with ndiswrapper, it has since worked with XP and Ubuntu x4 (Hardy Live CD -> Hardy install -> Feisty Live CD -> fresh Feisty install, all using the native driver. It seemed to be okay under Hardy, but I really dislike Hardy for some reason). I tried ndiswrapper on my fresh install (using the exact same method and drivers I used original installation) and am having the same issue. rt2500usb, rt2750 and rt2x00 are blacklisted.

ndiswrapper -l output
netrtusb : driver installed
device (2001:3C00) present (alternate driver: rt2500usb)

ifconfig output:
Link encap:Ethernet HWAddr 00:15:E2:44:7X:X0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txquelen:1000
RX bytes:0 {0.0b) TX bytes:0 (0.0b)

sudo iwlist scan (truncated)
Cell 02 - Address: XX:XX:XX:XX:XX:XX
ESSID:"My Place"
Protocol:IEEE 802.11b
Mode: Managed
Frequency: 2.417 GHz (Channel 2)
Quality: 100/100 Signal level:-27 dBm Noise level: -96dBm
Encryption key: on
Bit Rates: 1 Mb/s; 2MB/s; ... 54Mb/s
Extra: bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher: WEP-40
Pairwise Ciphers (2) : TKIP WEP-40

/etc/network/interface contents:
auto wlan1
iface wlan1 inet dhcp
wireless-essid MyPlace
pre-up wpa_supplicant -Bw -Dwext -iwlan1 -c/etc/wpa_supplicant.conf
post-down killall -q wpa_supplicant

If anyone has any ideas, I'd be grateful for the help. Right now, my options seem to be: go wired at the expense of my other wireless devices; use WinXP, or rereinstall Gutsy and suffer with the native drivers. None of these are really viable, let alone appealing. This is doubly frustrating because I only went into XP so I could back things up and totally remove the native install. If I was slightly more paranoid, I'd say it knew and decided to sabatoge me.

[wieman01]

tragicglee,

This is so weird, have heard of it before. Could you please post this as well:
sudo lshw -C network

[tragicglee]

sudo lshw -C network
*-network
description: Ethernet interface
product: 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:03:08.0
logical name: eth0
version: 03
serial: 00:11:11:e4:9c:1a
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.17-k4-NAPI duplex=full firmware=N/A ip=74.76.203.159 latency=64 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s
*-network
description: Wireless interface
physical id: 1
logical name: wlan1
serial: 00:15:e9:33:8d:a5
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+netrtusb driverversion=1.52+D-Link,06/30/2004, 1.02.00. link=no multicast=yes wireless=IEEE 802.11g

[tragicglee]

tragicglee,

This is so weird, have heard of it before.

It's. Absolutely. Maddening! Somehow, it'd almost be easier to deal with if it happened every time I booted into XP, or if it happened after booting into another distro. But no, only XP. And there's never anything abnormally wrong with those XP sessions. I've seen somebody suggest it's a problem with hibernate/suspend, but I don't do either.

It's working now. I'm going to check my other 7.10 install later and see if it's also working there. If it isn't, I'll assume I did something right with this one, and try to figure out exactly what, so I can post the info on the off chance it will help anyone who runs into this at some point.

Thanks for being willing to help, wieman01. You're a saint :)

[wieman01]

It's. Absolutely. Maddening! Somehow, it'd almost be easier to deal with if it happened every time I booted into XP, or if it happened after booting into another distro. But no, only XP. And there's never anything abnormally wrong with those XP sessions. I've seen somebody suggest it's a problem with hibernate/suspend, but I don't do either.

It's working now. I'm going to check my other 7.10 install later and see if it's also working there. If it isn't, I'll assume I did something right with this one, and try to figure out exactly what, so I can post the info on the off chance it will help anyone who runs into this at some point.

Thanks for being willing to help, wieman01. You're a saint :)
Thanks, mate. :-)

Wipe out XP... That's the best advice I can give. Lol!

[Scoobylu]

I'm a total noob when it comes to Linux; I only installed it yesterday. I can't seem to get my wireless internet to work. I found this tutorial but, because I'm such a noob, am unable to follow it. First of all, what's "Synaptic/Adept?" Then, what am I supposed to do with those lines under quote? Any help would be great! :) The wireless card/connection isn't showing up at all in Networking. I have a Linksys WMP54GX Wireless G PCI Adapter with SRX.

[unutbu]

Hello Scoobylu, welcome to Ubuntu. (Hey, that rhymes!)
You might want to try the steps from one of these guides:

https://help.ubuntu.com/8.04/internet/C/troubleshooting.html
http://ubuntuforums.org/showthread.php?t=621088 (Google "WMP54GX Ubuntu")

If you have problems, I suggest posting on the second thread mentioned above. That one is specifically about the WMP54gx. It looks like a number of of posters report success with bmullan's directions, so it looks hopeful that things should work out for you too.

PS. According to http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list_g-l/, you have an Airgo networks chipset. This thread is about cards with the RT2500 chipset. So it's probably a good thing you didn't go very far with weiman01's instructions.

[Cliste]

Somewhat very similar to Scoobylu I'm also a complete noob- enter problem, I've tried to get my wireless card running using the ndiswrapper, but if you look at the attached picture it says that it cannot be installed on my Pc for some reason... Any ideas,:confused:

Thanks

[wieman01]

Somewhat very similar to Scoobylu I'm also a complete noob- enter problem, I've tried to get my wireless card running using the ndiswrapper, but if you look at the attached picture it says that it cannot be installed on my Pc for some reason... Any ideas,:confused:

Thanks
Open the package manager... called Synaptic. You will find it there as well.

[Cliste]

Open the package manager... called Synaptic. You will find it there as well.

I love the optimism... see attached, when I searched it it doesn't show..

Basically it's not installing on my Pc for whatever reason, any idea why, another way of trying or another wrapper

Thanks wieman...:)

[unutbu]

I think the package you need is called
ndiswrapper-utils-1.9.

If Synaptic does not work, you could open a terminal and type

sudo apt-get install ndiswrapper-utils-1.9

If that does not work, post any error messages from the line above and, in addition, the output of

cat /etc/apt/sources.list

[Cliste]

Here she comes:

for sudo apt-get install ndiswrapper-utils-1.9 we get:


Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package ndiswrapper-utils-1.9

And for cat /etc/apt/sources.list we get:
ciaran@ciaran-desktop:~$ cat /etc/apt/sources.list
# deb cdrom:[Ubuntu 8.04 _Hardy Heron_ - Release i386 (20080423)]/ hardy main restricted
deb-src http://archive.ubuntu.com/ubuntu/ hardy main restricted #Added by software-properties
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://ie.archive.ubuntu.com/ubuntu/ hardy main restricted multiverse
deb-src http://ie.archive.ubuntu.com/ubuntu/ hardy restricted main universe #Added by software-properties

## Major bug fix updates produced after the final release of the
## distribution.
deb http://ie.archive.ubuntu.com/ubuntu/ hardy-updates main restricted multiverse
deb-src http://ie.archive.ubuntu.com/ubuntu/ hardy-updates restricted main universe #Added by software-properties

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.
deb http://ie.archive.ubuntu.com/ubuntu/ hardy universe
deb http://ie.archive.ubuntu.com/ubuntu/ hardy-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://ie.archive.ubuntu.com/ubuntu/ hardy-backports main restricted universe multiverse
# deb-src http://ie.archive.ubuntu.com/ubuntu/ hardy-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository. This software is not part of Ubuntu, but is
## offered by Canonical and the respective vendors as a service to Ubuntu
## users.
deb http://archive.canonical.com/ubuntu hardy partner
deb-src http://archive.canonical.com/ubuntu hardy partner

# Line commented out by installer because it failed to verify:
# deb http://security.ubuntu.com/ubuntu hardy-security main restricted
# Line commented out by installer because it failed to verify:
# deb-src http://security.ubuntu.com/ubuntu hardy-security main restricted
# Line commented out by installer because it failed to verify:
# deb http://security.ubuntu.com/ubuntu hardy-security universe
# Line commented out by installer because it failed to verify:
# deb-src http://security.ubuntu.com/ubuntu hardy-security universe
# Line commented out by installer because it failed to verify:
# deb http://security.ubuntu.com/ubuntu hardy-security multiverse
# Line commented out by installer because it failed to verify:
deb http://security.ubuntu.com/ubuntu/ hardy-security restricted main multiverse universe
deb http://ie.archive.ubuntu.com/ubuntu/ hardy-proposed restricted main multiverse universe
# deb-src http://security.ubuntu.com/ubuntu hardy-security multiverse

[unutbu]

Edit: Hold on...
ie.archive.ubuntu.com has what you need. I'm not sure why your sources.list was not working. Your .deb is right here:
http://ie.archive.ubuntu.com/ubuntu/pool/main/n/ndiswrapper/

You may not want to follow my instructions below. There may be a way to get ie.archive.ubuntu.com working...
------------------------------------------------------------
Go to http://packages.ubuntu.com/hardy/i386/ndiswrapper-utils-1.9/download

You'll see a list of archive mirror sites. You can test how fast is your connection is to ge.archive.ubuntu.com, for example, by typing

ping -c4 ge.archive.ubuntu.com

Test a few until you are satisfied. Then edit your sources.list:


cd /etc/apt
cp sources.list sources.list.bak
gksudo gedit sources.list

and add a line like

deb http://ge.archive.ubuntu.com/ubuntu hardy main

Save and exit. At the terminal, you then type

sudo apt-get update
sudo apt-get install ndiswrapper-utils-1.9


I don't see ie.archive.ubuntu.com in the list of mirrors, so once you find a mirror which is good for you, you might want to edit your sources.lst in a number of places, adding the new mirror everywhere you see ie.archive.ubuntu.com. That way in the future hopefully you won't have this problem (not with Synaptic either). Every time you make a change to sources.lst, re-run

sudo apt-get update

[Cliste]

That'd be great, but I'm interneting through XP, as such can I download and then copy it over?

Edit: I'm guessing changing from http:\ might work?

[unutbu]

Oh. Stupid me.
Open Synaptic and check the box which enables installation of packages from CD. Stick in your LiveCD. ndiswrapper is on there.

If for some reason, that does not work, you can download the *.debs from the link in my previous post. Save them on your windows partition. Then boot up Ubuntu, mount your windows partition, copy the *.debs over, and then install by double-clicking or by typing

sudo dpkg -i ndiswrapper-common_1.50-1ubuntu1_all.deb

sudo dpkg -i ndiswrapper-utils-1.9_1.50-1ubuntu1_*.deb

You'll need a .deb that says i386 or amd64, depending on your hardware. And you'll need
2 .debs:

ndiswrapper-common (http://ie.archive.ubuntu.com/ubuntu/pool/main/n/ndiswrapper/ndiswrapper-common_1.50-1ubuntu1_all.deb)
and (ndiswrapper-utils-1.9 for amd64 (http://ie.archive.ubuntu.com/ubuntu/pool/main/n/ndiswrapper/ndiswrapper-utils-1.9_1.50-1ubuntu1_amd64.deb) or
ndiswrapper-utils-1.9 for i386 (http://ie.archive.ubuntu.com/ubuntu/pool/main/n/ndiswrapper/ndiswrapper-utils-1.9_1.50-1ubuntu1_i386.deb)).

All-in-all, this is more complicated than using the LiveCD. I'd try that first.

[Cliste]

I got it off Wubi.... no Live CD :(

[unutbu]

Okay, download the .debs that are linked in my previous post onto your hard drive or (better yet) a USB stick. Then copy them into your Wubi partition.

[Cliste]

Hmmm More Fricking errors (see pic)

Any completely foolproof methods(!?) starts to miss the old .exe files, begins drifting back to windows :D

[unutbu]

ndiswrapper-utils-1.9 depends on ndiswrapper-common being installed first.

[Cliste]

Ah sorry, I didn't see that, listen thanks, it's working now, it only picks up my neighbours wireless now though, hmmm, I'll look at it before asking anything though. Thanks :D

[Cliste]

Right, some progress:

ciaran@ciaran-desktop:~$ iwconfig
lo no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:05:5D:25:9B:F4
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
ciaran@ciaran-desktop:~$ sudo ndiswrapper -l
[sudo] password for ciaran:
rt2500 : driver installed
rt61 : driver installed
device (1814:0301) present (alternate driver: rt61pci)
ciaran@ciaran-desktop:~$

Now I've tried to delete, and skip the alternate driver as advised here (http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,troubleshooting/)
(Ndiswrapper site) however thats not working, every time i reboot it just comes back as was

[unutbu]

Have you tried

sudo ndiswrapper -r rt61
?

[Cliste]

Thanks for the quick reply:

ciaran@ciaran-desktop:~$ sudo ndiswrapper -r rt61pci
[sudo] password for ciaran:
couldn't delete /etc/ndiswrapper/rt61pci: No such file or directory
ciaran@ciaran-desktop:~$ sudo ndiswrapper -l
rt2500 : driver installed
rt61 : driver installed
device (1814:0301) present (alternate driver: rt61pci)

Edit: Sorry I think its the rt61pci thats the problem, the rt61 is the one which I installed from the sitecom site...

[unutbu]

Oops, sorry.
echo 'blacklist rt61pci' | sudo tee -a /etc/modprobe.d/blacklist
This should prevent the rt61pci module from loading at boot time.

[Cliste]

That worked so well it even stopped wireless altogether see attached, on start up no wireless, no wlan0 etc either

[Cliste]

Linux is absolutely, completely and fruitlessly DEAD to me

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list_o-z/

[unutbu]

Cliste, to get back to where you were before,

gksudo gedit /etc/modprobe.d/blacklist

Go to the last line in the file, and erase:

blacklist rt61pci
Save, Exit, Reboot.

[Ang]

Hi everyone. This will be the first time that i actually have to write something. Before this it seems i have never been alone or first with a problem. :)

Anyway. My RT2500 based mini-PCI card (built in my notebook by MSI) had an extremely poor range and i read it was almost certainly because of wrong drivers. So I followed this guide and now comes my problem:

I have two wireless cards, and after installing this driver so did I finally, at least, get a lot better range with the RT2500 card.
But I cannot connect to my router anymore with the RT2500 based card, but it can "see" the router!?

When I'm trying to connect so will the "wireless icon" just "spin" and stay grey.

Please help. Why is my RT2500 half dead?

*edit
It appears that it works for open networks. Could it be the drivers that doesn't support security networks?

[screwballl]

My install: Ubuntu 8.04, MSI6855B or Ralink RT2560F installed in a HP ze4500 (Pavilion ze4540us). It is also setup for dual boot with XP and the wireless works perfectly under XP.
I tried the method used here and for some reason it would not let me install it this way. It would say that rt2500 is installed after "ndiswrapper -i rt2500.inf".. but then when I checked "ndiswrapper -l" it would say rt2500 is not installed. I tried to reboot and would still not work.

So here is what I did that worked perfectly, I made sure everything was installed for ndiswrapper through Synaptic Package Manager. Then under the System area was a new Windows Drivers option, I chose that, selected my rt2500.inf and it installed it in a matter of seconds.
Within minutes I was connected to my wireless network and surfing. Granted the signal is very low when I am sitting next to the router but at least I have the option now.

[evanct]

alright, i have a WUSB54GC card with rt73(taken directly from the install cd) on feisty. i've done everything EXACTLY as detailed in the stickied thread, but it still won't work. i've installed the driver, blacklisted it, but when i type ndiswrapper -l i just get this:

rt73: invalid driver!

and i can't connect. when i try to install it again, it just tells me rt73 is already installed.

on my old computer i got this same card working with the same driver, also with feisty. idk what went wrong here, this is really frustrating

i also tried the rt73 python script, it didnt work either.

edit: nevermind, i fixed it

[devosion]

That worked so well it even stopped wireless altogether see attached, on start up no wireless, no wlan0 etc either

This is exactly the same problem I am having whenever I blacklist the native driver for my ralink card, wusb54gv4. Everytime I blacklist rt2500usb wlan0 disappears. Nothing I have tried has managed to get it up again. Manual configurations, reinstallations, nothing works, and im operating on a 64bit version of Hardy. Is this a bug, or is there a fix im not seeing?

By the way my wireless is operating on the native driver, just abysmally slow even after the iwconfig 54m 'fix'. Please help.

[devosion]

Well for the moment I have given up on using a 64bit version of hardy and instead am trying to get 32bit to work with my wusb54gv4.

The good news is that now when I blacklist wlan0 doesnt disappear from iwconfig. Although the bad news is that my wireless card isnt roaming upon boot-up, and when I manually setup the information for the card in network manager it often freezes my machine. This has occured twice already. The third time I tried it didn't work at all and didn't detect my network. When I performed iwlist scan nothing came up either. Is there something I am missing? I followed the instructions exactly as they were told. Any other choices besides ndiswrapper at this point?

[wieman01]

Well for the moment I have given up on using a 64bit version of hardy and instead am trying to get 32bit to work with my wusb54gv4.

The good news is that now when I blacklist wlan0 doesnt disappear from iwconfig. Although the bad news is that my wireless card isnt roaming upon boot-up, and when I manually setup the information for the card in network manager it often freezes my machine. This has occured twice already. The third time I tried it didn't work at all and didn't detect my network. When I performed iwlist scan nothing came up either. Is there something I am missing? I followed the instructions exactly as they were told. Any other choices besides ndiswrapper at this point?
The only option is the native driver or Serialmonkey's one...

[Eulolia]

Well for the moment I have given up on using a 64bit version of hardy and instead am trying to get 32bit to work with my wusb54gv4.

The good news is that now when I blacklist wlan0 doesnt disappear from iwconfig. Although the bad news is that my wireless card isnt roaming upon boot-up, and when I manually setup the information for the card in network manager it often freezes my machine. This has occured twice already. The third time I tried it didn't work at all and didn't detect my network. When I performed iwlist scan nothing came up either. Is there something I am missing? I followed the instructions exactly as they were told. Any other choices besides ndiswrapper at this point?

Ahh, WUSB54Gv4, just spent all day trying to get this working on the 64-bit build.

In the end this driver worked very well for me in ndiswrapper with the amd64 install:

http://files.aoaforums.com/I2130-RT2500V3.0.1.0_for_Win2003.zip.html

I think this is the problem lots of people are having. The drivers on the linksys site and CD are all 32bit. 32bit drivers won't work on the 64bit kernel. These ones linked in this message are dated 2005, but they're 64 bit, and seem to work perfectly in non-roaming mode (not sure about Roaming, haven't tried).

Following the instructions at post 1 or http://ubuntuforums.org/showpost.php?p=4373325&postcount=121 but using the inf from the amd64 link above instead of the linksys should work fine for anyone trying to get this adapter working with x64 ubuntu.

[Michael%S]

I'm starting to give up... Ever since I brought over my main machine to my new home (in my new country) I have not been able to get online via wifi on Ubuntu. I have a Ralink RT2500 miniPCI card. I followed this guide and cannot connect. Ubuntu (well, Xubuntu now) can see the networks, whereas it couldn't before, and I once even caused Wicd to say it is connected... No dice, I still couldn't surf.

Before I tried the method described here, I tried to build rt2500-source using module-assistant... It gave me some error message and couldn't build.

Before that I was trying out a few distros before I decided to go back to the Xubuntu I know and love. The last one I tried before installing Xubuntu Hardy was Granular Linux, a Mandriva-based distro that uses apt package management... Wifi worked out of the box. So I know there is hope for me, this is just getting extremely frustrating and tiring. I am not a very experienced Linux user. I understood everything in this guide, but when I had to use module-assistant I was basically shooting in the dark for lack of understanding.

Please somebody help me.

I have two wireless routers here, connected to one another by LAN cable. one acts as gateway and one as access point... The latter is much faster, so I prefer to use it, but I can't connect to the other one either.

$ sudo iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wlan0 Scan completed :
Cell 01 - Address: 00:19:5B:BF:8B:59
[neighbors' wifi]
Cell 02 - Address: 00:13:49:A1:19:0A
ESSID:"ArcorWirelessLANpmKw" <--gateway
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.452 GHz (Channel 9)
Quality:67/100 Signal level:-53 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:0E:2E:6F:47:2A
ESSID:"DIRA" <--access point
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.472 GHz (Channel 13)
Quality:75/100 Signal level:-48 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0


$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Ethernet interface
[irrelevant]
*-network:1
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: f
bus info: pci@0000:00:0f.0
logical name: wlan0
version: 01
serial: 00:50:fc:8d:38:20
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+rt2500 driverversion=1.52+Ralink Technology, Inc.,12/ latency=32 module=ndiswrapper multicast=yes wireless=IEEE 802.11g


Hope this helps, and I hope someone can help me sort this out.

[unutbu]

Please post

ifconfig
iwconfig
cat /etc/network/interfaces
Blank out any password/key that you have in /etc/network/interfaces. I see encryption is on on both your routers. Are you using WEP or WPA?

Also post the ip address of DIRA (the access point).

[Michael%S]

Thank you for your quick answer!
ifconfig
eth0 Link encap:Ethernet HWaddr 00:e0:18:dd:bf:18
inet addr:192.168.1.88 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:18ff:fedd:bf18/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12684 errors:0 dropped:0 overruns:0 frame:0
TX packets:10189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14113895 (13.4 MB) TX bytes:1302959 (1.2 MB)
Interrupt:16 Base address:0x8800

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:338 errors:0 dropped:0 overruns:0 frame:0
TX packets:338 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24071 (23.5 KB) TX bytes:24071 (23.5 KB)

wlan0 Link encap:Ethernet HWaddr 00:50:fc:8d:38:20
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:305 (305.0 B) TX bytes:2911 (2.8 KB)
Interrupt:22 Memory:b3800000-b3802000

wlan0:avahi Link encap:Ethernet HWaddr 00:50:fc:8d:38:20
inet addr:169.254.5.112 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:22 Memory:b3800000-b3802000

$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Auto Frequency:2.472 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:20 dBm Sensitivity=-110 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface wlan0 inet static
address 192.168.1.88
netmask 255.255.255.0
gateway 192.168.1.1
wireless-key s:******
wireless-essid DIRA

iface eth0 inet static
address 192.168.1.88
netmask 255.255.255.0
gateway 192.168.1.1

auto eth0


DIRA is located at 191.168.1.222 and uses WEP. The gateway is at 192.168.1.1, and Wicd reports it uses WEP too, but I don't remember if that is correct.
I should also note I have a laptop running Xubuntu as well, and I tried to mimic its configuration as much as possible in the network options, interfaces, Wicd, etc.

[unutbu]

Edit /etc/network/interfaces:
auto wlan0
iface wlan0 inet static
address 192.168.1.88
netmask 255.255.255.0
gateway 191.168.1.222
wireless-key s:****** <-- the wireless-key should be a 26 character hex string. "s:" should not be there.
wireless-essid DIRA

Then try
sudo /etc/init.d/networking restart
Depending on your driver, sometimes you need to reboot instead of using the above command. For other drivers, all you need to do is remove the driver and re-insert it with

modprobe -r <driver>
modprobe <driver>
Since you are using ndiswrapper, the `modprobe -r` command might make your system hang, so if the
`sudo /etc/init.d/networking restart` command does not work, try powering off your machine and rebooting. Note: you may have to power off the machine. A soft reboot may not reset your wireless card to the proper state.

[Michael%S]

I purposely set the gateway to 1.1 because with 1.222 it doesn't work - neither in Windows on this machine, nor in Xubuntu on the other.
And how should I set my key? The actual key is an ascii string, 13 characters long.

[unutbu]

Michael%S, you are right that the WEP key can be 13 text digits. That would be the same as 26 hex digits.

I'm sorry I don't know enough to diagnose your problem immediately. For what they are worth, here are a few thoughts:

1) You are getting stuck at the stage of obtaining a DHCP lease. I know this because I see in your ifconfig:


wlan0:avahi Link encap:Ethernet HWaddr 00:50:fc:8d:38:20
inet addr:169.254.5.112 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:22 Memory:b3800000-b3802000

The "avahi" indicates that wlan0 was looking for and failed to receive an IP address via DHCP. avahi steps in and assigns an ip address (169.254.5.112) but this of course does not help you communicate on the 196.168.1.* network.

I think if you are using wicd that it does not read /etc/network/interfaces. So my guess is that wicd has been configured to look for a DHCP connection.
Is your router also configured for DHCP? and are you going for a DHCP or a static connection?

Assuming you are going for a DHCP connection, go to your router's "DHCP Settings" configuration page, make sure the DHCP Start Address and End Address allocate sufficient addresses to accomodate all (both?) your machines.

Another way to see that the problem involves DHCP leases is to check the output of

sudo /etc/init.d/networking restart
The output would include something like

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.

2) I tried setting up a connection with an rt2500 card using WICD and had problems. I found success after removing WICD and reinstalling network-manager and network-manager-gnome. I don't know if it was necessary to reinstall network-manager and network-manager-gnome, however, because in the end I got the connection working manually using
http://ubuntuforums.org/showthread.php?t=684495.

Since WICD seems to interfere with the reading of /etc/network/interfaces, I think you would have to uninstall WICD if you want to try to connect using /etc/network/interfaces.

If you haven't tried that yet (or even if you have), perhaps it is worth a/another shot.

3) I don't have any experience with bridging, so if you say the proper thing to do is set the gateway to 192.168.1.1 instead of the bridge device, then I can only defer to your experience.

However, I find that rather odd, since I thought the philosophy behind networking is that each device has its own routing table, and gets to decide how to interact with packets based on its routing table.

My simplistic picture of a bridge therefore was that you send packets to the bridge (192.168.1.222) as though it were the gateway, and DIRA (the bridge) use its routing table to decide to forward all packets to the gateway (192.168.1.1).

Maybe a more knowledgable forum reader can settle this.

[Michael%S]

Oh, when I posted the ifconfig output the card was set to DHCP. Actually I'm going for static IP, I set it up like I want it in Wicd and even managed to get Wicd to connect, but couldn't surf. Here was the ifconfig output when I was "connected"
ifconfig
eth0 Link encap:Ethernet HWaddr 00:e0:18:dd:bf:18
inet6 addr: fe80::2e0:18ff:fedd:bf18/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:68786 errors:0 dropped:0 overruns:0 frame:0
TX packets:57780 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:67407152 (64.2 MB) TX bytes:8727511 (8.3 MB)
Interrupt:16 Base address:0x8800

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:712 errors:0 dropped:0 overruns:0 frame:0
TX packets:712 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:42925 (41.9 KB) TX bytes:42925 (41.9 KB)

wlan0 Link encap:Ethernet HWaddr 00:50:fc:8d:38:20
inet addr:192.168.1.88 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:363 (363.0 B) TX bytes:6718 (6.5 KB)
Interrupt:22 Memory:b3800000-b3802000
But it doesn't work any better with DHCP, and my router is certainly configured correctly for DHCP.

I will try the manual method tomorrow, it looks interesting and I haven't tried it yet. It's getting late here. :)

As for bridging, you're right in theory, but DIRA is not configured to do things automatically and cannot be configured to do so as far as I know. In fact, DIRA still thinks it's a router in Israel, where I used to live. I'm not sure I've exhausted all options as far as teaching DIRA to use the real router as its router, but my meager attempts so far have been fruitless. It also seems to work just fine the way it is when I tell the machine to use 1.1 as gateway, on all other systems and machines but this one.

Anyhow, thanks for your time and help, perhaps the guide you linked to might solve my problem after all.

[Michael%S]

It worked! The manual configuration solved the problem! (With a little tweaking of my own)
And I think I found the problem as well: for some reason route add default gw 192.168.1.1 returned an error when I tried it - but when I put eth0 down first, it worked and the problem was solved.
So I'm guessing for some reason two interfaces can't be set to the same gateway at the same time. This might have been the reason things didn't work before either.

The odd thing is that even when I was supposedly connected but didn't have the gateway set up, I couldn't access DIRA on ...1.222 via http. It only worked after I resolved the gateway issue.

[wieman01]

unutbu,

Just a word of appreciation. Thanks for helping me out. I don't have much time at the moment and have limited access to the internet during the week, so I appreciate the effort you are putting into this. Big thank you.

[unutbu]

Thanks for the words of encouragement, weiman01. I was at times worried I was dragging the thread off topic.
With that concern set aside, I'm glad to be of service.

[EarthMind]

Thank you for this guide, now I'm finally able to use my Asus wlan-167g USB adapter on Linux, this was the only reason that prevented me from keeping Ubuntu installed.

One note: restarting Ubuntu didn't make it work so I had to execute the following command in order to connect:
sudo /etc/init.d/networking restart

And I also have a question:
Now that I followed your instructions my Network Manager doesn't have a wireless connection interface anymore so how do I enable this again? I'm using 8.04

Edit: Never mind, found an even better tool called Wicd

Many thanks

[unutbu]

EarthMind, I'm not following you when you say
"Network Manager doesn't have a wireless connection interface anymore" can you describe this further?
or post a screenshot with Applications>Accessories>Take a Screenshot. (Extra points for keeping the png file size small).

Is the problem that the connection isn't being established at boot time? and you have to run
sudo /etc/init.d/networking restart
every time manually?

If so, please post

cat /etc/network/interfaces

[EarthMind]

EarthMind, I'm not following you when you say
"Network Manager doesn't have a wireless connection interface anymore" can you describe this further?
or post a screenshot with Applications>Accessories>Take a Screenshot. (Extra points for keeping the png file size small).

Is the problem that the connection isn't being established at boot time? and you have to run
sudo /etc/init.d/networking restart
every time manually?

If so, please post

cat /etc/network/interfaces

Well what I meant is that, and I noticed that this has been mentioned before somewhere on this forum, the Network Manager applet didn't search for wireless networks anymore after I used this guide. But I also found a much better tool in that topic which is called Wicd so my problem is solved.

Thanks for the help

[Lee_is_alive]

Hi All,

I'm using a sitecom WL 181 which uses the ra2860sta.ko module. Currently everything is running fine (on a AMD 64), but every time I reboot I need to insert the module:

sudo insmod /opt/Ralink/os/linux/rt2860sta.ko

Instead of doing this manually I would this to be done on boot.
For this I created the following folder:

/opt/lib/`uname -r`/ralink

and copied the module in here. After this I added this line in /etc/modules

rt2860sta

However this is not working, and trying to use

sudo modprobe rt2860sta

results in:

lee@lee-desktop:~$ sudo modprobe rt2860sta
FATAL: Module rt2860sta not found.

Any advice on how I can make modprobe pick up my module? How can I find back the what is really the name of the module? because now I'm trying with rt2860sta, just because the module name is rt2860sta.ko. But I believe the module name could just as well be "Ralink" or something else?

I was thinking that I would need to add something in /etc/modprobe.d/aliases
or add a file linking the a name "rt2860sta" to the rt2860sta.ko module?

But as I am far from a Linux expert, I don't know what to put there.

Any help is much appreciated!!!

Cheers,

Lee

[unutbu]

Did you download the tar.bz2, http://www.ralinktech.com.tw/data/drivers/2008_0522_RT2860_Linux_STA_v1.6.1.0.tar.bz2
from http://web.ralinktech.com/ralink/Home/Support/Linux.html?

It sounds like you've run make, but maybe you have not run


sudo make install

I've looked in the Makefile, and it seems like
the "sudo make install" command should put rt2860sta.ko in
/lib/modules/`uname -r`/kernel/drivers/net/wireless/
and run depmod -a for you.
It does not look to me like it would put the module in /opt/Ralink/os/linux, but I could be wrong -- I'm not that good at reading Makefiles.

Anyway, if you haven't already done so, try running "sudo make install" or "sudo checkinstall -D make install" (see below). This
should make the module load at boot. If that doesn't work, then try explicitly loading the module at boot by editing /etc/modules and appending

rt2860sta

to the end of the file. (You already tried this, but your kernel won't find rt2860sta.ko unless it is somewhere in the /lib/modules/`uname -r` directory tree and depmod -a has been run.)

Let me emphasize, I don't recommend you moving the module and running depmod -a manually unless you have to, because I might be wrong. It would be best to use the tar.bz2's Makefile's "sudo make install" command or to use checkinstall:

Regarding checkinstall:

There is a problem with running make install: it potentially spews files all over the place and there is no record of where it placed what. You also have to keep the Makefile so you can run "make uninstall" if necessary.

A better way to install files from tar.bz2s is to use the checkinstall package.
To install it:
sudo apt-get install checkinstall

Then instead of running

sudo make install
you run

sudo checkinstall -D make install # creates the .deb package
dpkg --contents package.deb # to see which files will be installed before you install it.
dpkg -i package.deb # to install


Once you install it from a .deb, you can also use these commands:

dpkg --listfiles package # to list what files have been installed
dpkg -r package # to remove

[blackaardvark]

Hi guys,

I've got a Belkin 7050 v3 usb which uses the rt73 driver (ralink right?)

My problem is that my machine's loading incorrect drivers at start up. I've tried blacklisting them but they're loaded anyway..

It's gotten to the point where i have to put in lsmod, check which one's are loaded and then do "modprobe -r rt2XXXusb" for each one EVERY TIME I START UP!

Perhaps I have the wrong blacklist file??? I do know that I have multiple firmware directories but that can't matter can it?

[unutbu]

1) Are you using Hardy 8.04? According to
http://ubuntuforums.org/showthread.php?p=4732883
your wireless card should (most likely) be supported out-of-the-box.

2) Please post

grep -r "blacklist rt" /etc/modprobe.d

[blackaardvark]

I'm using 7.10 for now as I have my reservations about upgrading just yet with all the work I have planned.

Here's the result of that grep call:

/etc/modprobe.d/blacklist:blacklist rt73usb
/etc/modprobe.d/blacklist:blacklist rt2570
/etc/modprobe.d/blacklist:blacklist rt2500usb
/etc/modprobe.d/blacklist:blacklist rt2x00lib
/etc/modprobe.d/blacklist:blacklist rt2x00usb
grep: /etc/modprobe.d/alsa-base.save: Permission denied
/etc/modprobe.d/blacklist~:blacklist rt73usb
/etc/modprobe.d/blacklist~:blacklist rt2570
/etc/modprobe.d/blacklist~:blacklist rt2500usb
/etc/modprobe.d/blacklist~:blacklist rt2x00lib
/etc/modprobe.d/blacklist.dpkg-old:blacklist rt73usb
/etc/modprobe.d/blacklist.dpkg-old:blacklist rt2570

Thanks for the speedy reply, it's very much appreciated!

[unutbu]

Is it the same unwanted modules that constantly show up? If so, which ones are they?
Also, please post (modules.out and depmod.out)

cat /etc/modules > modules.out
grep wireless /lib/modules/`uname -r`/modules.dep > depmod.out


I do know that I have multiple firmware directories but that can't matter can it?
Can you describe more about this? Where are the directories, and how are they tied into the system?

[blackaardvark]

When I say I have multiple firmware directories I mean that every time I update the kernel it creates a separate directory for each one, so
ls /lib64/firmware
gives me:
2.6.17-10-generic 2.6.20-15-generic 2.6.22-14-generic
2.6.17-11-generic 2.6.20-16-generic

I probably explained that in the wrong way :confused:

The module I need is rt73, the others (rt2x00usb,rt2500usb,rt73usb) interfere with it (they create an interface called wmaster0).

As requested here's those output files.

[unutbu]

Remove "ndiswrapper" from /etc/modules. (Unless you have a second wireless device that requires ndiswrapper).

The ndiswrapper modules is only necessary when you are trying to use a Windows driver from within Linux. The rt73 is a native (Linux) driver, so ndiswrapper is not necessary.

Your depmod.txt lacks a line for your rt73.ko driver. That means rt73.ko driver has not been properly installed within the /lib/modules/`uname -r` directory tree.

Where did you get the rt73.ko driver? If you got it from a tar.gz or tar.bz2 file then it should have come with a Makefile. I have a feeling you have not yet run

sudo make install or
sudo checkinstall -D make install

Either by luck or by virtue of having a one-track mind, I think my post
http://ubuntuforums.org/showpost.php?p=5285199&postcount=567
is relevant to your situation as well.

So in summary:
1) Remove "ndiswrapper" from /etc/modules
2) Read http://ubuntuforums.org/showpost.php?p=5285199&postcount=567
3) If unsure what to do, post an explanation/link about where you got the rt73 driver

[wieman01]

Just an update: Also works with the rt2860 chipset... Took me 5 minutes to set it up.

[_El_Chojin_]

I'm using Ubuntu Hardy + Conceptronic C54Ri wich use ralink chipset and i have made this but system locks all time so what can i do, i have done a lot of how to (before make one i make a new install of ubuntu but all how to failed and i cant use ubuntu).
I'm loader rt61.inf with ndiswrapper someone has same card as me and can help me to solve this big problem.

Thanks.

[yosumi]

wow finally a guide that works. i've wasted a whole day trying to make Linksys WUSB11 v2.6 work. i should've read this thread sooner!

[wieman01]

I'm using Ubuntu Hardy + Conceptronic C54Ri wich use ralink chipset and i have made this but system locks all time so what can i do, i have done a lot of how to (before make one i make a new install of ubuntu but all how to failed and i cant use ubuntu).
I'm loader rt61.inf with ndiswrapper someone has same card as me and can help me to solve this big problem.

Thanks.
If it continues locking up, then you will have to compile diswrapper from source. Seen this before and generally compiling solves the problem.

[_El_Chojin_]

After do it my card is not recogniced by the system, only appears eth0 and lo with ifconfig -a :S
Maeby i mustn't load rt61.inf and i must load other driver??

[wieman01]

After do it my card is not recogniced by the system, only appears eth0 and lo with ifconfig -a :S
Maeby i mustn't load rt61.inf and i must load other driver??
Are you on a 32-bit or 64-bit system?

You can check for the right driver here:

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

[_El_Chojin_]

I was trying to install it on a 64 bit system and now i'm going to install it on a 32 bit system to try.
C54Ri is not listed on that page.

[_El_Chojin_]

With 32 bits system works fine i think because i have been using it 2hour and didn't lock computer so i think that on 32bits system how to works good.

Could be interesting to look why this how to don't work with 64 bits system.

Thanks for the how to.

[DieselSnorter]

.

[DieselSnorter]

ME AGAIN!!!
okay, same box, but I'm trying to get a WMP54Gv4 (RT2500) PCI card working now. i still have the Belkin dongle, and that works, but I can't leave things alone.

So.currently I'm on the Belkin and life is good. But when i shut it down and disconnect it, and bring up the PCI adapter, it sees my connection, but won't connect to it.

I've installed it via Ndiswrapper (piece of cake) and pretty much just copied the config from the other adapter for my /etc/network/interfaces file.

ifconfig -a


wlan1 Link encap:Ethernet HWaddr 00:1c:df:1c:49:1c
inet addr:192.168.0.107 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1097 errors:0 dropped:0 overruns:0 frame:0
TX packets:730 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:911570 (890.2 KB) TX bytes:138640 (135.3 KB)

wlan2 Link encap:Ethernet HWaddr 00:12:17:a0:19:c3
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20 Memory:fdbfe000-fdc00000

wlan2:avahi Link encap:Ethernet HWaddr 00:12:17:a0:19:c3
inet addr:169.254.6.84 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:20 Memory:fdbfe000-fdc00000
Wlan1 is my Belkin, Wlan2 is the Linksys.

ndiswrapper -l

rt2500 : driver installed
device (1814:0201) present (alternate driver: rt2500pci)
rt73 : driver installed
device (050D:705A) present (alternate driver: rt73usb)
lspci


04:06.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
Subsystem: Linksys WMP54G 2.0 PCI Adapter
Flags: bus master, slow devsel, latency 32, IRQ 20
Memory at fdbfe000 (32-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
now, what's funny, is if I have them both scan.

iwlist scan

wlan 1 finds my AP as a G.


Cell 02 - Address: 00:0F:66:E4:73:5E
ESSID:"*****"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:37/100 Signal level:-72 dBm Noise level:-96 dBm
Encryption keyn
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=60
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1)
But Wlan2 sees is as B

Cell 01 - Address: 00:0F:66:E4:73:5E
ESSID:"*****"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:32/100 Signal level:-75 dBm Noise level:-96 dBm
Encryption keyn
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=60
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
my config file (etc/network/interfaces)


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback



# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.

auto wlan1
iface wlan1 inet dhcp
wpa-driver wext
wpa-ssid *****
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk KEY

auto wlan2
iface wlan2 inet dhcp
wpa-driver wext
wpa-ssid *****
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk KEY
iwconfig


wlan2 IEEE 802.11g ESSIDff/any
Mode:Auto Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:20 dBm Sensitivity=-120 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Managementff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

wlan1 IEEE 802.11g ESSID:"*****" Nickname:"*****"
Mode:Managed Frequency:2.442 GHz Access Point: 00:0F:66:E4:73:5E
Bit Rate=24 Mb/s Tx-Power:20 dBm Sensitivity=-121 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Managementff
Link Quality:34/100 Signal level:-74 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
So, oh great mand wonderful OZ...can you figure this one out?

Thanks in advance.

Eric

[unutbu]

Are you trying to get two wireless cards connected to the same computer to both talk to the same access point (router)?

[DieselSnorter]

yes, but not at the same time....
My goal is to replace the USB with the PCI...but I need to get the PCI working first.

I have removed the RT73 driver from Ndiswrapper to make sure there wasn't a conflict, I have completely removed it from my system, and the linksys still won't connect.
If I use a GUI monitor (kwifimanager) I can see it connecting to the AP while it tries to get an IP, but then it drops every few seconds.
this isn't a HUGE deal, but I would much prefer to have the on board adapter.

[unutbu]

Have you checked that your router is not doing MAC filtering, or if it is, that 00:12:17:a0:19:c3 is included in the list of accepted MACs?

Also, I notice that ifconfig returns

wlan2:avahi Link encap:Ethernet HWaddr 00:12:17:a0:19:c3
inet addr:169.254.6.84 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:20 Memory:fdbfe000-fdc00000

The presence of "avahi" indicates that wlan2 failed to receive an IP address from the router via DHCP. I'm not sure exactly why this might be, but it would probably be good to double check the DHCP settings on the router.

Finally, please post the output of

route -n

[DieselSnorter]

I am doing MAC filitering, but I verified that it is permitted on my router.
i've double checked it about 13 times just in case I fat fingered.
My router isn't actually doing my DHCP, my PFSense firewall is. just FYI.

I'm currently connected on the RT73 (or I have no connection) so this is what is showing as valid.

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan1
0.0.0.0 192.168.0.1 0.0.0.0 UG 100 0 0 wlan1


i'm going ot drop my connection, set ifconfig wlan1 down and unplug it, then bring up the Linksys and post the results after I get them and reconnect to the USB.

just for fun, I'll give you the ifup -v wlan2

Configuring interface wlan2=wlan2 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/hostapd
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan2.pid -i wlan2 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWPMKSA]: Invalid argument
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan2
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "*****" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP TKIP -- OK
wpa_supplicant: wpa-group CCMP TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan2.pid -lf /var/lib/dhcp3/dhclient.wlan2.leases wlan2
There is already a pid file /var/run/dhclient.wlan2.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan2/00:12:17:a0:19:c3
Sending on LPF/wlan2/00:12:17:a0:19:c3
Sending on Socket/fallback
DHCPDISCOVER on wlan2 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan2 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan2 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant


route -n

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan2
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 wlan2


ifdown -v wlan2

Configuring interface wlan2=wlan2 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-down.d/50firestarter exited with return code 2
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan2.pid -lf /var/lib/dhcp3/dhclient.wlan2.leases wlan2
There is already a pid file /var/run/dhclient.wlan2.pid with pid 8564
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan2/00:12:17:a0:19:c3
Sending on LPF/wlan2/00:12:17:a0:19:c3
Sending on Socket/fallback
DHCPRELEASE on wlan2 to 192.168.0.1 port 67
ifconfig wlan2 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/hostapd
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan2.pid
Stopped /sbin/wpa_supplicant (pid 8530).

[unutbu]

i'm going ot drop my connection, set ifconfig wlan1 down and unplug it, then bring up the Linksys and post the results after I get them and reconnect to the USB.

When you switch NICs, do you shutdown the machine and powerup with wlan2 connected?
ndiswrapper does not always behave properly when NICs are hotswapped.

If that doesn't help, I'm afraid I've run out of ideas...

[DieselSnorter]

so I tried removing the RT73 driver from Ndiswrapper, then shut down. Removed the RT73 from my system. Booted up, installed the linksys driver, configured the interfaces file, rebooted....same problem.

I think the problem lies here

Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWPMKSA]: Invalid argument
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan2

but I haven't the foggiest idea how to fix it.

[unutbu]

Perhaps try this thread to get wpa working: http://ubuntuforums.org/showthread.php?t=684495

[wieman01]

DieselSnorter,

Still struggling with this?
ioctl[SIOCSIWPMKSA]
Have you got any separate wpa_supplicant file for your system? It complains about an invalid line, and I like to know which one it might be referring to.

[ubugeek]

With 32 bits system works fine i think because i have been using it 2hour and didn't lock computer so i think that on 32bits system how to works good.

Could be interesting to look why this how to don't work with 64 bits system.

Thanks for the how to.

Yes, the howto was indispensable. The kernel rt61 module wasn't working well at all, however after installing the ndiswrapper modules and getting my 64-bit drivers installed via that, it STILL locks my 8.04.1 system up under heavy network load (specifically torrents, but today YouTube brought it down as well).

I'm running a version of Hardy at work, and it runs flawlessly. I upgraded my Vista box to Hardy and now due to the flaky wireless drivers I can barely use it as a workstation. I'm not giving up in the slightest but damn this is annoying. :)

[nsegative]

Hmm I'm having problems with the rt2860. I turned wlan on in the bios on my eeepc901 (wireless led is lit up blue). I installed ndiwrapper and the graphic tool. Then I put the winxp driver onto usb, put it on the desktop. LSPCI shows "01:00.0 Network cntroller: RaLink unknwon device 0781". Installing the driver in cnsole and doing ndiswrapper -l:
Installed drivers: rt2860 Invalid Driver!.

The graphic vesion of ndiswrapper says:
rt2860. Hardware present: no.

Any idea?

[unutbu]

nsegative, perhaps take a look at xodeus's post #6:
http://ubuntuforums.org/showthread.php?t=708499

[nsegative]

nsegative, perhaps take a look at xodeus's post #6:
http://ubuntuforums.org/showthread.php?t=708499
Can't, this is why I am using this program. I got it to work once but reformated to a bigger hd and can't get it to work again. The eeepc has no ethernet working either, and no cd so there's no way to get the build-install package (and all the ones ive tried required tons and tons of libraries in a never ending cycle).

[JamesRock]

Just wanted to thank you for taking the time for writing such excellent and detailed instructions, they worked perfectly for me first go!

[nsegative]

Never mind I'm retarded. I installed ndiswrapper version 1.20 for both utilities and common. Once I noticed that in my usb drive I installed version 1.50 and it worked fine again. Back online on the eeepc :)

[sputnikkk]

Ok so is the ndiswrapper and windows driver method absolutely neccessary to make my working WPA2 Static IP configuration "stick" through reboots?

Wireless WPA2, Static IP, Networking WORKS ... but my issue is if i put it into NetworkManager, I have to do it at every reboot. The computer illiterate user of this desktop will not be able to do this and other such required nonsense on reboots.

How can I make my settings stick?

[wieman01]

Ok so is the ndiswrapper and windows driver method absolutely neccessary to make my working WPA2 Static IP configuration "stick" through reboots?

Wireless WPA2, Static IP, Networking WORKS ... but my issue is if i put it into NetworkManager, I have to do it at every reboot. The computer illiterate user of this desktop will not be able to do this and other such required nonsense on reboots.

How can I make my settings stick?
The only way to make it stick at the moment it configuring your WPA2 settings manually (look at my WPA tutorial in the signature). I don't think Network Manager is ready yet for static IP addresses. Sad though.

[wesswei]

The only way to make it stick at the moment it configuring your WPA2 settings manually (look at my WPA tutorial in the signature). I don't think Network Manager is ready yet for static IP addresses. Sad though.

Thanks wieman! I totally missed the second post in your wpa howto which explains this... bug.

I did this to update the links for all the rc folders.
sudo update-rc.d wireless-networking defaults 40

Thanks again.

[sputnikkk]

I solved all this BS from NetworkMisManager by installing Wicd.

I tried to be all geeky and core like a command line commando - but in the end - the Wicd GUI saved the day.

The only way to make it stick at the moment it configuring your WPA2 settings manually (look at my WPA tutorial in the signature). I don't think Network Manager is ready yet for static IP addresses. Sad though.

[limkopi]

i try this but it became worst before i did this ubuntu still can detect my wireless device and all but after i did this and reboot i dont even have a wireless option anywhere can you plz help thanks

[unutbu]

Please tell us the manufacturer/model of your wireless card, and also post the output of

sudo lshw -C net
lsmod | grep ndiswrapper
ndiswrapper -l

[linuxquestusa]

Dapper Drake users should take a look at this thread (http://ubuntuforums.org/showthread.php?t=192588) if this one doesn't work. This guide was tested with Feisty Fawn, Gutsy Gibbon, and Hardy Heron.
--
To all RT73 users, please also see this post (http://ubuntuforums.org/showthread.php?p=4732883). Thanks to Kiefer Rodriguez (http://ubuntuforums.org/member.php?u=490665) for this solution.

Please post to this Launchpad bug report (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/163020) with all of your specs, if you have problems with a Ralink based wireless adapter.

This is a simple guide for all Ralink based wireless adapters and everyone who wants to replace the Linux driver with "ndiswrapper" (e.g. because you want to make use of either Network Manager (http://www.gnome.org/projects/NetworkManager/) or WICD (http://wicd.sourceforge.net/)).

INSTRUCTIONS:

Get the latest version of the Windows driver for your card from Linksys' website (http://www.linksys.com/servlet/Satellite?c=L_CASupport_C1&childpagename=US%2FLayout&cid=1166859840888&pagename=Linksys%2FCommon%2FVisitorWrapper&lid=4088837314B372&displaypage=download) or from the CD that came with your device (whatever vendor).



Install "ndiswrapper" package with working internet connection (Ethernet):




Install "ndiswrapper" package without working internet connection (alternatively, install it via Synaptic/Adept):




Load new driver module (may not be necessary any longer, but does no harm either):




Add the module to "/etc/modules" to have it load automatically:




Create alias directive:




Pick a valid Ralink driver based on the chipset of your card (you might blacklist all of them if you are not sure):




Blacklist Ralink driver:




Now unzip the driver archive you have just downloaded (e.g. in your home directory):




Now find the right driver in the resulting folder & deploy it (folder should also contain other driver files i.e. .cat, .sys):




Make sure it has installed correctly:




The output should yield something like this:




Last but not least open this file...




...and add these 2 lines if they are not there yet [also try without adding them if Network Manager does not pick up the card & reboot]:


You can now safely delete the extracted driver files & folders. Then reboot the computer and see if you can connect using your favorite networking applet (e.g. Network Manager, WICD, Wifi Radar, etc.).

Feedback is - as always - appreciated.

CHANGE LOG:
30/09/2007: Minor fixes.
07/10/2007: Expanded "blacklist".
20/10/2007: Added missing part concerning "interfaces" file.
22/10/2007: Load module "ndiswrapper" at boot.
23/10/2007: Enhanced blacklist.
07/11/2007: Bug fix for Network Manager.
12/11/2007: Updated blacklist & module section.
13/01/2008: Launchpad bug report.
15/04/2008: Update for Hardy.
17/04/2008: RT73 note.
Everything works until I type the following command:

Quote:
ndiswrapper -l

When I type this command the message comes back as

invalid driver

and that is for rt2500usb.inf, rt2500usb.sys and rt2500usb.cat.

Please help resolve this

[unutbu]

linuxquestusa, open a terminal and type

cd path/to/drivers # change the path to the correct path where rt2500usb.* are located
sudo ndiswrapper -r rt2500usb
sudo ndiswrapper -i rt2500usb.inf
ndiswrapper -l

What is the output?
Also, if it doesn't work, please tell us what make/model wireless card you are using.

[limkopi]

Please tell us the manufacturer/model of your wireless card, and also post the output of

sudo lshw -C net
lsmod | grep ndiswrapper
ndiswrapper -l

i have a linksys WUSB54G ver.4
i did what you told me to do this is what i get
[CODE]
jordan@jordan-desktop:~$ sudo lshw -C net
[sudo] password for jordan:
*-network
description: Ethernet interface
product: NetXtreme BCM5751 Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 11
serial: 00:01:6c:dc:d3:d8
size: 100MB/s
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.86 duplex=full firmware=5751-v3.29a ip=192.168.1.68 latency=0 link=yes module=tg3 multicast=yes port=twisted pair speed=100MB/s
jordan@jordan-desktop:~$ lsmod | grep ndiswrapper
ndiswrapper 244736 0
usbcore 169904 9 gspca,ndiswrapper,zc0301,usbhid,usb_storage,libusu al,ehci_hcd,uhci_hcd
jordan@jordan-desktop:~$ ndiswrapper -l
rt2500usb : driver installed
device (13B1:000D) present (alternate driver: rt2500usb)
jordan@jordan-desktop:~$

jordan@jordan-desktop:~$ sudo lshw -C net
[sudo] password for jordan:
*-network
description: Ethernet interface
product: NetXtreme BCM5751 Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 11
serial: 00:01:6c:dc:d3:d8
size: 100MB/s
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.86 duplex=full firmware=5751-v3.29a ip=192.168.1.68 latency=0 link=yes module=tg3 multicast=yes port=twisted pair speed=100MB/s
jordan@jordan-desktop:~$ lsmod | grep ndiswrapper
ndiswrapper 244736 0
usbcore 169904 9 gspca,ndiswrapper,zc0301,usbhid,usb_storage,libusu al,ehci_hcd,uhci_hcd
jordan@jordan-desktop:~$ ndiswrapper -l
rt2500usb : driver installed
device (13B1:000D) present (alternate driver: rt2500usb)
jordan@jordan-desktop:~$

hope you can help thx

[unutbu]

limkopi, the good news is that the "lsmod" and "ndiswrapper -l" seem to indicate the driver is properly installed.

The bad news is lshw is not listing the wireless adapter. It's as though the computer does not recognize the Linksys has been plugged in. I'm not sure why this is so.

Would you please do the following:
Power down (not just reboot), then power up the computer, with the WUSB54G attached to a USB port
Then run:

lsusb # I'm just curious to see if the WUSB54G will show up here
bzip2 -c < /var/log/messages > messages.bz2
dmesg | bzip2 -c > dmesg.bz2

Please post the output of "lsusb" and post messages.bz2, dmesg.bz2 as attachments.

[Darwiesh]

thanQ .....
i have did all these steps my dear :( the ndiswrapper installed successfuly but the driver can't get any wireless connection i tried in all ways but i failed ...the problem is when i go to administrator >>wireless i can see my driver RTL8185 and all thing is good and driver installed but the nothing goes on ....need your help
my OSs are Ubuntu 8.04 64 bit & Vista ultimate 32 bit

[unutbu]

Darwiesh, please post the output of

ifconfig
iwconfig
iwlist scan
lsmod | grep ndis

[TheMaxzilla]

Ok, so I followed all of the instructions in the HOWTO, and it worked, no errors. But it won't connect to any networks. Can someone please help me resolve this problem? I don't know what other information to give you, so...

[fooman]

just dug out an old nf2 motherboard (abit nf7...classic). through on an nvidia 6600gt, a gig of ram and a belkin wireless g card that had not been used in awhile. it has the rt2500 chipset.

tried a few different approaches to get the card up to speed but had no luck. even tried this thread once before with no luck. decided to try from scratch, sooo...reinstalled hardy and after running the updates, i headed right to this thread first.

worked like a dream this time. :)

thanks

[HereInOz]

Hi All,

I have a MSI cb56g2 PCMCIA card with a Ralink 2500 chip on it, and it worked fine in Gutsy with the standard rt2500pci driver connecting with WPA-PSK security.

Since upgrading to Hardy, the connection has been very weak (low level) and the network speed has been awful - about 20KB/s across the lan - like slow internet speeds.

I re-installed Gutsy as a test, and it all began to work well again.

So I installed Hardy again, and then used the "how to" to set up the adaptor using ndiswrapper and the driver downloaded from the MSI site, and while I can connect when the Access Point is set to WEP 64 bit security, I am unable to get a connection when I set the Access Point to WPA-PSK.

Has anyone experienced this, and can anyone offer any suggestions as to how I might improve the situation.

Cheers,

Alan.

[DavidTangye]

I have installed an RT2500 PC card without needing Windows drivers (nor therefore ndiswrapper) under Hardy. Its a Minitar Wireless Cardbus MN54GCB-R: Ralink RT2500 chipset (see all cards based on this chipset at http://ralink.rapla.net/)

Also see Chipsets supported by Linux (http://www.wlug.org.nz/WirelessChipsets)
• PrismGTWirelessChipset by Intersil
• RT2x00WirelessChipset (2500) by RaLink
• Intel IPW2200
• AtherosWirelessChipset
• BroadcomWirelessChipset

for more info. There is no need to install Windows drivers for many people.

[DavidTangye]

That is interesting that the Windows driver seems to run that adapter faster. You might find that the windows driver does not support WPA. Look inside the ascii support file (.cat or .inf or something) that comes in the driver set. It indicates whether WPA is supported in its codes. You should see WEP in the definitions of its internal data codes. That is what I did with a Netgear Window driver, which confirmed that WPA was not going to work. If you do not see WPA I guess that means it is not supported in the driver.

[leona]

I am having problems with an rt2500pci card. it will list my network but it refuses to connect to it, any ideas? I have turned off all security, so I'm sure that's not an issue. Using 'stock' setup (no nsdiwrappers etc) yet, that how to looks complicated and last resort if I can't get it working.

[unutbu]

leona, have you tried using Network Manager?
(Clicking on Wireless, the Properties button, uncheck the roaming mode box, enter your ESSID, and going for a DHCP connection?)

[leona]

leona, have you tried using Network Manager?
(Clicking on Wireless, the Properties button, uncheck the roaming mode box, enter your ESSID, and going for a DHCP connection?)
Hi there, thank you but yes with little joy, it doesn't even seem to be making any attempt to contact the router, I can't see it in my 'attached devices' list. very odd.

[unutbu]

To help us gather more information about your situation, please post the output of the following commands

ifconfig
iwconfig
iwlist scan
cat /etc/network/interfaces
sudo /etc/init.d/networking restart

[leona]

To help us gather more information about your situation, please post the output of the following commands

ifconfig
iwconfig
iwlist scan
cat /etc/network/interfaces
sudo /etc/init.d/networking restart


Hi & thanks, I've got the first 3, just go and get you the rest of them :)

from lspci -nn

00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge [1106:3189]
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8235 PCI Bridge [1106:b168]
00:0b.0 FireWire (IEEE 1394) [0c00]: NEC Corporation uPD72874 IEEE1394 OHCI 1.1 3-port PHY-Link Ctrlr [1033:00f2] (rev 01)
00:0e.0 Network controller [0280]: RaLink RT2500 802.11g Cardbus/mini-PCI [1814:0201] (rev 01)
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 82)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177]
00:11.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06)
00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 50)
00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102 [Rhine-II] [1106:3065] (rev 74)
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV44A [GeForce 6200] [10de:0221] (rev a1)


From iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:14:6C:01:26:7A
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



from ifconfig

eth0 Link encap:Ethernet HWaddr 00:0c:6e:07:18:21
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:18

eth0:avahi Link encap:Ethernet HWaddr 00:0c:6e:07:18:21
inet addr:169.254.2.3 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:18

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:3059 errors:0 dropped:0 overruns:0 frame:0
TX packets:3059 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:154824 (151.1 KB) TX bytes:154824 (151.1 KB)

wlan0 Link encap:Ethernet HWaddr 00:0e:2e:50:64:38
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-0E-2E-50-64-38-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


From lshw -C Network

*-network:0
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: e
bus info: pci@0000:00:0e.0
logical name: wmaster0
version: 01
serial: 00:0e:2e:50:64:38
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt2500pci latency=32 module=rt2500pci multicast=yes wireless=IEEE 802.11g
*-network:1
description: Ethernet interface
product: VT6102 [Rhine-II]
vendor: VIA Technologies, Inc.
physical id: 12
bus info: pci@0000:00:12.0
logical name: eth0
version: 74
serial: 00:0c:6e:07:18:21
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=half latency=32 link=no maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=10MB/s

[leona]

Ok here is the rest

iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

cat /etc/network/interfaces

auto lo
iface lo inet loopback

iface eth0 inet dhcp
gateway 192.168.1.200

auto eth0

and finally
sudo /etc/init.d/networking restart

[sudo] password for linux:
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth0.pid with pid 18140
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:0c:6e:07:18:21
Sending on LPF/eth0/00:0c:6e:07:18:21
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.200 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:0c:6e:07:18:21
Sending on LPF/eth0/00:0c:6e:07:18:21
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ OK ]


I hope that is of help in working out what the problem is.

Just looking at this myself, shouldn't there be a wlan0 config in the interfaces file? Can I add one manually?

Thank you.

[unutbu]

First: my biggest concert is the output of iwlist scan:

wlan0 No scan results

Even without a connection, "iwlist scan" should return a list of all the access points (routers) your network adapter can detect. If you are not seeing anything, it means the signal between your network adapter and the router is not good. Maybe just to debug this situation, would it be possible to bring the router closer to your computer?

No connection will ever be formed until "iwlist scan" starts returning some access points, so keep fiddling with the physical location of your network adapter and router until you start seeing something.


Second: Is your eth0 (ethernet card) plugged into anything? If not, it may be helpful to
shut it off for now by doing two things:

sudo ifdown eth0

gksu gedit /etc/network/interfaces

Put a # sign in front of these two lines:


iface eth0 inet dhcp
#gateway 192.168.1.200

#auto eth0



Third: Network Manager seems to have failed to make a proper entry for your wlan0 wireless interface. No worries, we can do it ourselves:

Add these lines to /etc/network/interfaces:

auto wlan0
iface wlan0 inet dhcp
gateway 192.168.1.1 # Change 192.168.1.1 to your router's IP address
netmask 255.255.255.0

Fourth: reboot your computer. Do a hard power off / power on. Some network adapters seem to need this. After you get things working, you may find you do not need this, but let's do this to eliminate one otherwise hard-to-debug problem.

[leona]

Sorry for the delay in reply, that wasn't straigh forward, had noticed it had decided to disable all network devices, so I removed the interface file and set it up again via network.

So some success in that it can now 'see' at network, but it still refuses to connect to it, even though I have no security, as far as my router is telling me, its not even bothering to make a connection.


iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:14:6C:01:26:7A
ESSID:"xena"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=49/100 Signal level=-66 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000002f3c9ae5c

[unutbu]

Congratulations. We're making progress.

Here are some options:


Try Network Manager again. It's easy, so why not?
Check /etc/network/interfaces looks as described in my previous post.
Type

sudo /etc/init.d/networking restart

Shutdown/power up. If no connection starts automaically, type

sudo /etc/init.d/networking restart

I know it sounds silly, but sometimes it works.
If none of the above work, we can try the solution taken from
http://ubuntuforums.org/showthread.php?t=684495:

sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid "xena"
sudo iwconfig wlan0 mode Managed
sudo dhclient wlan0
If it works we can then put these commands in a script so the computer can run them at boot time for you automatically.

[leona]

Hi there unutbu and thank you again, sadly though, this hasn't worked, it will sit there and display a network, just will not connect to it. Very odd,
Is it worth persuing this further or locate a card that will work?

[unutbu]

leona, since you can get output from "iwlist scan", your network card can communicate with your router. Your router told your network card that its essid is "xena", for example. Therefore, your hardware is probably fine, and it is only a matter of configuring software to make everything work.

I do not think buying a different card is necessary. Sorry for the trouble you're having. I'm afraid it has more to do with my inability to deliver the right piece of advice than any inherent problem with your hardware. (Note to forum readers: I welcome suggestions! All help appreciated!)

Here are some options:

Post the output of

route
iwconfig
sudo /etc/init.d/networking restart
cat /etc/network/interfaces

Perhaps an error message will give us a clue as to what is going wrong.
Try using wicd instead of Network Manager. Some forum posters have reported that their cards worked automatically after installing wicd and going through the usual configuration GUI. Be warned however, that installing wicd uninstalls Network Manager. So if wicd does not work for you and you want to return to Network Manager, you will need to download the network-manager-gnome and network-manager .deb (package) files from http://packages.ubuntu.com/ from a computer with an internet connection, copy them to your machine, and re-install them by double-clicking on the debs.
Wait for a more knowledgable forum reader to kindly lend a hand. (Sorry I haven't been more helpful).

[leona]

Hey unutbu, I really do appriecate your help and that you took time out to lend a hand, so don't go apologiesing ok, its ok, Linux can be very frustrating at thimes, I feel you need a LOT of paicents to get on with this OS, and a degree in computer sience (which I don't have) would also help :)
Ok I'll try and get you that out put you asked for this week, I agree with your reasoning though, that its detecting the network, but something is preventing it from using it, some debugging infomation would be good, to try to determine why its refusting to work, is there some verbosity mode I could put it in to see output? Not that I'd understand what it would be saying, but could google it :)
Thank you again.

[leona]

it would seem, from doing some forum searches, that this is a long standing known bug with the current kernal and NetworkManger (so why hasn't it been fixed?), seems the work around is to install windows driver somehow, al seems a bit, what's the word, messy and complicated, to me, was hoping for a more cleaner soluciton.

[unutbu]

If you go to the first post in this thread, you will find wieman01's step-by-step guide on using ndiswrapper with your wireless adapter. If you have any questions about that guide, you can post back here. I'll be happy to help if I can.

(Here is a tip, though, that may help: a lot of very active experienced forum helpers don't bother reading posts with dozens of replies -- like this one. Sometimes creating a new thread in the Absolute Beginners forum generates a better response because there are teams of helpers there who search for unanswered posts.)

[leona]

Hi unutbu, thank you, yes I'll print off those instructins and see how far I get with them, I have the windows disk.

Maybe if enough people report this bug on this bug report (https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/134660) there might be some hope of it being fixed.

[leona]

oh no, I am a stupid, stupid, stupid girl! Cut me off a large slice of humble pie, it was MY mistake.

I forgot to check the router, I had removed all security, but what I had overlooked was "Wireless Card Access List" I had forgotten I had set this up, once I had disabled this, the card worked, so now I've added its MAC address to the list, enabled security and restarted it works now (although only a 20% signal, but its only 6 foot away from the router!).

So thank you so much for your help, but this time, it was the squidgy bit between the keyboard and the chair that was the problem, I feel so dum, d'oh! :(

[unutbu]

Ah! I'm really glad to hear you got it working. MAC filtering... I'll have to try to remember that for next time.

Thanks for getting back to us and posting the solution.

[wieman01]

oh no, I am a stupid, stupid, stupid girl! Cut me off a large slice of humble pie, it was MY mistake.

I forgot to check the router, I had removed all security, but what I had overlooked was "Wireless Card Access List" I had forgotten I had set this up, once I had disabled this, the card worked, so now I've added its MAC address to the list, enabled security and restarted it works now (although only a 20% signal, but its only 6 foot away from the router!).

So thank you so much for your help, but this time, it was the squidgy bit between the keyboard and the chair that was the problem, I feel so dum, d'oh! :(
Glad to hear it works. By the way... MAC filtering adds no real security at all. Please use WPA2 encryption instead which is the best option there is. MAC addresses can be faked in a matter of seconds.

[wieman01]

Ah! I'm really glad to hear you got it working. MAC filtering... I'll have to try to remember that for next time.

Thanks for getting back to us and posting the solution.
Unutbu, there are more such "hidden traps". See section "Common stumbling blocks" in this thread:

http://ubuntuforums.org/showthread.php?t=202834

I had totally forgotten about them as well... :-)

[Cushie]

Hardy 8.04 with Belkin f5d7050, USB g adapter the hardware is recognised as v1000 but I used v3000 which also has the rt2500usb drivers.
Note v4000 uses the zd1211 which is set up automatically with Hardy's own drivers.

The driver files must be copied to the home directory , not a sub directory. All went well except :-
ndiswrapper -l gave the alternate driver as p54usb (dont think that is a problem?)

Set up using Network manager rebooted and and all OK.


I notice there is a GUI front end ndisgtk Windows Wireless Drivers which may be worth a try, I installled it and ran it from Sytem/administration and it shows the rt2500usb present.

Many thanks for the workout, appreciated.

[Maupertus]

*Ahum, blush* euhm...what if you made a mistake and used the WMP54G v 4.1 Rt61 driver for the blacklist etc. instead of the v 4.0 Rt2500...

(sorry, I can just feel the earth open beneath me right now :lolflag:)

[wieman01]

*Ahum, blush* euhm...what if you made a mistake and used the WMP54G v 4.1 Rt61 driver for the blacklist etc. instead of the v 4.0 Rt2500...

(sorry, I can just feel the earth open beneath me right now :lolflag:)
You can remove stuff from the blacklist... just open it with a text editor. Do you know how to do that?

[Maupertus]

I hope you can help me, as I haven't got that much experience with wifi cards.

I basicly followed your guide like so:

Blacklist Ralink driver:


echo 'blacklist Rt61' | sudo tee -a /etc/modprobe.d/blacklist/
Now find the right driver in the resulting folder & deploy it (folder should also contain other driver files i.e. .cat, .sys)


sudo ndiswrapper -i <your_ralink_driver>.inf/

and the output was as follows:


rt61 : driver installed
device (13B1:000D) present (alternate driver: rt61pci)


But that killed my connection after restart.
When I looked at the hardware I saw that although I just bought the card, it's a WMP54G v4 not a v4.1, can you tell me how to correct my mistake?

Thanks!

[the_weekend]

I got my setup working this morning!

So there are a few things to note for amd64 users on Gutsy:

You need a 64-bit driver, which I found here: http://forums.linksys.com/linksys/board/message?board.id=Wireless_Adapters&message.id=2699

Install it as you normally would (as per the sticky) with ndiswrapper. However, this driver doesn't seem to like the wlan0 interface id, so you need to use rausb0 in your /etc/network/interfaces file. Other than that, make sure that the appropriate drivers are listed in your /etc/modprobe.d/blacklist file, and that ndiswrapper is included in your /etc/modules file. Reboot, and voila! (At least that's how it worked for me.)

Thanks again to everyone that helped out with this! :)

This driver worked okay for me, but I found this one works better: http://www.planetamd64.com/lofiversion/index.php?t14735.html

[Blackmag+c]

hey

I have the rt73usb chipset

and as far as I can tell the steps worked and I was surfing for maybe like 5 minutes and then it just dropped and now won't connect again.

the ouput of ndiswrapper -l

was 'rt73 : invalid driver!'

what gives?

ID 148f:2573 RaLink Technology, Corp.

[wieman01]

Perhaps you have the wrong driver... Are you on 32-bit or 64-bit? Where does the driver come from?

[Narel]

I have the Netopia 3D Reach (Ralink rt2500 usb adapter). I'm really having a hard time installing it. Ndiswrapper is installed and that about how far I have got done.

[unutbu]

Hello Narel,

When you boot up do you see any lights on the wireless card turn on?
If so, it means the machine detects the wireless adapter.
If not, it means we need to check that ndiswrapper and the Windows driver have been installed properly.

Please open a terminal (http://www.psychocats.net/ubuntu/terminal)
and post the output of the following commands:

lsusb
ndiswrapper -l
cat /etc/network/interfaces
iwlist scan

[Narel]

Yeah, there is a constant green light, but it should be blinking orange.

I am at work right now, but I'll post the output when I get back home.

[Narel]

narel@Sonny:~$ lsusb
Bus 004 Device 008: ID 0781:9393 SanDisk Corp.
Bus 004 Device 007: ID 148f:2570 Ralink Technology, Corp. 802.11g WiFi
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
narel@Sonny:~$ ndiswrapper -l
narel@Sonny:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

narel@Sonny:~$ iwlist scan
lo Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

eth0 Interface doesn't support scanning.

narel@Sonny:~$

[unutbu]

Okay Narel. The "ndiswrapper -l" output would have read something like

neta5agu : driver installed
device (07D1:3A08) present

if the Windows driver had been installed. That is, you should have gotten some output, although your driver is something other than "neta5agu". So it appears you have installed the ndiswrapper package (since the machine knew about the ndiswrapper command) but the Windows driver has not yet been installed.

You know, I believe Hardy comes with native driver support for RT2500 cards, so we don't we try connecting using the native driver first?

Do you see an icon on your gnome panel that looks like two overlapping computers? That would be the Network Manager app. Click on it and try to configure the wireless device using Network Manager first. If you don't see the Network Manager icon, right-click on the gnome panel, select "Add to Panel" and then select "Network Monitor".

You'll will need to know the router's ESSID. Try going for a Automatic Configuration using (DHCP) first. To make establishing a connection easier, I recommend shutting off WEP or WPA encryption on the router for now and just try to establish a clear connection first. Once you get such a connection, you can then try to add security. Also make sure MAC address filtering is turned off on your router (for now).

Configure the settings, make a note of your settings, then see if your network connection is working by using a web browser and/or by typing

iwlist scan
ping 209.85.171.99 # google.com

If it doesn't work, type

sudo /etc/init.d/networking restart

If it still doesn't work click on the Network Manager icon and toggle the "Enable" box. The GUI for Network Manager is different from Gutsy to Hardy so my description here may not be correct in the specifics. But the idea is to toggle wireless off and then on to try to get the connection to restart.

Also note that sometimes even when you have the right configuration settings in Network Manager, your wireless adapter may not work until you shutdown the machine and do a power up. (Rebooting may not be sufficient, you may have to shutdown and then power on.)

So if all that still does not work, try shutting down and powering up. Sometimes the wireless card needs to be powered up with the right settings in order for it to work.

If none of that works, post back with a description of what you tried, and we'll think about what to do next. We can always try the ndiswrapper approach if the above doesn't work.

[Narel]

I had some progress. I was able to go to Google, but it took some time for the page to load. It also started openssl-blacklist, but it had a slow download speed and it stopped after a few seconds. The light on usb adapter blinks orange for a few seconds and it goes solid green.

[Narel]

I shutdown my pc and turn it back on. Now the internet connection is working for longer periods of times and then it will stop. It repeats that process over and over. What am I missing? Can I fix the problem?

[Narel]

Can anyone help me? Also, I changed the channels.

[unutbu]

Please post the output of

iwlist scan

[Narel]

lo interface doesn't support scanning.
eth0 interface doesn't support scanning.
wmaster0 interface doesn't support scanning.
wlan0 no scan results

[unutbu]

Narel, I don't know for sure the solution to your problem.

Even without a connection, "iwlist scan" should return a list of all the access points (routers) your network adapter can detect. If you are not seeing anything, it means the signal between your network adapter and the router is not good. Maybe just to debug this situation, would it be possible to bring the router closer to your computer? Or try minimizing dense matter or metal along the straight-line path between the two devices.

No connection will ever be formed until "iwlist scan" starts returning some access points, so keep fiddling with the physical location of your network adapter and router until you start seeing something.

If you managed to reach a Google page, then it means "iwlist scan" must have been working at that time, but then the connection was lost some time later.
It would be interesting to see the output of iwlist scan when the connection is working.

[Narel]

Okay.
Thx

Should I try the ndiswrapper again?

[unutbu]

You have two choices, both reasonable:

Option 1: Stick with the native Linux driver
Option 2: Try ndiswrapper+Windows driver

Option 1 Pros:

First, you seem to be quite close to having a good connection. Usually, once you succeed in forming a connection, it just works. If for some reason the connection is lost, usually it can be regained by toggling the "Enable wireless" box in Network Manager, or by typing

sudo /etc/init.d/networking restart

(Have you tried that already?)
Second, by using the native Linux driver you can benefit from bug fixes or improvements in the driver as they come out. If you use ndiswrapper+Windows driver, you are at the mercy of a black box.


Option 2 Pros:

If the native driver is for some reason not working for you, you might as well try
the Windows driver.


So, this is what I would suggest: try making your current setup work by experimenting with
the location of the router and wireless adapter, and by issuing

iwlist scan # to see the quality of the connection
sudo /etc/init.d/networking restart # to start/restart a connection

If you find no way to establish a strong connection, then
try ndiswrapper. Start by reading weiman01's excellent guide:
http://ubuntuforums.org/showthread.php?t=563547

You'll need Windows XP drivers for you wireless adapter. You might be able to locate the latest driver for the Netopia 3D Reach on the web, or you can try the one that came on a CD with your device.

[harveywb]

Dapper Drake users should take a look at this thread (http://ubuntuforums.org/showthread.php?t=192588) if this one doesn't work. This guide was tested with Feisty Fawn, Gutsy Gibbon, and Hardy Heron.
--
To all RT73 users, please also see this post (http://ubuntuforums.org/showthread.php?p=4732883). Thanks to Kiefer Rodriguez (http://ubuntuforums.org/member.php?u=490665) for this solution.

Please post to this Launchpad bug report (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/163020) with all of your specs, if you have problems with a Ralink based wireless adapter.

This is a simple guide for all Ralink based wireless adapters and everyone who wants to replace the Linux driver with "ndiswrapper" (e.g. because you want to make use of either Network Manager (http://www.gnome.org/projects/NetworkManager/) or WICD (http://wicd.sourceforge.net/)).

INSTRUCTIONS:

Get the latest version of the Windows driver for your card from Linksys' website (http://www.linksys.com/servlet/Satellite?c=L_CASupport_C1&childpagename=US%2FLayout&cid=1166859840888&pagename=Linksys%2FCommon%2FVisitorWrapper&lid=4088837314B372&displaypage=download) or from the CD that came with your device (whatever vendor).



Install "ndiswrapper" package with working internet connection (Ethernet):




Install "ndiswrapper" package without working internet connection (alternatively, install it via Synaptic/Adept):




Load new driver module (may not be necessary any longer, but does no harm either):




Add the module to "/etc/modules" to have it load automatically:




Create alias directive:




Pick a valid Ralink driver based on the chipset of your card (you might blacklist all of them if you are not sure):




Blacklist Ralink driver:




Now unzip the driver archive you have just downloaded (e.g. in your home directory):




Now find the right driver in the resulting folder & deploy it (folder should also contain other driver files i.e. .cat, .sys):




Make sure it has installed correctly:




The output should yield something like this:




Last but not least open this file...




...and add these 2 lines if they are not there yet [also try without adding them if Network Manager does not pick up the card & reboot]:


You can now safely delete the extracted driver files & folders. Then reboot the computer and see if you can connect using your favorite networking applet (e.g. Network Manager, WICD, Wifi Radar, etc.).

Feedback is - as always - appreciated.

CHANGE LOG:
30/09/2007: Minor fixes.
07/10/2007: Expanded "blacklist".
20/10/2007: Added missing part concerning "interfaces" file.
22/10/2007: Load module "ndiswrapper" at boot.
23/10/2007: Enhanced blacklist.
07/11/2007: Bug fix for Network Manager.
12/11/2007: Updated blacklist & module section.
13/01/2008: Launchpad bug report.
15/04/2008: Update for Hardy.
17/04/2008: RT73 note.

In using amd-64 ubuntu hardy didn't install correctly even using 64 bit driver from realtek for 8185. Installed x86 version of ubuntu and all was fine. I would have liked to gotten the 64 bit installed. Computer was DELL 531.

[tsteuerwald]

Hi all!

I have currently again a very old problem:
WLAN is only working after an additional ifdown/ifup. :-(

It's a MSI PC54G2 (Ralink RT2500 chip based), I'm using Ubuntu 8.10. I've been using now ndiswrapper since 9 months. At the beginning I had sometimes the ifdown/ifup issue, but since three-four month this issue didn't appeared any longer.
Since two days it happens very often, let's say everytime :mad:

All the time I had these two lines in /etc/rc.local:

ifdown wlan0
ifup wlan0


Now I commented out these lines and changed it to:

/etc/init.d/networking restart


I've added also one line per script file to check if it is executed on startup.

In /etc/rc.local:

echo "works" > /tmp/test_rclocal


In /etc/init.d/networking:

echo "works" > /tmp/test_networking


This is the content of /etc/network/interfaces:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-psk <my-network-key>
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid <my-ssid>
pre-up ifconfig wlan0 up


Next thing I will try is to pipe the output of the networking script to a file in /var/log to see the output.

Anyhow this issue is really annoying, I'm wondering why this can not be fixed reliable.

Cheers
Timo

[wieman01]

Still the same issue. No resolution yet.

[tsteuerwald]

Any other reliable alternative beside using ndiswrapper?
After upgrading to Ubuntu 8.10 the blacklist entries of the built-in drivers has been commented out and there appeared again the issue that this driver is pretty slow. Especially if you have a 16.000 Kbit/s DSL flatrate. :) So it seems that these drivers won't help. :(

[unutbu]

tsteuerwald, the suggestion below does not really unearth the cause of the problem, but it may help cut down on the annoyance:

Put this in a file like /usr/local/bin/get_connection.sh


#!/bin/bash
ipaddr=google.com
sleep_amount=1
dig +time=1 +retry=0 "$ipaddr" 2>/dev/null 1>&2
while [ "$?" -ne 0 ] && [ "$sleep_amount" -le 1000 ]; do
/etc/init.d/networking restart
sleep "$sleep_amount"
sleep_amount=$(($sleep_amount*2))
echo "$sleep_amount"
dig +time=1 +retry=0 "$ipaddr" 2>/dev/null 1>&2
done


Make it executable:
chmod 755 /usr/local/bin/get_connection.sh

Then put

/usr/local/bin/get_connection.sh &

in /etc/rc.local.

The 'dig' command will have a return value of 0 if you have a connection to ipaddr,
and will return a non-zero value if you don't have a connection.

If you don't have a good connection, then the script will fall into the while-loop, and keep calling "/etc/init.d/networking restart" until you have a connection. The time between calls to get_connection.sh will increase geometrically. Thus, when you boot up, the restart command will be called frequently until you have a connection -- if a connection is possible. If you happen to boot up when no network connection is possible, the frequency of the calls will slow down until it finally gives up after 10 or so tries.

[tsteuerwald]

Thank you very much unutbu! You are my personal hero of the day! :)
That seems to be a pretty good workaround.
Anyhow, I'm wondering why this pretty popular ifdown/ifup problem still exists.

Cheers
Timo

[wieman01]

Very nice, unutbu. You ought to own this thread, I mean it. :-)

[unutbu]

tsteuerwald, wieman01, thank you for your kind words. They make me feel great! :)

[Ant68]

hello,
I am struggling to set up the wifi connection for my RTL8185 wireless card. I have followed all the instructions at the beginning of this post and I had it to work for hardy (8.04).

I have now upgraded to intrepid and followed all the instructions again but with no luck.The driver seems not to be set up correctly and when I try to configure the network manager the system freezes.

I have set up different variations of the interfaces file. the latest being the default one:
auto lo
iface lo inet loopback

This is what I get when I start the network again:
my-desktop:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... Ignoring unknown interface wlan0=wlan0.
Ignoring unknown interface eth1=eth1.


iwlist:

hemona@hemona-desktop:~$ iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 Interface doesn't support scanning.
wmaster0 Interface doesn't support scanning.
wlan0 No scan results
pan0 Interface doesn't support scanning.



What do you suggest I am doing to get the wireless RTL8185 working with 8.10?

[unutbu]

I'm not sure if I can help you Ant68. I have no particular knowledge about the rtl8185,
and so I'm mainly going by the information in this post:
http://ubuntuforums.org/showpost.php?p=3967740&postcount=2
(I don't recommend you follow those directions literally, however, since Ubuntu 8.10 ships with ndiswrapper 1.52, while those instructions downloads and compiles ndiskwrapper 1.50.)

Nevertheless, let's check how close your setup matches that which would be achieved by following those instructions. Please post the output of the following:

ls -lR /etc/ndiswrapper/
ndiswrapper -l
cat /etc/modules
cat /etc/modprobe.d/blacklist

Turn off all encryption (WEP or WPA) on your router.
Turn off MAC address filtering on your router.
We can try turning these things back on later after we succeed at getting a connection.

[tlois]

I am adding this for eee box b202 users who have installed ubuntu 8.10 with AzurWave aw-ne766 wireless- rt2860 driver. After working on the wireless problem for a few days, I finally found this and it worked:

http://www.ubuntu-eee.com/wiki/index.php5?title=Getting_the_network_drivers_worki ng_on_the_901

for the people like me, who know just a little about linux, sometimes you can get hung up by just not capitalizing a word in the terminal. type things exactly as they are.

another good thing to have around the house is a linksys usb wireless dongle. that worked no problem and helped to continue getting the internal wireless working.

sorry if this is in the wrong place or is already here, but read this thread until i was bleary eyed last night. gave up. did a google search with apparently just the right terms and found the above.

(to the people who post all this great stuff, thanks. i am having a lot of fun with linux/ubuntu. now have versions of it on an eee701, an ibm thinkpad and this new little baby)

[unutbu]

Congratulations, tlois, on getting networking running! That's often the most challenging part of setting up a linux box.

Moreover, thank you for taking the time to post what worked for you. If enough of us do that, linux will become easier and easier to use :)

Enjoy your new Linux/Ubuntu systems!

[brun059]

tlois, can only confirm what unutbu said : "thank you", your link gives me hope again :)

your post plus the one from surfed at http://forum.eeeuser.com/viewtopic.php?id=49865&p=1 together finally made it work for me.

(after a long weekend trying to get ubuntu 8.10 working on my eee-1000 I was on the verge of giving in, bowing to big-MS and install XP :( )

eee eeepc wireless intrepid 8.10 ralink ra2860

[tlois]

Following up here to say that I installed eeebuntu on the eee box and everything worked without adding driver wrappers, etc. (Did it because of a strange reboot freeze problem with regular Ubuntu.)

Bruno, glad you got it figured out. I'll, personally, never go back to MS.

Happy New Year.

[ProNux]

Guys,

I have Edimax EW-7318USg based on RT73. I got this working using the native Linux driver from Ralink when I started using Ubuntu on kernel version 2.6.24-19. But lately, after installation of kernel 2.6.24-22 onwards, the WLAN became unstable. Even after removing the later kernels and booting to the old kernel version.

I tried running Live Intrepid Ibex and found it stable.

Have I missed something here?

Thanks.

[unutbu]

Well, I could be wrong, but given the facts you've reported, it seems to me that the "instability" is not related to the kernel.

Wireless devices have no memory. If the drivers and config files are the same, the performance of the device will be the same as long as there is no hardware failure.

So if you've reverted to your old kernel and are still experiencing instability, then
the cause is either hardware failure or some environmental condition like bad weather or electromagnetic interference.

My experience with wireless devices suggest that dropped connections have a gamma function probability distribution (yes, I admit it, I collect such data) -- similar to the wait times of radioactive decay. A funny side-effect of this is that sometimes dropped connections seem to happen quite frequently and then during other periods quite infrequently. You need to collect a considerable amount of data before you can tell if one setup is truly more stable than another.

This is just my inexpert opinion. I hope this helps. I'd love to be proven wrong and learn something new.

[ProNux]

Thanks for the info unutbu.

I forgot to mention that I am on dual-boot (Windows XP/Ubuntu Hardy). At Windows, I got no problems at all, running continuously for hours. I tend to agree that it may not be kernel related.

At the network manager, sometimes, the WLAN has no IP address reported (0.0.0.0) but on the net monitor, it has (192.168.0.XXX, DHCP).

When my connection drops, I just do

sudo dhclient rausb0

to restore. But still, this is not the corrective action.

By the way, I just have found this thread today. Might read it all over again tomorrow (it's 1AM now, gotta sleep :)). Thanks for this thread.

[wieman01]

You're welcome. Not sure how useful this thread still is, most Ralink related problems seem to have been solved as of 8.10. Let's keep it open for a few more months then.

[ProNux]

You're welcome. Not sure how useful this thread still is, most Ralink related problems seem to have been solved as of 8.10. Let's keep it open for a few more months then.
Thanks.

I might switch to Interpid if I cannot fix it soon. But still, I am just curious what's the reason behind the instability. And upgrading to Intrepid only gets rid of my RT73 problem, not solving it.

[ProNux]

Guys, I think my problem (unstable RT73 USB WLAN)is related to "conflict" with the built-in WLAN of my laptop.

Will it really cause the problem since both WLANs are active and both acquires separate IP addresses from one AP? What I did was just disable my built-in WLAN (Intel 3945).

So far, my RT73 is now okay.

Got to say sorry to my RT73 Wlan...

[wieman01]

Good for you, dude. Yes, a conflict seems possible.

[Fevrin]

Now that Jaunty's been released, I thought I'd give it a go (64-bit), but the inability to connect wirelessly has stopped me straight away. Intrepid (64-bit) also has this issue, but Hardy (64-bit) doesn't.

I have a Hawking HWP54G rev. 01 card, which uses the rt2500pci driver, according to Jaunty's version of 'lspci -vvnn'. But I won't bore you with details; I'll let the following speak for itself:

Hardy 'lspci -vvnn':
03:07.0 Network controller [0280]: RaLink RT2500 802.11g Cardbus/mini-PCI [1814:0201] (rev 01)
Subsystem: Edimax Computer Co. Unknown device [1432:0b54]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fe8fc000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-Jaunty 'sudo lspci -vvnn':
03:07.0 Network controller [0280]: RaLink RT2500 802.11g Cardbus/mini-PCI [1814:0201] (rev 01)
Subsystem: Edimax Computer Co. Device [1432:0b54]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fe8fc000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: rt2500pci
Kernel modules: rt2500pciHardy 'ifconfig wlan0':
wlan0 Link encap:Ethernet HWaddr 00:0e:3b:04:93:27
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20e:3bff:fe04:9327/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:65414 errors:0 dropped:0 overruns:0 frame:0
TX packets:46443 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:68231535 (65.0 MB) TX bytes:15130286 (14.4 MB)Jaunty 'sudo ifconfig wlan0':
wlan0 Link encap:Ethernet HWaddr 00:0e:3b:04:93:27
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)Hardy 'sudo iwconfig wlan0':
wlan0 IEEE 802.11g ESSID:"HOME"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1B:11:62:B9:20
Bit Rate=1 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key: sorry!
Link Quality=62/100 Signal level=-55 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0Jaunty 'sudo iwconfig wlan0':
wlan0 IEEE 802.11bg ESSID:"HOME"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key: sorry!
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0Hardy 'sudo iwlist wlan0 scanning':
wlan0 Scan completed :
Cell 01 - Address: 00:1B:11:62:B9:20
ESSID:"HOME"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=42/100 Signal level=-56 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=000002cee6024158Jaunty 'sudo iwlist wlan0 scanning':
wlan0 Scan completed :
2 Cell 01 - Address: 00:1B:11:62:B9:20
3 ESSID:"HOME"
4 Mode:Master
5 Channel:6
6 Frequency:2.437 GHz (Channel 6)
7 Quality=52/100 Signal level:-55 dBm
8 Encryption key:on
9 IE: Unknown: 0004484F4D45
10 IE: Unknown: 010482848B96
11 IE: Unknown: 030106
12 IE: Unknown: 2A0100
13 IE: Unknown: 32080C1218243048606C
14 IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F 00
15 IE: Unknown: DD1E00904C334E101EFFFF0000000000000000000000000000 00000000000000
16 IE: Unknown: DD1A00904C3406070700000000000000000000000000000000 000000
17 IE: Unknown: 2D1A4E101EFFFF000000000000000000000000000004000000 000000
18 IE: Unknown: 3D1606070300000000000000000000000000000000000000
19 IE: Unknown: DD050050F20502
20 IE: Unknown: DD820050F204104A0001101044000102103B00010310470010 B64B8D83CDCF327F82984058B975B1C81021000E442D4C696E 6B2053797374656D731023000744495 22D3635351024000541312F4132104200046E6F6E651054000 800060050F204000110110017587472656D65204E204749474 142495420526F757465721008000200 04
21 Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
22 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
23 48 Mb/s; 54 Mb/s
24 Extra:tsf=000002cdc71e0bc9
25 Extra: Last beacon: 56ms agoand both /etc/network/interfaces were the same:

auto lo
iface lo inet loopbackAlso, I've attached the relevant part of dmesg's output. So does anyone see anything wrong or can you think of anything as to why my wireless card works in Hardy, but not either of its successors? I'm concerned that future Ubuntu releases may not support my card for good :(

Lastly, I have to say that it's kind of annoying that this forum's file attachment component doesn't accept a file without an extension....

[unutbu]

Fevrin, I can't say for sure if this will help you or not, but perhaps try this:

#!/bin/bash
sudo ifup wlan0
# routerip=192.168.1.1
routerip=google.com
sleep_amount=1
dig +time=1 +retry=0 "$routerip" 2>/dev/null 1>&2
while [ "$?" -ne 0 ] && [ "$sleep_amount" -le 1000 ]; do
sudo /etc/init.d/networking restart
sleep "$sleep_amount"
sleep_amount=$(($sleep_amount+2))
echo "$sleep_amount"
dig +time=1 +retry=0 "$routerip" 2>/dev/null 1>&2
done

Save the script in, say, ~/bin/up

Make it executable

chmod 755 ~/bin/up

and run it like this:

up

The script will check if an internet connection exists, and if not, it will run "sudo /etc/init.d/networking restart". It will do this repeatedly until a connection is established.

I find I sometimes have to run the "networking restart" command a few times before connection is actually established.

[joylessdave]

ive just installed xubuntu 9.04 on a old pc with a pci wifi card

i don't know who the manufacturer of the card is, the chip on the card is a RT2560F

ethernet is working correctly

lspci identifies the card as

00:09.0 Network controller: RALink RT2500 802.11g Cardbus/mini-PCI (rev 01)

both networkmanager and wicd can see the card and both pick up the wireless networks in the area

networkmanager continually asks for the wep key
wicd just fails at obtaining IP address

dmesg | grep wlan0 give the following:
[ 46.254306] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 51.878227] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 54.044791] wlan0: authenticate with AP 00:18:4d:6a:2d:f0
[ 54.070900] wlan0: authenticated
[ 54.070934] wlan0: associate with AP 00:18:4d:6a:2d:f0
[ 54.073588] wlan0: RX AssocResp from 00:18:4d:6a:2d:f0 (capab=0x431 status=0 aid=2)
[ 54.073608] wlan0: associated
[ 54.079767] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 54.432269] wlan0: authenticate with AP 00:18:4d:6a:2d:f0
[ 54.475778] wlan0: authenticated
[ 54.475807] wlan0: associate with AP 00:18:4d:6a:2d:f0
[ 54.567281] wlan0: RX ReassocResp from 00:18:4d:6a:2d:f0 (capab=0x431 status=0 aid=2)
[ 54.567302] wlan0: associated
[ 64.504044] wlan0: no IPv6 routers present
[ 135.976616] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 136.107420] wlan0: deauthenticating by local choice (reason=3)
[ 136.891150] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 138.364948] wlan0: authenticate with AP 00:18:4d:6a:2d:f0
[ 138.366480] wlan0: authenticated
[ 138.366496] wlan0: associate with AP 00:18:4d:6a:2d:f0
[ 138.370080] wlan0: RX AssocResp from 00:18:4d:6a:2d:f0 (capab=0x431 status=0 aid=2)
[ 138.370101] wlan0: associated
[ 138.386809] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 148.504098] wlan0: no IPv6 routers present
[ 215.014572] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 215.078821] wlan0: deauthenticating by local choice (reason=3)
[ 215.386372] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 216.852863] wlan0: authenticate with AP 00:18:4d:6a:2d:f0
[ 216.854278] wlan0: authenticated
[ 216.854293] wlan0: associate with AP 00:18:4d:6a:2d:f0
[ 216.857888] wlan0: RX AssocResp from 00:18:4d:6a:2d:f0 (capab=0x431 status=0 aid=2)
[ 216.857907] wlan0: associated
[ 216.861966] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 227.080044] wlan0: no IPv6 routers present
[ 295.022396] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 295.087992] wlan0: deauthenticating by local choice (reason=3)
[ 295.382375] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 296.852864] wlan0: authenticate with AP 00:18:4d:6a:2d:f0
[ 296.854348] wlan0: authenticated
[ 296.854363] wlan0: associate with AP 00:18:4d:6a:2d:f0
[ 296.858085] wlan0: RX AssocResp from 00:18:4d:6a:2d:f0 (capab=0x431 status=0 aid=2)
[ 296.858105] wlan0: associated
[ 296.862180] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 307.020045] wlan0: no IPv6 routers present

i read in several other forums that the no ipv6 routers message is common and that disabling ipv6 makes no difference but just to be safe i blacklisted ipv6

ip a | grep inet6 now give no response however dmesg | grep wlan0 still has the no ipv6 routers message

unfortunately i cannot disable encryption as people are using the network at the same time to test if it can connect at all

i then attempted to setup the connection manually however the card is not identified by ifconfig / iwconfig if a network manager is not running

~~~~~~~~UPDATE~~~~~~~

ifconfig

eth0 Link encap:Ethernet HWaddr 00:e0:4c:00:ed:d2
inet addr:192.168.0.46 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:4cff:fe00:edd2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:816 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:358770 (358.7 KB) TX bytes:4027 (4.0 KB)
Interrupt:5 Base address:0xe000

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:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:840 (840.0 B) TX bytes:840 (840.0 B)

wlan0 Link encap:Ethernet HWaddr 00:13:d3:6a:8a:08
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:280 errors:0 dropped:0 overruns:0 frame:0
TX packets:113 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:122211 (122.2 KB) TX bytes:24414 (24.4 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-13-D3-6A-8A-08-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


wlist scan


lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:18:4D:6A:2D:F0
ESSID:"Gmans"
Mode:Master
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=52/100 Signal level:-46 dBm
Encryption key:on
IE: Unknown: 0005476D616E73
IE: Unknown: 010882848B0C12961824
IE: Unknown: 030103
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: Unknown: DD180050F2020101060003A4000027A4000042435E0062322F 00
IE: Unknown: DD0900037F010100240000
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=000000780542934c
Extra: Last beacon: 1340ms ago
Cell 02 - Address: 00:90:D0:4C:2B:A2
ESSID:"walkermicki"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=46/100 Signal level:-79 dBm
Encryption key:on
IE: Unknown: 000B77616C6B65726D69636B69
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: Unknown: 32040C121860
IE: Unknown: DD060010180200F0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101880003A4000027A4000042435E0062322F 00
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000018252aa9837
Extra: Last beacon: 1148ms ago

pan0 Interface doesn't support scanning.



cat /etc/network/interfaces


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
#iface eth0 inet dhcp


sudo /etc/init.d/networking restart


* Reconfiguring network interfaces...
Ignoring unknown interface eth0=eth0.


I noticed my interfaces file was a little empty so i added


auto wlan0
iface wlan0 inet dhcp
gateway 192.168.0.1
netmask 255.255.255.0


after this alteration
dmesg | grep wlan0 reads

[ 46.083949] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 177.554823] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 180.116878] wlan0: authenticate with AP 00:18:4d:6a:2d:f0
[ 180.118369] wlan0: authenticated
[ 180.118385] wlan0: associate with AP 00:18:4d:6a:2d:f0
[ 180.121936] wlan0: RX AssocResp from 00:18:4d:6a:2d:f0 (capab=0x431 status=0 aid=2)
[ 180.121956] wlan0: associated
[ 180.126027] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 190.640096] wlan0: no IPv6 routers present
[ 259.073073] wlan0: deauthenticating by local choice (reason=3)
[ 267.150626] ADDRCONF(NETDEV_UP): wlan0: link is not ready


which has made no difference

[unutbu]

Perhaps try editing /etc/network/interfaces directly:

auto wlan0
iface wlan0 inet dhcp
wireless-key XXXXXXXXXXXXXXXXXXXXXXXXXX
wireless-essid XXXXXXXXXXXX

It might not be true for all setups, but I find with mine that all wireless configuration files must be in place at boot time for the NIC to be setup properly. So you may have to do a shutdown / power up cycle after editing /etc/network/interfaces to see if it works.

If it doesn't work, please post the output of

ifconfig
iwconfig
sudo /etc/init.d/networking restart
Please post ifconfig again, so we can see if editing /etc/network/interfaces made any difference.

[wieman01]

Another thought... I had the same problem this morning with my Ralink adapter. I had to switch the USB connector from my USB hub directly to the PC. It worked after that.

[joylessdave]

made those changes unfortunatly no luck

ifconfig

eth0 Link encap:Ethernet HWaddr 00:e0:4c:00:ed:d2
inet addr:192.168.0.46 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:4cff:fe00:edd2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13827 errors:0 dropped:0 overruns:0 frame:0
TX packets:10403 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18754612 (18.7 MB) TX bytes:979569 (979.5 KB)
Interrupt:5 Base address:0xe000


iwconfig


lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"Gmans"
Mode:Managed Frequency:2.422 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


sudo /etc/init.d/networking restart

* Reconfiguring network interfaces... /etc/network/interfaces:2: misplaced option
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:2: misplaced option
ifup: couldn't read interfaces file "/etc/network/interfaces"
[fail]



cat /etc/network/interfaces

# This file describes the network interfaces available on your system
and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
#iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wireless-key 1c7d1d63ccc1610b6af218d9a0
wireless-essid Gmans


unfortunatly its a pci card not a usb dongle i had a go at switching the pci slots around but no luck

thanks

JLD

[unutbu]

Ahah. This might be part of the problem:

* Reconfiguring network interfaces... /etc/network/interfaces:2: misplaced option
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:2: misplaced option


Run

gksu gedit /etc/network/interfaces

Put a # sign at the front of the 2nd line:

Change

# This file describes the network interfaces available on your system
and how to activate them. For more information, see interfaces(5).

to

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

Save and exit gedit. The # sign tells the machine that line is just a comment.

Shutdown and reboot.

Also, you might want to edit your previous post so your real wireless-key is not showing.
It probably means nothing since we don't know where you are, but why tempt fate?

[joylessdave]

because of the error reading the interfaces file i restored the backup and i get

cat interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp


/etc/init.d/networking restart

* Reconfiguring network interfaces... Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:e0:4c:00:ed:d2
Sending on LPF/eth0/00:e0:4c:00:ed:d2
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.0.46 from 192.168.0.1
DHCPREQUEST of 192.168.0.46 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.0.46 from 192.168.0.1
bound to 192.168.0.46 -- renewal in 232765 seconds.
* if-up.d/mountnfs[eth0]: waiting for interface lo before doing NFS mounts
[ OK ]


i edited the replaced interfaces file to read

cat interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

#WIFI
auto wlan0
iface wlano inet dhcp



/etc/init.d/networking restart


* Reconfiguring network interfaces... Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:e0:4c:00:ed:d2
Sending on LPF/eth0/00:e0:4c:00:ed:d2
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER of 192.168.0.46 from 192.168.0.1
DHCPREQUEST of 192.168.0.46 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.0.46 from 192.168.0.1
bound to 192.168.0.46 -- renewal in 237714 seconds.
* if-up.d/mountnfs[eth0]: waiting for interface lo before doing NFS mounts
* if-up.d/mountnfs[eth0]: waiting for interface wlan0 before doing NFS mounts
Ignoring unknown interface wlan0=wlan0.
[ OK ]


i notice the last line of the networking rstart says that wlan0 is unknown however ifconfig reads

eth0 Link encap:Ethernet HWaddr 00:e0:4c:00:ed:d2
inet addr:192.168.0.46 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:4cff:fe00:edd2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:834 errors:0 dropped:0 overruns:0 frame:0
TX packets:517 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:722539 (722.5 KB) TX bytes:58665 (58.6 KB)
Interrupt:5 Base address:0xe000

wlan0 Link encap:Ethernet HWaddr 00:13:d3:6a:8a:08
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18072 (18.0 KB) TX bytes:6056 (6.0 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-13-D3-6A-8A-08-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)



so i don't know what is going on

thanks

jld

[unutbu]

You seem have two network interfaces: eth0 and wlan0.
eth0 is a wired network interface, and
wlan0 is a wireless network interface.

eth0 is already communicating with a router. And it successfully obtains an IP address:

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER of 192.168.0.46 from 192.168.0.1
DHCPREQUEST of 192.168.0.46 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.0.46 from 192.168.0.1
bound to 192.168.0.46 -- renewal in 237714 seconds.

eth0 is communicating on the 192.168.0.* network.
You can only have one network interface per network.

wlan0 can not communicate on the same network, since your machine has to decide which interface to use when it sends packets out on the 192.168.0.* network. Right now, it looks like eth0 is filling that role.

So what are you trying to do with wlan0? Do you have a second router? Do you want to disable eth0 and use wlan0 instead?

Also, there seems to be a problem with your lo interface:

* if-up.d/mountnfs[eth0]: waiting for interface lo before doing NFS mounts

I'm not sure what is causing this, or how to fix it.
Please post the contents of /etc/hosts.

[kay-man]

Seems to me you have an error in your /etc/network/interfaces.

In this line:

iface wlano inet dhcp

you spelled wlano with an o (an ooooh) at the end instaed of a 0 (zero). So you're referencing an unknown interface.

Change it and see and run

sudo /etc/init.d/networking restart

[wieman01]

Seems to me you have an error in your /etc/network/interfaces.

In this line:

iface wlano inet dhcp

you spelled wlano with an o (an ooooh) at the end instaed of a 0 (zero). So you're referencing an unknown interface.

Change it and see and run

sudo /etc/init.d/networking restart
Darn, you're right. Thanks for paying attention!

[joylessdave]

the machine is only connected over ethernet while i try and get wifi working (its easier to post the output of the commands if im using the same machine)

my etc/hosts file reads

27.0.0.1 localhost
127.0.1.1 The-den.localdomain The-den

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts


the error i was referring to not knowing what was happening was the error in my interfaces file where i had typed wlano instead of wlan0

having corrected this and rebooted i still cannot connect to the wireless network

following the correction of my interfaces file and still not being able to connect i get the following (with no ethernet cable connected)

ifconfig

eth0 Link encap:Ethernet HWaddr 00:e0:4c:00:ed:d2
inet6 addr: fe80::2e0:4cff:fe00:edd2/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:872 errors:0 dropped:0 overruns:0 frame:0
TX packets:724 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:732012 (732.0 KB) TX bytes:152142 (152.1 KB)
Interrupt:5 Base address:0xe000

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:26 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:1820 (1.8 KB) TX bytes:1820 (1.8 KB)

wlan0 Link encap:Ethernet HWaddr 00:13:d3:6a:8a:08
inet6 addr: fe80::213:d3ff:fe6a:8a08/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:185 errors:0 dropped:0 overruns:0 frame:0
TX packets:109 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:76079 (76.0 KB) TX bytes:22121 (22.1 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-13-D3-6A-8A-08-61-30-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


iwconfig


lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"Gmans"
Mode:Managed Frequency:2.422 GHz Access Point: 00:18:4D:6A:2D:F0
Bit Rate=1 Mb/s Tx-Power=20 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality=49/100 Signal level:-43 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


/etc/init.d/networking restart

* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.pid with pid 2342
removed stale PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:e0:4c:00:ed:d2
Sending on LPF/eth0/00:e0:4c:00:ed:d2
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:e0:4c:00:ed:d2
Sending on LPF/eth0/00:e0:4c:00:ed:d2
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
* if-up.d/mountnfs[eth0]: waiting for interface wlan0 before doing NFS mounts
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:13:d3:6a:8a:08
Sending on LPF/wlan0/00:13:d3:6a:8a:08
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ OK ]

[joylessdave]

ok this is very weird
i went and got a drink came back
did a dmesg | grep wlan0 to see if anything new had shown up
checked my ipcop dhcp logs and it had mystically connected

going to restart and see if it will connect again

~~~~UPDATE~~~~~

after 2 reboots its still connecting so i have no idea why it wasn't before

thanks for all the help

JLD

[kay-man]

I had this error myself recently :D

Cool that it's working, anyway!

[wieman01]

Done nothing, really. Glad you got it working, dude.

[coubury]

Can anyone help i followed the guide in the OP

I have a edimax EW711uan it used the RT2500 chipset.

I am using backtrack 4 in vmware

here is my problem

root@bt:~# sudo /etc/network/interfaces
sudo: /etc/network/interfaces: command not found
root@bt:~# sudo ndiswrapper -i /root/Desktop/Driver/rt2500usb.inf
installing rt2500usb ...
root@bt:~# ndiswrapper -l
rt2500usb : driver installed
rt73 : driver installed
root@bt:~# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

root@bt:~# iface wlan0 inet dhcp
bash: iface: command not found
root@bt:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0c:29:3e:0e:65
inet addr:192.168.0.6 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe3e:e65/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:331 errors:0 dropped:0 overruns:0 frame:0
TX packets:188 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:328973 (328.9 KB) TX bytes:13845 (13.8 KB)
Interrupt:19 Base address:0x2000

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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)




/etc/network/interfaces is not found

also when i type iwconfig the wireless usb adapter is not found

any ideas?

[wieman01]

Which version of Ubuntu are you running? 7.10? There is no need to install a separate driver, things have improved a lot since I published this tutorials.

[coubury]

No

I have not updated my avatar since last year

Im using backtrack 4 in vmware

The new Backtrack uses ubuntu right?

[wieman01]

No

I have not updated my avatar since last year

Im using backtrack 4 in vmware

The new Backtrack uses ubuntu right?
I don't really know what Backtrack is to be honest.

[coubury]

you serious? Of course you know what backtrack 4 is :S

Anyone it uses Ubuntu i need a guide to get my wireless adapter working AS far as i know Backtrack 4 uses the latest version of Ubuntu

So can you help me please sir? I need to get my RT2500usb working.

It's a edimax ew-7711Uan usb adapter

Can you help me please?

[unutbu]

This guide was written at a time when ndiswrapper was more of a necessity.
Now there are open source drivers for Wireless cards that use RT2500 chips.
I think you'll get better results using those drivers than by trying to use ndiswrapper.

I suggest you uninstall ndiswrapper:

sudo apt-get purge ndiswrapper

and then try the guide referenced here:
http://ubuntuforums.org/showthread.php?t=1048423

[wieman01]

you serious? Of course you know what backtrack 4 is :S

Anyone it uses Ubuntu i need a guide to get my wireless adapter working AS far as i know Backtrack 4 uses the latest version of Ubuntu

So can you help me please sir? I need to get my RT2500usb working.

It's a edimax ew-7711Uan usb adapter

Can you help me please?
I was serious but obviously it was a little late or early (can't remember) over here when I replied. I am with you now.

The latest Serialmonkey (Ralink) drivers should actually be included as of Jaunty. I am surprised the 2500 creates an issue.

Please follow unutbu's advice and report back how it goes.

[kevinguillorytraining]

Wow. My driver problem is resolved now

[wieman01]

Wow. My driver problem is resolved now
Which adapter have you got and what chipset is it exactly? Just out of curiousity...

[coubury]

This guide was written at a time when ndiswrapper was more of a necessity.
Now there are open source drivers for Wireless cards that use RT2500 chips.
I think you'll get better results using those drivers than by trying to use ndiswrapper.

I suggest you uninstall ndiswrapper:

sudo apt-get purge ndiswrapper

and then try the guide referenced here:
http://ubuntuforums.org/showthread.php?t=1048423


I followed this. But it appears my card is still not being reconized

Im using BT3 this time with a RT2870 driver it's a EW-7711uan

bt ~ # wget
http://ubunturt2870.pbworks.com/f/2009_0820_RT2870_Linux_STA_V2.2.0.0.tar.bz2
--11:33:41--
http://ubunturt2870.pbworks.com/f/2009_0820_RT2870_Linux_STA_V2.2.0.0.tar.bz2
=> `2009_0820_RT2870_Linux_STA_V2.2.0.0.tar.bz2'
Resolving ubunturt2870.pbworks.com... 208.96.18.237, 208.96.18.238
Connecting to ubunturt2870.pbworks.com|208.96.18.237|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 584,289 (571K) [application/x-bz2]

100%[====================================>] 584,289 137.67K/s
ETA 00:00

11:33:48 (137.59 KB/s) - `2009_0820_RT2870_Linux_STA_V2.2.0.0.tar.bz2'
saved [584289/584289]

bt ~ # tar xvfj 2009_0820_RT2870_Linux_STA_V2.2.0.0.tar.bz2
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/action.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/ba_action.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/br_ftph.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/client_wds.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_aes.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_asic.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_cfg.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_cmd.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_data.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_data_usb.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_info.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_mac_usb.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_profile.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_sanity.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_sync.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_tkip.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_wep.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/cmm_wpa.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/crypt_aes.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/crypt_arc4.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/crypt_hmac.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/crypt_md5.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/crypt_sha2.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/dfs.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/eeprom.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/ee_prom.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/mlme.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/netif_block.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/rt2870.bin
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/rtmp_init.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/rtmp_mcu.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/rtmp_timer.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/rtusb_bulk.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/rtusb_data.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/rtusb_io.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/rt_channel.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/spectrum.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/common/vr_ikans.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/action.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/ap.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/chip/
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/chip/mac_usb.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/chip/rt2870.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/chip/rtmp_mac.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/chip/rtmp_phy.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/chlist.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/client_wds.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/client_wds_cmm.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/crypt_aes.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/crypt_arc4.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/crypt_hmac.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/crypt_md5.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/crypt_sha2.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/dfs.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/dot11i_wpa.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/eeprom.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/firmware.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/iface/
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/iface/rtmp_usb.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/link_list.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/mlme.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/netif_block.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/oid.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/os/
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/os/rt_linux.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtmp.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtmp_chip.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtmp_cmd.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtmp_def.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtmp_dot11.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtmp_iface.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtmp_mcu.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtmp_os.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtmp_timer.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtmp_type.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rtusb_io.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rt_ate.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/rt_config.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/spectrum.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/spectrum_def.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/vr_ikans.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/wpa.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/include/wpa_cmm.h
2009_0820_RT2870_Linux_STA_V2.2.0.0/iwpriv_usage.txt
2009_0820_RT2870_Linux_STA_V2.2.0.0/Makefile
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/config.mk
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/Makefile.4
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/Makefile.6
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/Module.symvers
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/modules.order
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/rt_ate.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/rt_linux.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/rt_main_dev.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/rt_profile.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/rt_usb.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/sta_ioctl.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/usb_main_dev.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/vr_ikans.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/README_STA
2009_0820_RT2870_Linux_STA_V2.2.0.0/RT2870STA.dat
2009_0820_RT2870_Linux_STA_V2.2.0.0/RT2870STACard.dat
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/assoc.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/auth.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/auth_rsp.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/connect.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/dls.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/rtmp_ckipmic.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/rtmp_data.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/sanity.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/sync.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta/wpa.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/sta_ate_iwpriv_usage.txt
2009_0820_RT2870_Linux_STA_V2.2.0.0/tools/
2009_0820_RT2870_Linux_STA_V2.2.0.0/tools/bin2h
2009_0820_RT2870_Linux_STA_V2.2.0.0/tools/bin2h.c
2009_0820_RT2870_Linux_STA_V2.2.0.0/tools/Makefile
bt ~ # cd 2009_0820_RT2870_Linux_STA_V2.2.0.0
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 #
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 #
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 # cd os/linux
bt linux #
bt linux # rm config.mk
bt linux #
bt linux # wget http://ubunturt2870.pbwiki.com/f/config.mk
--11:34:26-- http://ubunturt2870.pbwiki.com/f/config.mk
=> `config.mk'
Resolving ubunturt2870.pbwiki.com... 208.96.32.2, 208.96.32.3
Connecting to ubunturt2870.pbwiki.com|208.96.32.2|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://ubunturt2870.pbworks.com/f/config.mk [following]
--11:34:27-- http://ubunturt2870.pbworks.com/f/config.mk
=> `config.mk'
Resolving ubunturt2870.pbworks.com... 208.96.18.238, 208.96.18.237
Connecting to ubunturt2870.pbworks.com|208.96.18.238|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10,760 (11K) [application/x-mk]

100%[====================================>] 10,760 --.--K/s

11:34:28 (128.87 MB/s) - `config.mk' saved [10760/10760]

bt linux # cd 2009_0820_RT2870_Linux_STA_V2.2.0.0
-bash: cd: 2009_0820_RT2870_Linux_STA_V2.2.0.0: No such file or directory
bt linux # cd /root/2009_0820_RT2870_Linux_STA_V2.2.0.0
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 # sudo make
make -C tools
make[1]: Entering directory `/root/2009_0820_RT2870_Linux_STA_V2.2.0.0/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory `/root/2009_0820_RT2870_Linux_STA_V2.2.0.0/tools'
/root/2009_0820_RT2870_Linux_STA_V2.2.0.0/tools/bin2h
cp -f os/linux/Makefile.6
/root/2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux/Makefile
make -C /lib/modules/2.6.21.5/build
SUBDIRS=/root/2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux modules
make: *** /lib/modules/2.6.21.5/build: No such file or directory. Stop.
make: *** [LINUX] Error 2
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 #
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 # sudo make install
make -C /root/2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux -f
Makefile.6 install
mkdir: cannot create directory `/etc/Wireless': File exists
make[1]: Entering directory
`/root/2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux'
rm -rf /etc/Wireless/RT2870STA
mkdir /etc/Wireless/RT2870STA
cp /root/2009_0820_RT2870_Linux_STA_V2.2.0.0/RT2870STA.dat
/etc/Wireless/RT2870STA/.
install -d /lib/modules/2.6.21.5/kernel/drivers/net/wireless/
install -m 644 -c rt2870sta.ko
/lib/modules/2.6.21.5/kernel/drivers/net/wireless/
install: cannot stat `rt2870sta.ko': No such file or directory
make[1]: *** [install] Error 1
make[1]: Leaving directory
`/root/2009_0820_RT2870_Linux_STA_V2.2.0.0/os/linux'
make: *** [install] Error 2
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 #
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 # sudo modprobe rt2870sta
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 #
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 # sudo modprobe -r rt2870sta
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 # sudo modprobe rt2870sta
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 # sudo ifconfig ra0 up
ra0: ERROR while getting interface flags: No such device
bt 2009_0820_RT2870_Linux_STA_V2.2.0.0 #



If i type iwconig i get


bt ~ # sudo ifconfig ra0 down
ra0: ERROR while getting interface flags: No such device
bt ~ # iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

bt ~ #



Can you help please?

[jlangholzj]

Lets see how this goes....blasted windows drivers take forever.


I've got a rt2860 chipset wireless card, running lucid.

my router is a WPA2 security and Its has know issues with the standard linux drivers that are included with connecting to WPA2 servers. why this is, i don't know.

I've followed another fellas tutorial on getting it to work and it does, kind of. lol. It likes to drop my signal quite frequently and not be happy with any secured networks.

...judging from your other threads i think you've got some insight into this... :p

anywho...when these dang windows drivers are done DL'n I'll let you know how things go.


also, would this method work for say another chipset of drivers?? I've got a buddy who has a chipset that the manufacture wont allow linux drivers to be produced (damn medieval ijiots). I knew there was a way with the wrapper to run the windows driver but could i just follow your steps only with different names and such??

thanks in advance

-J