how to setup wireless on fedora 11 - Page 2

picxelplay · #16 2009-10-03, 04:00 PM CDT

what is the path to my desktop?
/home/USER/desktop --that didnt work

**stoat** · #17 2009-10-03, 05:39 PM CDT

Quote:

Originally Posted by picxelplay

what is the path to my desktop?
/home/USER/desktop --that didnt work

Try /home/USER/Desktop.

picxelplay · #18 2009-10-04, 01:44 AM CDT

Thanks stoat.
When I type:
ndiswrapper -i /home/myusername/Desktop/rt2500.inf

I get this:

Code:

installing rt2500 ...
couldn't find models section "Ralink" -
installation may be incomplete
couldn't find models section "ASUS" -
installation may be incomplete
couldn't find models section "Delta" -
installation may be incomplete
couldn't find models section "ZINWELL" -
installation may be incomplete
couldn't find models section "AMIT" -
installation may be incomplete
couldn't find models section "CASTLENET" -
installation may be incomplete
couldn't find models section "ACCTON" -
installation may be incomplete
couldn't find models section "Edimax" -
installation may be incomplete
couldn't find models section "Hawking" -
installation may be incomplete
couldn't find models section "Surecom" -
installation may be incomplete
couldn't find models section "Gigabyte" -
installation may be incomplete
couldn't find models section "Billionton" -
installation may be incomplete
couldn't find models section "Belkin" -
installation may be incomplete
couldn't find models section "VTech" -
installation may be incomplete
couldn't find models section "Sitecom" -
installation may be incomplete
couldn't find models section "Siemens" -
installation may be incomplete

John the train · #19 2009-10-04, 02:27 AM CDT

@picxelplay
Have you updated the install? From memory there have been several kernel updates since F11 launched, we're now in the 2.6.30 series, so an update may bring in the sections you seem to be missing. Certainly the RT61 driver in 2.6.30.x works nicely with my Edimax cardbus adaptor.

bbfuller · #20 2009-10-04, 03:15 AM CDT

Hello picxelplay

I think those error messages mean that the 'inf' file you are using is capable of installing for more than one manufacturers card.

I suggest that you go on now and try the 'ndiswrapper -l' to see if you have got a driver installed.

If you haven't then there ia a site that lists driver that are known to work with ndiswrapper and we can have a look there to see if there is a better one for the rt2500.

I agree with 'John the train' by the way, the rt61 driver works well here for me as well. It's just that the driver you need -rt2500 - hasn't worked for my rt2500 since probably as far back as F8.

picxelplay · #21 2009-10-04, 09:54 AM CDT

This is the version I am running:
2.6.30.8-64.fc11.i586

I typed ndiswrapper -l, and got:
rt2500 : invalid driver!

So, I guess it didn't work, lol. Where to next?

bbfuller · #22 2009-10-04, 10:08 AM CDT

Hello picxelplay

A quick look on the archived ndiswrapper site here:

http://web.archive.org/web/200801131...id,33/id,list/

revealed this driver:

http://www.ralinktech.com/drivers/Wi...or_Win2003.zip

that is reckoned to work.

If that's not a current link we'll have to look for others.

picxelplay · #23 2009-10-04, 10:19 AM CDT

That link was dead, but I searched for that file and found a mirror.
Downloaded it, this is what I got:

Code:

[root@xxx ~]# ndiswrapper -i /home/xxx/Desktop/Rt2500.inf
driver rt2500 is already installed
You have new mail in /var/spool/mail/root
[root@xxx ~]# ndiswrapper -l
rt2500 : invalid driver!

bbfuller · #24 2009-10-04, 11:46 AM CDT

Hello picxelplay

It looks like something got installed from your previous driver file that is enough to convince ndiswrapper not to install the new.

Try:

Code:

ndiswrapper -e rt2500

that should erase the previous driver. Then give it another go with the new one.

picxelplay · #25 2009-10-04, 12:38 PM CDT

Ok, this is what I got. I was really crossing my fingers this time

Code:

[root@xxx ~]# ndiswrapper -e rt2500
You have new mail in /var/spool/mail/root
[root@xxx ~]# ndiswrapper -i /home/xxx/Desktop/Rt2500.inf
couldn't open /home/xxx/Desktop/Rt2500.inf: No such file or directory at /usr/sbin/ndiswrapper line 219.

bbfuller · #26 2009-10-04, 12:58 PM CDT

Hello picxelplay

I probably wouldn't have had the contents of the driver file spread all over the desktop, but never mind.

If you do, in the terminal:

Code:

cd /home/xxx/Desktop

to actually move into that folder, does:

Code:

ls

list an 'Rt2500.inf' file.

Remember that file names are case sensitive in Linux.

picxelplay · #27 2009-10-04, 01:43 PM CDT

Now:

Code:

[root@xxx Desktop]# ndiswrapper -i /home/xxx/Desktop/Rt2500.INF
installing rt2500 ...
couldn't find models section "Ralink" -
installation may be incomplete
couldn't find models section "ASUS" -
installation may be incomplete
couldn't find models section "Delta" -
installation may be incomplete
couldn't find models section "ZINWELL" -
installation may be incomplete
couldn't find models section "AMIT" -
installation may be incomplete
couldn't find models section "CASTLENET" -
installation may be incomplete
couldn't find models section "ACCTON" -
installation may be incomplete
couldn't find models section "Edimax" -
installation may be incomplete
couldn't find models section "Hawking" -
installation may be incomplete
couldn't find models section "Surecom" -
installation may be incomplete
couldn't find models section "Gigabyte" -
installation may be incomplete
couldn't find models section "Billionton" -
installation may be incomplete
couldn't find models section "Belkin" -
installation may be incomplete
couldn't find models section "VTech" -
installation may be incomplete
[root@xxx Desktop]# ndiswrapper -l
rt2500 : invalid driver!

bbfuller · #28 2009-10-04, 01:47 PM CDT

Hello picxelplay

Very odd, it's doing the same as the other driver.

Could you list the rest of the contents of your desktop, there may be another file there that gives a clue.

picxelplay · #29 2009-10-04, 05:01 PM CDT

Sure.

Computer
xxx's Home
Trash
RT2500V3.0.1.0_for_Win2003.zip (the .zip folder of the driver)
Rt2500.INF (the .inf file we just used)
wireless key (just a text file with my wpa shard key in it)

bbfuller · #30 2009-10-04, 05:05 PM CDT

Hello picxelplay

That may be the reason for the failure all along. You need more than just the inf file for ndiswrapper to act upon. At the very least, you need the sys file that corresponds to the inf file.

Most people would put the zip file in a folder, unzip it, and point ndiswrapper at the inf file surrounded by the rest of the driver files. That way ndiswrapper can find all of the material it needs.