On Wed, 2007-07-04 at 09:33 -0400, John E. Perry wrote:
Hans van der Merwe wrote:
If I'd realized that sooner, and looked at kNetworkManager rather than KWiFiManager, I probably would have had complete success much sooner.
You must still figure out why ipw3945d is not loaded at startup (or at loading of module?)
Hm. Not being an experienced systems programmer or administrator, I assumed it was up to me to start it up somewhere in an initialization script.
So it should have come up on its own with ipw3945?
jp
Mine comes up automagically when ipw3945 module is loaded.
From the README of ipw3945d, it seems that it must be started after the module is loaded, "by hand" - I will check my system.
3. RUNNING BEFORE DRIVER FULLY LOADED The typical method for lauching the daemon is to spawn it from within the modprobe.conf or udev scripts as soon as the ipw3945 module is loaded. This can cause problems on systems where the module is loaded earlier in the boot process than the device is probed, or where the module load is delayed. To support this model, the daemon supports the '--timeout' parameter which can be used to specify how long the daemon should look for the driver before giving up. The default value is 0, which will exit immediately if the driver is not found. A value of -1 will result in the daemon waiting forever. Any other value specifies the number of seconds to wait. The daemon will poll the system once per second looking for the driver's sysfs entries. Example usage: % ipw3945d --timeout=-1 The above will fork the daemon into the background and then wait forever for the module to load. E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org