1 |
sorry, i accidentally sent that prematurely. |
2 |
|
3 |
as i was saying, the init scripts fail to set the encryption key and connect |
4 |
to my network. using iwconfig otoh i am able to set the essid, enc key and |
5 |
etc and connect to the AP of choice. |
6 |
|
7 |
worse, after running the init script the card becomes completely unable to |
8 |
connect--using iwconfig methods after using the init scripts has no effect, |
9 |
and even unloading the module , reloading it, and retsarting the |
10 |
driverloader init scripts does not remedy the situation. |
11 |
|
12 |
my question is can anyone tell me what the init scripts are doing in |
13 |
addition to what i would like them to do (execute the commands in |
14 |
/etc/conf.d/wireless) that may be clobbering my driver/card? any idea why |
15 |
the same commands work just fine usinmg iwconfig?? |
16 |
|
17 |
thanks in advance |
18 |
|
19 |
On 4/30/06, Leigh Stewart <agrodellic@×××××.com> wrote: |
20 |
> |
21 |
> Hi All, |
22 |
> I'm having a bit of trouble trying to get the Gentoo net init scripts to |
23 |
> play nice with the linuxant driverloader ndiswrapper. |
24 |
> |
25 |
> First, yes I have tried (read: struggled) with ndiswrapper a fair bit with |
26 |
> no luck...I can only get my card to connect to an unencrypted channel with |
27 |
> ndiswrapper, and am not able to set any parameters, including the encryption |
28 |
> key. driverloader works however, for the most part... |
29 |
> |
30 |
> So anyway here are some specs first: |
31 |
> card: Linksys WPC54G v4 |
32 |
> driver: wlipnds |
33 |
> relevant lspci line: 03:00.0 Ethernet controller: Linksys, A Division of |
34 |
> Cisco Systems [AirConn] INPROCOMM IPN 2220 Wireless LAN Adapter (rev 01) |
35 |
> driverloader version: 2.33 |
36 |
> |
37 |
> now my problem is that when I try to start the interface created by the |
38 |
> installed driverloader module using /etc/init.d/eth1... , it fails |
39 |
> miserably. by fails miserably i mean it is unable to connect to my |
40 |
> |
41 |
> |