[SOLVED] Systemd and laptop-mode-tools frequency scaling

Hi all.
After a long time with no arch updates (november 2011) for various reasons, I decided to reinstall Arch from point 0 on my Clevo laptop.
I was pleased to see nothing went bad, all is now set like I want. I installed systemd yesterday. All very straightforward for me, I only have a problem with CPU frequency scaling plus some minor glitches.
Before systemd, everything went fine. Ondemand governor, set up like I wanted.
Now when on AC the system uses ondemand, but when on battery it uses the conservative governor. What's more, it does not go over 1.6GHz (2.54GHz max).
Here are some infos about it:
[adriano@M735T ~] cpupower frequency-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 2.53 GHz
available frequency steps: 2.53 GHz, 2.53 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
boost state support:
Supported: yes
Active: yes
[yes this is all come out of the cpupower command, no mention of CPU 1. Is this normal?]
Of course LMT is set up correctly
CONTROL_CPU_FREQUENCY="1"
BATT_CPU_MAXFREQ=fastest
BATT_CPU_MINFREQ=slowest
BATT_CPU_GOVERNOR=ondemand
BATT_CPU_IGNORE_NICE_LOAD=1
LM_AC_CPU_MAXFREQ=fastest
LM_AC_CPU_MINFREQ=slowest
LM_AC_CPU_GOVERNOR=ondemand
LM_AC_CPU_IGNORE_NICE_LOAD=1
NOLM_AC_CPU_MAXFREQ=fastest
NOLM_AC_CPU_MINFREQ=slowest
NOLM_AC_CPU_GOVERNOR=ondemand
NOLM_AC_CPU_IGNORE_NICE_LOAD=0
[adriano@M735T ~] sudo systemctl status laptop-mode-tools.service
laptop-mode-tools.service - Laptop Power Saving Tools
Loaded: loaded (/usr/lib/systemd/system/laptop-mode-tools.service; enabled)
Active: active (exited) since Sun, 02 Sep 2012 17:03:45 +0200; 4h 34min ago
Main PID: 367 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/laptop-mode-tools.service
Sep 02 17:03:43 M735T laptop_mode[367]: /usr/sbin/laptop_mode: line 198: /dev/fd/1: No such device or address
Sep 02 17:03:44 M735T laptop_mode[367]: /usr/sbin/laptop_mode: line 198: /dev/fd/1: No such device or address
Sep 02 17:03:44 M735T laptop_mode[367]: /usr/sbin/laptop_mode: line 198: /dev/fd/1: No such device or address
I wonder why LMT status is "exited"
OK bin that, I just now see something is wrong. I said it used conservative, but I'm on battery and it now says ondemand (still 1.6GHz max). However it seems it does so casually.
ACPI:
[adriano@M735T ~] acpi
Battery 0: Discharging, 53%, rate information unavailable
This may be (?) or may not be linked with nother problem I have: when unplugging the AC the KDE battery monitor does not update. It says AC is plugged and it will not activate power saving features (screen dimming, suspend...)
Note that this battery monitor problem occurred even before systemd, so it should not be linked to the above problem. However I'm not 100% sure the above problems did not occur before installing systemd since I only had the system up and running for a comple of days. I seem to recall I checked and it worked fine.
Any idea why all this happens?
Last edited by OdinEidolon (2012-11-20 08:56:31)

Ok rebooted and this is the output of the pm-powersave log file:
(AC IN, no battery)
(pastebin)
http://pastebin.com/Kf2Lx7UQ
If I grep cpupower:
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
right now:
1) cpupower reports ondemand and 2.54GHz (right)
2) acpi -bi reports nothing as it should (battery is disconnected)
3) acpi -a reports AC in as it should
4) all KDE stuff works OK
Now I plug the battery in:
1) cpupower reports ondemand and 2.54GHz (right)
2) acpi -bi reports nothing, which is wrong
3) acpi -a reports AC in as it should
4) KDE battery monitor reports no battery in, as signaled by acpi
5) if performing acpi_listen ,it reports nothing interesting
Now I unplug AC:
Absolutely nothing changes (not even in the log file) but:
1) cpupower reports ondemand and 1.6GHz (wrong)
2) acpi -bi reports nothing, which is wrong
3) acpi -a reports no AC as it should
4) KDE battery monitor reports no battery in, as signaled by acpi,  but it also reports AC is inserted

Similar Messages

  • Slow boot with systemd due to NetworkManager and laptop-mode-tools

    ernestas ~ $ systemd-analyze blame
    25787ms NetworkManager.service
      3440ms laptop-mode-tools.service
      1792ms systemd-logind.service
      1573ms systemd-modules-load.service
      1519ms home.mount
      1305ms polkit.service
       977ms systemd-udevd.service
       903ms systemd-sysctl.servic
    What could be the underlying problem? How do I solve it?

    Okay. I no longer use laptop-mode-tools, but NetworkManager still seems to be slow:
    ernestas ~ $ systemd-analyze blame
      3592ms NetworkManager.service
      3013ms systemd-logind.service
       869ms dev-sda7.swap
       762ms home.mount
       666ms systemd-modules-load.service
       546ms systemd-udev-trigger.service
       523ms systemd-udevd.service
       500ms dev-hugepages.mount
       479ms sys-kernel-debug.mount
    Last edited by ernetas (2012-11-03 16:01:44)

  • Xfce4-power-manager and laptop-mode-tools + backlight problems.

    Cross posted from here: https://bbs.archlinux.org/viewtopic.php?id=127992
    I don't know which forum it belongs to, so maybe a mod can close the one in the wrong forum.
    Out of curiosity, do these two tools conflict with each other? There seems to be some features that do the same thing, ie harddrive spin down time, but I'm not sure if these two will try to kill each other trying to configure the same power settings. If they do conflict, how could I go about disabling the conflicting parts (on either)? laptop-mode-tools claims it needs acpid "for ACPI support", however, acpid seems to be grabbing the standby event and throwing the laptop in standby despite the standby button bound to do nothing in xfce-power-manager. If I take out acpid, does that mean laptop-mode will no longer detect acpi events such as connecting/disconnecting AC power and thus not change modes when its plugged in?
    Another problem I've had after installing xfce4-power-manager is that when I use the brightness hotkeys the backlight gets stuck and starts flashing, locking up the system until I force shutdown. However, I can use the brightness plugin without trouble at all. What's causing the power manager to screw up setting the brightness since it clearly seems to work otherwise.

    It is easier to close this one and move the other thread over here. Just continue there.
    BTW better use the Report button when you want to have a thread of yours moved to another forum. That way it is guaranteed a mod will see this in time. And you never need to cross post.

  • Power management: laptop-mode-tools and pm-utils confusion

    There have been a few threads recently that touch on this topic, but I'm still somewhat confused as to how best to use these two tools for power management.
    As I understand it, laptop-mode-tools is a set of scripts and config files for controlling various aspects of power saving, while pm-utils started as a tool for managing suspend/hibernate.  However, newer versions of pm-utils have begun to include general power management features that conflict with those of laptop-mode-tools, and respond to the pm-powersave command.
    Ideally, I would like to control power management in the following way: Have acpid as the only running daemon (rather than acpid and laptop-mode-tools as I have now), which then calls pm-suspend, pm-hibernate and pm-powersave in the appropriate circumstances. 
    The wiki has a brief guide on how to insert pm-powersave as an acpi event; however, it seems to me that pm-utils is not able to replicate all the functions of laptop-mode-tools yet, for example in controlling the eeepc's SHE.
    In this thread: https://bbs.archlinux.org/viewtopic.php?pid=784969, einhard seems to suggest that its quite a simple process to modify some hooks from laptop-mode-tools to make them work with pm-utils.  I would be eternally grateful if somebody could post an example of how to carry out this modification.  I have very minimal knowledge of bash, which means that I can't get going on my own but I think I could modify the rest of the hooks on my own if I had an example, a template, to guide me. 
    Of course if anyone has any other suggestions regarding how best to mix these tools for power management it would be very good to hear them.  I am aware of this thread: https://bbs.archlinux.org/viewtopic.php?id=88011&p=2, in which takedown suggests writing some dummy hooks to pm-utils to prevent any conflict, but I'm not entirely clear about which hooks I should apply this to, i. e. just the hooks in power.d or those in sleep.d, too?

    mordoc, what exactly is the problem your having?
    Since I made the original post I have actually succeeded in creating the setup I described, i.e. I have removed laptop-mode-tools and have pm-utils do all suspend, hibernate and power management functions using acpid.  This required adding a very simple custom hook to pm-powersave to deal with all the power-saving functions of laptop-mode-tools that pm-powersave does not (yet) replace OOTB.

  • Autohibernate with pm-utils and laptop-mode

    Hi all,
    I know this is a frequent problem but I cannot find any solution around the web.
    I am using pm-utils and am able to suspend to disk and ram properly.
    Now I want to hibernate automatically based on battery condition of my laptop.
    I have installed acpi and laptop-mode-tool,  and both seem to work correctly, my battery status appear on conky, and every other events based on laptop-mode run smoothly.
    I even wrote an /etc/laptop-mode/auto-hibernate.conf according to this post https://bbs.archlinux.org/viewtopic.php?id=50702.
    But the problem is still there, the laptop doesn't autohibernate on low battery.
    If anyone has managed to autohibernate based on low battery, I will glad to know his/her solution,
    regards
    Last edited by capnion (2012-01-25 10:38:18)

    even if im not using the tools you pasted. this is what ive done (since my battery hardware is a bit shaky, i had to add some cornercases, which lead to me creating a new script).
    some bits have been taken from the web (notify-send function for example).
    see if it works for you. of course, input will be appreciated too!.
    #!/bin/bash
    # power management script for my crappy laptop
    #BAT_FILE='/proc/acpi/battery/BAT0/state'
    BAT_BASE='/sys/class/power_supply/BAT0/'
    BAT_FILE='/sys/class/power_supply/BAT0/voltage_now'
    PDIR="/run/"
    LCK_FILE=${PDIR}`basename $0`.pid
    SAFE_STATE='5000000'
    MIN_STATE='10000000'
    MAX_STATE='12500000'
    THRESHOLD='10500000'
    HIB_SECS=60
    notify() {
    # Usage: notify "title" "description" [options to pass to send-notify"
    title="$1"
    body="$2"
    shift 2
    opts="$*"
    # Send messages to users listed by the 'users' command, but only once
    # Maybe sh has a better way of doing set operations, but this works:
    SENT=""
    for USER in $(users); do
    case $SENT in
    "$USER") ;;
    *" $USER") ;;
    "$USER "*) ;;
    *" $USER "*) ;;
    # use 'su USER' to send the message
    *) SENT="$SENT $USER";DISPLAY=:0 su $USER -c "notify-send $opts \"$title\" \"$body\"" ;;
    esac
    done
    # test if we are root.
    if [ $EUID != 0 ]; then
    sudo "$0" "$@"
    exit $?
    fi
    #test if we are running already
    echo "LCK_FILE=$LCK_FILE"
    if [ -f "${LCK_FILE}" ]; then
    MYPID=`head -n 1 "${LCK_FILE}"`
    TEST_RUNNING=`ps -p ${MYPID}|grep ${MYPID}`
    if [ -z "${TEST_RUNNING}" ]; then
    #the process is not running
    echo $$ > "$LCK_FILE"
    else
    echo "`basename $0` is already running [${MYPID}]"
    exit 0
    fi
    else
    echo $$ > "$LCK_FILE"
    fi
    if [ -a "$BAT_BASE" ]; then
    PRESENT=$(cat ${BAT_BASE}/present)
    if [ $PRESENT == '0' ]; then
    echo "Battery not present!"
    rm "${LCK_FILE}"
    exit 0
    else
    CURR_STATE=$(cat ${BAT_BASE}/voltage_now)
    CHAR_STATE=$(cat ${BAT_BASE}/status)
    fi
    else
    echo "Something wrong, file missing!"
    rm "${LCK_FILE}"
    exit 1
    fi
    if [ $CURR_STATE -lt $SAFE_STATE ]; then
    echo "buggy batt, ignored result: $CURR_STATE"
    rm "${LCK_FILE}"
    exit 0
    fi
    if [ $CURR_STATE -lt $THRESHOLD ]; then
    if [ $CHAR_STATE != "Charging" ]; then
    echo "battery level low, hibernating in $HIB_SECS seconds"
    notify "BATTERY STATUS" "battery level low, hibernating in $HIB_SECS seconds. Connect to AC to cancel"
    sleep $HIB_SECS
    CHAR_STATE=$(cat ${BAT_BASE}/status)
    if [ $CHAR_STATE != "Charging" ]; then
    /usr/sbin/pm-hibernate
    # notify "BATTERY STATUS" "Comming out of hibernate!!"
    rm "${LCK_FILE}"
    exit 0
    fi
    notify "BATTERY STATUS" "Charger plugged. hibernate disabled"
    fi
    else
    echo "battery state: $CHAR_STATE"
    echo "battery level: $CURR_STATE"
    # notify "battery level:" "$CURR_STATE"
    fi
    rm "${LCK_FILE}"
    it is run by root every minute. it warns through notify-send one minute prior to hibernating, and aborts if the laptop was plugged within that minute.
    some variables should be tweaked for your battery
    EDIT: fixed a bug when testing if battery was being charged/discharged. added test for root.
    Last edited by eldragon (2012-01-25 14:33:40)

  • [SOLVED]Laptop-mode-tools no cpu scaling

    Hi!
    After I installed laptop-mode-tools, I can't have my cpu freq scaling as I always did.
    Well, I'll explain better: without laptop-mode-tools I used to set my cpu freq via /etc/rc.local, and everything was fine.
    But now I need laptop-mode-tools and I have to say, everything works very well...But here comes the sun, uhm no, here comes the problem: when i plug in and out my ac cable, my frequency will stay at its lowest. The same thing happens after suspend... I can't understand...
    I tried with acpid, obviously, and for example, when i plug in ac power, lcd brightness changes as expected from my config files, but cpufreq will stay just as I said.
    So, here is my cpufreq-info now:
    limiti hardware: 1000 MHz - 1.67 GHz
    frequenze disponibili: 1.67 GHz, 1.33 GHz, 1000 MHz
    gestori disponibili: conservative, ondemand, userspace, powersave, performance
    gestore attuale: la frequenza deve mantenersi tra 1000 MHz e 1000 MHz.
    Il gestore "performance" può decidere quale velocità usare
    in questo intervallo.
    (it's italian sorry)
    this is /etc/laptop-mode/conf.d/cpufreq.conf
    # Configuration file for Laptop Mode Tools module cpufreq.
    # For more information, consult the laptop-mode.conf(8) manual page.
    # CPU frequency scaling and throttling
    # Laptop mode tools can automatically adjust your kernel CPU frequency
    # settings. This includes upper and lower limits and scaling governors.
    # There is also support for CPU throttling, on systems that don't support
    # frequency scaling.
    # This feature only works on 2.6 kernels.
    # IMPORTANT: In versions 1.36 and earlier, these settings were included in the
    # main laptop-mode.conf configuration file. If they are still present, they
    # overrule the settings in this file. To fix this, simply delete the settings
    # from the main config file.
    # Enable debug mode for this module
    # Set to 1 if you want to debug this module
    DEBUG=0
    # Should laptop mode tools control the CPU frequency settings?
    # Set to 0 to disable
    CONTROL_CPU_FREQUENCY=1
    # Legal values are "slowest" for the slowest speed that your
    # CPU is able to operate at, "fastest" for the fastest speed,
    # "medium" for some value in the middle, or any value listed in
    # /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies.
    # The "governor" can be any governor installed on your system, this usually
    # includes "ondemand", "conservative", and "performance". The
    # "IGNORE_NICE_LOAD" setting specifies that background programs that have
    # a low priority ("nice level") should not cause the CPU frequency to
    # be increased. (You generally want this to be enabled in battery mode.)
    BATT_CPU_MAXFREQ=fastest
    BATT_CPU_MINFREQ=slowest
    BATT_CPU_GOVERNOR=ondemand
    BATT_CPU_IGNORE_NICE_LOAD=1
    LM_AC_CPU_MAXFREQ=fastest
    LM_AC_CPU_MINFREQ=slowest
    LM_AC_CPU_GOVERNOR=performance
    LM_AC_CPU_IGNORE_NICE_LOAD=1
    NOLM_AC_CPU_MAXFREQ=fastest
    NOLM_AC_CPU_MINFREQ=slowest
    NOLM_AC_CPU_GOVERNOR=performance
    NOLM_AC_CPU_IGNORE_NICE_LOAD=0
    # Should laptop mode tools control the CPU throttling? This is only useful
    # on processors that don't have frequency scaling.
    # (Only works when you have /proc/acpi/processor/CPU*/throttling.)
    # This is only useful on older P4 processors that do not support frequency
    # scaling. On such processors, this is the only way to reduce power consumption
    # but at the cost of higher performance penalty.
    # Enable this only if you have a processor that does not support frequency scaling
    # On most new processors, you might want to disable it.
    # Set to 0 to disable.
    CONTROL_CPU_THROTTLING=0
    # Legal values are "maximum" for the maximum (slowest) throttling level,
    # "minimum" for minimum (fastest) throttling level, "medium" for a value
    # somewhere in the middle (this is usually 50% for P4s), or any value listed
    # in /proc/acpi/processor/CPU*/throttling. Be careful when using "maximum":
    # this may be _very_ slow (in fact, with P4s it slows down the processor
    # by a factor 8).
    BATT_CPU_THROTTLING=medium
    LM_AC_CPU_THROTTLING=medium
    NOLM_AC_CPU_THROTTLING=minimum
    I'm using kernel 3.1.6 with no testing repo.
    I'm using pm-utils to suspend.
    As far as I understand, the problem is in one of the file laptop-mode installs on my hd...the only solution I found was to remove laptop-mode...but I need it because it's simple and i have no time to find something else,
    Thanks everybody!
    Bye!
    Last edited by nierro (2011-12-31 10:19:09)

    Ok, after i removed laptop-mode-tools and managed to have my cpu freq scaling,lcd brightness and eeepc she through rc.local and acpid events , i found that the real problem is located in ondemand governor: after suspend it stays at lowest freq possible.
    If i change then my governor, with for example performance, it works, but if i change again to ondemand, it stays to its lowest...any idea?
    EDIT: tried with granola and userspace governor, but nothing changes... tried on my other laptop with kernel 3.1.5-ARCH, and there everything it's ok, but i noticed i haven't acpi and acpid installed there...so may be the problem is related to them? (i use the same cpufreq driver in these laptops)
    I'll try to kick out acpi and acpid and i'll make you know what happens.
    Last edited by nierro (2011-12-31 09:04:54)

  • Laptop Mode Tools causes frequency scaling governor error on shut down

    Hi guys,
    When I have the laptop mode tools service enabled, I get some errors whenever I shut down my computer. I can't catch the errors because they move by pretty quickly, and I can't find the error anywhere in /var/log directory. But I think it says something along the lines of KERNEL ERROR blah/freq_scaling_governor.
    The error does not occur when I disable laptop mode tools. I have also tried uninstalling and reinstalling laptop-mode-tools and acpid, but that didn't change the error.
    How can I log the errors that occur on shutdown so that I can have the exact error?
    What can I do to remove this error?
    Thank you for any help you may give me

    Running cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver did give me intel_pstate.
    Disabling laptop-mode-tools cpu frequency governors seems to have gotten rid of the error messages.
    For future reference, where can I find all my error logs and a log of messages that occur when I log out? I still seem to get some errors, but I can never read what they are.

  • [SOLVED] systemd: laptop-mode-tools fails to start (No such file ...)

    Hi,
    I recently moved to systemd. I noticed that 'laptop-mode-tools' does not start:
    Loaded: error (Reason: No such file or directory)
    Active: inactive (dead)
    Also laptop-mode itself does not run (but exits successfully), maybe this has something to do with it:
    laptop-mode.service - Laptop Mode Tools
    Loaded: loaded (/usr/lib/systemd/system/laptop-mode.service; enabled)
    Active: active (exited) since Sat, 2012-11-10 10:44:13 CET; 2min 17s ago
    Process: 1020 ExecStart=/usr/sbin/laptop_mode init auto (code=exited, status=0/SUCCESS)
    CGroup: name=systemd:/system/laptop-mode.service
    I cannot find anything in journal that would help resolve this issue. Has someone else come across this problem? Where should I look to fix this issue?
    Sidenote: When I boot up, there show up some errors about 'eth0' and 'wlan0' "No such file or directory", but I cannot find them in the journal so I don't know them exactly.
    Last edited by javex (2012-11-10 12:41:07)

    When I upgraded, pacman said the following
    [2012-11-04 09:41] The systemd service name has changed from \laptop-mode-tools" to "laptop-mode"
    [2012-11-04 09:41] The change requires the old symlink to be manually removed:
    [2012-11-04 09:41] rm /etc/systemd/system/multi-user.target.wants/laptop-mode-tools.service
    [2012-11-04 09:41] The laptop-mode.service can be enabled using:
    [2012-11-04 09:41] systemctl enable laptop-mode
    [2012-11-04 09:41] upgraded laptop-mode-tools (1.61-2 -> 1.62-2)

  • Laptop-mode-tools/cpufrequtils Questions [SOLVED]

    I am running a Sony Vaio VGN-FW480J and am trying to optimize these two tools to save battery life and hard drive life span.   I have added @laptop-mode to my daemon array and acpi-cpufreq to modules. A few issues I immediately notice:
    1) cpufreq doesn't revert back to higher frequencies if I unplug and plug power source back in (before unplugging: CPU 0 - 800 MHz, CPU 1 - 2.00 GHz; after both are 800 and won't change if I plug power source back in)
    2) I believe the hard disk is actually spinning down more frequently (and fan is almost always on, even when no work is being done).  Here are the relevant files/the ones that I have altered.
    laptop-mode.conf
    # Configuration for Laptop Mode Tools
    # There is a "system" to the configuration setting names:
    # CONTROL_something=0/1 Determines whether Laptop Mode Tools controls
    # something
    # LM_something=value Value of "something" when laptop mode is active
    # NOLM_something=value Value of "something" when laptop mode is NOT
    # active
    # AC_something=value Value of "something" when the computer is running
    # on AC power
    # BATT_something=value Value of "something when the computer is running
    # on battery power
    # There can be combinations of LM_/NOLM_ and AC_/BATT_ prefixes, but the
    # available prefixes are different for each setting. The available ones are
    # documented in the manual page, laptop-mode.conf(8). If there is no LM_/
    # NOLM_ in a setting name, then the value is used independently of laptop
    # mode state, and similarly, if there is no AC_/BATT_, then the value is used
    # independently of power state.
    # Some options only work on ACPI systems. They are marked ACPI-ONLY.
    # Note that this configuration file is a fragment of shell script: you
    # can use all the features of the shell scripting language to achieve your
    # desired configuration.
    # Modules
    # Laptop Mode Tools modules have separate configuration files, that can be
    # found in /etc/laptop-mode/conf.d. Please look through these configuration
    # files as well, there are many useful power saving tools in there!
    # Enable/Disable laptop-mode-tools execution
    # Set it to 0 to completely disable laptop-mode-tools from running
    ENABLE_LAPTOP_MODE_TOOLS=1
    # Configuration debugging
    # Set this to 1 if you want to see a lot of information when you start/stop
    # laptop_mode.
    VERBOSE_OUTPUT=0
    # Set this to 1 if you want to log messages to syslog
    LOG_TO_SYSLOG=1
    # Run in shell debug mode
    # Enable this if you would like to execute the entire laptop-mode-tools program
    # in shell debug mode. Warning: This will create a lot of text output
    # If you are debugging an individual module, perhaps you would want to enable
    # each module specific debug mode (available in module conf files)
    DEBUG=0
    # When to enable laptop mode
    # "Laptop mode" is the mode in which laptop mode tools makes the computer
    # consume less power. This includes the kernel "laptop_mode" feature, which
    # allows your hard drives to spin down, as well as various other settings which
    # can be tweaked by laptop mode tools. You can enable or disable all of these
    # settings using the CONTROL_... options further down in this config file.
    # Enable laptop mode when on battery power.
    ENABLE_LAPTOP_MODE_ON_BATTERY=1
    # Enable laptop mode when on AC power.
    ENABLE_LAPTOP_MODE_ON_AC=1
    # Enable laptop mode when the laptop's lid is closed, even when we're on AC
    # power? (ACPI-ONLY)
    ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=0
    # Enable all simple zero-configuration auto modules
    # This option enables all simple modules (listed below) without requiring
    # the user to enable each module individually
    # List of modules which can be automatically enabled with this setting are:
    # ac97-powersave
    # cpufreq
    # dpms-standby
    # eee-superhe
    # ethernet
    # exec-commands
    # hal-polling
    # hdparm
    # intel-hda-powersave
    # intel-sata-powermgmt
    # runtime-pm
    # sched-mc-power-savings
    # sched-smt-power-savings
    # terminal-blanking
    # usb-autosuspend
    # wireless-ipw-power
    # wireless-iwl-power
    # wireless-power
    # Set this to 1 to enable all simple zero-configuration auto modules listed above.
    # NOTE: You can explicitly enable/disable any of the above modules by changing their
    # values in the individual settings file
    ENABLE_AUTO_MODULES=1
    # When to enable data loss sensitive features
    # When data loss sensitive features are disabled, laptop mode tools acts as if
    # laptop mode were disabled, for those features only.
    # Data loss sensitive features include:
    # - laptop_mode (i.e., delayed writes)
    # - hard drive write cache
    # All of the options that follow can be set to 0 in order to prevent laptop
    # mode tools from using them to stop data loss sensitive features. Use this
    # when you have a battery that reports the wrong information, that confuses
    # laptop mode tools.
    # Disabling data loss sensitive features is ACPI-ONLY, and it only works if
    # your battery gives off frequent ACPI events to indicate a change in battery
    # level.
    # NOTE: If your battery does NOT give off battery events often enough, you can
    # enable the battery-level-polling module to make this work. Look at the
    # file /etc/laptop-mode/conf.d/battery-level-polling.conf for more information.
    # Disable all data loss sensitive features when the battery level (in % of the
    # battery capacity) reaches this value.
    MINIMUM_BATTERY_CHARGE_PERCENT=3
    # Disable data loss sensitive features when the battery reports its state
    # as "critical".
    DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL=1
    # Controlled hard drives and partitions
    # For spinning down your hard drives, laptop mode will remount file systems and
    # adjust hard drive spindown timeouts. These parameters specify which
    # devices and partitions are affected by laptop mode.
    # The drives that laptop mode controls.
    # Separate them by a space, e.g. HD="/dev/hda /dev/hdb". The default is a
    # wildcard, which will get you all your IDE and SCSI/SATA drives.
    HD="/dev/[hs]d[abcdefgh]"
    # The partitions (or mount points) that laptop mode controls.
    # Separate the values by spaces. Use "auto" to indicate all partitions on drives
    # listed in HD. You can add things to "auto", e.g. "auto /dev/hdc3". You can
    # also specify mount points, e.g. "/mnt/data".
    PARTITIONS="auto /dev/mapper/*"
    # If this is enabled, laptop mode tools will assume that SCSI drives are
    # really SATA drives that only _look_ like SCSI drives, and will use hdparm
    # to control them. Set this to 0 if you have /dev/sd devices and you want
    # laptop mode tools to use the "sdparm" command to control them.
    ASSUME_SCSI_IS_SATA=1
    # Hard drive behaviour settings
    # These settings specify how laptop mode tools will adjust the various
    # parameters of your hard drives and file systems.
    # Maximum time, in seconds, of work that you are prepared to lose when your
    # system crashes or power runs out. This is the maximum time that Laptop Mode
    # will keep unsaved data waiting in memory before spinning up your hard drive.
    LM_BATT_MAX_LOST_WORK_SECONDS=600
    LM_AC_MAX_LOST_WORK_SECONDS=360
    # Should laptop mode tools control readahead?
    CONTROL_READAHEAD=1
    # Read-ahead, in kilobytes. You can spin down the disk while playing MP3/OGG
    # by setting the disk readahead to a reasonable size, e.g. 3072 (3 MB).
    # Effectively, the disk will read a complete MP3 at once, and will then spin
    # down while the MP3/OGG is playing. Don't set this too high, because the
    # readahead is applied to _all_ files that are read from disk.
    LM_READAHEAD=3072
    NOLM_READAHEAD=128
    # Should laptop mode tools add the "noatime" option to the mount options when
    # laptop mode is enabled?
    CONTROL_NOATIME=0
    # Should laptop use relatime instead of noatime? The "relatime" mount option has
    # more standards-compliant semantics, and allows more applications to work,
    # while retaining a low level of atime updates (i.e., disk writes).
    USE_RELATIME=0
    # Should laptop mode tools control the hard drive idle timeout settings?
    CONTROL_HD_IDLE_TIMEOUT=1
    # Idle timeout values. (hdparm -S)
    # Default is 2 hours on AC (NOLM_HD_IDLE_TIMEOUT_SECONDS=7200) and 20 seconds
    # for battery and for AC with laptop mode on.
    LM_AC_HD_IDLE_TIMEOUT_SECONDS=20
    LM_BATT_HD_IDLE_TIMEOUT_SECONDS=20
    NOLM_HD_IDLE_TIMEOUT_SECONDS=7200
    # Should laptop mode tools control the hard drive power management settings?
    # Set to 0 to disable
    CONTROL_HD_POWERMGMT="auto"
    # Power management for HD (hdparm -B values)
    BATT_HD_POWERMGMT=128
    LM_AC_HD_POWERMGMT=254
    NOLM_AC_HD_POWERMGMT=254
    # Should laptop mode tools control the hard drive write cache settings?
    CONTROL_HD_WRITECACHE=0
    # Write cache settings for HD (hdparm -W values)
    NOLM_AC_HD_WRITECACHE=1
    NOLM_BATT_HD_WRITECACHE=0
    LM_HD_WRITECACHE=0
    # Settings you probably don't want to touch
    # It is usually not necessary to change these parameters. They are included
    # for completeness' sake.
    # Change mount options on partitions in PARTITIONS? You don't really want to
    # disable this. If you do, then your hard drives will probably not spin down
    # anymore.
    CONTROL_MOUNT_OPTIONS=1
    # Dirty synchronous ratio. At this percentage of dirty pages the process
    # which calls write() does its own writeback.
    LM_DIRTY_RATIO=60
    NOLM_DIRTY_RATIO=40
    # Allowed dirty background ratio, in percent. Once DIRTY_RATIO has been
    # exceeded, the kernel will wake pdflush which will then reduce the amount
    # of dirty memory to dirty_background_ratio. Set this nice and low, so once
    # some writeout has commenced, we do a lot of it.
    LM_DIRTY_BACKGROUND_RATIO=1
    NOLM_DIRTY_BACKGROUND_RATIO=10
    # kernel default settings -- don't touch these unless you know what you're
    # doing.
    DEF_UPDATE=5
    DEF_XFS_AGE_BUFFER=15
    DEF_XFS_SYNC_INTERVAL=30
    DEF_XFS_BUFD_INTERVAL=1
    DEF_MAX_AGE=30
    # This must be adjusted manually to the value of HZ in the running kernel
    # on 2.4, until the XFS people change their 2.4 external interfaces to work in
    # centisecs. This can be automated, but it's a work in progress that still
    # needs some fixes. On 2.6 kernels, XFS uses USER_HZ instead of HZ for
    # external interfaces, and that is currently always set to 100. So you don't
    # need to change this on 2.6.
    XFS_HZ=100
    # Seconds laptop mode has to to wait after the disk goes idle before doing
    # a sync.
    LM_SECONDS_BEFORE_SYNC=2
    cpufreq.conf
    # Configuration file for Laptop Mode Tools module cpufreq.
    # For more information, consult the laptop-mode.conf(8) manual page.
    # CPU frequency scaling and throttling
    # Laptop mode tools can automatically adjust your kernel CPU frequency
    # settings. This includes upper and lower limits and scaling governors.
    # There is also support for CPU throttling, on systems that don't support
    # frequency scaling.
    # This feature only works on 2.6 kernels.
    # IMPORTANT: In versions 1.36 and earlier, these settings were included in the
    # main laptop-mode.conf configuration file. If they are still present, they
    # overrule the settings in this file. To fix this, simply delete the settings
    # from the main config file.
    # Enable debug mode for this module
    # Set to 1 if you want to debug this module
    DEBUG=0
    # Should laptop mode tools control the CPU frequency settings?
    # Set to 0 to disable
    CONTROL_CPU_FREQUENCY="auto"
    # Legal values are "slowest" for the slowest speed that your
    # CPU is able to operate at, "fastest" for the fastest speed,
    # "medium" for some value in the middle, or any value listed in
    # /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies.
    # The "governor" can be any governor installed on your system, this usually
    # includes "ondemand", "conservative", and "performance". The
    # "IGNORE_NICE_LOAD" setting specifies that background programs that have
    # a low priority ("nice level") should not cause the CPU frequency to
    # be increased. (You generally want this to be enabled in battery mode.)
    BATT_CPU_MAXFREQ=fastest
    BATT_CPU_MINFREQ=slowest
    BATT_CPU_GOVERNOR=ondemand
    BATT_CPU_IGNORE_NICE_LOAD=1
    LM_AC_CPU_MAXFREQ=fastest
    LM_AC_CPU_MINFREQ=slowest
    LM_AC_CPU_GOVERNOR=ondemand
    LM_AC_CPU_IGNORE_NICE_LOAD=1
    NOLM_AC_CPU_MAXFREQ=fastest
    NOLM_AC_CPU_MINFREQ=slowest
    NOLM_AC_CPU_GOVERNOR=ondemand
    NOLM_AC_CPU_IGNORE_NICE_LOAD=0
    # Should laptop mode tools control the CPU throttling? This is only useful
    # on processors that don't have frequency scaling.
    # (Only works when you have /proc/acpi/processor/CPU*/throttling.)
    # This is only useful on older P4 processors that do not support frequency
    # scaling. On such processors, this is the only way to reduce power consumption
    # but at the cost of higher performance penalty.
    # Enable this only if you have a processor that does not support frequency scaling
    # On most new processors, you might want to disable it.
    # Set to 0 to disable.
    CONTROL_CPU_THROTTLING=0
    # Legal values are "maximum" for the maximum (slowest) throttling level,
    # "minimum" for minimum (fastest) throttling level, "medium" for a value
    # somewhere in the middle (this is usually 50% for P4s), or any value listed
    # in /proc/acpi/processor/CPU*/throttling. Be careful when using "maximum":
    # this may be _very_ slow (in fact, with P4s it slows down the processor
    # by a factor 8).
    BATT_CPU_THROTTLING=medium
    LM_AC_CPU_THROTTLING=medium
    NOLM_AC_CPU_THROTTLING=minimum
    battery-level-polling.conf
    # Configuration file for Laptop Mode Tools module battery-level-polling.
    # For more information, consult the laptop-mode.conf(8) manual page.
    # Battery level polling settings
    # This module allows laptop mode to react to battery level changes, even if the
    # battery does not send out frequent ACPI events for such battery level changes.
    # Note that this does NOT make ACPI-only features work on non-ACPI hardware.
    # Enable debug mode for this module
    # Set to 1 if you want to debug this module
    DEBUG=0
    # Enable this setting to enable battery level polling.
    ENABLE_BATTERY_LEVEL_POLLING=1
    hal-polling.conf
    # Configuration file for Laptop Mode Tools module hal-polling.
    # For more information, consult the laptop-mode.conf(8) manual page.
    # HAL polling settings
    # If you enable this module, laptop mode tools will control the polling of
    # your CD/DVD drives by HAL. Disabling polling saves a considerable amount of
    # power, but for some older CD/DVD drives it means that inserted CDs are no
    # longer autodetected. In such cases, you must turn this option off.
    # Alternatively, you can configure laptop mode tools to turn HAL polling on only
    # when the laptop is running on AC power. This would mean that CDs are not
    # autodetected while the laptop is running on battery power, but the power
    # savings may be worth the extra manual labour when you insert a CD.
    # Enable debug mode for this module
    # Set to 1 if you want to debug this module
    DEBUG=0
    # Control HAL polling?
    # Set to 0 to disablei, vs "auto".
    CONTROL_HAL_POLLING=0
    # Disable HAL polling on battery?
    BATT_DISABLE_HAL_POLLING=0
    # Disable HAL polling on AC?
    AC_DISABLE_HAL_POLLING=0
    # Drives to apply HAL polling settings to
    HAL_POLLING_DEVICES="/dev/scd?"
    Please let me know if you require any additional information. Thank you in advance for any help.
    Last edited by Aesir (2011-04-14 14:35:09)

    Aesir wrote:Can I make BATT_CPU_GOVERNOR=conservative even if it is not listed in the scaling_available_governors file?
    If your governor isn't listed in scaling_available_governors, it won't work.  See stqn's link for info on adding governors.
    stqn wrote:Edit2: oh well, scrolling a bit up, the wiki says you don't need to add governors if you're using laptop-mode-tools... I don't know.
    You do need governors if you're using laptop-mode-tools, because all laptop-mode-tools does is flip between them automatically.
    If you're using cpufrequtils, you'll need the userspace governor for it to work properly.  I don't use cpufrequtils personally, so I'm not sure how to get it to work in conjunction with laptop-mode-tools.  You may have to disable frequency scaling in laptop-mode-tools by changing CONTROL_CPU_FREQUENCY to 0 in cpufreq.conf
    Edit - now that I think about it, maybe laptop-mode-tools and cpufrequtils know how to load the modules themselves automatically.  I guess try it and see if they can.  You can check which governor is in use with:
    $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    You can also manually change governors by running (as root):
    #  echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    Of course, substitue the governor you want.
    Last edited by redden0t8 (2011-03-29 19:27:12)

  • How to Define Specific CPU Frequency in Laptop Mode Tools?

    I would like to know how to set a specific maximum and minimum frequency for Laptop Mode Tools. Here is my /etc/laptop-mode/conf.d/cpufreq.conf:
    # Configuration file for Laptop Mode Tools module cpufreq.
    # For more information, consult the laptop-mode.conf(8) manual page.
    # CPU frequency scaling and throttling
    #__COMMENT Laptop mode tools can automatically adjust your kernel CPU frequency
    #__COMMENT settings. This includes upper and lower limits and scaling governors.
    #__COMMENT There is also support for CPU throttling, on systems that don't support
    #__COMMENT frequency scaling.
    #__COMMENT
    #__COMMENT This feature only works on 2.6 kernels.
    #__COMMENT
    #__COMMENT
    #__COMMENT IMPORTANT: In versions 1.36 and earlier, these settings were included in the
    #__COMMENT main laptop-mode.conf configuration file. If they are still present, they
    #__COMMENT overrule the settings in this file. To fix this, simply delete the settings
    #__COMMENT from the main config file.
    # Enable debug mode for this module
    # Set to 1 if you want to debug this module
    DEBUG=0
    # Should laptop mode tools control the CPU frequency settings?
    # Set to 0 to disable
    CONTROL_CPU_FREQUENCY="auto"
    # Legal values are "slowest" for the slowest speed that your
    # CPU is able to operate at, "fastest" for the fastest speed,
    # "medium" for some value in the middle, or any value listed in
    # /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies.
    # The "governor" can be any governor installed on your system, this usually
    # includes "ondemand", "conservative", and "performance". The
    # "IGNORE_NICE_LOAD" setting specifies that background programs that have
    # a low priority ("nice level") should not cause the CPU frequency to
    # be increased. (You generally want this to be enabled in battery mode.)
    BATT_CPU_MAXFREQ=fastest
    BATT_CPU_MINFREQ=slowest
    BATT_CPU_GOVERNOR=ondemand
    BATT_CPU_IGNORE_NICE_LOAD=1
    LM_AC_CPU_MAXFREQ=fastest
    LM_AC_CPU_MINFREQ=slowest
    LM_AC_CPU_GOVERNOR=ondemand
    LM_AC_CPU_IGNORE_NICE_LOAD=1
    NOLM_AC_CPU_MAXFREQ=fastest
    NOLM_AC_CPU_MINFREQ=slowest
    NOLM_AC_CPU_GOVERNOR=ondemand
    NOLM_AC_CPU_IGNORE_NICE_LOAD=0
    # Should laptop mode tools control the CPU throttling? This is only useful
    # on processors that don't have frequency scaling.
    # (Only works when you have /proc/acpi/processor/CPU*/throttling.)
    # This is only useful on older P4 processors that do not support frequency
    # scaling. On such processors, this is the only way to reduce power consumption
    # but at the cost of higher performance penalty.
    # Enable this only if you have a processor that does not support frequency scaling
    # On most new processors, you might want to disable it.
    # Set to 0 to disable.
    CONTROL_CPU_THROTTLING=0
    # Legal values are "maximum" for the maximum (slowest) throttling level,
    # "minimum" for minimum (fastest) throttling level, "medium" for a value
    # somewhere in the middle (this is usually 50% for P4s), or any value listed
    # in /proc/acpi/processor/CPU*/throttling. Be careful when using "maximum":
    # this may be _very_ slow (in fact, with P4s it slows down the processor
    # by a factor 8).
    BATT_CPU_THROTTLING=medium
    LM_AC_CPU_THROTTLING=medium
    NOLM_AC_CPU_THROTTLING=minimum
    I have a new Intel Haswell CPU, so I know that CPU throttling isn't applicable to me. In the section about scaling, how do I set a specific GHz or MHz value for the minimum and maximum CPU?
    Thanks

    No, I just want to save battery power. I don't want the CPU to be clocked as high when I'm on battery. I would set the CPUFreq governor to ondemand, but when I issue sudo cpupower frequency-set -g ondemand, I get:
    Setting cpu: 0
    Error setting new values. Common errors:
    - Do you have proper administration rights? (super-user?)
    - Is the governor you requested available and modprobed?
    - Trying to set an invalid policy?
    - Trying to set a specific frequency, but userspace governor is not available,
    for example because of hardware which cannot be set to a specific frequency
    or because the userspace governor isn't loaded?
    The output of ls /lib/modules/$(uname -r)/kernel/drivers/cpufreq/ is:
    acpi-cpufreq.ko.gz cpufreq_stats.ko.gz powernow-k8.ko.gz
    amd_freq_sensitivity.ko.gz cpufreq_userspace.ko.gz speedstep-lib.ko.gz
    cpufreq_conservative.ko.gz p4-clockmod.ko.gz
    cpufreq_powersave.ko.gz pcc-cpufreq.ko.gz
    Doing modprobe cpufreq_ondemand and trying again does nothing.
    So, since I can't use the ondemand governor and then raise the threshold, I need to limit the CPU frequency.
    Thanks.

  • [solved][laptop-mode-tools] hard drive power settings not applied

    I've used the laptop-mode-tools now for quite some time. However, recently the power management settings are not applied anymore. Possibly since updating to systemd...
    My laptop-mode.conf looks as follows:
    CONTROL_HD_POWERMGMT=1
    # Power management for HD (hdparm -B values)
    BATT_HD_POWERMGMT=254
    LM_AC_HD_POWERMGMT=254
    NOLM_AC_HD_POWERMGMT=254
    However, even after doing a systemctl restart laptop-mode-tools.service I always get
    $ sudo hdparm -B /dev/sda
    /dev/sda:
    APM_level = 96
    Setting it manually works:
    $ sudo hdparm -B 254 /dev/sda
    /dev/sda:
    setting Advanced Power Management level to 0xfe (254)
    APM_level = 254
    $ sudo hdparm -B /dev/sda
    /dev/sda:
    APM_level = 254
    Of course, the settings are lost upon rebooting in this case.
    Any idea where the problem could be?
    Last edited by rggjan (2012-10-08 12:25:04)

    I apologize if it is bad style to answer to a post marked as [solved] but:
    Same problem here!
    HDParm-settings are not applied on boot by LMT.
    laptop-mode.conf:
    # Should laptop mode tools control the hard drive power management settings?
    # Set to 0 to disable
    CONTROL_HD_POWERMGMT="auto"
    # Power management for HD (hdparm -B values)
    BATT_HD_POWERMGMT=100
    LM_AC_HD_POWERMGMT=200
    NOLM_AC_HD_POWERMGMT=254
    # hdparm -B /dev/sda
    /dev/sda:
    APM_level = 96
    Any ideas or solutions on this so far?
    And why is this post marked as 'solved'?
    edit:
    1.) manual set hdparm-settings survive reboot but not suspend!
    2.) no difference between CONTROL_HD_POWERMGMT="auto" or "1"
    3.)
    # systemctl status laptop-mode
    laptop-mode.service - Laptop Mode Tools
    Loaded: loaded (/usr/lib/systemd/system/laptop-mode.service; enabled)
    Active: active (exited) since Do 2013-01-24 14:05:20 CET; 8min ago
    Process: 664 ExecStart=/usr/sbin/laptop_mode init auto (code=exited, status=0/SUCCESS)
    4.) pointed out that this seems to be a bug: https://bugs.archlinux.org/task/33262 as systemd does not restore apm values on wake up.
    Last edited by renegat (2013-03-09 11:01:42)

  • Laptop-mode-tools and hdparm -B settings

    Since the change to systemd (I think so), I have a problem with laptop-mode-tools and hdparm. The hdparm -B settings (settings to park the hard drive) are most of the times not applied on startup of my laptop. But: sometimes the setting in the config file of laptop-mode-tools is applied.
    These configs I have in /etc/laptop-mode/laptop-mode.conf:
    # Power management for HD (hdparm -B values)
    BATT_HD_POWERMGMT=254
    LM_AC_HD_POWERMGMT=254
    NOLM_AC_HD_POWERMGMT=254
    If I check the settings of hdparm after starting my laptop (sudo hdparm -B /dev/sda), most of the times the setting is 128. Because I am afraid that my hard drive will damage with this setting, every time I have to do 'sudo systemctl restart laptop-mode.service'. After that, the setting of hdparm -B is 254.
    Does anybody know something to solve this annoying problem? Thanks in advance!

    You could write an udev rule. That's what I did, although laptop-mode-tools was giving me the same result - I just wanted to reduce the list of services for the sake of boot speed.
    Mine looks like this:
    /etc/udev/rules.d/75-hdparm.rules
    ACTION=="add", KERNEL=="sda", ATTR{queue/rotational}=="1", RUN+="/sbin/hdparm -B 254 /dev/$kernel"
    You might have to change "sda" according to your system.
    Disclaimer (and friendly hint): I didn't come up with this by myself, I had to borrow it from somewhere on this forum.
    Edit: from here, but you can also find it there.
    Last edited by sano (2013-04-04 23:53:09)

  • Laptop-mode-tools fixes and improvements

    I have been in contact with the autor of laptop-mode-tools and new version is coming some time next month or maybe even in March. So I decided to share my tweaks because some things are broken right now and some need improvements.
    There are some modules I don't use and so didn't notice any problems with them, if there are any (lcd-brightness, video-out and those for which I don't have suitable hardware like cpufreq, iwl/ipw and sched-mc).
    Alright then, first is the problem with systems where the battery doesn't report events and has no alarm support on which the auto-hibernate module depends. There is a script from gentoo-wiki which is quite popular among people with lousy batteries. It would be great if the package manager would take care of it for us. Author of laptop-mode-tools also said (on debian lists) that such script could be included in future versions, for now the common "solution" is to create a cronjob that calls /usr/sbin/laptop_mode every few minutes. I don't quite like it compared to the gentoo script. For now I include the script in the package as /usr/sbin/battery_mode and call it from rc.local on boot.
    Currently there is a module called ac97-powersave that controls power management on those sound cards. Intel HDA sound cards also support this and in the future versions a module them will probably be included. For now I patch the ac97-powersave module to include the support for Intel HDA.
    Bluetooth module removes bluetooth and hci_usb modules when disabling the device. However on my system it's not enough to completly turn it off. For now I patch the bluetooth module to include rfkill support. Only then the system reports a USB disconnect and the LED goes off. The default path in the patch is for my acer system with acer-wmi rfkill support.
    Due to w differences the dpms-standby module is broken on many systems. The module uses xset and arguments are piped from the command w -hs where the third field is supposed to be DPMS_SCREEN but it's actually IDLE time, so xset command fails because the argument passed to xset -d is something like 4:54. On Debian/Ubuntu they went around this by including this in their acpi-support package. I didn't bother to see what they actually did, to backport it. It should be done in future laptop-mode-tools anyway. For now I just hardcode the display value for my single-user/one-X-screen system in the dpms-standby module.
    Due to a simple mistake LM_VERBOSE was broken. Meaning that none of those informative status messages from laptop-mode-tools were logged when VERBOSE LOGGING was enabled. Only the output of called commands was logged. For now I fix this in the build process.
    Speaking of logging, default output for verbose is /dev/stdout, and I would like to log everything to a file. So I modify it in the build process to log everything to /var/log/laptop-mode.log, and also include a logrotate script in the package. With the above fix I have a complete and informative log file.
    It's not a bad idea to stop/restart laptop-mode-tools when suspending, so a pm-utils hook is helpful. Arch PKGBUILD already includes installing pm-utils support but it's actually pbbuttonsd/pmud support and not pm-utils. Such a script/hook could one day be included in laptop-mode-tools however there is/was a debate going if it's their job to provide it. I read somewhere that Ubuntu already provides such script/hook but I'm not sure if it's provided by acpi-support or laptop-mode-tools package. For now I wrote my own pm-utils hook and I include it in the build process.
    Powertop suggests usbcore.autosuspend=1 sysctl, but it would be nice if we have all this power management control in one place. Usb-autosuspend module will be included in future versions of laptop-mode-tools, but for now someone wrote a module and posted it to the Debian bug tracker. I keep the module and configuration in my build dir but don't include it in the final package for now. I'll wait a bit and see how things will develop.
    To help you start hacking on laptop-mode-tools you can take a look at all the above patches and my PKGBUILD. Every step is documented in PKGBUILD comments, and please do check them because some things I patch but some I modify inline with sed. I also don't install acpid handlers and before mentioned false pm-utils support... everything is commented: http://sysphere.org/~anrxc/local/softwa … ode-tools/

    Hello,
    this was one year ago, and I helped the author improve these things. Today I don't have to patch my laptop-mode-tools... (I still do with some minor things, but that's just to satisfy some personal preferences . Use the arch package, even the battery polling helper is included.

  • Laptop-mode-tools no longer adjusts LCD brightness

    I just discovered that laptop-mode-tools no longer adjusts the brightness of the LCD when switched to battery. This is not a general issue. laptop-mode is active on battery (as well as being enabled via the systemd service), the computer knows it is on battery (checking with on_ac_power and reading from /sys/class/power_supply/*/* give the expected results) and other things are correctly adjusted e.g. bluetooth is blocked with rfkill. Moreover, as root I can adjust the brightness in the usual way by hand:
    echo 10 >| /sys/class/backlight/acpi_video0/brightness
    works just fine. The >| is needed because for interactive shell's, root's .bashrc sets noclobber. This obviously doesn't affect laptop-mode tools because it doesn't run an interactive shell. In contrast:
    $ cat /etc/laptop-mode/conf.d/lcd-brightness.conf | grep -v "^#"
    DEBUG=1
    CONTROL_BRIGHTNESS=1
    BATT_BRIGHTNESS_COMMAND="echo 7"
    LM_AC_BRIGHTNESS_COMMAND="echo 10"
    NOLM_AC_BRIGHTNESS_COMMAND="echo 12"
    BRIGHTNESS_OUTPUT="/sys/class/backlight/acpi_video0/brightness"
    DEBUG wasn't 1 when the problem started. I tried setting it to get more info but haven't found anything more in the journal/logs.
    KDE is set to not touch the default brightness at all. All it does is (further) dim the display after so many minutes depending on the power supply and status.
    This did work fine but I haven't been on battery for a while so I'm not sure when exactly it stopped working. My brightness is set by default to 12 on boot or wake from sleep which suggests laptop-mode tools does something or something else is now handling this which I'm not aware of. But the switch to battery does not trigger any alteration in the brightness and laptop-mode status does not even mention LCD brightness as one of the things laptop-mode tools controls.
    Have I missed a change in how this is handled somewhere?

    I doubt this is related but it is currently my only lead so here goes. I set the LCD brightness control for debug so I've been trying to watch it. However, so far it is all smiles e.g. on boot it all works fine and says so.
    However, I found I'm getting another error on boot which is
    /usr/share/laptop-mode-tools/modules/pcie-aspm: line 10: write error: Operation not permitted
    Note that I copied that by eye from VT1 so if a colon is out of place, that's why.
    The contents of that file is:
    #! /bin/sh
    # Laptop mode tools module: PCIe Active State Power Management
    if [ x$CONTROL_PCIE_ASPM = x1 ] || [ x$ENABLE_AUTO_MODULES = x1 -a x$CONTROL_PCIE_ASPM = xauto ]; then
    if [ $ON_AC -eq 1 ]; then
    log "VERBOSE" "On AC power: setting pcie_aspm to default"
    if [ -f /sys/module/pcie_aspm/parameters/policy ]; then
    echo default > /sys/module/pcie_aspm/parameters/policy
    if [ $? -eq 0 ]; then
    log "VERBOSE" "PCIe ASPM set to 'default'"
    else
    log "VERBOSE" "PCIe ASPM tweaking is prohibited by the kernel"
    fi
    else
    log "VERBOSE" "PCIe ASPM is not available"
    fi
    else
    log "VERBOSE" "On battery: setting pcie_aspm to powersave"
    if [ -f /sys/module/pcie_aspm/parameters/policy ]; then
    echo powersave > /sys/module/pcie_aspm/parameters/policy
    if [ $? -eq 0 ]; then
    log "VERBOSE" "PCIe ASPM set to 'powersave'"
    else
    log "VERBOSE" "PCIe ASPM tweaking is prohibited by the kernel"
    fi
    else
    log "VERBOSE" "PCIe ASPM is not available"
    fi
    fi
    else
    log "VERBOSE" "PCIe ASPM power savings module is disabled"
    fi
    So I assume it is saying it cannot write to /sys/module/pcie_aspm/parameters/policy but the permissions etc. on that, at least, don't look strange:
    l /sys/module/pcie_aspm/parameters/
    total 0
    drwxr-xr-x 2 root root 0 Gor 25 21:24 ./
    drwxr-xr-x 3 root root 0 Gor 25 21:23 ../
    -rw-r--r-- 1 root root 4.0K Gor 25 21:24 policy
    Last edited by cfr (2013-07-25 20:47:13)

  • Acpid vs dbus vs laptop-mode-tools - What's the relationship?

    I disabled acpid from daemons, and uninstalled it, and to my surprise, the Suspend option still appears in the XFCE4 logout window, and when I open the lid the lappy comes right back. I had been under the impression that acpid was required for actions to take place on lid open/close. After a bit more research it appears that acpid is nothing more than a daemon that watches /proc and /sys for power and laptop related events, and that any daemon can do this, and in fact, cpufrequtils is such a daemon that just has a subset of events that it watches.
    Then I noticed today that on my Arch that when I close the lid, my LCD brightness goes down, and I have to use the function keys to bring brightness back. If I don't have acpid or laptop-mode-tools installed, I assume that dbus is handling this dimming? Or the hardware BIOS?
    Why isn't dbus handling things like AC adapter plugging and unplugging, and button events? Is there any reason to use acpid at all these days?

    Confirmed that like pogeymanz, laptop-mode-tools really does nothing without acpid. I guess it will set some of the other static values for devices listed in /etc/laptop-mode/conf.d/ but that's it. Tested by setting laptop-mode-tools to change the cpu scaling governor to powersave on battery, disabling acpid and unplugging laptop, then running cpufreq-info. No change.
    Then started acpid again from the init script, plug and unplug, now governor is powersave.
    It appears that acpid is a hard dependency, and that package should really be changed to fix that. If you look at the file list, there are 6 scripts placed into /etc/acpi/events/
    etc/acpi/actions/lm_ac_adapter.sh
    etc/acpi/actions/lm_battery.sh
    etc/acpi/actions/lm_lid.sh
    etc/acpi/events/lm_ac_adapter
    etc/acpi/events/lm_battery
    etc/acpi/events/lm_lid
    So laptop-mode-tools isn't even watching the acpid socket itself (/var/run/acpid.socket), and it relies solely on acpid to tell it about AC and lid status, so any configuration that you do in laptop-mode-tools that depends on checking for normal status changes on a notebook computer will fail to change anything without acpid installed and running.

Maybe you are looking for