Adapt laptop-mode-tools invocation to ubuntu's acpi-support / pm-tools packages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
laptop-mode-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: laptop-mode-tools
Adaption would would mean to include scripts that call "/usr/bin/
It is suggested to acpi-support to stop calling laptop-mode-tools and hdparm directly (in non-config files).
bug #244831, bug #244832, bug #244833, bug #244836
(Beware: resume.d, and start.d may be obsoleted by some pm-tools directory)
bug #244839, bug #205005
(Adapt the approach from the original laptop-mode-tools debian package to current ubuntu acpi-support)
laptop_mode may need the options "auto force" when called on resume events. (To reapply hdparm settings even though AC state has not changed.)
(The current laptop-mode disk-idleing approach seems to be a left-over from before the ubuntu-laptop-mode package was droped for laptop-mode-tools.)
https:/
description: | updated |
Changed in laptop-mode-tools (Ubuntu): | |
status: | New → Fix Released |
A copy of my comment https:/ /bugs.launchpad .net/ubuntu/ +source/ pm-utils/ +bug/239419/ comments/ 5
Actually, you are quite right. Currently, all that /etc/acpi/power.sh and /usr/lib/ pm-utils/ power.d/ laptop- tools do is perfectly replicable with identical settings in /etc/laptop- mode/laptop- mode.conf (*_HD_POWERMGMT, *_HD_IDLE_ TIMEOUT_ SECONDS, *_RATIO in /etc/laptop- mode/laptop- mode.conf, and ENABLE_ LAPTOP_ MODE=true in /etc/default/ acpi-support) . Even the argument that laptop-mode is freezing some computers is no longer valid, because /proc/sys/ vm/laptop_ mode is hard-coded to 2 on battery power, and you will get the same functionality as long as ENABLE_ LAPTOP_ MODE_ON_ AC=0 (which is default). So if there are still problems people already should have been experiencing that.
Also, /usr/sbin/ laptop_ mode already has all that state code commented out, so it doesn't need any force argument, WAS_ACTIVE is always 0 with the version shipped in Ubuntu, so it always reapplies its parameters.