I am officially retiring this thread.
You can make this card work by changing dapper's native acx module firmware using Kobalt's method instead of this howto. It integrates with network manager and there's not nearly as much CLI editing involved (just three lines). You can find well written directions for it here: http://www.ubuntuforums.org/showthre...ghlight=wpc54g
To make this card work in any distribution after Edgy, try this link: http://www.ubuntuforums.org/showthread.php?t=324148
I can no longer make the following method work to enable my wpc54g v2 card in Dapper.
Disclaimers:
======================================
This how to is specific to THIS card; however, it may be adapted to work on other cards. The chipset in question here is the Texas instruments ACX111 chipset. I have no experience with any other wireless cards other than the ones in my possession, so if you have a Linksys card but it does not have an ACX111 chipset, I will not likely be able to assist you. Furthermore, most cards containing this chipset seem to work "out of the box".
I have not tested, nor will I be able to test WEP as I am using a wireless HUB without encryption capabilities. Brickferd has tested and successfuly enabled encryption using this method. Directions appear at the end of this thread as well as in post number 23.
Also note, most of this has been pulled from an existing thread here: http://www.ubuntuforums.org/showthread.php?t=5645 so if what follows doesn't help you, you may find your answer there.
I have foccused on CLI interface instructions to allow this method to work in any of the winodow managers supported in the Ubuntu line (mine happened to be icewm).
======================================
First of all, you're going to need ndiswrapper installed:
This howto does not require the cvs version of ndiswrapper, so the one in the universe repos will be fine (note: If you already have the cvs version installed, I cannot garantee this method). Just make sure you get both the ndiswrapper, and the ndisgtk packages.
Just open synaptic, search for ndiswrapper and both packages should appear.
Next, you’re going to need the windows driver:
Create a directory in your home folder called linksys:
Code:
cd
mkdir linksys
cd linksys
Download the windows driver from Linksys:
Code:
wget ftp://ftp.linksys.com/pub/network/wpc54g_v2_driver_utility_v2.0.zip
Extract the archive:
Code:
unzip wpc54g_v2_driver_utility_v2.0.zip
(special thanks to yellow5 for the next step)
linux is case sensitive for file names, but windows is not, so there's a little file name snafu that we have to fix before we can move on.
- tnet1130.sys should be TNET1130.sys
- LSTINDS4.sys should be Lstinds4.sys
Code:
mv tnet1130.sys TNET1130.sys
mv LSTINDS4.sys Lstinds4.sys
Load the driver into ndiswrapper for the module:
Code:
sudo ndiswrapper -i lsbcmnds.inf
sudo ndiswrapper -i LSTINDS.INF
sudo modprobe ndiswrapper
With your WPC54g ver. 2 card in the PCMCIA slot, check to make sure ndiswrapper correctly loaded the card:
note: this is a lower case L, not an upper case i or the number one.
You should get output that looks something like this:
Code:
Installed drivers:
lsbcmnds driver installed
lstinds driver installed, hardware present
If not, you may need to go back and review some of the steps or take a look at the wiki here: https://help.ubuntu.com/community/Wi...ndiswrapper%29
Now we associate the module with the card:
At this point, my card still did not have a power light because Ubuntu is trying to load the acx_pci module to drive this card. But the acx_pci module won't drive the card (thanks to blazerte for this tip). There were other modules trying to load for this card too. You can remove them with sudo modprope -r modulename and then blacklisting them, but I wanted the ndiswrapper module to load automatically for this card. This can be done by making an entry in /etc/pcmcia/config.opts as follows:
First, you need to figure out what Ubuntu calls your card. Just look at the entry for your card in lspci:
and it should give an output similar to this:
Code:
0000:06:00.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface
The following step listed in grey is not needed (left here for my own reference)
#Next, you need to know the manfid:
#and the output should look similar to this:
Code:
Socket 0:
no product info available
Socket 1:
no product info available
manfid: 0xf7ff, 0xfe5b
Resume howto from here:
Now, using the above information we can edit pcmcia config with a new entry. Using your favorite editor (mine's nano) edit /etc/pcmcia/config.opts and add the following lines (adjusting yours so that it matches the output of lspci and cardctl ident from above)
Code:
card "Texas Instruments ACX 111 54Mbps Wireless Interface"
bind "ndiswrapper"
Add ndiswrapper to your modules file so that it will be included on boot up:
Code:
sudo echo ndiswrapper >> /etc/modules
Restart your network:
Code:
sudo /etc/init.d/networking restart
Your power light should come on (if not, try rebooting). Also check iwconfig and you should have wlan0 listed.
Finally, connecting to the internet:.
This card needs a scan before it can accept wireless settings. But you can't add wireless settings while the card is up, thus making it difficult to connect after entering the wireless settings becase the whole process is time sensitive. To get around this, I just splice the whole command together with && like so:
Code:
sudo iwlist wlan0 scan&& sudo iwconfig wlan0 channel 1 essid youressid mode Managed&& sudo ifup wlan0
If you don't already know what your network settings are, you can just scan (sudo iwlist wlan0 scan) first and then edit the above string to your settings.
At this point, your card should be connected, however, the link light will not come on. You can check ifconfig to verify that you have a dhcp lease.
Just a few additional notes:
Thanks to brickferd, for the following information on wep in post 23:
You should also be able to enable encryption by adding “key open XXXXXXXXXXXXXXXX”, where X is your key in hex format, to the end of this section: “sudo iwconfig wlan0 channel 1 essid youressid mode Managed”
Though you will not have to load the ndiswrapper module at every boot, you will have to issue the “sudo iwlist wlan0 ...” command at every boot. I included it in a startup script so it comes up “automatically”. Sloppy, but it works.
If you get an error that reads "Ignoring unknown interface wlan0=wlan0" you can fix it by doing the following:
(Breezy only) Edit /etc/network/run/ifstate to include the line wlan0=wlan0.
(Dapper and Breezy) Include iface wlan0 inet dhcp (or the appropriate static references) in /etc/network/interfaces.
Any problems, post 'em and I'll do what I can to help.
Bookmarks