I had no luck with a screen brightness step of 1, in acpi handler. Adding these clauses to handler.sh works better.
video/brightnessdown) bl_dev=/sys/class/backlight/acpi_video0 actual_bl=`cat $bl_dev/actual_brightness` # Lower brightness has no effect until it is lowered enough to change actual_brightness. # Brightness less than 10 causes problems when increasing! while [ $actual_bl -gt 10 -a $actual_bl == `cat $bl_dev/actual_brightness` ] do echo $((`cat $bl_dev/brightness` - 1)) > $bl_dev/brightness done ;; video/brightnessup) bl_dev=/sys/class/backlight/acpi_video0 actual_bl=`cat $bl_dev/actual_brightness` # Change in brightness has no effect until it is changed enough to change actual_brightness. while [ $actual_bl -lt 100 -a $actual_bl == `cat $bl_dev/actual_brightness` ] do echo $((`cat $bl_dev/brightness` + 1)) > $bl_dev/brightness done ;;
- This is a mess, it should be cleaned up before adding it to the article (e.g use
$( )instead of
`, input redirection not cat, avoid
[, etc). -- Alad (talk) 14:34, 4 June 2015 (UTC)
Banner to warn users that logind already implements some of these tips?
Hi! I think it can be useful if we put a banner on top of this page to warn users that logind already implements some acpid features. Eventually we can highlight which of these features are already implemented, and a link to the systemd wiki page. Nierro (talk) 17:40, 3 August 2013 (UTC)
- The Power Management page (a section from systemd was recently moved there) links to this page correctly, but you are right - some note to read Power Management#Power management with systemd first would be useful. But I'd still keep the old examples using pm-suspend etc. until pm-utils is finally deprecated. -- Lahwaacz (talk) 17:51, 3 August 2013 (UTC)
Minor addition to Introduction
I'm troubleshooting a laptop specific acpi module. The command `dmesg | grep [module]` reports the module is loaded. Subsequently, I assumed the ACPID package was also installed and loaded. I think a little bit of explanation here would go a long way to warn about this gap.
- [add info: Why a module could be loaded, but not the ACPID package/Why the package might be inactive]
- [maybe a test, then continue with the existing intro]
- Install the acpid package.
- Start and/or enable acpid.service.
- # systemctl start acpid.service
- Verify the service is loaded:
- # systemctl status acpid.service
- The ACPI modules come with the kernel (i.e. the Lahwaacz (talk) 20:09, 29 October 2017 (UTC) package), not with the package. So why the acpid package might be missing: simply because you haven't installed it yet. I'm sorry but that's a basic thing to know about your system, I don't see why it should be included on this page when it's not anywhere else on the wiki. Also note that the acpid package is not necessary to make the ACPI module(s) more functional - it is just one way to connect events to actions, there are multiple alternatives. --
- I don't follow this logic. The wiki is very informative, and instructs users in many basic things to know about their systems. If your objection is about style--for example--Why add more explanation, when a simple one liner will do? I get that objection. I figured out that I skipped over this line, and I fixed it. But for my taste, I like those wiki pages which instruct readers to test first and then choose an action. But if your objection is writing more instruction gives the appearance this is the only way, then more explanation is needed, not less. I'm not the person to write that. I simply like the explicit test style I find in many of these wiki pages better than a more terse style. Xtian (talk) 01:31, 30 October 2017 (UTC)