(In reply to comment #3)
> Does anyone know if pm-suspend performs any tricks on suspending?
>
> What about "pm-suspend --quirk-none"?
Yes. By default it will store its quirks in /var/cache/pm-utils/last_known_working.quirkdb (source: man pm-utils)
Also, from /usr/share/doc/pm-utils/README.debugging:
* If a parameter (or lack thereof) passed to pm-suspend and friends is causing
problems, or you need to debug the suspend/resume process to work out what
quirks are causing problems, you can use the ADD_PARAMETERS and
DROP_PARAMETERS environment variables. To do this, create a file in
/etc/pm/config.d, and add the following lines to it:
ADD_PARAMETERS="--parameter-to-add --another-parameter"
DROP_PARAMETERS="--parameter-to-drop --another-parameter-to-drop"
If you want to drop all parameters (for testing purposes, or to work around
bugs in HAL), you can use DROP_PARAMETERS="all"
(In reply to comment #3)
> Does anyone know if pm-suspend performs any tricks on suspending?
>
> What about "pm-suspend --quirk-none"?
Yes. By default it will store its quirks in /var/cache/ pm-utils/ last_known_ working. quirkdb (source: man pm-utils)
Also, from /usr/share/ doc/pm- utils/README. debugging:
* If a parameter (or lack thereof) passed to pm-suspend and friends is causing S="--parameter- to-add --another- parameter" PARAMETERS= "--parameter- to-drop --another- parameter- to-drop"
problems, or you need to debug the suspend/resume process to work out what
quirks are causing problems, you can use the ADD_PARAMETERS and
DROP_PARAMETERS environment variables. To do this, create a file in
/etc/pm/config.d, and add the following lines to it:
ADD_PARAMETER
DROP_
If you want to drop all parameters (for testing purposes, or to work around ="all"
bugs in HAL), you can use DROP_PARAMETERS