[driverloader] Config with every boot
Linuxant support (Jonathan)
support at linuxant.com
Tue Jan 11 16:22:31 EST 2005
in DriverLoader 2.07, we have added hooks to make it easier to
automatically start the wpa_supplicant daemon.
Please name your wpa_supplicant daemon binary
'/usr/sbin/dldr_wpa_supplicant' and please name your wpa_supplicant
configuration file '/etc/driverloader/dldr_wpa_supplicant.<iface>.conf'.
For example, if you wireless interface is named 'wlan0', the file name
When these files will be in place, the wpa_supplicant daemon will
automatically be started when you will use the 'ifup' command in a root
shell. This command is used after a reboot to bring up your wireless
interface so it should also automatically work after a reboot.
Technical specialist / Linuxant
support at linuxant.com
> Linuxant support (Jonathan) wrote:
>> using a trial license should not be the problem. Since you have a
>> CardBus (32-bit PCMCIA) wireless adapter, it is quite possible that
>> the problem is that the 'pcmcia' service is started after the
>> 'network' service. Please change the starting order of your services
>> with the following instructions, these instructions should work fine
>> on Red Hat, Fedora Core, Mandrakelinux and SuSE :
>> Please take a look at both the '/etc/init.d/network' and the
>> '/etc/init.d/pcmcia' files. In each file, you should see a line like
>> this :
>> # chkconfig <run level number> <start prio number> <kill prio number>
>> Then, please edit the '/etc/init.d/pcmcia' file and change the <start
>> prio number> to the <start prio number> found in the
>> '/etc/init.d/network' file minus one. You will also have to change the
>> <kill prio number> which can be calculated with this simple formula :
>> <kill prio number> = 100 - <start prio number>
>> After the modifications have been made to the '/etc/init.d/pcmcia'
>> file, please run the following command in a root shell :
>> chkconfig pcmcia reset
>> Technical specialist / Linuxant
>> support at linuxant.com
>> Lloyd Webb wrote:
>>> Apologies if this has been covered, I couldn't find a good way of
>>> searching the archives.
>>> Why do I have to configure driverloader with the correct driver, ie
>>> delete it then reload it via http://127.0.0.1:18020/ every time my
>>> machine boots to make my WPC54G card work?
>>> Is this because I am on a temporary license?
>>> Many regards,
>>> Message sent using UebiMiau 2.7.2
>>> driverloader mailing list
>>> driverloader at lists.linuxant.com
> Nice one Jonathon. That seems to work fine.
> Has anyone changed the startup scripts to auto load wpa_supplicant?
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader