sorry, i accidentally sent that prematurely.

as i was saying, the init scripts fail to set the encryption key and connect
to my network.  using iwconfig otoh i am able to set the essid, enc key and
etc and connect to the AP of choice.

worse, after running the init script the card becomes completely  unable to
connect--using iwconfig methods after using the init scripts has no effect,
and even unloading the module , reloading it, and retsarting the
driverloader init scripts does not remedy the situation.

my question is can  anyone tell me what the init scripts are doing in
addition to what i would like them to do (execute the commands in
/etc/conf.d/wireless) that may be clobbering my driver/card? any idea why
the same commands work just fine usinmg iwconfig??

thanks in advance

On 4/30/06, Leigh Stewart <agrodellic@gmail.com> wrote:
>
> Hi All,
> I'm having a bit of trouble trying to get the Gentoo net init scripts to
> play nice with the linuxant driverloader ndiswrapper.
>
> First, yes I have tried (read: struggled) with ndiswrapper a fair bit with
> no luck...I can only get my card to connect to an unencrypted channel with
> ndiswrapper, and am not able to set any parameters, including the encryption
> key.  driverloader works however, for the most part...
>
> So anyway here are some specs first:
> card: Linksys WPC54G v4
> driver: wlipnds
> relevant lspci line: 03:00.0 Ethernet controller: Linksys, A Division of
> Cisco Systems [AirConn] INPROCOMM IPN 2220 Wireless LAN Adapter (rev 01)
> driverloader version: 2.33
>
> now my problem is that when I try to start the interface created by the
> installed driverloader module using /etc/init.d/eth1... , it fails
> miserably.  by fails miserably i mean it is unable to connect to my
>
>