Laptops :: WPC54G v5 & ndiswrapper

I've been working on getting my Linksys WPC54G v5 wireless card working in my laptop with DSL. I have managed to get a NDIS driver installed, I THINK! Anyway, here's what I get:

root@box:/home/dsl#ndiswrapper -l
Installed ndis drivers:
lsmvnds hardware present

The I try the,
depmod -a

and I get the following errors,

depmod: *** Unresolved symbols in /lib/modules/2.4.26/kernel/drivers/usb/auerswald.o
depmod: *** Unresolved symbols in /lib/modules/2.4.26/kernel/drivers/usb/speedtch.o
depmod: *** Unresolved symbols in /lib/modules/2.4.26/kernel/net/bridge/bridge.o
depmod: *** Unresolved symbols in /lib/modules/2.4.26/kernel/net/sctp/sctp.o

I'm not sure what this is actually saying. I have a feeling it's telling me I need to update my kernel but I'm not positive.

Do I actually have a ndis driver installed?
Am I close to getting this card to work?
Do I need to update my kernel?

Can anyone help?

:cool:

I have a Linksys 54A and the only way I could get it to work is with Prism2.

Set the adapter as ath0. Dont know if this will help but if it can get an A card to work it should work with yours.

There is an ndiswrapper configuration utility in the DSLpanel ... though I commend you for setting things up manually.
Don't worry about those "*** Unresolved symbols" errors - they don't relate to the ndiswrapper module.

There is a thorough explanation of ndiswrapper usage here -
http://ndiswrapper.sourceforge.net/mediawi...._driver
... but here's a quick summary -

ndiswrapper -i /path/to/my/driver/mydriver.inf
depmod -a
modprobe ndiswrapper

iwconfig wlan0 essid MY_ESSID key 1234567890 mode managed
pump -i wlan0 # (for automatic IP)

Don't attempt to use the prism2 (linux-wlan-ng) drivers - these drivers are completely wrong for your Marvell chipset.

Thanks Tempestuos

Still haven't had any luck as of yet. I still get the

lsmvnds hardware present

message but when I do dmesg | grep ndiswrapper I get a line that says that the driver can't be started or something close to that.

I'm still trying!!

:cool:

Try using either the win9x *.inf....it that doesnt work try the NT/2000/XP *.inf

Brian
AwPhuch

Next Page...
original here.