[Ndiswrapper-general] Linksys WPC54g & Fedora Core 2

[Corey W. <co...@in...>]

Dear All,

I'm trying to get my Linksys WPC54g card working under Fedora Core 2.
The ndiswrapper package compiles and installs with no errors. The
Linksys drivers are successfully installed by ndiswrapper as well. The
problem occurs during the finalisation of the installation.

I can load the ndiswrapper kernel module with no errors reported.
However when I check dmesg the following to lines are associated with
the wlan0 interface. 

wlan0: ndiswrapper ethernet device 00:0c:41:2c:c3:20 using driver
bcmwl5.sys
wlan0: adding wep key 0 failed (C0010015)

When I try to configure the wlan0 to use a wep encryption key the
following error message is reported

# /sbin/iwconfig wlan0 key restricted s:mypassword
Error for wireless request "Set Encode" (8B2A) :
    SET failed on device wlan0 ; Invalid argument.

However the wlan0 device is recognised and I can use the network
configuration tool to configure the wlan0 device. The problem though is
that it is unable to use dhcp to get a valid IP from the access point.
I'm also unable to set the ESSID and make it stick. 

When I run iwconfig with no parameters the following is output. 

wlan0  IEEE 802.11g  ESSID:""  Nickname:"myhost"
       Mode:Managed  Frequency:2.437GHz  Access Point: FF:FF:FF:FF:FF:FF
       Bit Rate=54Mb/s   Tx-Power:17 dBm
       RTS thr=2347 B   Fragment thr=2346 B
       Encryption key:####-####-####-####-####   Security mode:open
       Power Management:off
       Link Quality:100/100  Signal level:-10 dBm  Noise level:-256 dBm
       Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
       Tx excessive retries:0  Invalid misc:0   Missed beacon:0

It would appear that the wep key has made it to the configuration but I
can't set the security mode to restricted. I believe the card is able to
contact the access point but is unable to communicate with it because
there is something going wrong with the wep encryption. 

What am I missing? This is a stock standard installation of Fedora,
could this be a 4K stacks issue?

With many thanks. 

-Corey