[driverloader] Re: on driverloader 2.04

Linuxant support (Jonathan) support at linuxant.com
Tue Aug 17 13:40:08 EDT 2004


in both DriverLoader 1.77 and DriverLoader 2.04, since Debian uses the 
'chkconfig' program to manage init scripts, the DriverLoader init script 
have 11 as start priority.

If you want to change the start priority of DriverLoader, please edit 
the file '/etc/init.d/driverloader' and change the following line :

# chkconfig: 2345 11 91

11 is the start priority of DriverLoader and the last number (91) is the 
kill priority of the service. You can use this simple formula to obtain 
the kill priority :

kill_prio = 100 - start_prio

After you have made changes to this file, please run the following 
command in a root shell :

chkconfig driverloader reset

This command will update the contents of the '/etc/rcN.d' directories.


Technical specialist / Linuxant
support at linuxant.com

Cristiano De Michele wrote:
> On Tue, 2004-08-17 at 00:29, Linuxant support (Jonathan) wrote:
>>if you have a CardBUS (32-bit PCMCIA) wireless device, the is the normal 
>>behavior that the 'pcmcia' service must be started before the 
>>'driverloader' service. The 'pcmcia' service will make your wireless 
>>device available in the output of the 'lspci' command so when the 
>>DriverLoader module is inserted into the kernel, the module will be able 
>>to find the wireless device. As you noticed, the 'driverloader' service 
>>does insert the DriverLoader module in the kernel.
> yes I have a cardbus device (USR805410 pcmcia card) 
> but in this case driverloader debian package should create a symbolic
> link under /etc/rcNN.d/ with a sequence number greater than 20, that is
> the sequence number for pcmcia-cs on debian.
> Driverloader debian package set 14 as sequence number for driverloader
> init script.
> Probably does driverloader 1.77 set a sequence number greater than 20
> while 2.04 does not?
> regards Cristiano
>>Technical specialist / Linuxant
>>support at linuxant.com
>>Cristiano De Michele wrote:
>>>I recently installed driverloader 2.04 on my debian unstable and I noted
>>>that if driverloader module is loaded before pcmcia (through
>>>/etc/init.d/driverloader init script) then wireless interface does not
>>>come up.
>>>On the contrary if I start pcmcia first and then driverloader, interface
>>>comes up regularly.
>>>I did not have such a problem with version 1.77.
>>>driverloader mailing list
>>>driverloader at lists.linuxant.com

More information about the driverloader mailing list