[gobolinux-users] Gobolinux and ipw3945

[Daniele Maccari]

Well, now I have another problem, with net configuration :P
Everything works fine if I do every step manually (modprobe the module, 
start the daemon, start wpa_supplicant and finally run dhcpcd).
I use wpa_supplicant to connect to my wpa-psk network, so I added the 
following line to the BootUp script:

Exec "Starting WPA service..." wpa_supplicant -B -w -i eth1 -c 
/System/Settings/wpa_supplicant.conf -D wext

I've also specified to load the ipw3945 module on boot in the 
BootOptions file (and the modules is correctly loaded indeed). So I 
added another line in the BootUp script to tell Gobolinux to run the 
ipw3945 daemon after the log and kernel log daemons.

Daemon ipw3945d

Then I have a BootUp scripts that looks like the following:

.
.
.
Daemon ipw3945d
.
.
.
LoadModules (the command which load user-defined modules)
.
.
.
Exec "Starting WPA service..." wpa_supplicant -B -w -i eth1 -c 
/System/Settings/wpa_supplicant.conf -D wext
.
.
.
StartTask Network (the command which start the network)

In the NetworkOptions I've specified what interfaces I want on boot, 
following the wiki, and also to use DHCP.
Despite all this I constantly get a "Network initialization failed" 
error on boot, even if when I look for each component to be started I 
have the module loaded, the daemon running, and so wpa_supplicant.

What could it be?

Thanks in advance.

Jonas Karlsson ha scritto:
> 2007/11/2, gobo users <gobo.users at gmail.com>:
>   
>> Well, I've tried the packages and everything went fine. As for the recipe I
>> get an "Installation step failed" error due to some leftover files in
>> System/Kernel/Modules/net/. Something about map, I'll post the complete
>> error asap.
>>     
>
> I pretty sure what the error is, and that is that 'modprobe' is being
> run from 'make install'.
>
>   
>> Anyway I used SymlinkProgram to finish (or so I suppose) the installation
>> and then symlinked manually the kernel module (ipw3945.ko) from the
>> Programs' dir to the kernel modules dir. Then everything works just fine.
>>
>>     
> Ok, great! Then I'll fix the recipe to remove the above error and
> commit it and the packages.
>
>   
>> I hope this helps.
>>
>>     
> Yes it does, thanks. :)
>
>