Linksys WPC54g

[brdweb]

I have sucessfully hooked up to my home 54G network with WEP using my Linksys WPC54G pcimia card. I went to the linksys site, downloaded the latest windows driver for the card, and installed it using ndiswrapper. Took a little bit of trial and error plus checking the ndiswrapper site to get my settings correct but now I have a full strength connection.

[ramzez]

can you write step by step guide, please?

cheers.

[danpre]

Yeah - I have the same PCMCIA card - fighting with it for a few weeks now - a can't get it working

Any chances for help from you?

DANIeL

Originally Posted by brdweb I have sucessfully hooked up to my home 54G network with WEP using my Linksys WPC54G pcimia card. I went to the linksys site, downloaded the latest windows driver for the card, and installed it using ndiswrapper. Took a little bit of trial and error plus checking the ndiswrapper site to get my settings correct but now I have a full strength connection.

[ramzez]

actually it is very simple

install ndiswrapper from synaptic package manager.

then download ftp://ftp.linksys.com/pub/network/wp...ility_v2.0.zip

unzip the downloaded zipfile, find the correct .inf (lsbcmnds.inf in my case) file and run
sudo ndiswrapper -i lsbcmnds.inf

load the module and make it reload on reboot:
modprobe ndiswrapper
echo ndiswrapper >> /etc/modules

in gnome, goto networking and put your settings.

hope it helps.

[danpre]

ramirez:

thx

but it is too late now

I was plaing around with linuxant driverloader it was working very fine for almoust one mounth so I have both a license - I spent 20 bucks

well - good thing about it - 20 bucks for a company working for LINUX

thanks anyway


DANIeL

Originally Posted by ramzez actually it is very simple install ndiswrapper from synaptic package manager. then download ftp://ftp.linksys.com/pub/network/wp...ility_v2.0.zip unzip the downloaded zipfile, find the correct .inf (lsbcmnds.inf in my case) file and run sudo ndiswrapper -i lsbcmnds.inf load the module and make it reload on reboot: modprobe ndiswrapper echo ndiswrapper >> /etc/modules in gnome, goto networking and put your settings. hope it helps.

[Joshua]

It took me quite a while to figure out how to get this working, so I wanted to post something about it and possibly save someone a little time.

I've got an old Gateway Solo 5100 and I bought the WPC54G. My home network is run on the WRT54G. My solution might not apply to normal Ubuntu users because of my installation method, so I'll describe it.

My CD-ROM, apparently, doesn't like normal sized CDs. When I try to install Ubuntu it gets hung up towards the end while installing the system base packages. It does fine, however, with the Debian netinstall CDs on the smaller 80mm disks. So I installed a minimal Debian system with the netinstall CD and then changed the APT repositories to the Ubuntu Hoary ones. Then, I upgraded (it took a little investigation to complete dependencies and stuff). Once that was done, I installed the linux-686 packages so that I would have the most recent Ubuntu Kernel.

Then, I followed the normal instructions for installing ndiswrapper and the windows drivers. Ndiswrapper is in the 2.6.10 Kernel so that was easy with "modprobe ndiswrapper".

Anyway, once all that was done, I couldn't get the card to work. iwlist wlan0 scan said that it couldn't pick anything up. ifup wlan0 said it couldn't get a dhcp response. After loads of trying different drivers and reloading modules, etc. I looked at the dmesg output and saw that there was some module called acx_pci that seemd to be trying to operate my card. There was even a little warning that my card used proprietary drivers and that acx_pci might not work. So I rmmod ndiswrapper, rmmod acx_pci, modprobe ndiswrapper. BINGO! ifup wlan0 and everything is hunky-dory. Now I need to figure out how to keep acx_pci from loading on boot and how to get ndiswrapper to load on boot. If anyone knows, please let me know. I've tried ndiswrapper -m. It says that it's good, but when I boot - no ndiswrapper...

[YorYor]

Hi all, recently got myself stuck to Ubuntu Hoary after I sorta trialed 10+ distributions over a week. One of the immediate hurdles was to get this WPC54G working, and after hours of searching, I managed to find another solution which worked for me (http://tiefighter.et.tudelft.nl/~arthur/wpc54g/).

In summary,

1. Use Synaptic to get ndiswrapper-tools
2. Get the windows drivers, and copy the .sys and .inf to somewhere (say /home/<yourusername>/Linksys/)
3. Open terminal, and enter the following commands:
3a. cd Linksys
3b. sudo ndiswrapper -i <name>.inf (mine was lsb something, but I just renamed it to linksys.inf as it makes it easier). The screen should show something about Forcing parameter RadioState|0 to RadioState|1... mine had 4 lines.
3c. cd /etc/ndiswrapper/
3d. Edit all the .conf files, look for the line RadioState|1 and change it to RadioState|0 (to do this, I had to type sudo gedit and open the files from the GUI... gedit didn't quite like opening files with \: from the command line, not sure why) I'm not sure if just changing one or two files will work, but I just changed all 4.
3e. sudo modprobe ndiswrapper
3f. (optional) sudo echo ndiswrapper >> /etc/modules
3g. sudo iwlist wlan0 scan (look for your access point in the list)
3h. sudo iwconfig wlan0 channel <X> essid <ESSID> mode Managed (the X and ESSID should come from the iwlist)
3i. sudo ifup wlan0

I think that should do it really. Hope that will be useful for someone else.

[epb613]

Originally Posted by YorYor Hi all, recently got myself stuck to Ubuntu Hoary after I sorta trialed 10+ distributions over a week. One of the immediate hurdles was to get this WPC54G working, and after hours of searching, I managed to find another solution which worked for me (http://tiefighter.et.tudelft.nl/~arthur/wpc54g/). In summary, 1. Use Synaptic to get ndiswrapper-tools 2. Get the windows drivers, and copy the .sys and .inf to somewhere (say /home/<yourusername>/Linksys/) 3. Open terminal, and enter the following commands: 3a. cd Linksys 3b. sudo ndiswrapper -i <name>.inf (mine was lsb something, but I just renamed it to linksys.inf as it makes it easier). The screen should show something about Forcing parameter RadioState|0 to RadioState|1... mine had 4 lines. 3c. cd /etc/ndiswrapper/ 3d. Edit all the .conf files, look for the line RadioState|1 and change it to RadioState|0 (to do this, I had to type sudo gedit and open the files from the GUI... gedit didn't quite like opening files with \: from the command line, not sure why) I'm not sure if just changing one or two files will work, but I just changed all 4. 3e. sudo modprobe ndiswrapper 3f. (optional) sudo echo ndiswrapper >> /etc/modules 3g. sudo iwlist wlan0 scan (look for your access point in the list) 3h. sudo iwconfig wlan0 channel <X> essid <ESSID> mode Managed (the X and ESSID should come from the iwlist) 3i. sudo ifup wlan0 I think that should do it really. Hope that will be useful for someone else.

Wow thanks so much - this fiixed my wifi after it not working for months!

[jon_hill987]

Originally Posted by YorYor http://tiefighter.et.tudelft.nl/~arthur/wpc54g/).

I get a 404 from that, i'll try your summary though and see if it works. I havn't got the same wifi card as you but i'm ready to try anything....

[Dillius]

I'm having an infinite ammount of trouble with this card. Using the WPC54G v.2. I've been trying a number of drivers and such. I've found that there are 2 .inf files that have differet effects.

"lsbcmnds.inf" causes no errors, but ndiswrapper -l only shows driver present, and says nothing about the hardware

"lstinds.inf" shows in ndiswrapper as both driver present and hardware present, but whenever i try to add ndiswrapper with modprobe, I have the following error:

ndiswrapper version 1.0rc2 loaded (preempt=yes,smp=no)
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:02:00.0 to 64
ndiswrapper (ndis_init_one_pci:95): Windows driver couldn't initialize the device (C0000001)
lstinds: probe of 0000:02:00.0 failed with error -22
ndiswrapper: driver lstinds (Linksys,03/10/2004,6.0.0.18 ) added

Also, the Device Manager keeps listing this card as some Texas Instruments ACX 100 card.... I had to blacklist some other drivers so they wouldnt load due to hotplug, but I can't be sure that worked correctly(The drivers were acx100 and acx_pci).