[driverloader] driverloader breaks suspend (for Laptops) on 2.6.9 ?

Linuxant support (Jonathan) support at linuxant.com
Wed Jan 26 10:43:10 EST 2005


using the 'dldrstop' command will also bring down the wireless interface 
on supported distributions (by using the 'ifdown' command available on 
many distributions) before removing the module from the kernel. This is 
more clean than simply doing simply a 'rmmod' on the module.


Technical specialist / Linuxant
support at linuxant.com

Peter Wittich wrote:
> I just do a rmmod on the module, which works for me, and then modprobe
> it again at the end.   This works for me.  Is there any advantage to
> doing the dldrstop?
> Peter
> On Tue, 25 Jan 2005 17:49:25 -0800, Michael Perry <meperry at gmail.com> wrote:
>>On Tue, 25 Jan 2005 21:25:01 +0100 (CET), Olivier Kaloudoff
>><kalou at kalou.net> wrote:
>>>        I'm using driverloader version 2.10 (Debian), and
>>>it seems that my computer refuses to suspend to RAM due to the
>>>driverloader module.
>>>        Indeed, when I type "echo 1 > /proc/acpi/sleep", the
>>>kernel complains about:
>>>Strange, kdldrd/wrk not stopped
>>>Strange, kdldrd/eth2 not stopped
>>>Strange, kdldrd/dpc not stopped
>>>Strange, kdldrd/hyperwrk not stopped
>>>        are there plans to fix this ?
>>>driverloader mailing list
>>>driverloader at lists.linuxant.com
>>To get around this with the present driver, you can include a line in
>>your /etc/acpi event script to bring down driverloader.  I use
>>dldrstop and then modprobe driverloader in the script when I bring it
>>back up again.
>>Works for me everytime.
>>Michael Perry
>>meperry at gmail.com
>>driverloader mailing list
>>driverloader at lists.linuxant.com
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader

More information about the driverloader mailing list