HOWTO: RT2500, etc. wireless cards

[wieman01]

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):
sudo apt-get install ndiswrapper-common ndiswrapper-utils-1.9



Install "ndiswrapper" package without working internet connection (alternatively, install it via Synaptic/Adept):
sudo apt-cdrom add
sudo apt-get update
sudo apt-get install ndiswrapper-common ndiswrapper-utils-1.9



Load new driver module (may not be necessary any longer, but does no harm either):
sudo depmod -a
sudo modprobe ndiswrapper




Add the module to "/etc/modules" to have it load automatically:
echo 'ndiswrapper' | sudo tee -a /etc/modules



Create alias directive:
sudo ndiswrapper -m



Pick a valid Ralink driver based on the chipset of your card (you might blacklist all of them if you are not sure):
rt2500usb
rt2500pci
rt2500
rt2570
rt73usb
rt73pci
rt73
rt61usb
rt61pci
rt61
rt2860
rt2860sta
rt2x00usb
rt2x00lib



Blacklist Ralink driver:
echo 'blacklist <your_ralink_driver>' | sudo tee -a /etc/modprobe.d/blacklist



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



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



Make sure it has installed correctly:
ndiswrapper -l



The output should yield something like this:
rt2500usb : driver installed
device (13B1:000D) present (alternate driver: rt2500usb)




Last but not least open this file...
sudo gedit /etc/network/interfaces



...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]:
auto wlan0
iface wlan0 inet dhcp

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.

[grovulent]

No luck...

My problem I think is in finding a reliable copy of the windows drivers. I can't extract them from the exe on the ralink website (cabextract, and various windows programs don't work). so I've been trying random rt2500.inf files (+ sys and cat) found through googling.

The first set I found caused the same freeze problem when it tried to connect, the second wouldn't install via ndiswrapper - received an error 'couldn't find models section "insert model here" for multiple models.

Anyone know where to find the actual latest inf, sys, cat files?

[wieman01]

No luck...

My problem I think is in finding a reliable copy of the windows drivers. I can't extract them from the exe on the ralink website (cabextract, and various windows programs don't work). so I've been trying random rt2500.inf files (+ sys and cat) found through googling.

The first set I found caused the same freeze problem when it tried to connect, the second wouldn't install via ndiswrapper - received an error 'couldn't find models section "insert model here" for multiple models.

Anyone know where to find the actual latest inf, sys, cat files?
What wireless adapter have you got? You did not find anything on the vendor's website?

[grovulent]

What wireless adapter have you got? You did not find anything on the vendor's website?

Ah - silly me... didn't think to check the laptop makers site (MSI) - downloaded their driver.. but the latest they offer is from august 2006 (whereas ralink has updated as of 2007). Tried it - no luck - same hanging problem. Full reboot required each time.

Might have to email MSI to see if they can release a later driver.

[bapoumba]

https://bugs.launchpad.net/ubuntu/+bug/34902
I ran in the problem yesterday...
I bought this card because it was supported. My home network is wired now, so I was not using it any longer. But yesterday, I had to when I went to my LUG's install party.

I'm not sure I'm willing to try win drivers for a chipset that used to be fully supported. Am I missing something? (in that case, please accept my apologies).

[wieman01]

Ah - silly me... didn't think to check the laptop makers site (MSI) - downloaded their driver.. but the latest they offer is from august 2006 (whereas ralink has updated as of 2007). Tried it - no luck - same hanging problem. Full reboot required each time.

Might have to email MSI to see if they can release a later driver.
Do you run Feisty or Gutsy? I used to have these lockups in Dapper, but compiling the latest "ndiswrapper" from source did solve the problem later on. No more hanging.

[wieman01]

https://bugs.launchpad.net/ubuntu/+bug/34902
I ran in the problem yesterday...
I bought this card because it was supported. My home network is wired now, so I was not using it any longer. But yesterday, I had to when I went to my LUG's install party.

I'm not sure I'm willing to try win drivers for a chipset that used to be fully supported. Am I missing something? (in that case, please accept my apologies).
If you want to use GNOME Network Manager, you don't have a choice at the moment. You can always configure it manually by editing "/etc/network/interfaces", but I find that too big a hassle.

EDIT:
This thread is a good reference: http://ubuntuforums.org/showthread.php?t=560229

[bapoumba]

If you want to use GNOME Network Manager, you don't have a choice at the moment. You can always configure it manually by editing "/etc/network/interfaces", but I find that too big a hassle.
Hmm.. I removed completely network-manager, working with the conf files (n-m does not handle switching from DHCP to static IP very well..). End of the off-topic, thanks for the input, wieman01 :)

[wieman01]

Hmm.. I removed completely network-manager, working with the conf files (n-m does not handle switching from DHCP to static IP very well..). End of the off-topic, thanks for the input, wieman01 :)
Yeah, static IPs are still an issue. Very sad... That's what keep me from using Network Manager as well.

[bapoumba]

Yeah, static IPs are still an issue. Very sad... That's what keep me from using Network Manager as well.
Have you checked wicd (http://wicd.sourceforge.net/)? Works perfectly with feisty (I'm with gutsy on this laptop).

[wieman01]

Have you checked wicd (http://wicd.sourceforge.net/)? Works perfectly with feisty (I'm with gutsy on this laptop).
I know it does, but I have been reluctant because I don't want to use a 3rd party tool as much as I appreciate their effort. I might have to resort to it though... It makes me furious that Canonical don't get a grip on it. Such a basic feature.

Thanks anyway, mate.

[bapoumba]

I know it does, but I have been reluctant because I don't want to use a 3rd party tool as much as I appreciate their effort. I might have to resort to it though... It makes me furious that Canonical don't get a grip on it. Such a basic feature.

Thanks anyway, mate.
Agreed :)
And you're welcome!

[grovulent]

Do you run Feisty or Gutsy? I used to have these lockups in Dapper, but compiling the latest "ndiswrapper" from source did solve the problem later on. No more hanging.


Recently upgraded from feisty to gutsy in the hope wireless would improve. I used to be able to get it to work in feisty by editing the interfaces file... but that doesn't work anymore.

I must admit I really don't know what compiling the latest 'ndiswrapper' involves...

[wieman01]

Recently upgraded from feisty to gutsy in the hope wireless would improve. I used to be able to get it to work in feisty by editing the interfaces file... but that doesn't work anymore.

I must admit I really don't know what compiling the latest 'ndiswrapper' involves...
Gutsy should not have such a problem. So I don't think it has anything to do with the package, but the driver, don't you think so? Gutsy works fine for me.

[odiseo77]

Hi, I'm using a card with the rt2500 chipset on Feisty and I'll upgrade to Gutsy Gibbon as soon as the stable version comes out, but I have a question, why using ndiswrapper when these chipsets are supposed to be fully supported in Ubuntu? You mean they don't work very well in Gutsy? (Feisty's default driver is working like a charm here, in spite of the fact I'm using a smp kernel on a core 2 duo machine).

[wieman01]

Hi, I'm using a card with the rt2500 chipset on Feisty and I'll upgrade to Gutsy Gibbon as soon as the stable version comes out, but I have a question, why using ndiswrapper when these chipsets are supposed to be fully supported in Ubuntu? You mean they don't work very well in Gutsy? (Feisty's default driver is working like a charm here, in spite of the fact I'm using a smp kernel on a core 2 duo machine).
It is meant for those users that want to be able to use Network Manager or WICD. I suppose that you got it working through command line only, right?

[odiseo77]

Yes, I edited my /etc/network/interfaces file to my like and my wireless connection is working like a charm here. Thanks for clarify this to me, I was getting scared about the idea of using ndiswrapper :)

[wieman01]

Yes, I edited my /etc/network/interfaces file to my like and my wireless connection is working like a charm here. Thanks for clarify this to me, I was getting scared about the idea of using ndiswrapper :)
Yeah, I hate to use as well, but hey, no choice. Thanks for asking, I have updated the thread and highlighted the purpose of this thread. It was indeed misleading.

[Logarithymic]

I'm using feisty fawn and tried this tutorial, followed it step by step, and WICD still won't connect for me!
I'm using WEP if that makes any difference.

[odiseo77]

I'm using feisty fawn and tried this tutorial, followed it step by step, and WICD still won't connect for me!
I'm using WEP if that makes any difference.

Maybe you should open a new topic since this one is related to Gutsy Gibbon? :) Anyway, if you're using WEP, then it's fairly easy to connect to your AP; simply go to 'System>Administration>Network', select the wireless interface and click on properties, enter your settings there, then click on accept, check the checkbox at the left of your wireless interface (on the main window) and it should work.

[Logarithymic]

Maybe you should open a new topic since this one is related to Gutsy Gibbon? :) Anyway, if you're using WEP, then it's fairly easy to connect to your AP; simply go to 'System>Administration>Network', select the wireless interface and click on properties, enter your settings there, then click on accept, check the checkbox at the left of your wireless interface (on the main window) and it should work.



Didn't work :(

[odiseo77]

Didn't work :(

hmm, weird. Sorry if I can't be of help here, but then I'd suggest you to open a new thread in the 'Networking & Wireless (http://ubuntuforums.org/forumdisplay.php?f=136)' section of the forum.

Greetings.

[grovulent]

Gutsy should not have such a problem. So I don't think it has anything to do with the package, but the driver, don't you think so? Gutsy works fine for me.

Yeah - it does sound like the driver... I'd like to get my hands on the latest version from ralink...

The files should be the same right? ie... inf, sys and cat - no matter the specific vendor? So if anyone could post the latest versions of the driver files somewhere I'd greatly appreciate it.

[grovulent]

Sorry for double post - managed to get the latest drivers from Ralink via email. If anyone else needs them feel free to PM me.

I'll test em out tonight. Here's hoping.

[wieman01]

Yeah - it does sound like the driver... I'd like to get my hands on the latest version from ralink...

The files should be the same right? ie... inf, sys and cat - no matter the specific vendor? So if anyone could post the latest versions of the driver files somewhere I'd greatly appreciate it.
Yes, the files should be the same.

[wieman01]

Sorry for double post - managed to get the latest drivers from Ralink via email. If anyone else needs them feel free to PM me.

I'll test em out tonight. Here's hoping.
If you happen to have a link I could include it in my tutorial... just a thought.

[wieman01]

Didn't work :(
Now when you scan for other networks, what is the output?
sudo iwlist scan
And what does this one one?
sudo ndiswrapper -l
What sort of card have you got & what chipset?

[Logarithymic]

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.

rausb0 No scan results


rt2500usb : driver installed
device (13B1:000D) present (alternate driver: rt2570)


Card: WUSB54G
Chipset: Ralink something :-\

[wieman01]

@Logarithymic:

Have you really blacklisted "rt2500usb"?

Second you need to edit your interfaces file. Do this:
sudo gedit /etc/network/interfaces
Now replace the contents with this (don't worry, it's safe):
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
That should do. Now restart the computer and scan once again:
sudo iwlist scan
Any results?

[jgrf77]

ok..............i failed at the first hurdle. Im very new to this so any help is really appreciated. here´s what happened

justin@Justinotronic:~$ sudo apt-get install ndiswrapper-common ndiswrapper-utils-1.9
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package ndiswrapper-utils-1.9

any ideas?

cheers

[wieman01]

ok..............i failed at the first hurdle. Im very new to this so any help is really appreciated. here´s what happened

justin@Justinotronic:~$ sudo apt-get install ndiswrapper-common ndiswrapper-utils-1.9
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package ndiswrapper-utils-1.9

any ideas?

cheers
Yes, please open Synaptic and check for package "ndiswrapper-util". You might have a different version number in the repositories depending on the version of Ubuntu you are running. Can you find it? Perhaps "ndiswrapper-utils-1.8"?

[vekaz]

Hi all,

I am also having trouble with WEP :S

I have a Linksys WUSB54G card on my Ubuntu desktop, and an Intel card on my laptop.

I am trying to connect my laptop with my desktop (ad hoc), with static IPs.

I tried network manager, wifi radio, wcid, kwifi... and console (iwconfig).

If I disable encryption, I get connected pretty easy.

When I enable WEP though, on my laptop (XP), I see a connection established but only for few seconds.

When connection is lost, XP shows my ESSID set in Ubuntu (which is the same as the one in XP) as a new network that has encryption disabled.

From errors I get from
iwconfig wlan0 key open 12345
I concluded that this needs to be more like
iwconfig wlan0 key open 3132333435 (http://www.andrewscompanies.com/tools/wep.asp)


So, then I tried all combination of generated WEP keys and passphrases on both computers, quotes, no quotes...

This reminds me of configuring PEAP on SuSE, couple of years ago, but it shouldn't be that difficult...

I slept only few hours, took a day off, have a horrible headache...

Help! :)

Edit: I forgot to mention that I first tried with rt2500, but iwconfig showed no wifi cards...

[wieman01]

Hi all,

I am also having trouble with WEP :S

I am trying to connect my laptop with my desktop (ad hoc), with static IPs.

I tried network manager, wifi radio, wcid, kwifi... and console (iwconfig).

If I disable encryption, I get connected pretty easy.

When I enable WEP though, on my laptop (XP), I see a connection established but only for few seconds.

When connection is lost, XP shows my ESSID set in Ubuntu (which is the same as the one in XP) as a new network that has encryption disabled.

From errors I get from
iwconfig wlan0 key open 12345
I concluded that this needs to be more like
iwconfig wlan0 key open 3132333435 (http://www.andrewscompanies.com/tools/wep.asp)


So, then I tried all combination of generated WEP keys and passphrases on both computers, quotes, no quotes...

This reminds me of configuring PEAP on SuSE, couple of years ago, but it shouldn't be that difficult...

I slept only few hours, took a day off, have a horrible headache...

Help! :)
Hi,

This post does not really belong here. Please open your own thread. No disrespect meant.

[vekaz]

I saw other people talking about WEP problems, so...

OK, I'm leaving :)

[fulat2k]

Hey folks,

Tried the ndiswrapper method, but couldn't work. I'm using a DLink DWL-G122 Rev B1 USB stick. Out of the box, GG was able to detect and load the appropriate driver. However, performing a iwlist wlan0 scanning doesn't return any results.

But all is not lost :) Blacklisted the rt2500usb module. Download the latest CVS tar ball for rt2570 (USB) from http://rt2x00.serialmonkey.com/wiki/index.php/Downloads. Make sure it's the latest CVS tarball, the beta doesn't compile in GG.

Follow the instructions in the README to create an alias in /etc/modprobe.conf. You may have to create the file if it's not there. Then change wlan0 to rausb0 in /etc/network/interfaces. Reboot and it should work.

One thing's missing though, network-manager didn't detect rausb0 as a wireless device :(

Hope this helps someone.

[wieman01]

Hey folks,

Tried the ndiswrapper method, but couldn't work. I'm using a DLink DWL-G122 Rev B1 USB stick. Out of the box, GG was able to detect and load the appropriate driver. However, performing a iwlist wlan0 scanning doesn't return any results.

But all is not lost :) Blacklisted the rt2500usb module. Download the latest CVS tar ball for rt2570 (USB) from http://rt2x00.serialmonkey.com/wiki/index.php/Downloads. Make sure it's the latest CVS tarball, the beta doesn't compile in GG.

Follow the instructions in the README to create an alias in /etc/modprobe.conf. You may have to create the file if it's not there. Then change wlan0 to rausb0 in /etc/network/interfaces. Reboot and it should work.

One thing's missing though, network-manager didn't detect rausb0 as a wireless device :(

Hope this helps someone.
That's why I wrote this tutorial actually. NM does not work with native Ralink drivers yet.

[jgrf77]

Thanks for that. Progress has been made. Unfortunately progress has been halted once again.

Here´s what happened

justin@Justinotronic:~$ sudo apt-get install ndiswrapper-common ndiswrapper-utils-1.8
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
ndiswrapper-source
The following NEW packages will be installed:
ndiswrapper-common ndiswrapper-utils-1.8
0 upgraded, 2 newly installed, 0 to remove and 5 not upgraded.
Need to get 42.6kB of archives.
After unpacking 213kB of additional disk space will be used.
Get:1 http://nz.archive.ubuntu.com edgy/main ndiswrapper-common 1.18-1ubuntu2 [13.7kB]
Get:2 http://nz.archive.ubuntu.com edgy/main ndiswrapper-utils-1.8 1.18-1ubuntu2 [29.0kB]
Fetched 42.6kB in 1s (23.1kB/s)
Selecting previously deselected package ndiswrapper-common.
(Reading database ... 118215 files and directories currently installed.)
Unpacking ndiswrapper-common (from .../ndiswrapper-common_1.18-1ubuntu2_all.deb) ...
Selecting previously deselected package ndiswrapper-utils-1.8.
Unpacking ndiswrapper-utils-1.8 (from .../ndiswrapper-utils-1.8_1.18-1ubuntu2_i386.deb) ...
Setting up ndiswrapper-common (1.18-1ubuntu2) ...
Setting up ndiswrapper-utils-1.8 (1.18-1ubuntu2) ...
justin@Justinotronic:~$ sudo depmod -a
justin@Justinotronic:~$
justin@Justinotronic:~$ sudo modprobe ndiswrapper
FATAL: Error inserting ndiswrapper (/lib/modules/2.6.17-11-server/kernel/drivers/net/ndiswrapper/ndiswrapper.ko): Invalid argument

Any way to overcome this? Really appreciate your help.

[wieman01]

Thanks for that. Progress has been made. Unfortunately progress has been halted once again.

Here´s what happened

justin@Justinotronic:~$ sudo apt-get install ndiswrapper-common ndiswrapper-utils-1.8
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
ndiswrapper-source
The following NEW packages will be installed:
ndiswrapper-common ndiswrapper-utils-1.8
0 upgraded, 2 newly installed, 0 to remove and 5 not upgraded.
Need to get 42.6kB of archives.
After unpacking 213kB of additional disk space will be used.
Get:1 http://nz.archive.ubuntu.com edgy/main ndiswrapper-common 1.18-1ubuntu2 [13.7kB]
Get:2 http://nz.archive.ubuntu.com edgy/main ndiswrapper-utils-1.8 1.18-1ubuntu2 [29.0kB]
Fetched 42.6kB in 1s (23.1kB/s)
Selecting previously deselected package ndiswrapper-common.
(Reading database ... 118215 files and directories currently installed.)
Unpacking ndiswrapper-common (from .../ndiswrapper-common_1.18-1ubuntu2_all.deb) ...
Selecting previously deselected package ndiswrapper-utils-1.8.
Unpacking ndiswrapper-utils-1.8 (from .../ndiswrapper-utils-1.8_1.18-1ubuntu2_i386.deb) ...
Setting up ndiswrapper-common (1.18-1ubuntu2) ...
Setting up ndiswrapper-utils-1.8 (1.18-1ubuntu2) ...
justin@Justinotronic:~$ sudo depmod -a
justin@Justinotronic:~$
justin@Justinotronic:~$ sudo modprobe ndiswrapper
FATAL: Error inserting ndiswrapper (/lib/modules/2.6.17-11-server/kernel/drivers/net/ndiswrapper/ndiswrapper.ko): Invalid argument

Any way to overcome this? Really appreciate your help.
What system are you on? 64-bit or 32-bit and what version of Ubuntu.

[fulat2k]

That's why I wrote this tutorial actually. NM does not work with native Ralink drivers yet.

Well, at least it works now. Somehow your tutorial didn't work for me :(

[wieman01]

Well, at least it works now. Somehow your tutorial didn't work for me :(
Good to know it does. :-) Thanks for the feedback.

[grovulent]

Well no luck for me unfortunately...

I tried the latest drivers from ralink and the ones listed as working with ndiswrapper (on the list from their website).

I think before I wasn't correctly blacklisting the driver... I just used rt2500 when I think it should be rt2500pci for me. I think so because upon checking with the windows driver is installed it lists rt2500pci as the alternative driver.

Unfortunately when I blacklist this driver - the system can no longer detect the wireless device at all.

[wieman01]

Well no luck for me unfortunately...

I tried the latest drivers from ralink and the ones listed as working with ndiswrapper (on the list from their website).

I think before I wasn't correctly blacklisting the driver... I just used rt2500 when I think it should be rt2500pci for me. I think so because upon checking with the windows driver is installed it lists rt2500pci as the alternative driver.

Unfortunately when I blacklist this driver - the system can no longer detect the wireless device at all.
What does "ndiswrapper -l" yield after blacklisting the driver & restarting the system?

[awakatanka]

Somehow my blacklist won't work, tryed it on main and on laptop but both still load the driver.

00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:05.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 11)
00:07.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
00:07.1 Input device controller: Creative Labs SB Live! Game Port (rev 0a)
00:08.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 04)
00:0a.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
01:00.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200] (rev a1)
02:08.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
02:09.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
and netmw225 : driver installed
rt2500 : driver installed
device (1814:0201) present (alternate driver: rt2500pci)

Still got problems with speed and requesting pages where it hangs for seconds before it goes. Other wireless usb is working good without the problems.

Kubuntu gutsy beta fully updated.

[wieman01]

Somehow my blacklist won't work, tryed it on main and on laptop but both still load the driver.

and
Still got problems with speed and requesting pages where it hangs for seconds before it goes. Other wireless usb is working good without the problems.

Kubuntu gutsy beta fully updated.
Ok, what device have you blacklisted (e.g. rt2500pci) and what hardware have you got?

[awakatanka]

Ok, what device have you blacklisted (e.g. rt2500pci) and what hardware have you got?

blacklisted rt2500 and RT2500

1 pci kaart in main with rt2500 chipset and a pcmcia in laptop with rt2500 chipset.


edit:
Blacklisted the rt2500pci now and seems to work now. only signal strenght is weaker then before. But it works with networkmanager and wpa where it never worked before. but i need to do a modprobe to get it working after a restart

edit 2:
It worked but it wasnt a real improvement same problem, think i need to look a different things for my problem.

[wieman01]

blacklisted rt2500 and RT2500

1 pci kaart in main with rt2500 chipset and a pcmcia in laptop with rt2500 chipset.


edit:
Blacklisted the rt2500pci now and seems to work now. only signal strenght is weaker then before. But it works with networkmanager and wpa where it never worked before. but i need to do a modprobe to get it working after a restart

edit 2:
It worked but it wasnt a real improvement same problem, think i need to look a different things for my problem.
After doing all the steps you still have to modprobe after restart? Does everything else work now?

[grovulent]

What does "ndiswrapper -l" yield after blacklisting the driver & restarting the system?

hi there - appreciate the help...

It says:

rt2500 : driver installed
device (1814:0201) present (alternative driver: rt2500pci)

[wieman01]

hi there - appreciate the help...

It says:

rt2500 : driver installed
device (1814:0201) present (alternative driver: rt2500pci)
You should definitely blacklist "rt2500pci" in that case. After a restart you cannot scan for networks, right?
sudo iwlist scan
That generally means that something has gone wrong during the deployment of the Windows driver. Question: While you installed the .inf file, where other driver files present in the same folder (e.g. .cap, etc.)? That is a requirement that I have not highlighted.

Could you redo the whole procedure once again after blacklisting the driver? Perhaps even remove/purge "ndiswrapper" and reinstall everything from scratch. Any better?

[awakatanka]

After doing all the steps you still have to modprobe after restart? Does everything else work now?

everytime.

Everything is working then but it has stability problems. It random disconnect and its also slow, but thats probably because the lower signal strenght.

But i believe Kubuntu also have some problems because fresh install with a other kind of wireless usb stick causes konqueror to be dead slow to on requesting pages. I going to try a ubuntu install to see if it behave the same. Going to try it also with 2 different wireless chipsets/cards

Feisty and mepis install with old drivers are fast, but they need some config work before it works in wpa mode. But knetworkmanager never worked before and now it finaly does but with those problems of speed.

[wieman01]

everytime.

Everything is working then but it has stability problems. It random disconnect and its also slow, but thats probably because the lower signal strenght.

But i believe Kubuntu also have some problems because fresh install with a other kind of wireless usb stick causes konqueror to be dead slow to on requesting pages. I going to try a ubuntu install to see if it behave the same. Going to try it also with 2 different wireless chipsets/cards

Feisty and mepis install with old drivers are fast, but they need some config work before it works in wpa mode. But knetworkmanager never worked before and now it finaly does but with those problems of speed.
Odd. You could modprobe the module using a normal startup script. That way, you won't have to do it manually all the time.

[grovulent]

You should definitely blacklist "rt2500pci" in that case. After a restart you cannot scan for networks, right?

That generally means that something has gone wrong during the deployment of the Windows driver. Question: While you installed the .inf file, where other driver files present in the same folder (e.g. .cap, etc.)? That is a requirement that I have not highlighted.

Could you redo the whole procedure once again after blacklisting the driver? Perhaps even remove/purge "ndiswrapper" and reinstall everything from scratch. Any better?


Well - it looks like the latest updates to the gutsy system have fixed the problems with the linux driver at least for me. Not flawless - it still won't connect using roaming - but I can connect through network manager if I specify the ssid and password manually.

Strange that i couldn't get your workaround to work though. The other files were there in the directory (the rt2500.cat and rt2500.sys). Reinstalling ndiswrapper after blacklisting was something I tried - but no luck. It may have just been a combination of the ndiswrapper version + driver files + my system - just didn't happen to add up. But we may never know why.

Here's hoping further updates to gutsy don't break things!

[olbill]

I have discovered the reason my Belkin 7050 version 2.00 wireless card does not work in Feisty or Gutsy. It reports as a version 1.00 and loads the rt73usb driver as default. I have used ndiswrapper to load the XP driver rt2500usb from the mfg web site. Blacklist rt73usb and the wireless works great.

Good luck to all.


desktop:~$ sudo lsusb
Password:
Bus 001 Device 002: ID 050d:7050 Belkin Components F5D7050 ver 1000 WiFi
Bus 001 Device 001: ID 0000:0000

desktop:~$ ndiswrapper -l
drivername : invalid driver!
rt2500usb : driver installed
device (050D:7050) present (alternate driver: rt73usb)

[JawsThemeSwimming428]

wieman01,

I did a fresh install of Gusty Gibbon last night after I finished downloading it. In Feisty, when I disabled Network Manager my wireless worked fine. This is not the case in Feisty. I don't need to use Network Manager (it doesn't bother me either way as I am unsure of the advantages/disadvantages) but if that is the way it will work then that's fine. You have helped me out before (witch success) and I appreciate that. I think I am going to try your tutorial when I get home tonight after work, but I have a few questions that might be helpful for the install.

1. I have the WUSB54Gv4 Linksys wireless card, how do I know what chipset it uses? Is it Ralink?

2. If I end up using ndiswrapper, what version should I use? Is the version that comes with the Gusty CD ok?

3. If I were to try to edit the interfaces file, what does that entail? Is it a lot more difficult than using ndiswrapper?

Thanks for everything, hopefully I will be posting back here with my success later tonight!

[wieman01]

wieman01,

I did a fresh install of Gusty Gibbon last night after I finished downloading it. In Feisty, when I disabled Network Manager my wireless worked fine. This is not the case in Feisty. I don't need to use Network Manager (it doesn't bother me either way as I am unsure of the advantages/disadvantages) but if that is the way it will work then that's fine. You have helped me out before (witch success) and I appreciate that. I think I am going to try your tutorial when I get home tonight after work, but I have a few questions that might be helpful for the install.

1. I have the WUSB54Gv4 Linksys wireless card, how do I know what chipset it uses? Is it Ralink?

2. If I end up using ndiswrapper, what version should I use? Is the version that comes with the Gusty CD ok?

3. If I were to try to edit the interfaces file, what does that entail? Is it a lot more difficult than using ndiswrapper?

Thanks for everything, hopefully I will be posting back here with my success later tonight!
Hello,

Nice to see you again... :-)

1. It is a Ralink. I know because I happen to own one myself.

2. Use the version that comes with the CD. No problem with it.

3. There is not connection between the interfaces file and ndiswrapper. Once you have installed the driver using ndiswrapper, you can either use Network Manager or edit "interfaces" file to set up your WPA wireless LAN. But that is entirely up to you.

Please make sure that you have the latest latest version of the Windows driver that supports WPA2. That will spare you a lot of trouble.

[JawsThemeSwimming428]

Awesome, thanks for the quick reply! Ok...I have the Ralink chipset, so which Ralink driver do I blacklist in the beginning? I will try this tonight when I get home from work (around 6-6:30 EST) and post back here to let you know how I made out! Thanks.

[wieman01]

Awesome, thanks for the quick reply! Ok...I have the Ralink chipset, so which Ralink driver do I blacklist in the beginning? I will try this tonight when I get home from work (around 6-6:30 EST) and post back here to let you know how I made out! Thanks.
To begin with you could blacklist all of them. Will do no harm. But the right one for you is "rt2500usb". See you then!

[terdon]

Hi everyone,
I thought I'd post here as none of the solutions above worked for me. OK, I have a Fujistu-Siemens Amilo A1630 with an on board RAlink rt2500 card which worked fine under Feisty. (Oddly enough it had never worked under windows, not even with the latest drivers nor under various flavours of SuSe).

When I upgraded to Gutsy yesterday, the card was recognised but no networks were found (using either command line or wlanassistant).

I tried ndiswrapper but had the same problem. In the end I iused the latest CVS of serialmonkey's driver (http://rt2x00.serialmonkey.com/rt2500-cvs-daily.tar.gz)

Just download, untar, follow the instructions in the README of the Module directory and the add these lines to /etc/modprobe.d/blacklist:

blacklist rt2500pci
blacklist rt2x00pci
blacklist rt2x00lib

It now works fine with wlanassistant although not with wicd. I realise this thread is for people who want to use network-manager or wicd but still, at least now I can connect.


Hope this helps

[JawsThemeSwimming428]

wieman01,

I just went through your walkthrough step by step, and there were no errors reported. However when I open up Network Manager (after I rebooted) I only have a Wired connection and modem? The wireless isn't even in there.

[JawsThemeSwimming428]

Also, all that is in /etc/network/interfaces is

auto lo
iface lo inet loopback


Isn't there supposed to be a wireless connection in there?

[saz]

when i rebooted my pc the wlan device wasn't there... i've installed the device correctly... i have a wusb54gv4, on feisty i used ndiswrapper (rt2570 blacklisted) no probs..

[ricardisimo]

My Network Monitor isn't working properly since upgrading. Anyone else having this problem? It displays as there being no connection, even though it's clearly up and running.

Also, it appears that I have to manually configure my connection at every boot, selecting WEP key (hexadecimal) over the default (and quite insistent) WPA Personal. Otherwise I can't connect. Any idea what that's all about?

Here's my /etc/network/interfaces:
auto lo
iface lo inet loopback

auto eth0
#iface eth0 inet dhcp

auto eth1
#iface eth1 inet dhcp

auto eth2
#iface eth2 inet dhcp

auto ath0
#iface ath0 inet dhcp

auto wlan0
#iface wlan0 inet dhcp



iface ra0 inet dhcp
wireless-essid <coffeeshopnextdoor>

auto ra0

I see that Wieman also has a HowTo on WPA, which I will dive into once I can set up a reliable connection.

Finally, I remember, from when I tried running Kubuntu, that commenting out all of the extra eths and moving ra0 up the list made quite a difference. Will that help in this case? Thanks in advance.

[wieman01]

Also, all that is in /etc/network/interfaces is

auto lo
iface lo inet loopback

Isn't there supposed to be a wireless connection in there?
What happens when you put in:
auto wlan0
iface wlan0 inet dhcp
Then reboot the PC.

EDIT:
One more thing... When you go to "Manual Configuration" in NM, is your new "wlan0" device shown? You need to activate it as I believe. Then close the networking applet and see if NM recognizes it.

[wieman01]

My Network Monitor isn't working properly since upgrading. Anyone else having this problem? It displays as there being no connection, even though it's clearly up and running.

Also, it appears that I have to manually configure my connection at every boot, selecting WEP key (hexadecimal) over the default (and quite insistent) WPA Personal. Otherwise I can't connect. Any idea what that's all about?

Here's my /etc/network/interfaces:
auto lo
iface lo inet loopback

auto eth0
#iface eth0 inet dhcp

auto eth1
#iface eth1 inet dhcp

auto eth2
#iface eth2 inet dhcp

auto ath0
#iface ath0 inet dhcp

auto wlan0
#iface wlan0 inet dhcp



iface ra0 inet dhcp
wireless-essid <coffeeshopnextdoor>

auto ra0

I see that Wieman also has a HowTo on WPA, which I will dive into once I can set up a reliable connection.

Finally, I remember, from when I tried running Kubuntu, that commenting out all of the extra eths and moving ra0 up the list made quite a difference. Will that help in this case? Thanks in advance.
Commenting out all unused interfaces should help, yes. In fact NM required you to remove all interfaces from "/etc/network/interfaces" in the past. But I don't think that is still the case.

[JawsThemeSwimming428]

Well, I am posting this from my Gusty machine so it would seem I got it working. The key was that my /etc/network/interfaces file had nothing in it except lo. I added my ethernet connection and wlan0, rebooted, and in network manager I selected wlan0 and it was up right away. Thanks for the nice tutorial wieman01!

[wieman01]

Well, I am posting this from my Gusty machine so it would seem I got it working. The key was that my /etc/network/interfaces file had nothing in it except lo. I added my ethernet connection and wlan0, rebooted, and in network manager I selected wlan0 and it was up right away. Thanks for the nice tutorial wieman01!
Thanks, mate, for letting us know. I will highlight this in the tutorial... I was not aware that this might be an issue. Great!

[ricardisimo]

Thanks again. So, no idea why the monitor isn't registering? Also, why does NM insist on the password type being WPA instead of WEP?

[wieman01]

Thanks again. So, no idea why the monitor isn't registering? Also, why does NM insist on the password type being WPA instead of WEP?
You have a Ralink card which does not work well together with NM unless you replace the driver with "ndiswrapper". You have not done so, is that right?

[ricardisimo]

No, not yet. (Damn! I was hoping he wouldn't ask that question).Here's the card's specs:
product: RT2500 802.11g Cardbus/mini-PCI
I'll go back to the start of the HowTo and get started, but in the meantime, please confirm that there is nothing peculiar about this card. It should work just fine, no?

[ricardisimo]

Something I don't get... why won't these drivers (http://www.ralinktech.com/ralink/Home/Support/Linux.html) work? Is this what is already being used (and failing) in Feisty and Gutsy, etc.?

[terdon]

Well,
the one that came with Gutsy didn't work but the latest one did for me. I have a Ralink RT2500 card.

[ricardisimo]

Huh? The one that came with Gutsy is the latest one, isn't it? I have the exact same card (I think). Does the Network Monitor work for you? Can you see your connection's activity and strength?

[ricardisimo]

Something is definitely wrong here. Right now I' m running on the 7.04 Live CD, and the connection (after some tinkering) is very, very fast, as it should be. All is not well in Gutsyland. Any ideas?

P.S. - My best connection on Gutsy was in the 20-30 kbps range.

[Talkie_Toaster]

Hey, I'm thinking of dual booting, but my wireless connection is my only connection. Is there anything I can do that doesn't need me to be connected to the Internet in Ubuntu? (I can connect in Windows fine)

[wieman01]

Something is definitely wrong here. Right now I' m running on the 7.04 Live CD, and the connection (after some tinkering) is very, very fast, as it should be. All is not well in Gutsyland. Any ideas?

P.S. - My best connection on Gutsy was in the 20-30 kbps range.
Hang on... what driver are you using now? You have somewhat lost me.

[wieman01]

Hey, I'm thinking of dual booting, but my wireless connection is my only connection. Is there anything I can do that doesn't need me to be connected to the Internet in Ubuntu? (I can connect in Windows fine)
Well, if you happen to have a Ralink card and want to follow this tutorial, then you can install "ndiswrapper" from the CD ROM... you don't need a working connection for that.

[saz]

when i rebooted my pc the wlan device wasn't there... i've installed the device correctly... i have a wusb54gv4, on feisty i used ndiswrapper (rt2570 blacklisted) no probs..

anyone help?

[wieman01]

anyone help?
Have you added these lines to "interfaces"?
auto wlan0
iface wlan0 inet dhcp
What does a scan yield?
sudo iwlist scan

[saz]

can't believe I was so lamme..

auto wlan0

solved the problem obviously... xD writing from gutsy right now..

thanks wieman01! helpful as always!

P.S.: I'm using ndiswrapper cuz with the "rt2500usb" that came in gutsy would connect to my network but i would have no signal nor internet (strange).. just saying cuz dev might want to have a look at it.. as I said, i'm using a Linksys WUSB54Gv4..

[saz]

can't believe I was so lamme..

auto wlan0

solved the problem obviously... xD writing from gutsy right now..

thanks wieman01! helpful as always!

P.S.: I'm using ndiswrapper cuz with the "rt2500usb" that came in gutsy
would connect to my network but i would have no signal nor internet
(strange).. just saying cuz dev might want to have a look at it.. as I
said, i'm using a Linksys WUSB54Gv4..

[saz]

oooppss... double post... sorry.. network problem i guess..

[wieman01]

can't believe I was so lamme..

auto wlan0

solved the problem obviously... xD writing from gutsy right now..

thanks wieman01! helpful as always!

P.S.: I'm using ndiswrapper cuz with the "rt2500usb" that came in gutsy would connect to my network but i would have no signal nor internet (strange).. just saying cuz dev might want to have a look at it.. as I said, i'm using a Linksys WUSB54Gv4..
Great. Thanks for letting me know. My fault that I did not mention that earlier... I have updated the guide accordingly. See you. :-)

[AdHavoc]

I have an RT2600 pci, so I am unsure of this will work. My issue is that the card is recognized, and my network is found, but I can't seem to connect to it or other free networks in my area. Can I simply follow this tutorial and blacklist one of the other things?

[Gina]

I have been testing the pre-release of Gutsy for a while and now installed the full release version. I was unable to get wireless working with this so have a wired connection to router. I decided to leave having a concerted effort at getting wireless to work until the full release. Trying now and no luck.

I have a Belkin F5D700UK PCI card that has the Ralink RT2500 chipset. lspci entry is :-
00:0d.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)

This was working fine in Feisty except that I had to down the interface, set essid and then up the interface to get it to work. Now in Gutsy this doesn't work. I just want a wireless connection that works and not mess with ndiswrapper or network manager etc. I know this thread is about using ndiswrapper but I can't find anything about using the supplied driver - I expected the known bug of downing the interface to be cured in Gutsy. I'm sure I'm missing something. Can anyone suggest an answer, please?

This is a copy of my terminal window when I try this in Gutsy (iwconfig shows AP as Not-Associated - iwlist scan shows the correct router MAC but empty ESSID) :-

gina@old-desktop:~$ sudo iwconfig
[sudo] password for gina:
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
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

gina@old-desktop:~$ sudo ifdown wlan0
ifdown: interface wlan0 not configured
gina@old-desktop:~$ sudo iwconfig wlan0 essid mystery mode managed channel 11
gina@old-desktop:~$ sudo ifup wlan0
Ignoring unknown interface wlan0=wlan0.
gina@old-desktop:~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"mystery"
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
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

gina@old-desktop:~$ sudo iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:14:6C:A8:DA:2A
ESSID:""
Mode:Master
Channel:11
Frequency:2.462 GHz
Signal level=-52 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=0000003756a04181

gina@old-desktop:~$

[ricardisimo]

Hang on... what driver are you using now? You have somewhat lost me.

Good question. What driver am I using? How do I determine that? And also, how do I know if the driver I'm using is or is not the same as the Linux driver that RaLink provides on their website (link in previous post)? Thanks again.

[sabrateur]

Wieman, this tutorial is great!

I'm using WUSB54Gv4 (just bought it this morning) and initially although Network Manager could detect the device and showed my wireless SSID, I couldn't connect.

Thanks for showing new Ubuntu users like me how to use ndiswrapper! :)

[ricardisimo]

I just want a wireless connection that works and not mess with ndiswrapper or network manager etc.
I'm with you, Gina. Unfortunately, I don't know that we have much choice this time around.

What I don't understand is how the support could be getting worse at every stage. My connection under Dapper was immaculate, Under Feisty I had to do the same sort of tinkering as you. And now with Gutsy I'm at a total loss... I don't think I can avoid ndiswrapper. I'm hoping that that will work. We'll see. Right now, just to be able to post here and try to download the Windows driver, I'm having to run Feisty off of the Live CD. Bizarre.

[douradinhos]

* Last but not least open this file...
Quote:
sudo gedit /etc/network/interfaces

* ...and add these 2 lines if they are not there yet:
Quote:
auto wlan0
iface wlan0 inet dhcp


ahhhh, now it works on 7.10!! (btw, im using rt2500usb for linksys WUSB54G v4)

tks for the tutorial

[Suriel]

I'm with you, Gina. Unfortunately, I don't know that we have much choice this time around.

What I don't understand is how the support could be getting worse at every stage. My connection under Dapper was immaculate, Under Feisty I had to do the same sort of tinkering as you. And now with Gutsy I'm at a total loss...

Same here. Dapper worked, Feisty worked after a few days of surfing for tips and torturing my Linux books.

I'll not give up hope yet for Gutsy and I will not yet go for NDISWRAPPER either.

Actually, ain't this the real fun about Linux? ;)

Good to know though there is this tutorial to come back to! Good job, Wieman01.

[ricardisimo]

I've followed all of the instructions in this HowTo, and my connection is present at startup, without having to do anything extraordinary - Thank you Wieman!

Still, there is something dreadfully wrong here. This same connection that is superfast when I connect on the Feisty Live CD, is sssssllllloooooooooooooooowwwwwwwwwww on Gutsy. A small part of the problem appears to be Firefox, which is a major drag, a bigtime hog right now. But even on, say, Galeon, the connection is in single-digit kbps. Any idea as to what is going on?

Here's my iwconfig:
$ sudo iwconfig
[sudo] password for ricardo:
lo no wireless extensions.

eth0 no wireless extensions.

ra0 IEEE 802.11g ESSID:"<essid>"
Mode:Managed Frequency:2.417 GHz Access Point: 00:30:BD:65:7A:56
Bit Rate=1 Mb/s Tx-Power:20 dBm Sensitivity=-121 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:14/100 Signal level:-87 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
Thanks in advance for any help.

P.S. - Here I am again on the Feisty Live CD, just checking to see if I'm crazy, imagining it all, or what... ZOOM! ZIP! It's a great high speed connection that for some reason Gutsy is slowing to a crawl. Truly bizarre.

[wieman01]

I have an RT2600 pci, so I am unsure of this will work. My issue is that the card is recognized, and my network is found, but I can't seem to connect to it or other free networks in my area. Can I simply follow this tutorial and blacklist one of the other things?
AdHavoc,

Yes, you could try it, messing around with "ndiswrapper" won't do any damage to your system. And removing your card from the blacklist plus removing "ndiswrapper" is easy.

I would think that you need to blacklist:
rt2600pci
I will be here to help.

[wieman01]

Still, there is something dreadfully wrong here. This same connection that is superfast when I connect on the Feisty Live CD, is sssssllllloooooooooooooooowwwwwwwwwww on Gutsy. A small part of the problem appears to be Firefox, which is a major drag, a bigtime hog right now. But even on, say, Galeon, the connection is in single-digit kbps. Any idea as to what is going on?

P.S. - Here I am again on the Feisty Live CD, just checking to see if I'm crazy, imagining it all, or what... ZOOM! ZIP! It's a great high speed connection that for some reason Gutsy is slowing to a crawl. Truly bizarre.
Yes, this issue sounds very familiar.

Let me think... it could relate to "ipv6" that is enabled by default. You need to turn it off both globally (i.e. in the system) and in Firefox. This is a helpful link for you:

Gobal "ipv6":
http://ubuntuforums.org/showthread.php?t=87798

Firefox:
http://kb.mozillazine.org/Network.dns.disableIPv6

Those settings should make your browsing speed significantly faster.

[wieman01]

I have been testing the pre-release of Gutsy for a while and now installed the full release version. I was unable to get wireless working with this so have a wired connection to router. I decided to leave having a concerted effort at getting wireless to work until the full release. Trying now and no luck.

I have a Belkin F5D700UK PCI card that has the Ralink RT2500 chipset. lspci entry is :-
00:0d.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)

This was working fine in Feisty except that I had to down the interface, set essid and then up the interface to get it to work. Now in Gutsy this doesn't work. I just want a wireless connection that works and not mess with ndiswrapper or network manager etc. I know this thread is about using ndiswrapper but I can't find anything about using the supplied driver - I expected the known bug of downing the interface to be cured in Gutsy. I'm sure I'm missing something. Can anyone suggest an answer, please?[/CODE]
Gina,

I know you don't like it but the current driver does not work as far as I can tell. It scans fine but I could never get it to connect with my WPA2 network, not to mention the fact that Network Manager could not handle it.

As far as I remember they are in the process of redesigning Ralink based drivers and they should improve a lot in future. But as of yet, you don't have too many options if you are in need of a wireless connection.

Serialmonkey's OS Ralink driver is another option, but frankly the driver is no better either. NM does not recognize it.

[AdHavoc]

[


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 e.g. .cab, etc.):




I got ndiswrapper from the Gutsy Gibbon cdrom, and I don't quite understand what this means. Where is the driver archive? Why is it dealing with .exe files? Sorry for asking probably stupid questions, but I need to figure this out :p

[wieman01]

I got ndiswrapper from the Gutsy Gibbon cdrom, and I don't quite understand what this means. Where is the driver archive? Why is it dealing with .exe files? Sorry for asking probably stupid questions, but I need to figure this out :p
No problem.

The archive is simply a ZIP file that contains all your driver files. Very often the extension is .EXE, however, that file is also simply a ZIP file which you can then extract. This is not very obvious, so your question is no stupid at all.

You get the (Windows) driver file from your vendor's web-site I believe.

[JLR is me]

Ok, so after much turmoil, I managed to get my wusb54gv4 to work on 7.04 (I originally was trying to do it on 7.10, but after it failing I ended up giving up) So now I'm wondering... If I were to just do an upgrade, would it keep all my settings, or would I have to go through hell to get it working again?

Edit: I restarted my computer to be sure it's working, and now the adapter isn't even being recognized...It doesn't even turn on when I'm using Ubuntu now, if I plug it in it says power on for about 3 seconds, then shuts down.

[wieman01]

Ok, so after much turmoil, I managed to get my wusb54gv4 to work on 7.04 (I originally was trying to do it on 7.10, but after it failing I ended up giving up) So now I'm wondering... If I were to just do an upgrade, would it keep all my settings, or would I have to go through hell to get it working again?

Edit: I restarted my computer to be sure it's working, and now the adapter isn't even being recognized...It doesn't even turn on when I'm using Ubuntu now, if I plug it in it says power on for about 3 seconds, then shuts down.
Have you followed every step in the tutorial? Somehow the settings don't stick.

No, an upgrade should not mess around with current settings unless you have compiled "ndiswrapper" from source. You should be ok, although that's no promise of course.

[JLR is me]

I followed every detail exact. Theoretically it should work fine (hell, it even did work five minutes ago, untill I restarted my computer) In order of things happening, I connected online, it asked for a keyring manager thing (Which I followed) then I restarted, and upon boot the wireless adapter doesn't work at all now.

Edit: I had an idea on what the issue was, and it seems to be right. the interfaces gedit removed the auto wlan0 for some reason. If that happens again, is their any way to enable it from the terminal?

[dingansich]

First off, let me just thank wieman01 for all the work put in here. Unfortunately I'm still having problems though. I think the best thing I can do is explain what I've done (I followed the tutorial closely), and maybe someone can tell me where I've gone wrong. Here goes...

I'm running Gutsy (amd64), with a Linksys WUSB54Gv4 interface (which worked 'out of the box' in Feisty but no longer works in Gutsy).

I downloaded the ndiswrapper-common_1.43, ndiswrapper-utils-1.9_1.43, ndisgtk_0.6 deb install packages, and the latest Linksys driver (from the Linksys site) to my Windows partition, and copied them over to my Ubuntu partition. ndiswrapper installed without a problem, the driver files extracted easily, and using ndiswrapper -i rt2500usb.inf the driver installed nicely.

Then I edited my /etc/network/interfaces file, which now looks like this:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

Then I edited my /etc/modprobe.d/blacklist file to include the following lines at the end of the file:
blacklist rt2500
blacklist RT2500
blacklist rt2500usb

Then I rebooted.

Now the NM interface shows no wireless adapter installed (it used to before the ndiswrapper config). iwconfig lists only lo and eth0 ("no wireless extensions"), as does ifconfig - though it also lists eth0:avah.

sudo ndiswrapper -l yields the following:

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


lsusb confirms that the device is at least detected on the usb bus, and that the ID number is correct.

What am I missing? :confused: Any help is greatly appreciated!

[wieman01]

First off, let me just thank wieman01 for all the work put in here. Unfortunately I'm still having problems though. I think the best thing I can do is explain what I've done (I followed the tutorial closely), and maybe someone can tell me where I've gone wrong. Here goes...

I'm running Gutsy (amd64), with a Linksys WUSB54Gv4 interface (which worked 'out of the box' in Feisty but no longer works in Gutsy).

...

lsusb confirms that the device is at least detected on the usb bus, and that the ID number is correct.

What am I missing? :confused: Any help is greatly appreciated!
Odd... All you have said & done looks quite right. Please check "Manual Configuration..." and confirm that the "wlan0' interfaces is enabled.

Second please do a scan and post the results if possible:
sudo iwlist scan
Does the scan yield any results & do you see your network? And what happens when you restart the network:
sudo ifdown -v wlan0
sudo ifup -v wlan0

[wieman01]

I followed every detail exact. Theoretically it should work fine (hell, it even did work five minutes ago, untill I restarted my computer) In order of things happening, I connected online, it asked for a keyring manager thing (Which I followed) then I restarted, and upon boot the wireless adapter doesn't work at all now.

Edit: I had an idea on what the issue was, and it seems to be right. the interfaces gedit removed the auto wlan0 for some reason. If that happens again, is their any way to enable it from the terminal?
Yes, you can restart the network manually:
sudo /etc/init.d/networking restart
See if that works. But it is strange that this sort of thing should happen in the first place...

[terdon]

Huh? The one that came with Gutsy is the latest one, isn't it? I have the exact same card (I think). Does the Network Monitor work for you? Can you see your connection's activity and strength?

No, I got the latest CVS snapshot (see link at my previous post). If you download and install that it should work fine (I am now connected using gutsy and RT2500).

As for networkmanager I don't know, I don't use it. wlanasistant works fine, and iwlist scan gives me a list of access points. So try downloading the new driver it should work if you have the same card.

[dingansich]

Please check "Manual Configuration..." and confirm that the "wlan0' interfaces is enabled.

That's the first really odd thing. When I select "Manual Configuration..." the window that pops up doesn't even list my wireless connection! It only lists "Wired Connection" (which is enabled) and "Modem Connection" (which is not enabled, probably because I don't have a modem connected to my PC).

Second please do a scan and post the results if possible:

When I execute sudo iwlist scan I get the following:


lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

Does the scan yield any results & do you see your network? And what happens when you restart the network:

No I don't see my network. When I take the network down (sudo ifdown -v wlan0) I get the following:

ifdown: interface wlan0 not configured

When I try to bring it up (sudo ifup -v wlan0) I get the following (bear with me - I am typing this all out from another computer):

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
wlan0: ERROR while getting interface flags: No such device
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant

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

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0

Any ideas? What could possibly be keeping my interface from even being detected? Is there anywhere other than /etc/network/interfaces that this kind of information is specified?

[wieman01]

That's the first really odd thing. When I select "Manual Configuration..." the window that pops up doesn't even list my wireless connection! It only lists "Wired Connection" (which is enabled) and "Modem Connection" (which is not enabled, probably because I don't have a modem connected to my PC).

...

Any ideas? What could possibly be keeping my interface from even being detected? Is there anywhere other than /etc/network/interfaces that this kind of information is specified?
Please post the contents of:
sudo gedit /etc/network/interfaces
And:
sudo gedit /etc/modprobe.d/ndiswrapper
Also again:
sudo ndiswrapper -l

[dingansich]

Here's the contents of /etc/network/interfaces:


auto lo
iface lo inet loopback

auto eht0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp


Here's the contents of /etc/modprobe.d/ndiswrapper:


alias wlan0 ndiswrapper


Here's the output of sudo ndiswrapper -l:


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


Again, thanx much for all of this help.

[dingansich]

Sorry for the double post, but I was just looking around the ndiswrapper install and noticed that in my /etc/ndiswrapper/rt2500usb directory I have 3 conf files. They are named as follows:

13B1:000D.F.conf
13B1:0011.F.conf
13B1:001A.F.conf

The first one matches the hardware ID for the WUSB54Gv4 returned by lusb. I'm mot sure what the others are. I at one time tried installing some other windows drivers - but they were removed when I had no success with them (their entries no longer show in /etc/ndiswrapper). Are these (extra?) conf files potentially causing the problem?

--edit--
Well I copied the 2 mismatched files (13B1:0011.F.conf and 13B1:001A.F.conf) to a temporary directory and rebooted. Made no difference.

[wieman01]

Sorry for the double post, but I was just looking around the ndiswrapper install and noticed that in my /etc/ndiswrapper/rt2500usb directory I have 3 conf files. They are named as follows:

13B1:000D.F.conf
13B1:0011.F.conf
13B1:001A.F.conf

The first one matches the hardware ID for the WUSB54Gv4 returned by lusb. I'm mot sure what the others are. I at one time tried installing some other windows drivers - but they were removed when I had no success with them (their entries no longer show in /etc/ndiswrapper). Are these (extra?) conf files potentially causing the problem?

--edit--
Well I copied the 2 mismatched files (13B1:0011.F.conf and 13B1:001A.F.conf) to a temporary directory and rebooted. Made no difference.
Ok, which driver did you blacklist and how? Could you post the relevant section please?

EDIT:
Are you on Gutsy or Feisty?

[dingansich]

I'm on Gutsy (amd64). My adapter was working under Feisty. It crapped out after I did the upgrade.

I blacklisted the drivers by adding them to the /etc/modprobe.d/blacklist file. Originally I only blacklisted the rt2500usb driver, but as of now I have blacklisted all of the drivers listed in the original HOWTO:

rt2500usb
rt2500pci
rt2500
rt2570
rt73usb
rt73pci
rt73
rt2x00usb
rt2x00lib

Also, I looked into those other device IDs. I'm not sure about 13B1:001A, but 13B1:0011 is reported as the device ID for the Linksys WUSB54Gv4 as is 13B1:000D (which is what lsusb identifies my adapter with). In any case, as moving those (seemingly) additional conf files to a temporary directory did not make a difference, I moved them back to their original place: /etc/ndiswrapper/rt2500usb.

Incidentally, I also took a look at the output from lsmod. ndiswrapper is listed as a loaded module, and there do not seem to be any other modules loaded that look like they might pertain to wireless networking adapters.

[wieman01]

I'm on Gutsy (amd64). My adapter was working under Feisty. It crapped out after I did the upgrade.

I blacklisted the drivers by adding them to the /etc/modprobe.d/blacklist file. Originally I only blacklisted the rt2500usb driver, but as of now I have blacklisted all of the drivers listed in the original HOWTO:

rt2500usb
rt2500pci
rt2500
rt2570
rt73usb
rt73pci
rt73
rt2x00usb
rt2x00lib

Also, I looked into those other device IDs. I'm not sure about 13B1:001A, but 13B1:0011 is reported as the device ID for the Linksys WUSB54Gv4 as is 13B1:000D (which is what lsusb identifies my adapter with). In any case, as moving those (seemingly) additional conf files to a temporary directory did not make a difference, I moved them back to their original place: /etc/ndiswrapper/rt2500usb.

Incidentally, I also took a look at the output from lsmod. ndiswrapper is listed as a loaded module, and there do not seem to be any other modules loaded that look like they might pertain to wireless networking adapters.
When you installed the driver file (.INF) where there any other files present e.g. .CAB or similar?

It might relate to the fact that you are on a 64-bit machine. If we cannot find a solution here I'll have to refer you to the 64-bit section... They might know a solution.

[dingansich]

When I installed the driver, the files in the directory from which I executed the ndiswrapper command were: rt2500usb.cat, rt2500usb.inf, and rt2500usb.sys.

I'm wondering if it's a a 64 bit issue as well. But AMD64 is a fairly common platform, and the WUSB54Gv4 is a common adapter. If this were a problem I'd have thought it would be well flagged by now. Maybe I've overlooked it? Can anyone browsing this thread confirm that they managed to get a Linksys WUSB54Gv4 working in Gutsy on the amd64 platform?

[wieman01]

When I installed the driver, the files in the directory from which I executed the ndiswrapper command were: rt2500usb.cat, rt2500usb.inf, and rt2500usb.sys.

I'm wondering if it's a a 64 bit issue as well. But AMD64 is a fairly common platform, and the WUSB54Gv4 is a common adapter. If this were a problem I'd have thought it would be well flagged by now. Maybe I've overlooked it? Can anyone browsing this thread confirm that they managed to get a Linksys WUSB54Gv4 working in Gutsy on the amd64 platform?
I am tempted to think this has to do with the "ndiswrapper" port to the 64-bit environment. I cannot offer much more support at this stage as I am clueless as to what the issue is.

[dingansich]

Well thanks much for all your help an patience. I'll add one small development before I start poking around elsewhere.

I figured it might be worth while going back to square one ... so I restored my /etc/network/interfaces file (it now contains only references to lo, eth0, and rausb0 - which is how the stock install of Gutsy had set it up - wlan0 is totally gone). Then I commented out all of the additions I made to the /etc/modprobe.d/blacklist file. Then I rebooted the machine. Odd thing is that even after reverting to the original broken state, the wireless interface doesn't even register in the network manager, or through ifconfig or iwconfig. It used to. So I'm thinking that somewhere something has gone wrong - but I don't know where or how it could have happened. lsmod doesn't list any wireless drivers loaded - so I tracked the rt2x00usb driver down that Ubuntu installs (somewhere buried under /var) and ran modprobe rt2x00usb against it. lsmod now shows it loaded, but it doesn't list under NM, iwconfig, or ifconfig. What's odd about this is that the symptoms of this problem are identical to those of the ndiswrapper problem. This leads me to believe that it my not be ndiswrapper, but something else connected to how modules are loaded. I dunno ... maybe I'm off my rocker.

Again, thanx a ton for all the help! :)

[dingansich]

Well I found the problem! And it is a 64bit issue. Here is the output of cat /var/log/dmesg | grep ndis:


ndiswrapper version 1.45 loaded (smp=yes)
ndiswrapper (check_nt_hdr:153): kernel is 64-bit, but Windows driver is not 64-bit;bad magic: 010B
ndiswrapper (load_sys_files:216): couldn't prepare driver 'rt2500usb'
ndiswrapper (load_wrap_driver:118) couldn't load driver rt2500usb; check system log for messages from loadndisdriver
usbcore: registered new interface driver ndiswrapper


So that's it. Still doesn't work, but at least I know why now. So I guess I'm off to hunt down a 64-bit solution.

Thanx much for the help. Hopefully this will save someone some time troubleshooting.

[wieman01]

Well I found the problem! And it is a 64bit issue. Here is the output of cat /var/log/dmesg | grep ndis:


ndiswrapper version 1.45 loaded (smp=yes)
ndiswrapper (check_nt_hdr:153): kernel is 64-bit, but Windows driver is not 64-bit;bad magic: 010B
ndiswrapper (load_sys_files:216): couldn't prepare driver 'rt2500usb'
ndiswrapper (load_wrap_driver:118) couldn't load driver rt2500usb; check system log for messages from loadndisdriver
usbcore: registered new interface driver ndiswrapper


So that's it. Still doesn't work, but at least I know why now. So I guess I'm off to hunt down a 64-bit solution.

Thanx much for the help. Hopefully this will save someone some time troubleshooting.
Hang on... Could you get ahold of the 64-bit version of the Windows driver? Plus the latest "ndiswrapper" CVS should support 64-bit, if not the current one also.

Try again with the 64-bit Windows driver. This is a very interesting finding, mate. Perhaps there is a solution.

[douradinhos]

my connection works fine, but everytime i restart i have to do

sudo modprobe ndiswrapper

or my wireless conection doesnt even show. anyway i can fix this?? my driver is rt2500usb and im on Gutsy

[kashms]

Add ndiswrapper to the end of the /etc/modules file.

[wieman01]

my connection works fine, but everytime i restart i have to do

sudo modprobe ndiswrapper

or my wireless conection doesnt even show. anyway i can fix this?? my driver is rt2500usb and im on Gutsy
Yes, do this:
sudo ndiswrapper -m
The module should be loaded on startup from now on. If that does not do try this:
sudo -s
cat ndiswrapper >> /etc/modules
exit

[douradinhos]

sudo ndiswrapper -m -> didnt work, i have to sudo modprobe ndiswrapper anyway.

xtanki@xtanki-desktop:~$ sudo -s
root@xtanki-desktop:~# cat ndiswrapper >> /etc/modules
cat: ndiswrapper: No such file or directory

[wieman01]

Then do like Kashms has pointed out:
sudo gedit /etc/modules
Then add...
ndiswrapper
...at the very end of it. Then reboot.

[douradinhos]

It Works!! thanks kashms and wieman01 :guitar:

[wieman01]

It Works!! thanks kashms and wieman01 :guitar:
My fault... I missed that part in the tutorial as I don't use Network Manager. NM requires you to load the module at boot. Thanks for your patience, mate. I have corrected it.

[jnorthr]

pardon me for asking this question as perhaps it is too dumb but are you runing your wireless networks as ad-hoc systems where the devices talk computer-to-computer or in infrastructure mode where there is supposed to be some device that acts as the access point ?

I've been working for a few weeks trying to get my windows XP with adsl connection and linksys wusb54g v4 network adapter to play ball with my ubuntu 7.0.4 laptop with pcmcia linksys wpc54gs v2. It worked for a few days using ad-hoc mode but something killed the wlan0 device and i lost it all. No notes as usual could bring it back. So i thought i'd try infrastructure mode cos there was no wep/wpa security on the ad-hoc settings.

My thinking was that if the XP system with internet connect could be the 'server' and all the laptops act as 'clients' that should work (in theory). So how to implement this plan ? Use ad-hoc network with weak security or infra... with something better. Any ideas ? :frown:

[dingansich]

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! :)

[Bertybulldog]

I just spent all day installing GG on my desktop in the hope that the wifi issues had finally been solved. Unfortunately in the process my previously (mostly) working installation of Freespire 2 has been disabled (even though it is installed on another hard drive). Freespire has its issues but at least I could get on the internet - first time as it happens.

I am absolutely staggered that something as fundamental to an operating system as providing a reliable way of connecting ot the internet is still not available in Ubuntu.

Frankly, what on earth are they thinking of? I'm off to reinstall my Freespire 2; I like everything else about Ubuntu, which is why I keep coming back, hoping against hope that they've finally sorted this basic issue.

FYI I tried the tutorial, but as I have no internet connection without wifi, it's a bit of a chicken and egg situation, so the whole thing falls over at the first line.

A very disappointed Berty signing off of Ubuntu for the third time.

:(:(:(:(:(:(:(

[terdon]

That's a shame cause I have exactly the opposite experience with Ubuntu. It is in fact the ONLY operating system (the card never worked under windows nor various versions of SuSe linux) which has recognised my onboard wireless both correctly and automatically (in feisty, see my previous post for Gutsy).

PS. What's wrong with your other system? Are you sure it is not just a simple grub/lilo error? If the system is still there, it is quite simple to load it.

[AdHavoc]

My vendor CD for Windows had the rt61 driver on it, and it installed with ndiswrapper fine... but it hasn't worked. I'm wondering if I should add rt61 to the blacklist to get it functioning correctly?

[wieman01]

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! :)
Thanks for letting us know. I'll update the tutorial and mention your post concerning 64-bit.

[wieman01]

FYI I tried the tutorial, but as I have no internet connection without wifi, it's a bit of a chicken and egg situation, so the whole thing falls over at the first line.
No, it does not. You either connect to Internet via Ethernet (very simple I promise) or install from CD as highlighted in the tutorial. Perhaps read it carefully once again?

[wieman01]

My vendor CD for Windows had the rt61 driver on it, and it installed with ndiswrapper fine... but it hasn't worked. I'm wondering if I should add rt61 to the blacklist to get it functioning correctly?
Yes, you could try:
rt61
rt61usb
rt61pci
Please blacklist all of them and get back to us. Would be nice to hear if it works for you or not. Thanks.

[bigboy_pdb]

For those of you who don't want to use ndiswrapper (and you'd prefer to use the modules that came with Gutsy) you might want to try the solution that worked for me. It can be found here:
http://ubuntuforums.org/showthread.php?t=587727

[kashms]

My vendor CD for Windows had the rt61 driver on it, and it installed with ndiswrapper fine... but it hasn't worked. I'm wondering if I should add rt61 to the blacklist to get it functioning correctly?

Yes, you should otherwise they could be conflicting with eachother. I blacklisted rt61pci and added ndiswrapper to the end of /etc/modules and everything worked.

Right click on network manager in panel and select "Connection Information" to see which driver is being used.

[wieman01]

Yes, you should otherwise they could be conflicting with eachother. I blacklisted rt61pci and added ndiswrapper to the end of /etc/modules and everything worked.

Right click on network manager in panel and select "Connection Information" to see which driver is being used.
So the RT61 works as well? Great, I have updated the "blacklist". Thanks for letting me know.

[kashms]

So the RT61 works as well? Great, I have updated the "blacklist". Thanks for letting me know.

Yes the RT61 chipset works under Gutsy. The supplied drivers called rt61pci works as well, but in my experience they were unstable. That's why I changed to Windows drivers with ndiswrapper.

[grayarea]

Sorry but I am a relative noob but upgraded from 7.04 to 7.10 and now my Belkin card refuses to work. The first install 7.04 worked without installing any driver in fact it was a breeze but now I am stuck and not sure how to fix problem. I have installed rt2500.inf ndiswrapper tells me it is installed correctly but network manager does not recognise the wireless card. I have been trying to change /etc/netowrk/interfaces but no joy. I am frustrated and deeply regretting the upgrade.
Any help appreciated.

[wieman01]

Sorry but I am a relative noob but upgraded from 7.04 to 7.10 and now my Belkin card refuses to work. The first install 7.04 worked without installing any driver in fact it was a breeze but now I am stuck and not sure how to fix problem. I have installed rt2500.inf ndiswrapper tells me it is installed correctly but network manager does not recognise the wireless card. I have been trying to change /etc/netowrk/interfaces but no joy. I am frustrated and deeply regretting the upgrade.
Any help appreciated.
Please post the results of:
sudo iwlist scan
sudo ifdown -v wlan0
sudo ifup -v wlan0

[beejaycee]

Feedback is - as always - appreciated.

Thank you, thank you, thank you! I struggled with my WUSB54G V4 and was finally able to get it running under Feisty but had been unable to get it working w/Gutsy. I walked through your steps and it came up immediately after the reboot. =D>=D> Boo-yeah!

[grayarea]

Please post the results of:

Here are the results of various ouputs. ra0 was the previous wireless name so I wonder whether it may be confused. Also of concern although the device is listed in device manager I can't find any reference if I run dmesg. I think maybe the easiest way out will be to clean install 7.04.

Sorry also not very clued in how to quote previous message

[mummra1]

Hey wieman,
I think I'm going to frame your ndiswrapper install guide and hang it in my room. I upgraded to Gutsy and it broke my Belkin wireless, but now it's back up and runnin' smooth! Thanks!

[wieman01]

Here are the results of various ouputs. ra0 was the previous wireless name so I wonder whether it may be confused. Also of concern although the device is listed in device manager I can't find any reference if I run dmesg. I think maybe the easiest way out will be to clean install 7.04.

Sorry also not very clued in how to quote previous message
Mmm... to what extend did you follow this tutorial? It seems that you have missed a few crucial steps. Do you have the right drivers for your adapter?

[stevoo]

cause i am not sure .... i have a Dell 6400 with network card

Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)
14e4:4311 (rev 01)

And as my Wirelles connection with Gutsy is extremely buggy, i wanna give a shot to this perhaps it may work better. But i am not sure what version should i use.
Any help will be greatly appreciated !

[bastikr]

I updated from feisty to gutsy and like many others I now have the problem that my wlan isn't working anymore. I followed your howto as good as possible, but I have the problem that when I unzipped the driver exe I found no .inf file. (I had to use cabextract since simply unzipping didn't work for me,)
does cabextract not extract all files or is it possible that my driver is different?

[wieman01]

I updated from feisty to gutsy and like many others I now have the problem that my wlan isn't working anymore. I followed your howto as good as possible, but I have the problem that when I unzipped the driver exe I found no .inf file. (I had to use cabextract since simply unzipping didn't work for me,)
does cabextract not extract all files or is it possible that my driver is different?
You should be able to unzip the file in Windows. Or could you not download the driver from the web somewhere? It should be available as an .EXE archive.

[wieman01]

cause i am not sure .... i have a Dell 6400 with network card

Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)
14e4:4311 (rev 01)

And as my Wirelles connection with Gutsy is extremely buggy, i wanna give a shot to this perhaps it may work better. But i am not sure what version should i use.
Any help will be greatly appreciated !
Honestly I have no experience with Broadcom drivers. I have seen tutorials in the forums, so you might want to check them out first. We could try this one, but I cannot be of much help in that case.

[bd@cb8be8510]

I made an upgrade van feisty to gutsy. So I' cant use my wireless network either (I'm using a ASUS WL-167G USB-adapter). However if I start gutsy from the previous kernel build Kernel 2.6.20-16 all is working fine again!

Temporarily I'm working with kernelbuild 2.6.20-16 i.s.o.
2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux.

I think that 2.6.22-14 is not loading the right drivers?
Listing the hardware gives me the following results:

Kernel 2.6.20-16 :

*-network
description: Wireless interface
physical id: 1
logical name: rausb0
serial: 00:11:d8:8e:79:2d
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=RT2500USBSTA driverversion=1.0.0 - BETA2 multicast=yes wireless=RT2500USB WLAN

Kernel 2.6.22-14 :

*-network
description: Wireless interface
physical id: 1
logical name: rausb0
serial: 00:11:d8:8e:79:2d
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11g

How can I skip the IEEE 802.11g driver and use the rt2500-drivers instead (as they are working fine with build 2.6.20-16)?

[magician]

Hi,


Thanks for your advices.

I studied for more then four days many threads to create a wireless connection with my usb ralink rt2500, which worked fine under feisty fawn.

I tried Rutilt, WICD, lots of other advices and finally I followed your instructions completely, but at the end again no result.

At top of the desktop there is a icon with the connection visible, but I cannot contact the router nor internet.

At another location Gutsy works fine with wired.

Now I reached the end and I am thinking of de-install Gutsy 64-bits.

My system is sempron3000_754 2048 MB of DDR

Sometimes only I have the:

loopback interface (lo)
Ethernet interface (eth0)
Unknown interface (Wmaster0)
Wireless interface (wlan0)
Wireless interface (wlan0: avani)

Another time 1,2,3 and 4
And sometimes just the first to ones,
or number 1,2 and 4.

The more I follow the threads the more I am puzzled.

Kind Regards

John


magician@sempron3000:~$ sudo iwlist scan
[sudo] password for magician:
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:03:C9:73:28:EC
ESSID:"Wanadoo_9594"
Mode:Master
Channel:10
Frequency:2.457 GHz
Signal level=-27 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=000000020361301f



magician@sempron3000:~$ sudo ifdown -v wlan0
ifdown: interface wlan0 not configured


magician@sempron3000:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 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:06:f4:0e:64:20
Sending on LPF/wlan0/00:06:f4:0e:64:20
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 12
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/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
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/wpasupplicant
magician@sempron3000:~$

[bastikr]

I extracted the driver on windows and like before in linux there were no .inf files inside. Only some dll, tlb and rgs files seem to be in the exe.
I tried the same with the driver I found at http://www.treiberupdate.de/treiber-download/download-159199-treiber-Ralink-RT2500USB.html
but I got the same files as before.
Has someone an idea what I'm doing wrong?

[Fruhwirth]

I hate to be the really dumb kid, but I can' t get the unzip command to work.

user@user-laptop:~/RA2500driver$ unzip driver.exe
Archive: driver.exe
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of driver.exe or
driver.exe.zip, and cannot find driver.exe.ZIP, period.


Note, I changed the name of the file to "driver.exe" from the really, really long version. lspci says I have RaLink RT2500 802.11g Cardbus/mini-PCI. I'm trying to open this file (http://www.ralinktech.com.tw/data/drivers/IS_AP_STA_6x_D-1.2.3.0_VA-2.0.7.0_2500_D-3.2.0.0_VA-3.2.0.0_RU-2.0.3.0_VA-1.0.18.0_AU_1.2.0.0_091407_0.1.0.29.exe) found second-from-the-last on this page (http://www.ralinktech.com/ralink/Home/Support/Windows.html). That's the correct driver, right?

I think I've got everything else in the HOWTO setup and ready to go, but it's hard to know if it will all work without the proper driver in ndiswrapper.

I googled and searched the forum and only found this, (http://ubuntuforums.org/showthread.php?p=3633610#post3633610) where I also posted.

help?

[ricardisimo]

Yes, this issue sounds very familiar.

Let me think... it could relate to "ipv6" that is enabled by default. You need to turn it off both globally (i.e. in the system) and in Firefox. This is a helpful link for you:

Gobal "ipv6":
http://ubuntuforums.org/showthread.php?t=87798

Firefox:
http://kb.mozillazine.org/Network.dns.disableIPv6

Those settings should make your browsing speed significantly faster.

It looks like you may have hit the nail on the head. I haven't tried anything yet, so I'll make sure to let you know how it went when I do. But, I just noticed that the problem appears to be restricted to web server usage. My newsreader is downloading at 400-500 kbps, which is exactly what I've been expecting all along. Wish me luck, and thanks for those links.

P.S. - Has anyone else noticed that the Mozilla apps are dragging well beyond what they've done in the past? They just seem like complete resource hogs, and slow about it, too.

[bd@cb8be8510]

I downloaded the latest drivers from serialmonkey, installed them and got my wireless network working again! (I' m using a See ASUS WL-167G USB-adapte) No legacy-drivers are required.

See http://ubuntuforums.org/showthread.php?t=584657

[magician]

Dapper Drake users should take a look at this thread (http://ubuntuforums.org/showthread.php?t=192588) if this one doesn't work.
--
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/)).


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 (use "kate" instead of "gedit" in Kubuntu):

Now add this to the end & save the file:




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 by opening this file...




...and adding this line at the end (e.g. blacklist rt2500usb):




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:


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.

Thanks alot Wieman1 and excellent forum
Today I decided to install Gutsy anew and without changing anything, nor following other threads I work around like you adviced.

On restart Network Manager did not work for me on my Ralink rt2500usb.

Then decided to uninstall Netwoirk Manager and installed Rutilt.

First time after restart Rutilt did not work, but received only error messages on entering allowed.
I restarted two other times and then the connection was OK.

Thanks again.

Kind :KS Regards

[Fruhwirth]

Since no one seems immediately able to help me with the "End-of-central-directory signature not found" error I tried to use this driver file (http://www.yournewdriver.com/Ralink_RT2500_Wireless_LAN_Card_1149.htm). Within it, there is are drivers for "winx64" which I used because I am on GG64. It installed correctly but now I can not scan.

user@user-laptop:~$ sudo iwlist scan
[sudo] password for user:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 No scan results

jesse@jesse-laptop:~$

My intereface file:

auto lo
iface lo inet loopback


auto eth0
iface eth0 inet dhcp


auto ra0
iface ra0 inet dhcp
I tried logical name wlan0 instead of ra0 in the interface file and got the same results - i.e. it's recognized but non-functional. I switched to ra0 because that was the logical name for the device under dapper.

ndiswrapper is listed on my modules file and I blacklisted every driver that is listed in this HOWTO. I've followed this HOWTO from top to bottom four-er-five times or so, even uninstalling ndiswrapper and starting from scratch. I've done it all but fresh install Gutsy and start the HOWTO anew.

It seems to me this driver file is no good or isn't right for my card. If there is anyone who has used successfully a 64-bit driver for the RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) in accordance with wieman's fantastic HOWTO, could you please post the .inf, .cat, and .sys? Or, can anyone tell me why I can't open the .exe file from Ralink's web site like everyone else seems to be doing?

Alternatively, if any of you wise and helpful souls think I'm sunk and wieman's HOWTO simply isn't going to work for my hardware for whatever reason, let me know that, too.

[Startacus]

I'm a beginner to Linux and I'm trying to get my Belkin 54g USB Adapter to work with the rt73 driver from their website.

I should note that my router has a WPA TKIP passphrase set and the SSID isn't being broadcast.

I followed the instructions above and when I run "ndiswrapper -l" It displays:
rt73 : driver installed

It doesn't display that the hardware is present though.

When I run "sudo iwlist scan" this is the result:

lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wmaster0 Interface doesn't support scanning.
wlan1 Interface doesn't support scanning : Network is down

At this point I am lost.

Another thing, my network manager icon (Like in Windows where it tells you are connected or not) has an exclamation point. When I try to enter my SSID and my password in the "Connect to Other Network Option" it looks for it but then goes back to the exclamation point.

I would really appreciate any help that you can give.

EDIT: I used the rt2500usb driver from the CD and now it works! I just need to figure out how to get WPA to work now.............

[wieman01]

Since no one seems immediately able to help me with the "End-of-central-directory signature not found" error I tried to use this driver file (http://www.yournewdriver.com/Ralink_RT2500_Wireless_LAN_Card_1149.htm). Within it, there is are drivers for "winx64" which I used because I am on GG64. It installed correctly but now I can not scan.


My intereface file:


I tried logical name wlan0 instead of ra0 in the interface file and got the same results - i.e. it's recognized but non-functional. I switched to ra0 because that was the logical name for the device under dapper.

ndiswrapper is listed on my modules file and I blacklisted every driver that is listed in this HOWTO. I've followed this HOWTO from top to bottom four-er-five times or so, even uninstalling ndiswrapper and starting from scratch. I've done it all but fresh install Gutsy and start the HOWTO anew.

It seems to me this driver file is no good or isn't right for my card. If there is anyone who has used successfully a 64-bit driver for the RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) in accordance with wieman's fantastic HOWTO, could you please post the .inf, .cat, and .sys? Or, can anyone tell me why I can't open the .exe file from Ralink's web site like everyone else seems to be doing?

Alternatively, if any of you wise and helpful souls think I'm sunk and wieman's HOWTO simply isn't going to work for my hardware for whatever reason, let me know that, too.
Sorry for my absence. I was not around for 3 days.

Question... you have a 64-bit system. 64-bit can be a pain in the throat. Nevertheless, can you not find a driver on the vendor's website for instance? Have you downloaded the 64-bit version of it?

There is another HOWTO which might help if you fail to set it up using this one:

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

[wieman01]

I made an upgrade van feisty to gutsy. So I' cant use my wireless network either (I'm using a ASUS WL-167G USB-adapter). However if I start gutsy from the previous kernel build Kernel 2.6.20-16 all is working fine again!

Temporarily I'm working with kernelbuild 2.6.20-16 i.s.o.
2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux.

I think that 2.6.22-14 is not loading the right drivers?
Listing the hardware gives me the following results:

Kernel 2.6.20-16 :

*-network
description: Wireless interface
physical id: 1
logical name: rausb0
serial: 00:11:d8:8e:79:2d
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=RT2500USBSTA driverversion=1.0.0 - BETA2 multicast=yes wireless=RT2500USB WLAN

Kernel 2.6.22-14 :

*-network
description: Wireless interface
physical id: 1
logical name: rausb0
serial: 00:11:d8:8e:79:2d
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11g

How can I skip the IEEE 802.11g driver and use the rt2500-drivers instead (as they are working fine with build 2.6.20-16)?
Maybe you need to compile them against the latest kernel?

[wieman01]

I used the rt2500usb driver from the CD and now it works! I just need to figure out how to get WPA to work now.............
Great. You could try my tutorial on WPA. See if it works for you (it definitely should). :-)

[wieman01]

I extracted the driver on windows and like before in linux there were no .inf files inside. Only some dll, tlb and rgs files seem to be in the exe.
I tried the same with the driver I found at http://www.treiberupdate.de/treiber-download/download-159199-treiber-Ralink-RT2500USB.html
but I got the same files as before.
Has someone an idea what I'm doing wrong?
Aren't there any of the mentioned files on the CD that came with the card?

[bastikr]

On CD there is only a file RaLink2_RT2500USB.exe. When I extract it, I get the following files:
- IKernel.dll
- ctor.dll
- IScript.dll
- IUser.dll
- objectps.dll
- DotNetInstaller.exe
- iKernel.rgs
- ISProBE9x.tlb
- ISProBENT.tlb

[wieman01]

On CD there is only a file RaLink2_RT2500USB.exe. When I extract it, I get the following files:
- IKernel.dll
- ctor.dll
- IScript.dll
- IUser.dll
- objectps.dll
- DotNetInstaller.exe
- iKernel.rgs
- ISProBE9x.tlb
- ISProBENT.tlb
Any other way you can get ahold of driver files? You are right, these aren't the correct ones.

[anteus]

Loved the HOWTO! Now I get the same speed as I did in Feisty (without ndiswrapper).

[mocha]

Thanks for this HOWTO! It worked for me! Nice find on Rutil as well.

[fsufitch]

Hey. I'm building myself a computer to experiment with Linux on. Right now it's a pretty pathetic box but nevertheless is running Kubuntu Feisty and running it well.
The problem is that, my box just having been upgraded from a scavengeable computer, and with me being just a penniless high school student, it doesn't have a wireless network card! I borrowed one from school, and it's a Linksys WMP54G, but doesn't have a version number marked on it, as the Linksys website says it must. I tried installing all of the drivers using the method described in this thread, but the only effect it had was to make knetworkmanager stop complaining about not being able to configure the interface. It still doesn't connect. The way I got wireless to work on my laptop (the computer I'm currently using) was to install wlassistant, then just mess around with it, but this time it doesn't seem to work.
A clue or something plz?
I'm trying to connect to a WEP'd interface and have no chance of getting it un-WEP'd as it's the only way my dad can control my internet use :). Any ideas?

Thanks,
fsufitch

[bastikr]

Any other way you can get ahold of driver files? You are right, these aren't the correct ones.

I found some drivers in the internet that seemed to be promising, but they are build like the one I already had:(

[xshakakee]

OK, it looks like everyone is having some trouble here, with the exception of the OP. This may not be quick, but I think I solved my problem, First, here is my system:

AMD Sempron 2800+, socket 754
Asus K8V-VM, one of those on-board everything boards
512 MB Kingston DDR400 RAM
160 gig Maxtor HDD
RT2500 PCI card. Belkin 7000, version 3

At least I think that's the card's name. I haven't looked at it in a while.
I know I plugged it into a Mac, and had to download the ralink utility.
That worked. I know it has a ralink chipset.

Anyway, I was buzzing along with Edgy (6.10) and decided to make the jump to Gutsy. I actually did a fresh install of Ubuntu 7.10 on a new hard drive. Big problem. Drivers for ra2500 didn't work "right out of the box" After some forum browsing, and lots of trial and error, I came to this solution.

Oh, and for those of you who hate to type sudo all the time, just go into terminal and type:

sudo su

enter your password at the prompt, and leave that terminal open.
Any time you need to code anything, just copy the part after "sudo".
It really saves time.
I started out on the wired network, so I had to change my default networking parameters.
I did this by running:

sudo gedit /etc/network/interfaces

and making it look like this:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.2.4
netmask 255.255.255.0
gateway 192.168.2.1

As you can see, I don't have dhcp enabled. It's a lot easier with dhcp. (Sorry, you'll have to go back to earlier posts if you need to set up dhcp.)

I plugged in the wire, and I was on my way. I must have done this the right way the first time, because I could resolve names at this point. I re-installed the OS because I had an unrelated issue (it had to do with xorg.conf)

Anyway, if plugging in the wire doesn't work for you, go into Network Manager, (System --> Administration --> Network) and futz around with it until you get on the network. Sorry, I'm going to assume you can at least get out on the internet from the wire. If you can't do even get that, then you'll have to use a different tutorial until you can.

First, I ran:

sudo apt-get install build-essential linux-headers-`uname -r`

For some reason, this prompted me to insert the CD-Rom into the drive. I did so, but I consider this stupid. Going on...
(Actually, the above step is unnecessary, but I included it because this is what I originally did. You need only download the cvs, from the wired network.)

I downloaded the latest CVS from

http://rt2x00.serialmonkey.com/wiki/index.php/Downloads

I pulled down the legacy rt2500 driver, which in my case was

rt2500-cvs-2007102623

Do Not Download the Beta!
The beta driver will not compile, on a default install of the OS. You get all these dependency errors. The CVS compiled nicely.

tar -xvzf rt2500-cvs-daily.tar.gz
cd rt2500-cvs-2007102623/Module
make
sudo make install

Then:

echo "blacklist rt2500pci" >> /etc/modprobe.d/blacklist


Next, Uninstalled networking manager

sudo apt-get remove network-manager-gnome

I restarted at this point, not knowing how to remove modules and add them on the fly.

Once I did that, I had a network conflict, since I was still plugged into the wired.

A better method would have been to use the following code:

sudo ifconfig wlan0 down
sudo modprobe -r rt2500pci
sudo modprobe rt2500

Then, in order to make my wired ethernet disappear:

sudo gedit /etc/network/interfaces

and edit the file so that it looks like this:

auto lo
iface lo inet loopback

#auto eth0
iface eth0 inet static
address 192.168.2.4
netmask 255.255.255.0
gateway 192.168.2.1

Last step, at this phase, is to restart the network:

sudo /etc/init.d/networking restart


OK -- but still no network! What gives. Let's be patient, shall we?

I added wicd through the Synaptic package manager, following the instructions here:

http://wicd.sourceforge.net/download.php

Turns out, I didn't actually use it to set up my network, but it is a handy network monitor; a good Network Manager surrogate

What seems to have worked, from this point onward, was going back to:

sudo gedit /etc/network/interfaces

and adding the following lines, in red:

auto lo
iface lo inet loopback

#auto eth0
iface eth0 inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.2.2
gateway 192.168.2.1
dns-nameservers <ip address of nameserver1>, <ip address of nameserver2>
netmask 255.255.255.0

pre-up ifconfig wlan0 up
pre-up ifconfig wlan0 down
pre-up ifconfig wlan0 up
pre-up ifconfig wlan0 down
pre-up iwconfig wlan0 essid "My SSID"
pre-up iwconfig wlan0 mode Managed
pre-up iwpriv wlan0 set AuthMode=WPAPSK
pre-up iwpriv wlan0 set EncrypType=TKIP
pre-up iwpriv wlan0 set WPAPSK="my preshared key"
pre-up ifconfig wlan0 up

As you can see, I modified the heck out of the eth0 portion, as well as adding
an entirely new portion, the wlan0.

Once I ran: sudo /etc/init.d/networking restart
it all came up. I rebooted a couple of times, and the changes seemed to have taken.

One caveat: I have a card with little blinking lights in the back, so I know when it is active. (I actually have the USB version of this adapter, and love it because it blinks at me when active. It's on the MAC, though.) At some point, the lights are going to go off. I got frustrated with this several times, and thought, what am I doing wrong? I solved it (I think) by using various iterations of the following code:

sudo ifconfig wlan0 down
sudo modprobe -r rt2500pci
sudo depmod
sudo modprobe rt2500
sudo depmod

I ran this, and ran the restart script, and the adapter seems to have kicked in. You need to have the original driver, rt2500pci blacklisted, in /etc/modprobe.d/blacklist

Also, you may need to modify your resolv.conf. I did because I got rid of network manager before I could even create this file. Therefore, my machine did not know where to go for DNS resolution. Here's how you do it.

sudo gedit /etc/resolv.conf

Make sure the following lines are in there:

nameserver 208.67.220.220
nameserver 208.67.220.222

That's all. The mandatory OpenDNS servers is all you need. You can also pull the nameservers from your cable/dsl provider, but I find it easier just to stick with these two.

That's it! Fire up WICD, restart your network:

sudo /etc/init.d/networking restart

and you should be on the way!

[bastikr]

@xshakakee
Thanks a lot for your tips. This was the right way for me! My wlan is running perfectly!\\:D/
Maybe you should post this howto in an own thread, since many people won't look for it here.

[bastikr]

Okay, I got now a new strange problem. The Interface of my wlan card switches it's name after startup always into a name that does'nt occur in /etc/network/interfaces!
For example, if my /etc/network/interfaces looks like the following:

auto lo
iface lo inet loopback

pre-up ifconfig rausb0 up
pre-up ifconfig rausb0 down
pre-up iwconfig rausb0 essid "default"
pre-up iwconfig rausb0 key "21EB0462EF11B394F8EEA982A3"
pre-up iwconfig rausb0 mode Managed
pre-up ifconfig rausb0 up
auto rausb0
iface rausb0 inet dhcp


Then after a reboot, ifconfig tells me that the interfaces name is wlan0.
When I change rausb0 to wlan0 and do /etc/init.d/networking restart
everything is alright until I reboot my system.
Then the game starts again: interface is the rausb0 and I have to change wlan0 to rausb0....

Maybe I should mention that I use Rutilt. (Don't know if this matters)

Has anyone experienced a similar problem?

[xshakakee]

bastikr, looks like there's something going on during initiation of your wireless card. To make things easier, you might try this.
Go into /etc/network/interfaces:

pre-up ifconfig rausb0 up
pre-up ifconfig rausb0 down
pre-up iwconfig rausb0 essid "default"
pre-up iwconfig rausb0 key "21EB0462EF11B394F8EEA982A3"
pre-up iwconfig rausb0 mode Managed
pre-up ifconfig rausb0 up
auto rausb0
iface rausb0 inet dhcp

pre-up ifconfig wlan0 up
pre-up ifconfig wlan0 down
pre-up iwconfig wlan0 essid "default"
pre-up iwconfig wlan0 key "21EB0462EF11B394F8EEA982A3"
pre-up iwconfig wlan0 mode Managed
pre-up ifconfig wlan0 up
auto wlan0
iface wlan0 inet dhcp

See if after reboot, the network "just works"
I'll try to post a better solution for you when I've learned more about interface name aliasing, but I think this should solve your immediate problem, for now.

Oh, and I don't think the use of Rutilt vs. WICD makes a difference. As long as you don't touch settings in the program, it shouldn't make any difference.

OK, I guess I should do a little more research on this before posting, but try this method, and see if it helps.

Obviously, you can delete or comment out the added lines if this doesn't help. Bye for now.

[bastikr]

I was surprised that it didn't come up with other interface names, but you were right. I added both names and it works now.
It's truly not a very elegant solution, but it is one.:)


I'll try to post a better solution for you when I've learned more about interface name aliasing, but I think this should solve your immediate problem, for now.


Let me now if you find out something, but thanks for your help so far.
Now I only have to set up rutilt to start automatically after bootup, but I think for this I'll look in another thread.

[wieman01]

OK, it looks like everyone is having some trouble here, with the exception of the OP.
What makes you think so?

If your tutorial works for other people as well, please let me know because I will include the link to your tutorial in mine. This way people are given options. I don't really like the fact that we need to use "ndiswrapper" at all, so I would appreciate your help. That said submit your tutorial and please send me the link, so that I can include it if you don't mind.

[alanmzifa]

wieman01, I'm trying to get an Asus WG107G PC Card going on Dapper (from my thread you answered last night).

It's a Ralink rt2500 chipped device.

I've followed your how-to and got it set-up wirelessly on wlan0 with no security. My goal is to get some sort of WPA set up. The rest of the network is using WPA2-PSK AES.

I've read that the card is supposed to support WPA-PSK in Windows.I'd settle for anything above WEP encryption but the higher the better.

Can you guide me through the rest? I briefly tried WICD but wouldn't even work without encryption. Currently no Network Manager, WPA Supplicant, Wifi Radar or WICD installed but stable without encryption.

thanks

[wieman01]

wieman01, I'm trying to get an Asus WG107G PC Card going on Dapper (from my thread you answered last night).

It's a Ralink rt2500 chipped device.

I've followed your how-to and got it set-up wirelessly on wlan0 with no security. My goal is to get some sort of WPA set up. The rest of the network is using WPA2-PSK AES.

I've read that the card is supposed to support WPA-PSK in Windows.I'd settle for anything above WEP encryption but the higher the better.

Can you guide me through the rest? I briefly tried WICD but wouldn't even work without encryption. Currently no Network Manager, WPA Supplicant, Wifi Radar or WICD installed but stable without encryption.

thanks
Hello Alan,

Of course I'll help. So the current Windows driver supports WPA, right? That's the same driver you used in Windows with full WPA support?

You might have seen my WPA howto in my signature. Guess that's a good start. Please try it first and post your problems there. I'll guide you through it.

[bfoos]

Thanks for the guide. I was having trouble with Gutsy's built in support for the RT61 chip-set. Network connection slowing to a crawl and eventually dropping. Ndiswrapper has sorted my problem nicely. Thanks again.

[alanmzifa]

Hello Alan,

Of course I'll help. So the current Windows driver supports WPA, right? That's the same driver you used in Windows with full WPA support?

You might have seen my WPA howto in my signature. Guess that's a good start. Please try it first and post your problems there. I'll guide you through it.

wieman01, I've foolowed that. Got the card working on no security then installed wpa supplicant and WICD. Went for WPA-PSK TKIP which the card is supposed to support under Windows but signal gets dropped straight away.

I set up using DHCP rather than static. Uninstalled WICD again, No other network management utility currenty installed. Card shows as wlan0 not ra0.

Can you suggest what I could try next?

thanks

[wieman01]

The standard networking applet (Network Manager) should do the job actually. If you don't need static IP and DHCP will do, NM should be a breeze.
sudo apt-get install network-manager-gnome
When you open NM, are you given an option to use WPA encryption?

[alanmzifa]

The standard networking applet (Network Manager) should do the job actually. If you don't need static IP and DHCP will do, NM should be a breeze.

When you open NM, are you given an option to use WPA encryption?

I'd tried Network Manager a couple of nights ago but it only gave me option for WEP. I can try it again.

[wieman01]

I'd tried Network Manager a couple of nights ago but it only gave me option for WEP. I can try it again.
Mate, if that's the case, then this might have two reasons (generally):

A. You have not installed "wpa-supplicant" (which you have, I know).

B. The Windows driver that you used can't do WPA. Get hold of the README file and see if it actually does.

That's all I can offer at the moment...

[seul]

wieman01, you are my hero! Thank you, thank you, thank you ever so much. After 1 1/2 years of trouble, ubuntu finally connects without a cable. I can't tell you how happy I am.
Cheers, seul

[wieman01]

@Seul:

Excellent, Seul. Would you mind telling me what hardware you have got? Did you have to edit your "/etc/network/interfaces" as well?

[hacklix]

It can be useful?
http://forum.ubuntu-it.org/index.php?topic=69879.0

[seul]

Do you mean the card or my computer hardwarewise? For the card it is a Belkin Wireless G F5D7010 ver6000uk (rt61).

I tried so many things and don't really know what I am doing when I use the terminal, so I can't really remember how my /interfaces looked like in the beginning. Currently I have
auto lo
iface lo inet loopback

#WIRED
auto eth0
iface eth0 inet dhcp

#WIRELESS
auto wlan0
iface wlan0 inet dhcp

Only thing is that it did not work before I reinstalled network manager because I couldn't choose "shared key" without netman.

I had tried ndiswrapper with edgy 1 1/2 years ago, but it didn't work, so I didn't give it another try until now. I think that the problem then was that the tutorial I was following didn't mention blacklisting.

Also, the Belkin card used to freeze my entire system when inserted (even when I did not connect), that's gone now, too.

[wieman01]

It can be useful?
http://forum.ubuntu-it.org/index.php?topic=69879.0
Don't really know, it's in Italian. Would should we use it for?

[seul]

I hope the info was what you were asking for. Let me know if not. Thanks again, all the best.

[seul]

I just made a dlink DWL-G122 H/W Ver C1 usb dongle work, too. What a beautiful day!

[wieman01]

I just made a dlink DWL-G122 H/W Ver C1 usb dongle work, too. What a beautiful day!
Seul, to answer your other question, yes, that's the info I needed. Thank you.

What chipset is that one?

[MarkMadsen]

Seul, to answer your other question, yes, that's the info I needed. Thank you.

What chipset is that one?

The D-Link DWL-G122 Rev C1 is a Ralink rt73. It works out of the box with 7.10 (even from the liveCD) and network manager has no problems with it.

[wieman01]

The D-Link DWL-G122 Rev C1 is a Ralink rt73. It works out of the box with 7.10 (even from the liveCD) and network manager has no problems with it.
Alright... some progress at last. Thanks for letting us know. Hope this thread will become unnecessary soon.

[seul]

The D-Link DWL-G122 Rev C1 is a Ralink rt73. It works out of the box with 7.10 (even from the liveCD) and network manager has no problems with it.

I, too, thought it was rt73 for the dlink, but I couldn't get it to work; neither out of the box, nor with serialmonkey (see my post (http://ubuntuforums.org/showthread.php?t=604690)).


What chipset is that one?

When I fetched the driver from dlink's homepage (link is in the post), I found it was called "dr71WU.inf", I don't know if that's just the windows name for rt73 or if it is a different driver after all.

I can't use gutsy because of this (http://ubuntuforums.org/showthread.php?t=587984), so I can only speak about my feisty-experience. I do know from my brief gutsy encounter that the Belkin Wireless G F5D7010 ver6000uk card worked out of the box without freezing the system.

[ricardisimo]

I hope this post isn't unwelcome, because Wieman's HowTo did, in fact, help me get my wireless up and running. However, I thought that maybe Gina and some of the other posters here would like to know about this: I was having way too many problems with Ubuntu 7.10, so I decided to try Kubuntu Gutsy instead. I was very pleasantly surprised. KNetworkManager worked as close to perfectly as anything since Dapper, both on the LiveCD and installed on the hard disk. Just right-click on KNM, find your preferred connection and select it.

There were lots of things I liked about Gnome, but this may have won me over to KDE permanently. We'll see. Thanks anyways, Wieman.

[ricardisimo]

Oops! Accidental double-post. Sorry.

[wieman01]

I hope this post isn't unwelcome, because Wieman's HowTo did, in fact, help me get my wireless up and running. However, I thought that maybe Gina and some of the other posters here would like to know about this: I was having way too many problems with Ubuntu 7.10, so I decided to try Kubuntu Gutsy instead. I was very pleasantly surprised. KNetworkManager worked as close to perfectly as anything since Dapper, both on the LiveCD and installed on the hard disk. Just right-click on KNM, find your preferred connection and select it.

There were lots of things I liked about Gnome, but this may have won me over to KDE permanently. We'll see. Thanks anyways, Wieman.
Actually I don't really believe it's a Kubuntu thing. Perhaps the current ISO is more up-to-date or repositories were after you had installed 7.10 first.

I believe this is due to the fact that they have replaced the drivers and put in the latest ones. Let's hope for the best then! Perhaps this thread is no more necessary soon.

[Fruhwirth]

Actually I don't really believe it's a Kubuntu thing. Perhaps the current ISO is more up-to-date or repositories were after you had installed 7.10 first.

I believe this is due to the fact that they have replaced the drivers and put in the latest ones. Let's hope for the best then! Perhaps this thread is no more necessary soon.

Are you saying that if I redownload Gutsy and reinstall it may be a different/work better than it did a month ago? I wouldn't even be asking this question (I gave up on Gutsy and reinstalled Dapper due to troubles (http://ubuntuforums.org/showthread.php?p=3646231#post3646231)) except that when i reinstalled Dapper (the fourth time I've done so) there were network problems that did not occurr the first, second and third times I installed it. In Dapper, basically, I can browse the internet fine, but no other network applications can connect at all. Except for having to install wlassisstant, I never had to tweak dapper in the past but now it's broken, too.

Should I redownload Gutsy and give it another try or am I just going to hate life again?

[wieman01]

Should I redownload Gutsy and give it another try or am I just going to hate life again?
Well, quite a number of other posts made me believe so, but I cannot confirm it myself.

Best option for you would be to run the latest life CD. Perhaps it recognizes your card. Or you reinstall Gutsy, then update the system via Ethernet and see if the driver's been updated and is able to connect.

If you do so, do a full backup of your current system (see signature for tutorial). This way you can revert back to Dapper without having to install from scratch again.

[Fruhwirth]

I tried to install Kubuntu 7.10 for amd64. Strangely, the live CD worked just as Ricardismo said - I just used the built-in Knetworkmanager and it "just worked." Feeling hopeful, I did a fresh install of it. How disheartening. It would not work after being installed, and tweaked, and carressed and all the rest. I ran the live CD again, just to make sure I wasn't nuts, and lo and behold, it still worked perfectly on there.

The whole main point of a live cd is undermined if it functions so much better than operating system once it's installed. sheesh.

Feeling bold, I installed Mandriva and both wireless and DRI (my two most common sore spots) worked out of the box with that. But it's not 64-bit.

So as I type this post, I'm downlaoding the 32-bit Gutsy Gibbon, hoping that my wireless and DRI work out of the box on that. I read once that 64-bit Ubuntu encodes roughly 30 percent faster than 32-bit. I do a lot of encoding, so I thought I should really try to get the 64-bit working, but that's beginning to look more and more like a pipe dream.

I'll let you know wieman01 how my wireless experience varies between GG64 and GG32. But for now Mandriva (which I do not prefer) is working perfectly.

[dingansich]

Haven't been in this thread for a while, but I seem to have most of my networking issues ironed out now, so I figured I'd add in what little I can:

A.) While the 64 bit driver for the WUS54Gv4 worked with ndiswrapper it seemed to destabilize the system (i.e. my computer would freeze)
B.) Replacing Network Manager with Wicd seemed to help with connectivity and stability
C.) Using the serial monkey driver for the RT2570 chipset, and ditching ndiswrapper, seems to have worked! I found a howto at: http://ubuntuforums.org/showthread.php?t=588045

Hope this helps someone.

[Chazall1]

I am having NO luck on getting my Wireless to Function any more, Before I added ndiswrapper, I had some functionality with picking up other non WEP Linksys connections, Now I do not even have a choice for any Wireless functions, Dell Dimension B110, Here are some outputs

ace@ace-desktop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

I added ndiswrapper and followed the How Too RT2500, etc wireless cards Gutsy in the forums.
When I add the drivers to the 'Blacklist in etc/modprobs, everything seems fine untill
I run ndiswrapper -l, my output is this,
ace@ace-desktop:~$ ndiswrapper -l
rt2500 : invalid driver!
rt2500pci : invalid driver!
ace@ace-desktop:~$
I have no Internet now, The NM does not give me an option for wireless!!
Here is my network interface file info as well

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 intel dhcp

Before ndiswrapper
Output I have Gutsy on a Dell Dimension B110 Desktop using a Linksys Router with WEP. I can not conect to my WEP. However I was connecting to the Internet using other Linksys networks in the neighborhood. This however has stoped working, I do not have ndiswrapper installed, would this make a difference???
Here are my outputs if I use wmaster0 as my interface:

ace@ace-desktop:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network:0
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: 0
bus info: pci@0000:01:00.0
logical name: wmaster0
version: 01
serial: 00:12:17:8c:99:3c
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt2500pci latency=64 module=rt2500pci multicast=yes wireless=IEEE 802.11g
*-network:1
description: Ethernet interface
product: 82562EZ 10/100 Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:01:08.0
logical name: eth0
version: 02
serial: 00:13:20:d4:8e:45
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=e100 driverversion=3.5.17-k4-NAPI firmware=N/A latency=64 maxlatency=56 mingnt=8 module=e100 multicast=yes

If I use wmaster0 in <interface>
ace@ace-desktop:~$ sudo ifconfig wmaster0 down
[sudo] password for ace:
ace@ace-desktop:~$ sudo dhclient -r wmaster0
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 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/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
ace@ace-desktop:~$ sudo ifconfig wmaster0 up
ace@ace-desktop:~$ sudo iwconfig wmaster0 essid "lish1"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wmaster0 ; Operation not supported.
ace@ace-desktop:~$ sudo iwconfig wmaster0 key 6063547000
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wmaster0 ; Operation not supported.
ace@ace-desktop:~$ sudo iwconfig wmaster0 mode Managed
Error for wireless request "Set Mode" (8B06) :
SET failed on device wmaster0 ; Operation not supported.
ace@ace-desktop:~$ sudo dhclient wmaster0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 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/wmaster0/
Sending on LPF/wmaster0/
Sending on Socket/fallback
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

If I run wlan0, here is the output:

ace@ace-desktop:~$ sudo ifconfig wlan0 down
[sudo] password for ace:
ace@ace-desktop:~$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 6040
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 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:12:17:8c:99:3c
Sending on LPF/wlan0/00:12:17:8c:99:3c
Sending on Socket/fallback
ace@ace-desktop:~$ sudo ifconfig wlan0 up
ace@ace-desktop:~$ sudo iwconfig wlan0 essid "lish1"
ace@ace-desktop:~$ sudo iwconfig wlan0 key 6063547000
ace@ace-desktop:~$ sudo iwconfig wlan0 mode Managed
ace@ace-desktop:~$ sudo dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 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:12:17:8c:99:3c
Sending on LPF/wlan0/00:12:17:8c:99:3c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Can anyone assist me, I have no WIRELESS at this time

[wieman01]

Hello Chazall1,

Are you 100% sure you have installed the right driver? Where did you find the driver and what chipset is your card?

[Chazall1]

I went to the Linksys, and downloaded the latest driver fro my Wireless card, Linksys, WMP54G.

[Chazall1]

Well # out what ndiswrapper configured in /etc/modules, and /etc/modprobe.d/blacklist. I set /etc/network/interfaces to

auto lo
iface lo inet loopback

I have Wireless back, I have been using the internet for the past 3 hrs, on another router, not mine. I disabled my WEP about an hour ago, and the NM still showes a security key in the NM Wireless networks. I will watch and see what happens!!!!!

Thanks

[ricardisimo]

I hope this post isn't unwelcome, because Wieman's HowTo did, in fact, help me get my wireless up and running. However, I thought that maybe Gina and some of the other posters here would like to know about this: I was having way too many problems with Ubuntu 7.10, so I decided to try Kubuntu Gutsy instead. I was very pleasantly surprised. KNetworkManager worked as close to perfectly as anything since Dapper, both on the LiveCD and installed on the hard disk. Just right-click on KNM, find your preferred connection and select it.

There were lots of things I liked about Gnome, but this may have won me over to KDE permanently. We'll see. Thanks anyways, Wieman.

It just keeps getting more and more discouraging. True, KNM under the latest Gutsy Kubuntu worked immediately without any tweaking, but I still have the previous problem of connection speed. Right now I'm on the 7.04 Live CD again, and just to test my theory I'm downloading one of the Ubuntu CD images. It' s going at a decent clip, roughly 500 kbps.

Mind you, I haven't moved the wireless antenna one micron from where it was when I was running Gutsy a few minutes earlier. On 7.10 the absolute best I have been able to get is about 15-20 kbps.

So here's the question: Is there a way for me to downgrade NM or KNM to the Feisty, Edgy, or better yet, Dapper versions? Who knows... maybe Hoary's what I should be going after. This is so frustrating. I can't understand how the support can literally be getting worse with each release. Can someone explain that to me?

Thanks in advance.

[wieman01]

Is there a way for me to downgrade NM or KNM to the Feisty, Edgy, or better yet, Dapper versions? Who knows... maybe Hoary's what I should be going after. This is so frustrating. I can't understand how the support can literally be getting worse with each release. Can someone explain that to me?
You could downgrade by compiling older version from source, however, I believe it has nothing to do with NM but something else, perhaps the kernel. I would be surprised if replacing NM would help.

What driver to you use at the moment?

[ricardisimo]

I'm just running NM defaults in Feisty. No idea to what specific driver that translates. Here's some info:
lspci -vvv=
00:08.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
Subsystem: Linksys WMP54G 2.0 PCI Adapter
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: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 21
Region 0: Memory at dfffa000 (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-

[wieman01]

I'm just running NM defaults in Feisty. No idea to what specific driver that translates. Here's some info:

And IPV6 is disabled?

[ricardisimo]

No. I read through the link you posted on disabling globally, and it seemed pretty clear to me by the end of it that doing so was either not a good idea or it was not a real solution. Besides... maybe I'm unclear on something, but wouldn't IPV6 be doing similar damage under Dapper, Edgy or Feisty as under Gutsy? Something else would seem to be the culprit.

[deviance]

I have followed this, but mine says:

device (13B1:000D) present (alternate driver: rt73usb)

Do I need to install the alternate as well as it is different?

[wieman01]

I have followed this, but mine says:

device (13B1:000D) present (alternate driver: rt73usb)

Do I need to install the alternate as well as it is different?
Looks fine actually. Now continue to follow the tutorial... Can you connect to any network? If not please scan for networks and post the results:
sudo iwlist scan

[srkelley]

I don't get the format for everything in bold. Can someone type in some examples of they should look like please?

* Now unzip the driver archive you have just downloaded (e.g. in your home directory):
Quote:
unzip <driver_archive>.exe

* Now find the right driver in the resulting folder & deploy it (folder should also contain other driver files i.e. .cat, .sys):
Quote:
sudo ndiswrapper -i <your_ralink_driver>.inf

* Make sure it has installed correctly:
Quote:
ndiswrapper -l

* The output should yield something like this:
Quote:
rt2500usb : driver installed
device (13B1:000D) present (alternate driver: rt2500usb)

* Last but not least open this file...
Quote:
sudo gedit /etc/network/interfaces

* ...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]:
Quote:
auto wlan0
iface wlan0 inet dhcp

[wieman01]

I don't get the format for everything in bold. Can someone type in some examples of they should look like please?

* Now unzip the driver archive you have just downloaded (e.g. in your home directory):
Quote:
unzip <driver_archive>.exe

* Now find the right driver in the resulting folder & deploy it (folder should also contain other driver files i.e. .cat, .sys):
Quote:
sudo ndiswrapper -i <your_ralink_driver>.inf

* Make sure it has installed correctly:
Quote:
ndiswrapper -l

* The output should yield something like this:
Quote:
rt2500usb : driver installed
device (13B1:000D) present (alternate driver: rt2500usb)

* Last but not least open this file...
Quote:
sudo gedit /etc/network/interfaces

* ...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]:
Quote:
auto wlan0
iface wlan0 inet dhcp
It basically says that you need to get hold of the latest driver file which usually comes in a ".exe" archive. So you need to download the archive, extract the files it contains and find a file that ends with ".inf". That's it.

What hardware have you got?

[srkelley]

I have a Nintendo USB adapter. i already have the driver and the executable, but I wanted to know how would I type it in. Would it be something like:

"sudo ndiswrapper -i srkelley/desktop/downloads/netu2g54.inf"

Or do I just type in the "sudo ndiswrapper -i netu2g54.inf"? I also need to know what extra bit goes before and after because I have typed in both and I don't know what it wants exactly.

[wieman01]

That is right:
sudo ndiswrapper -i /home/srkelley/desktop/downloads/netu2g54.inf
Then do...
sudo ndiswrapper -l
...and post the output.

[srkelley]

shirondale@shirondale-desktop:~$ sudo ndiswrapper -i /home/srkelley/desktop/netu2g54.inf
[sudo] password for shirondale:
driver netu2g54 is already installed
shirondale@shirondale-desktop:~$ sudo ndiswrapper -l
netu2g54 : invalid driver!
rt25usbap : invalid driver!
shirondale@shirondale-desktop:~$ sudo ndiswrapper -l
netu2g54 : driver installed
shirondale@shirondale-desktop:~$ sudo ndiswrapper -i /home/srkelley/desktop/U2K2G54/Win2000/netu2g54.inf
driver netu2g54 is already installed
shirondale@shirondale-desktop:~$
shirondale@shirondale-desktop:~$

I found out that it was already installed, but that the driver was invalid (I tried the modded one first) then I used the original one and it installed, but I can't use the usb adapter as a wireless ap in any way. The pc isn't recogniizing the hardware as what should properly belong with the driver. is there anything I'd be able to do about that?

[daengbo]

I tried desperately to follow the tutorial for an RT61pci and an RT73usb, but I didn't have .sys and .inf files in my drivers. I tried for hours to download other drivers, but still had no luck there. The one driver set that did have the files failed under ndiswrapper.

Finally, I gave up, downloaded the daily build from seamonkey, and compiled. Both machines work fine, though the wireless drops about every 24 hours and has to be restarted on the rt73.

Much easier than ndiswrapper. I'd suggest the seamokey drivers.

On a side note, I'm really disappointed that the drivers are open source, are included in Gutsy, but don't seem to work well or at all. rtxxxx had worked flawlessly since Dapper for me. Meh.

[wieman01]

I found out that it was already installed, but that the driver was invalid (I tried the modded one first) then I used the original one and it installed, but I can't use the usb adapter as a wireless ap in any way. The pc isn't recogniizing the hardware as what should properly belong with the driver. is there anything I'd be able to do about that?
Looks good so far. Have you followed the other steps as well?

Please post the results of:
sudo iwlist scan
And the contents of:
sudo gedit /etc/network/interfaces

[wieman01]

I tried desperately to follow the tutorial for an RT61pci and an RT73usb, but I didn't have .sys and .inf files in my drivers. I tried for hours to download other drivers, but still had no luck there. The one driver set that did have the files failed under ndiswrapper.

Finally, I gave up, downloaded the daily build from seamonkey, and compiled. Both machines work fine, though the wireless drops about every 24 hours and has to be restarted on the rt73.

Much easier than ndiswrapper. I'd suggest the seamokey drivers.

On a side note, I'm really disappointed that the drivers are open source, are included in Gutsy, but don't seem to work well or at all. rtxxxx had worked flawlessly since Dapper for me. Meh.
Great. Thanks for letting us know. Does the driver also support WPA and WPA2?

[daengbo]

Wow, I'm an idiot.
http://rt2x00.serialmonkey.com/
Serialmonkey, not Seamonkey. Wow.

Anyway, WPA is said to work (I don't use it), but you must use iwpriv to set it up instead of wpa supplicant.

[james_xxx]

One thing that is still unclear to me in posts like #162, is whether or not the mods to /etc/network/interfaces will work for someone not using WPA. What if you are using WEP?

I am really frustrated with Gutsy (and *ubuntu, in general), though I have been a Kubuntu user for several years. I don't get how a wireless card will not work in one version of Ubuntu, will work the next, then again not work in the next. Is this just sloppiness? If not, is it that difficult to eventually correct this with new restricted modules, etc.?

Right now, I am able to connect to my wireless router with everything entered EXACTLY in /etc/network/interfaces with the rt2500 driver that comes with Gutsy. The problem I have is with trying to connect to other networks, say at a coffee shop , etc. Frequently I just cannot connect, no matter what I do. Even at home, my wireless still disconnects at random times. I did not have these problems in Feisty, and I wish I hadn't upgraded, especially considering that this is not the only significant issue I have experienced since upgrading. Maybe none of this is the control of the *ubuntu devs, but I would be curious to know. I originally had a broadcom wireless card in this laptop, but pulled it to install an rt2500, because they are (supposedly) well-supported in Linux. I guess I made a bad choice.

I presume that compiling the CVS driver like this will work until a kernel upgrade comes out... how does one remove this driver in order to compile it again in the event of a new kernel being installed?

Sorry if part of this post is just ranting.
Peace

[wieman01]

One thing that is still unclear to me in posts like #162, is whether or not the mods to /etc/network/interfaces will work for someone not using WPA. What if you are using WEP?

I am really frustrated with Gutsy (and *ubuntu, in general), though I have been a Kubuntu user for several years. I don't get how a wireless card will not work in one version of Ubuntu, will work the next, then again not work in the next. Is this just sloppiness? If not, is it that difficult to eventually correct this with new restricted modules, etc.?

I presume that compiling the CVS driver like this will work until a kernel upgrade comes out... how does one remove this driver in order to compile it again in the event of a new kernel being installed?
Hey James,

I share your frustration, believe me.

WEP is possible as well, no doubt. So be our guest to try and report back if you have issues connecting.

As for the CVS driver, it should work also after a kernel upgrade, but that's no guarantee. That said, however, The next Ubuntu release is just 5 months down the road, and I am sure they will fix it. So why don't you just wait and live with it until then?

[ubulap]

Just wanted to say thanks for this thread.

It allowed me to use the windows driver with ndiswrapper on a Gigabyte GN-WI05GS embedded laptop card (uses rt73 chipset) and combined with the information of your other WPA thread have it working with WPA connection (rt73usb wouldn't work with WPA)

[ricardisimo]

As I mentioned earlier, I'm back on Feisty because of a slow connection under Gutsy. However, I would love to give 7.10 a try again as soon as anyone can confirm that a sure-fire fix or significant update (kernel update, probably) has arrived. Please post here if you had my same problem and it is now fixed. And thanks again to Wieman for this article.

[wieman01]

As I mentioned earlier, I'm back on Feisty because of a slow connection under Gutsy. However, I would love to give 7.10 a try again as soon as anyone can confirm that a sure-fire fix or significant update (kernel update, probably) has arrived. Please post here if you had my same problem and it is now fixed. And thanks again to Wieman for this article.
No problem. As soon as I hear anything I'll post here and make mention of it in my tutorial.

[devosion]

Im receiving this error message from ndiswrapper after installing my driver and running ndiswrapper -l.

rt2500usb: invalid driver

This is rather strange because i've used this driver for my linksys wireless adaptor before. I remembered that I didnt have the .sys file in the same directory when doing the installation this time so I decided i'd try removing the driver from ndiswrapper and got this message.

couldn't delete /etc/ndiswrapper/rt2500usb: Inappropriate ioctl for device

Not quite sure what that meant so I went over my blacklist, which I recently filled with all the ralink drivers because I was unsure which one belonged to my chipset. And quite honestly forgot since my last installation. I noticed the rt2500usb and removed it and attempted the removal of the driver from ndiswrapper and was given the same error again.

Im not quite sure how to rectify this problem at this point, and would appreciate any help in either deleting the driver, or fixing the driver so it works.

[wieman01]

Im receiving this error message from ndiswrapper after installing my driver and running ndiswrapper -l.



This is rather strange because i've used this driver for my linksys wireless adaptor before. I remembered that I didnt have the .sys file in the same directory when doing the installation this time so I decided i'd try removing the driver from ndiswrapper and got this message.



Not quite sure what that meant so I went over my blacklist, which I recently filled with all the ralink drivers because I was unsure which one belonged to my chipset. And quite honestly forgot since my last installation. I noticed the rt2500usb and removed it and attempted the removal of the driver from ndiswrapper and was given the same error again.

Im not quite sure how to rectify this problem at this point, and would appreciate any help in either deleting the driver, or fixing the driver so it works.
Are you on a 64-bit system and try to install a 32-bit driver by chance?

[devosion]

No thats not the case. This is the same driver i've used before and its worked just fine before on my architecture, which is incidentally 64bit capable but I run it 32bit anyways.

And my question and problem has pretty much flown out the window because I was tinkering away with ndiswrapper and completely uninstalled it. Then when I reinstalled it and attempted
sudo modprobe ndiswrapper im getting a fatal message.

Perhaps if I didnt locate every single file and delete them all then I wouldnt be having this problem. :)

No biggie though because this is a brand new install of gutsy and I wont lose anything by reinstalling gutsy. Unless of course you know how I can get around the FATAL message im getting now.

FATAL: Module ndiswrapper not found.

Even if you cant answer my question its ok. In any case im going to get some rest now.

[wieman01]

No thats not the case. This is the same driver i've used before and its worked just fine before on my architecture, which is incidentally 64bit capable but I run it 32bit anyways.

And my question and problem has pretty much flown out the window because I was tinkering away with ndiswrapper and completely uninstalled it. Then when I reinstalled it and attempted
sudo modprobe ndiswrapper im getting a fatal message.

Perhaps if I didnt locate every single file and delete them all then I wouldnt be having this problem. :)

No biggie though because this is a brand new install of gutsy and I wont lose anything by reinstalling gutsy. Unless of course you know how I can get around the FATAL message im getting now.



Even if you cant answer my question its ok. In any case im going to get some rest now.
The error message probably means that you have removed the 'ndiswrapper' package at some point. Why don't you reinstall it via Synaptic? Completely remove it if there are still files and dependencies and install it afterwards. That should fix your problem. That done start all over again. Would that fix it?

[aldo_m]

ok im getting a little problem here i tryed doing it with ndisgtk like i did the bc drivers but it says rt2500usb install hardware present:NO
o@ubuntu:~$ gedit /etc/network/interfaces
o@ubuntu:~$ sudo apt-get install ndiswrapper-common ndiswrapper-utils-1.9
[sudo] password for aldo:
Reading package lists... Done
Building dependency tree
Reading state information... Done
ndiswrapper-common is already the newest version.
ndiswrapper-utils-1.9 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
o@ubuntu:~$ sudo depmod -a
o@ubuntu:~$ sudo modprobe ndiswrapper
echo 'ndiswrapper' | sudo tee -a /etc/modules
ndiswrapper
o@ubuntu:~$ sudo ndiswrapper -m
module configuration already contains alias directive

aldo@ubuntu:~$ echo 'blacklist rt2500usb' | sudo tee -a /etc/modprobe.d/blacklist
blacklist rt2500usb
o@ubuntu:~$ sudo ndiswrapper -i rt2500usb.inf
driver rt2500usb is already installed
o@ubuntu:~$ ndiswrapper -l
rt2500usb : driver installed
so thene tryed it this way and not working this i s m hardware info

it dosnt have anything for a device butmyinternet works its using a linux default driver zd1211rw
say when i click my network bars at the topit says wireless networks {unknown usb device}

[wieman01]

ok im getting a little problem here i tryed doing it with ndisgtk like i did the bc drivers but it says rt2500usb install hardware present:NO
o@ubuntu:~$ gedit /etc/network/interfaces
o@ubuntu:~$ sudo apt-get install ndiswrapper-common ndiswrapper-utils-1.9
[sudo] password for aldo:
Reading package lists... Done
Building dependency tree
Reading state information... Done
ndiswrapper-common is already the newest version.
ndiswrapper-utils-1.9 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
o@ubuntu:~$ sudo depmod -a
o@ubuntu:~$ sudo modprobe ndiswrapper
echo 'ndiswrapper' | sudo tee -a /etc/modules
ndiswrapper
o@ubuntu:~$ sudo ndiswrapper -m
module configuration already contains alias directive

aldo@ubuntu:~$ echo 'blacklist rt2500usb' | sudo tee -a /etc/modprobe.d/blacklist
blacklist rt2500usb
o@ubuntu:~$ sudo ndiswrapper -i rt2500usb.inf
driver rt2500usb is already installed
o@ubuntu:~$ ndiswrapper -l
rt2500usb : driver installed
so thene tryed it this way and not working this i s m hardware info

it dosnt have anything for a device butmyinternet works its using a linux default driver zd1211rw
say when i click my network bars at the topit says wireless networks {unknown usb device}
Alright... First of all what hardware/wireless device have you got?

Then do a scan please, and post the results:
sudo iwlist scan

[devosion]

The error message probably means that you have removed the 'ndiswrapper' package at some point. Why don't you reinstall it via Synaptic? Completely remove it if there are still files and dependencies and install it afterwards. That should fix your problem. That done start all over again. Would that fix it?

Well the way I uninstalled it was first I went through and ran 'locate ndiswrapper', and deleted all the files that came up. This was probably the worst way of doing things, and manually extensive, but I did it anyways. After I completed this I tried to reinstall ndiswrapper, but aptitude still showed the package as installed. So I ran aptitude and set it for uninstall, which it did.

At this point I ran a reinstall from aptitude and everything seemed to work just fine. But when I tried to run 'ndiswrapper -l', to see if ndiswrapper would return a message, that is when I received the fatal message about the module.

Im not at my computer right now, but when I get home I will try a reinstall again and see what happens.

[devosion]

Fixed the problem. Just had to reinstall ndiswrapper manually. All that just cause I forgot to include the .sys file in the same directory as the .inf file.

[wieman01]

Fixed the problem. Just had to reinstall ndiswrapper manually. All that just cause I forgot to include the .sys file in the same directory as the .inf file.
Yeah... :-) I did fall into the same trap once as well. And that's why I mention it... ;-)

[kikos]

When I first did a fresh install of Gutsy, wifi did not work. Next, I tried the serialmonkey drivers with wicd utility, but this only worked with WEP/WPA off. So I reformatted the partition and reinstalled Gutsy. Then, my D-Link GW-122 Rev. B1 (RT2570) usb dongle started working and it works with WPA too.

Only thing that changed between my first and second install is my router settings: When I had the ssid hidden and mac filtering set to on, nothing worked. Now with the ssid broadcast and mac filtering off, wireless works in Gutsy.

[wieman01]

When I first did a fresh install of Gutsy, wifi did not work. Next, I tried the serialmonkey drivers with wicd utility, but this only worked with WEP/WPA off. So I reformatted the partition and reinstalled Gutsy. Then, my D-Link GW-122 Rev. B1 (RT2570) usb dongle started working and it works with WPA too.

Only thing that changed between my first and second install is my router settings: When I had the ssid hidden and mac filtering set to on, nothing worked. Now with the ssid broadcast and mac filtering off, wireless works in Gutsy.
They have replaced the drivers in the meantime... Good for you and a lot of other users. :-)

[dysphasi]

This method works great if I use roaming mode, but if I then go to manual configuration from network manager, enter all my details such as wep key, ip/gateway etc. etc.. it stops working.

This is a problem for me because I like to autologin and don't want to have to enter my keyring password every time I log on.

Can anyone shed some light on how I might be able to set manual configuration and get this all up and running?

Thanks in advance

EDIT: Ok, got it working by:

1) Going to Synaptic Package Manager, then, Settings -> Repositories -> Third Party Software
2) Adding deb http://apt.wicd.net gutsy extras
3) Uninstalling network-manager and network-manager-gnome and installing wicd
4) Restarting, firing up wicd and entering my settings there, hey-presto it works :-D

Can anyone tell me what wicd does that network manager doesn't?.....Just out of curiosity

[wieman01]

This method works great if I use roaming mode, but if I then go to manual configuration from network manager, enter all my details such as wep key, ip/gateway etc. etc.. it stops working.

This is a problem for me because I like to autologin and don't want to have to enter my keyring password every time I log on.

Can anyone shed some light on how I might be able to set manual configuration and get this all up and running?

Thanks in advance

EDIT: Ok, got it working by:

1) Going to Synaptic Package Manager, then, Settings -> Repositories -> Third Party Software
2) Adding deb http://apt.wicd.net gutsy extras
3) Uninstalling network-manager and network-manager-gnome and installing wicd
4) Restarting, firing up wicd and entering my settings there, hey-presto it works :-D

Can anyone tell me what wicd does that network manager doesn't?.....Just out of curiosity

The thing is that NM can only do DHCP, so you cannot use static leases which - I know - is rediculous. But NM just can't do. Therefore the emergence of WiCD which allows you to use static IP addresses.

[dysphasi]

The thing is that NM can only do DHCP, so you cannot use static leases which - I know - is rediculous. But NM just can't do. Therefore the emergence of WiCD which allows you to use static IP addresses.

This being the case, how come I can use a static IP on my laptop with network manager?

[wieman01]

This being the case, how come I can use a static IP on my laptop with network manager?
Can you? That would really surprise me as you would be the first one to achieve that. NM officially does not support static IP addresses. At least not when using wireless networking.

[dysphasi]

Perhaps I'm misunderstanding you here, but on my laptop, if I go to System>Administration>Network, and then into my wireless connection it lets me select 'Static IP address' in the configuration, an IP address, subnet mask and gateway address.

I then reboot and sure enough I've got this IP and can use the internet connection.

If I do the same on the desktop it won't connect when I use a static address unless I use Wicd.

[wieman01]

Perhaps I'm misunderstanding you here, but on my laptop, if I go to System>Administration>Network, and then into my wireless connection it lets me select 'Static IP address' in the configuration, an IP address, subnet mask and gateway address.

I then reboot and sure enough I've got this IP and can use the internet connection.

If I do the same on the desktop it won't connect when I use a static address unless I use Wicd.
Got it... slight misunderstanding here. You use the standard networking applet, but not Network Manager... The convention is a bit confusing I have to admit. Network Manager lets you configure wireless networks with WPA security. The standard applet only knows WEP, so I assume you have a WEP secured network there, is that right?

The network applet is capable of static IP leases.

[dysphasi]

Got it... slight misunderstanding here. You use the standard networking applet, but not Network Manager... The convention is a bit confusing I have to admit. Network Manager lets you configure wireless networks with WPA security. The standard applet only knows WEP, so I assume you have a WEP secured network there, is that right?

The network applet is capable of static IP leases.

Ahhh...that sounds about right. Yes I do use WEP (got some old adapters that can't cope with anything else).

Thank you for the explanation, any idea why I could only manage to connect with roaming using the applet?

[wieman01]

Thank you for the explanation, any idea why I could only manage to connect with roaming using the applet?
Frankly I don't... Sorry, mate.

[dysphasi]

Frankly I don't... Sorry, mate.

Lol, figured as much ;) Does seem really odd, set it all up exactly as would have with any other computer, just doesn't work. Ah well, at least wicd is working really well. I like having the signal meter as well for the tray icon even when using a static ip, plus my ubuntu seems to be a lil faster loading everything up.

Thanks anyways!

[cmirandamora]

Thanks for the How-to; I´ve made my rt2500 chipset based card work with ndiswrapper and Windows driver with the router channel set on 13 (with the driver that comes with Gutsy it works out of the box but only between channels 1 to 11, and I needed to set 13 because it´s the only channel where I can watch fine the movies in my PC in my Kiis dp-600).

The problem is the signal quality: it´s only 30% and previously was more than 70%. ¿Do you know a way to improve it?

[pckong]

Hi,

When I try to install window driver with ndiswrapper, it said no such a file in the directory. i am sure the spelling is right. What would the problem be?

-----------------------------------------------------------------------------------------
pckong@pckong-laptop:~$ sudo ndiswrapper -i WG511v2.inf
installing wg511v2 ...
couldn't open WG511v2.inf: No such file or directory at /usr/sbin/ndiswrapper-1.9 line 181.
pckong@pckong-laptop:~$
----------------------------------------------------------------------------------------
:confused:

[wieman01]

Hi,

When I try to install window driver with ndiswrapper, it said no such a file in the directory. i am sure the spelling is right. What would the problem be?

-----------------------------------------------------------------------------------------
pckong@pckong-laptop:~$ sudo ndiswrapper -i WG511v2.inf
installing wg511v2 ...
couldn't open WG511v2.inf: No such file or directory at /usr/sbin/ndiswrapper-1.9 line 181.
pckong@pckong-laptop:~$
----------------------------------------------------------------------------------------
:confused:
Well, what files are in the directory?
cd <your directory>
ls -l

[wieman01]

Thanks for the How-to; I´ve made my rt2500 chipset based card work with ndiswrapper and Windows driver with the router channel set on 13 (with the driver that comes with Gutsy it works out of the box but only between channels 1 to 11, and I needed to set 13 because it´s the only channel where I can watch fine the movies in my PC in my Kiis dp-600).

The problem is the signal quality: it´s only 30% and previously was more than 70%. ¿Do you know a way to improve it?
I don't know... Sorry, mate.

[pckong]

Hi Wieman,

I reinstall Ubuntu and follow the steps again, i got the LED in the network card blink! It works eventually.

But what happen before is quite weir, when i checked ndiswrapper installation with:
CODE:
ndiswrapper -l
OUTPUT:
ndiswrapper-1.50: invalid driver!
wg511v2: invalid driver!

Then I try to delete the driver and then reinstall it again,
CODE:
ndiswrapper -r wg511v2
OUTPUT:
couldn't delete /etc/ndiswrapper/wg511v2: Inappropriate ioctl for device

but thanks, finally it works!

[sherrife]

-----------------------------------------------------------------------------------------
pckong@pckong-laptop:~$ sudo ndiswrapper -i bcmwl5.inf
installing bcmwl5.inf...
couldn't open bcmwl5.inf: No such file or directory at /usr/sbin/ndiswrapper-1.9 line 181.
pckong@pckong-laptop:~$
----------------------------------------------------------------------------------------

I've got this problem as well, anyone have any ideas? I'm a total newbie and it shows methinks :) I've tried looking at line 181 in the .inf file but i have no idea how to interpret programming language.

[Matteran]

okay, so everything seems to be setup correctly.

with ndiswrapper -l I get:

rt61 : driver installed
device (1814:0301) present (alternate driver: rt61pci)


and when i go into the network manager it shows the wireless connection in roaming mode. However, there doesn't seem to be anyway for me to get a list of access points or anything.

It's probably something simple, and may have already been answered, but I haven't been able to figure it out. Thanks!

[edit] NEVERMIND GUYS, I FIGURED IT OUT, THANKS!

[sherrife]

Could you explain it mate?

I'm still struggling to detect my wireless network

[wieman01]

Could you explain it mate?

I'm still struggling to detect my wireless network
I am sorry, I must have overlooked your post.

Actually, I have no clue what is going on. Do you find your adapter on the list of compatible devices found here:

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

[sherrife]

Yea, I've got it installed and everything, shows up on iwconfig and ifconfig, but just doesn't detect any wireless networks.

[wieman01]

Yea, I've got it installed and everything, shows up on iwconfig and ifconfig, but just doesn't detect any wireless networks.
And you did blacklist the native driver/module?

[prplhazed]

Hello all
I installed ubuntu for the first time on my new computer build and everything was great except for wireless
after reading and googling and reading and googling, this seems to be the thread that is most helpful for my problem

I have a rt2500usb device, and i tried to do the command line stuff that this thread says to but it didnt work
before i could see wireless networks but not connect
now ubuntu doesnt seem to recognize that i have wireless and only offers wired networking

any help would be greatly apreciated, ubuntu's pretty great other than this (its kinda big though)

[wieman01]

Hello all
I installed ubuntu for the first time on my new computer build and everything was great except for wireless
after reading and googling and reading and googling, this seems to be the thread that is most helpful for my problem

I have a rt2500usb device, and i tried to do the command line stuff that this thread says to but it didnt work
before i could see wireless networks but not connect
now ubuntu doesnt seem to recognize that i have wireless and only offers wired networking

any help would be greatly apreciated, ubuntu's pretty great other than this (its kinda big though)
Ok, have you done all steps in the tutorial?

Please post the results of:
sudo ndiswrapper -l
sudo iwlist scan
sudo lshw -C network