1 |
On 20/11/09 Mick said: |
2 |
|
3 |
> Does your router know this? I'm not being funny, but I had run into a problem |
4 |
> sometime in the past where a change in the dhcpcd version caused the router to |
5 |
> not read the NIC MAC address correctly. That created a clash with the IP |
6 |
> address lease. |
7 |
|
8 |
If I configure it statically then it dhcpcd shouldn't run at all. It works |
9 |
fine when I configure it by hand. |
10 |
|
11 |
> OK, have you looked in your logs/dmesg? I think that the ndiswrapper has to |
12 |
> load first and probe your NIC, before /etc/init.d/net.wlan0 launches. It may |
13 |
> pay to keep an eye on the router logs while your machine boots. |
14 |
> |
15 |
> My line above with sleep_scan_wlan0="1" or say "3" seconds delay may help, if |
16 |
> this is the problem. |
17 |
|
18 |
I'll play with it a bit. |
19 |
|
20 |
> If you have not installed wpa_supplicant you don't need this. Just make sure |
21 |
> #modules=( "wpa_supplicant" ) is commented out. iwconfig is the default |
22 |
> anyway. ifconfig or iproute2 will work so I don't think that you need to |
23 |
> define that either. Your entries: |
24 |
> |
25 |
> essid_wlan0="digitaltorque" |
26 |
> config_wlan0=( "192.168.0.5/24" ) |
27 |
> routes_wlan0=( "default via 192.168.0.1" ) |
28 |
> |
29 |
> are correct - so the error is not because of these. |
30 |
> |
31 |
> > Or maybe I should just run an rc.local script. |
32 |
> |
33 |
> You could use the preup scripts in /etc/conf.d/net, if for some reason the |
34 |
> ndiswrapper takes for ever to kick into action. |
35 |
|
36 |
Hmm. I did put ndiswrapper in my /etc/modules.autoload.d/kernel-2.6, so it |
37 |
should be loaded at boot, but maybe it takes too long, causing a race |
38 |
condition at boot. |
39 |
|
40 |
Mike |
41 |
-- |
42 |
Michael P. Soulier <msoulier@×××××××××××××.ca> |
43 |
"Any intelligent fool can make things bigger and more complex... It takes a |
44 |
touch of genius - and a lot of courage to move in the opposite direction." |
45 |
--Albert Einstein |