Hello all - my first tech thread . . .

Mandriva 2007.0 distro, new installation.

Trying to connect working Belkin F5D7050 usb dongle to home wireless.
Specs on dongle and proposed linux connection configs:

http://opensource.bureau-cornavin.com/belkin/index.html

I tried an install through the Mandrake gui, which (not surprisingly) didn't work. As alternative I selected the ndiswrapper option, and so far it's been fairly smooth. I installed ndiswrapper, got the Win drivers from the vendor cd, installed the "wireless tools" utility. No problems to that point:

---confirmed valid ndiswrapper and driver installation:

[root@localhost martin]# ndiswrapper -l
rt73 driver installed, hardware present

---verified presence on usb port:

[root@localhost martin]# lsusb
Bus 001 Device 003: ID 050d:705a Belkin Components

---Problem - see iwconfig query below, re. "rausb0 RT2500USB." System is pulling in an incorrect Win driver that's also identified with Belkin 70xx dongles. First of all, I don't know where this driver is coming from. It may be a leftover from my attempt to configure the card through the Mandriva MCC. But, it's obviously blocking the correct rt73 ndiswrapper driver from binding to the dongle.

[root@localhost martin]# iwconfig
lo no wireless extensions.

sit0 no wireless extensions.

rausb0 RT2500USB WLAN ESSID:""
Mode:Managed Frequency=2.412 GHz
RTS thrff Fragment thrff
Encryption keyff
Link Quality=0/100 Signal level:-120 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

In any case, I need to get the usb config'd to bind to the rt73.inf driver that's configured correctly in ndiswrapper, and override whatever process is calling and using the rt2500 driver. I'd prefer a process that doesn't require running a console script every time I want to insert the dongle.

I found a Ubuntu forum thread that posed exactly the same problem on exactly the same device, and a working solution. See:

http://ubuntuforums.org/archive/index.php/t-333166.html

I understand the problem he describes, since it's mine exactly. Happily he figured out a solution. However, I'm new enough to this process that I can't interpret the user's fix, or how to apply it in my environment. A boot-time blacklist of that driver would seem to be the right direction, but I don't know how to configure it, or if that will even fix the problem. I assume there is a runtime configuration process activated (as usual with usb) just as the usb device is inserted. I have a basic grasp of linux commands, but I don't work extensively in a console. A bit of hand-holding may be in order.

Thanks!

hmmm well I'll try at some hand holding.

in a terminal, type
and post that,
and post that. from there, we can see if you need to remove the old drivers still. if you do, and then it works, then we'll go ahead and fix it so it won't load again.
:-D

hmmm well I'll try at some hand holding.

Thanks! Posted results - here ye be -

in a terminal, type
lsmod | grep rt
and post that

[root@localhost martin]# lsmod | grep rt
gameport 11912 1 snd_cmipci
snd_mpu401_uart 7616 1 snd_cmipci
snd_rawmidi 19936 1 snd_mpu401_uart
snd 46500 12 snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_cmipci,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,sn d_mpu401_uart,snd_rawmidi,snd_seq_device
agpgart 27240 3 drm,intel_agp
rt2570 189248 0
usbcore 113472 4 usblp,rt2570,uhci_hcd


lsmod | grep usb
and post that.


[root@localhost martin]# lsmod | grep usb
usblp 12352 0
usbcore 113472 4 usblp,rt2570,uhci_hcd


from there, we can see if you need to remove the old drivers still. if you do, and then it works, then we'll go ahead and fix it so it won't load again.
:-D

ok, it looks like the kernel driver is still loaded. I use ndiswrapper for my wireless card, and if the original kernel driver is still loaded, it can cause problems. try
this step may or may not be necessary, but go ahead and unplug the adapter, and plug it back in (it is a usb right? :-D )
see what happens with all of that

Success! Thanks for your help.
I had a sense it was just a few keystrokes away.

For the benefit of anyone else who may come across this thread:

Per your suggestion, entered:
Result not quite what I expected:
Interesting. Why can't ndiswrapper be removed from the kernel for a full modprobe reset?

Undeterred, entered:
. . . and the happy green light flickered away.

So - this is the 95% of way there.

Now, how to make it stick so I don't need to repeat this little console exercise every time I want to use the dongle?

Any reboot or removing the device causes a reversion back to the original problem configuration, complete with the rt2570 driver. On a shutdown sequence, the kernel shuts down completely without a failure message, but the restart sequence gives a "failure" message at the attempt to restore the wlan configuration: "device does not appear to be present." This happens whether the device is in the usb port or not.

One of several post-success queries:
I immediately enter:
and all is fixed.

Does this have to do with the failed rmmod?
How can I permanently get rid of the persistent rt2570 driver override and force the ndiswrapper config that works?

no, actually it has nothing to do with the failed rmmod. whats happening is that the kernel is loading the rt2570 module everytime, because it thinks its the right one. we can prevent that e from happening.
once we're in there, add these lines somewhere at the bottom
and save the file. this essentially tells the kernel not to ever load that module again, no matter what it WANTS to do. we may have to go into the mandriva control center to continue with the setup, but I'm not sure yet. go ahead an reboot the computer, and see if it works upon system start. if it doesn't, then at the terminal do
and that will at least turn the thing back on for that boot. let me know if you have to do that. If you do, then we'll do another step from inside the MCC, so *hopefully* you'll never have to type at the command prompt to get it working.
As a side note, the reason that you had a failed rmmod earlier is because you told the kernel to take out a module that wasn't there. I told you to issue that command simply because I didn't know if it was there or not. Sometimes, even if it (ndiswrapper) is loaded along with the incorrect driver, simply removing the incorrect one will not solve the issue. It just behaves screwily. so, i had you take it out (if it was there :-D ), and then re-add it, which usually solves problems.
anyways, get back to me on whether or not you have to do a modprobe ndiswrapper after your next boot.
:-D
--drew

Thanks. This all makes sense. I'll try this evening and let you know what I come up with. One minor question re your response -
I assume this command just calls kate as the Kubuntu-default text editor. I further assume that I can substitute whatever text editor I normally use for kate in that command. If not, let me know. I'm not sure I've ever called a text editor from the Command Line interface.

yes that is what its doing, however you need to use JUST a text editor. Openoffice, abiword and the like might add extra stuff to the file that would throw the kernel off when it is parsing the file (formatting characters, font info and the like). That's why i suggested kate. if kate doesn't work, you can try the time-tested vi editor. just replace kate with vi. that being said, vi would be a challenge because it is a modal text editor. to actually be able to enter text, you have to press the "a" key (which stands for append), and type. to save your work, you have to press, in this order, "Esc", ":", "w", "q", "Enter".
but, only use vi if kate doesn't work! you'll save yourself a headache and a half :-D
Interesting you mentioned Kubuntu... your profile said mandriva! :-D

best of luck!
--drew

Don't mean to go off-topic, but you know your stuff and appear very willing to share your knowledge.

Re: text editor
Yup - I learned that the hard way (long story)

Yes, I currently use Mandriva. I only know about the tie between Kate and Kubuntu from reasearching the elements of the command line per your post (i.e. I never heard of Kate before today)

I assume I could install Kate, but I would rather use something that's already there. I use KDE, so I assume that
in my environment would get me to the same place as
If that's the case you don't need to respond. But, if I'd have problems using Kedit, please let me know.

you know what, absolutely kedit would work. I was under the impression that kate was the default editor. whoops! :-) I'm a bit KDE-phobic, so I don't always know the default programs associated with it anymore. Now that I think about it, the only time I used KDE for any significant length of time was when I ran kubuntu. Oh well. kedit's fine.
Good Luck!
--Drew

A bit closer. I did use Kate, by the way. It was already installed.

Blacklisting the rt2570 appears appears to have worked. After a restart with the unit in the port, I queried usb and rt to see if the offending driver was removed.

Nothing showed up:
I still receive the "cannot initiate wlan - device not present" message on each boot sequence, so the device connection to the rt73 driver does not survive a disconnect from the usb port or a system restart.

But, I could at least skip the
Just entering activated the device.

You mentioned a further configuation in the Mandrake Control Center if the rt73 driver binding doesn't survive a shutdown or removing the device. What is the next step?

Thanks again!

Ok, we can fix this I belive. however, I'm gonna need to install a version of mandriva i have to five you some accurate advice from this point on. So, tonight I'll finish that up and I'll post asap.
--drew

Ok, here we go. (QEMU is a life-saver)
Section 1
1) Open the mandriva control center: Menu -> System -> Configuration -> Configure your Computer
2) Click the network tab
3) Click "Delete a network interface"
4) In the dropdown box there, see if there is a listing for the wireless device. If so, select it and continue. Otherwise, skip to Section 2.
5) Click Next
6) Click Finish

Section 2
1) Click "Set up a new network interface"
2) Select Wireless from the list and click Next
3) DON'T select Ndiswrapper from the options. As I am running in virtualization, advice is more fuzzy from here on out.
4) The next screen should have an option for "Module" . enter "ndiswrapper" into the box.
5) Continue on with any parameters you may want to add, such as essid and encryption.
6) you can probably figure out how to finish this setup wizard :-D

I'd give even more handholding advice :-D, but I am running the distro in virtualization. So, I can't actually add a network card, as the QEMU emulator doesn't supply one. :-(
However, I've set up a ndiswrapper device through mandriva before. You might think, well why don't we just use the tool from the start? It gives an option for ndiswrapper! \
1) I forgot
2) It didn't work for me anyways.

As long as you put ndiswrapper in the "Module" section of the wizard, you should be fine.

--Drew

Great!

Unless something urgent comes up I should be able to try this this evening.

Re:No problem. See my first post:
Been there. Done that.

Considering the mountains of support-forum threads on wireless Linux I saw prior to trying this, I really didn't expect something as simple as a gui configuration to work . . .

Perfect!

Excellent instructions! I am writing this from my fully wireless-enabled linux box.

Thank you for your able hand-holding and clear instructions. I hope others with the same problem can google into this thread and get their problem solved as well.

Thanks again for your work "above and beyond" for me.

- SM