iB::Topic::DSL 3.3 and Linksys Wireless WPC54GS ver.2

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » Networking » DSL 3.3 and Linksys Wireless WPC54GS ver.2

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (2) </ [1] 2 >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: DSL 3.3 and Linksys Wireless WPC54GS ver.2

< Next Oldest | Next Newest >

GDSLC

Group: Members
Posts: 8
Joined: Aug. 2007

Posted: Sep. 03 2007,21:55

Hi, I'm new to DSL and so far loving it after bouncinging WinXP from my Dell Inspiron 1200. Everything seems to work except my wireless card. I would greatly appreciate any help and update this topic dilligently for others.

Config: Dell Inspiron 1200 with Cisco Linksys Wireless-G 2.4 GHz 802.11g Notebook Adapter with Speed Booster Model WPC54GS ver.2.

The card has one green light on and was working fine with Windows. When I access 'DSLpanel' and click 'Wlanconfig' I get a message that reads 'No wireless network card found.'.

I went to the DSL wiki which linked me to ndiswrapper.sourceforge.net where I found:

1. Card: Linksys WPC54GS v2 SpeedBooster, 54mbps/125mbps – http://www.linksys.com/servlet....Wrapper

* Chipset: Broadcom BCM4318 Airforce One 54g 802.11g Wireless LAN Controller (rev 02)
* pciid: 14e4:4318 (rev 02)
* Driver: Linksys Driver CD: /mnt/cdrom0/Driver/NT/LSBCMNDS.inf, bcmwl5.sys, LSBCMNDS.cat
* Other: Kernel: 2.6.15-1-586tsc, Ndiswrapper: 1.5-1 via Debian Etch, wpasupplicant: 0.4.9-1. Works fine, per WPA . Reports speed up to 125Mb/s.

I downloaded the zip but I can't find any instructions anywhere on how to utilize the contents of the zip file with DSL.

I'm not sophisticated with PCs and could really use a few step by steps.

Thanks! Gary

^thehatsrule^ Offline

Group: Members
Posts: 3275
Joined: July 2006

Posted: Sep. 04 2007,00:23

To get the contents of the zip file, open a terminal and use `unzip <filename>`
That should get you everything in it, though I think ndiswrapper only needs the .inf and .sys files.

GDSLC

Group: Members
Posts: 8
Joined: Aug. 2007

Posted: Sep. 05 2007,01:01

Hi and thanks for the reply. After unzipping I see a directory structure that looks like this:

home/dsl/WPC54GS Setup Wizard 2.1/Driver/9X and
home/dsl/WPC54GS Setup Wizard 2.1/Driver/NT

Both directories have 3 files: LSBCMNDS.cat, LSBCMNDS.inf, and bcmw15.sys

but I don't know which to use, I don't want to pick the wrong ones and then have trouble trying to uninstall them.

Also, I don't understand how to use NDISWRAPPER. After choosing it from DSLpanel, it displays 4 fields:

Inf file - I assume I put the path to one of the inf files listed above?
device - it already has the value 'wlan0' pre-filled
sid - is empty (is this the name of my router?)
wep - is empty

GDSLC

jpeters

Group: Members
Posts: 804
Joined: April 2006

Posted: Sep. 05 2007,01:21

Quote (GDSLC @ Sep. 04 2007,21:01)

Both directories have 3 files: LSBCMNDS.cat, LSBCMNDS.inf, and bcmw15.sys

but I don't know which to use, I don't want to pick the wrong ones and then have trouble trying to uninstall them.

Also, I don't understand how to use NDISWRAPPER. After choosing it from DSLpanel, it displays 4 fields:

Inf file - I assume I put the path to one of the inf files listed above?
device - it already has the value 'wlan0' pre-filled
sid - is empty (is this the name of my router?)
wep - is empty

GDSLC

I'm guessing the windows/9x drivers should work. Paste them into home/dsl and direct ndiswrapper to /home/dsl/LSBMMNDS.inf (you can rename it to "netcard" so that the default name works). Check what your SSID is for your router...it probably defaults to "linksys."

Run "ifconfig" in aterm to check what interface to type in. It's usually eth0 or ath0. If you haven't set up WEP, don't put in anything. The SSID and WEP setting are usually found by typing 192.168.1.1 into your browser. The default user is "admin", with no password.

roberts

Group: Members
Posts: 4983
Joined: Oct. 2003

Posted: Sep. 05 2007,01:23

Typically the .inf and .sys files need to be in the same directory.
If you wish to manually issue commands and step through the process you can.

Open a xterm as root
cd into the directory containing the .inf and .sys
# ndiswrapper -i LSBCMNDS.inf

Then check by using this command

# ndiswrapper -l

Should say hardware

# modprobe nsidwrapper

Next check to see if a wireless ethernet device has been created by using

# iwconfig

Hopefully you will see an unconfigured device, likely wlan0

If your router broadcasts and is open, no wep, you can try

# pump -i wlan0

If you are using wep then you can use instead

# iwconfig wlan0 essid name-of-your-router key 99:99:99:99

Where 99:99:... is your wep entered as colon separated pairs.
Then finally

# pump -i wlan0

There could be many reasons for failure, like irq conflicts, bus assignments etc.

But by steppping through the process you can see how far you can get.

HTH

9 replies since Sep. 03 2007,21:55

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (2) </ [1] 2 >/

Damn Small Linux Board » Damn Small Linux » Networking » DSL 3.3 and Linksys Wireless WPC54GS ver.2