Laptop mode lowers LCD brightness when on AC [SOLVED]

I have configured laptop-mode to turn LCD brightness to half of max value when on battery. Everything works fine. When disconnect my laptop from the power source it automatically lowers LCD brightness and when back on AC it comes back to max value. The problem I have is when coming back to AC and only if I leave the laptop unattended for awhile and then move the mouse or touch any button it lowers LCD brightness to what its supposed to be when on battery!!
I don't know whether this is a bug or a misconfigured file. Here is my laptop-mode LCD brightness configuration:
# Commands to execute to set the brightness on your LCD
BATT_BRIGHTNESS_COMMAND="echo 12"
LM_AC_BRIGHTNESS_COMMAND="echo 24"
NOLM_AC_BRIGHTNESS_COMMAND="echo 24"
BRIGHTNESS_OUTPUT="/sys/class/backlight/acpi_video0/brightness"
Any help will be appreciated!!!
Thanks in advanced, José.
Last edited by boina (2011-10-10 00:29:26)

OK, seems it was some kind of a bug because after today's full system upgrade I'm not able to reproduce the problem I posted before, Thanks sad clown for your help!!

Similar Messages

  • Laptop-mode / laptop-mode-tools lcd brightness issue

    I have an issue with my lcd brightness config in laptop-mode tools
    here is the brightness values
    [venky@ARCHROCKS ~]$ cat /proc/acpi/video/VID/LCD/brightness
    levels: 72 24 12 24 36 48 60 72 84 100
    current: 72
    [venky@ARCHROCKS ~]$
    following is my lcd-bightness.conf file under /etc/laptop-mode/conf.d
    # Configuration file for Laptop Mode Tools module lcd-brightness.
    # For more information, consult the laptop-mode.conf(8) manual page.
    # LCD brightness settings
    # Using these settings, you can make laptop mode tools automatically adjust
    # your LCD's brightness settings. The settings are extremely simple -- they
    # only allow for the execution of a command, nothing more. The reason for this
    # is that LCD brightness settings are very different between laptop vendors.
    # Suggestions for commands:
    # * If your system has the file "/proc/acpi/video/VID/LCD/brightness" (VID may
    # be VID1 or similar), use this file as BRIGHTNESS_OUTPUT, and use
    # the command "echo <value>". The possible values can be listed using the
    # command:
    # cat /proc/acpi/video/VID/LCD/brightness
    # * If you have a file /sys/class/backlight/.../brightness, then you can use
    # that file as BRIGHTNESS_OUTPUT, and the command "echo <value>".
    # As far as I understand it the values are between 0 and
    # the value contained in the file /sys/class/backlight/.../max_brightness.
    # * For Toshiba laptops, use the command "toshset" with the -lcd or -inten
    # command. Read the toshset(1) manual page for more information on the
    # parameters for this command. If you use this command, set
    # BRIGHTNESS_OUTPUT to "/dev/null".
    # 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.
    # Should laptop mode tools control LCD brightness?
    CONTROL_BRIGHTNESS=1
    # Commands to execute to set the brightness on your LCD
    BATT_BRIGHTNESS_COMMAND="echo 24"
    LM_AC_BRIGHTNESS_COMMAND="echo 100"
    NOLM_AC_BRIGHTNESS_COMMAND="echo 72"
    BRIGHTNESS_OUTPUT="/proc/acpi/video/VID/LCD/brightness"
    so basically while in AC power i want full brightness when on battery i want one notch more than the minimum brightness and when laptop-mode is not running i want 2 notches less than maximum brightness.
    the battery mode works fine when i unplug the computer but when i replug the AC power it goes to 72 instead of 100. I mean laptop mode is running coz when I remove ac power it goes to 24 again.
    Am I doing something wrong?

    When you plug in AC power, laptop-mode probably turns down, so LCD brightness is set to 72. It depends on if you have set in /etc/laptop-mode/laptop-mode.conf ENABLE_LAPTOP_MODE_ON_AC to 0 or 1.

  • LCD Brightness is lowered when touching mouse or keyboard

    Hi Guys,
    hopefully, the newbie corner is the right place to post this, at least I am one, just switching from ubuntu to arch.
    Essentially I have the problem marked as solved here: https://bbs.archlinux.org/viewtopic.php?id=127818
    For me, however, it is not solved. I don't think it is related to laptop-mode, but I don't know. I am using my laptop on AC only.  If I leave the laptop unattended for a while and then move the mouse or touch any button it lowers LCD brightness. The laptop buttons for brightness do work. I really don't know which program is doing this and neither why.
    Since the system is pretty much unusable in this state, I did a workaround by taking away file privileges (chmod 444 /sys/class/backlight/nv_backlight/brightness).this has been overridden by the system after reboot, too.
    I am using a fresh install with gnome.
    Thank you very much in advance for any clues how to solve this.
    Karsten
    Last edited by karsten_m (2011-10-19 21:06:01)

    Ok, the / of all the strange behaviour was gnome-power-manager.
    Unfortunately I wasn't able to get to core of why it dims the screen, but the workaround is this: define the dimmed brightness as 100..
    You can do this by running
    dconf write /org/gnome/settings-daemon/plugins/power/idle-brightness 100
    It does the trick.
    If anyone's got a better idea - let it out...

  • Laptop-mode doesn't want to start when work on AC

    Hi all,
    I've noticed, than dispite I've set ENABLE_LAPTOP_MODE_ON_AC variable in /etc/laptop-mode/laptop-mode.conf on 1, when I'm switching on my laptop being on AC power, laptop-mode is not actually activated.
    So, if I check /proc/sys/vm/laptop-mode, I'll get 0 value. After rc.d restart laptop-mode or after workin on battery, everything is ok, and cat /proc/sys/vm/laptop-mode prints 2.
    Does anyone faced with this problem? May be, there is a way to make laptop-mode daemon do restart on system boot?
    Thank you!

    flan_suse wrote:Do you have acpid installed and acpid in your DAEMONS array? I would also place acpid before laptop-mode in the DAEMONS array.
    Sure.
    But today I've noticed, that laptop-mode is actually running before I login KDE. Looks like a problem is in KDE power management tools.

  • 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.

  • Trouble with Laptop-Mode-Tools, AC Plug-In

    I can't get Laptop-Mode-Tools to recognize when I plug my AC in, I have options for "AC_" as it says are allowed in the man page and ArchWiki, although there are no examples of just having the prefix "AC_".
    However, it says it should behave in the same way as "BATT_" does, independant of the laptop-mode status.
    I have LM enabled for AC in laptop-mode.conf, and acpi_listen has output for the AC in/out.   My current workaround is to have it as it is, with "LM_AC_*", but having entries for exclusively battery and AC is easier for me as I plan to always keep Laptop-Mode-Tools enabled.
    Is there something I misconfigured, or may I have misunderstood the manual/wiki?
    Alternatively, how would I go about debugging? I noticed there was a variable enabling debugging, but I couldn't find where the debugging output occurs.  I am a little new with regards to standard debugging practice.
    Last edited by mellowmaroon (2012-10-03 06:23:05)

    I'm terribly sorry, I fixed everything I had made bold.  I was trying to make the technical things stand out for people that were just glancing at the post. But you're absolutely right, I should have used more discretion.
    As for the configuration, I did not expect it to magically do what I want.  I will provide a more concrete example of what I am talking about, if it helps.
    In /etc/laptop-mode/conf.d/lcd-brightness.conf, I have BATT_BRIGHTNESS_COMMAND="echo 0".  This works: when I unplug AC, 0 gets output to /sys/class/backlight/acpi_video0/brightness.
    However, when I attempt AC_BRIGHTNESS_COMMAND="echo 15" (less than /sys/class/backlight/acpi_video0/max_brightness, hopefully demonstrating my reading of laptop-mode.conf), it is unsuccessful.  Instead, I currently use LM_AC_BRIGHTNESS_COMMAND="echo 15" as a workaround.  BATT_BRIGHTNESS_COMMAND works without editing /etc/acpid/handler.sh, I was simply wondering why the AC counterpart does not.
    I hope I have now supplied enough information now allows us to be on the same page, and I apologize again for the offensive formatting.

  • [SOLVED] Changing cpufreq governors and brightness when AC unplugged

    I can't seem to figure out how to make it so when I unplug the AC power source from my laptop commands are run that change the cpufreq governor and change the brightness with nvclock.
    Specifically, I want to have my laptop running cpufreq as ondemand while on AC power and powersave while on Battery power. I also want the command
    nvclock -S 30
    to be run when the AC is unplugged. Then, when it's plugged in again, I want this run:
    nvclock -S 90
    This is my /etc/acpi/handler.sh. I've been experimenting with it and following numerous guides and tips I've googled, I've read as much as I can about laptops and acpi in the arch wiki, but I just can't seem to get these commands run properly.
    #!/bin/sh
    # Default acpi script that takes an entry for all actions
    # NOTE: This is a 2.6-centric script. If you use 2.4.x, you'll have to
    # modify it to not use /sys
    minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
    maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
    setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
    set $*
    case "$1" in
    button/power)
    #echo "PowerButton pressed!">/dev/tty5
    case "$2" in
    PWRF) logger "PowerButton pressed: $2" ;;
    *) logger "ACPI action undefined: $2" ;;
    esac
    button/sleep)
    case "$2" in
    SLPB) echo -n mem >/sys/power/state ;;
    *) logger "ACPI action undefined: $2" ;;
    esac
    ac_adapter)
    case "$2" in
    AC)
    case "$4" in
    00000000)
    echo "powersave" >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    echo -n $minspeed >$setspeed
    nvclock -S 30
    #/etc/laptop-mode/laptop-mode start
    00000001)
    echo "ondemand" >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    echo -n $maxspeed >$setspeed
    nvclock -S 90
    #/etc/laptop-mode/laptop-mode stop
    esac
    *) logger "ACPI action undefined: $2" ;;
    esac
    battery)
    case "$2" in
    BAT0)
    case "$4" in
    00000000) #echo "offline" >/dev/tty5
    00000001) #echo "online" >/dev/tty5
    esac
    CPU0)
    *) logger "ACPI action undefined: $2" ;;
    esac
    button/lid)
    #echo "LID switched!">/dev/tty5
    logger "ACPI group/action undefined: $1 / $2"
    esac
    I would think the ac_adapter) part is the most relevant, but I posted the whole thing just in case something else needed to be done.
    Thanks for any help. Also, if there's a better way to accomplish the same thing, please let me know.
    P.S. I have laptop-mode-tools installed, but there is very little documentation and following forum posts to try to find what I want is more difficult than I thought. If posting any config files relating to that would help, I'll do that too.
    Last edited by Allamgir (2009-07-05 00:33:10)

    So I finally put together some scripts with the help of google that work properly with start/stop, but laptop-mode-tools doesn't use it for some reason. Here is the script I put in /etc/laptop-mode/batt-start called brightness.sh:
    case "$1" in
    'start')
    sh /home/agi/.bin/brightness-low.sh
    'stop')
    sh /home/agi/.bin/brightness-high.sh
    'restart')
    echo "Usage: $0 [start|stop]""
    esac
    What this does is run scripts that change the brightness found in my ~/.bin directory with start (to lower brightness) and stop (to raise it again). Here is brightness-low.sh:
    nvclock -S 30
    as you can see it's very simple. Just the command. brightness-high.sh is similar:
    nvclock -S 90
    Now, the strange part is that if I run brightness.sh in a terminal, it works perfectly:
    $ sh /etc/laptop-mode/batt-start/brightness.sh start
    Changing Smartdimmer level from 25% to 30%
    New Smartdimmer level: 30%
    $ sh /etc/laptop-mode/batt-start/brightness.sh stop
    Changing Smartdimmer level from 30% to 90%
    New Smartdimmer level: 90%
    I only put my brightness.sh script in batt-start and not nolm-ac-stop or anything because the config file says anything in *-start will be started on entry into the state and stopped on exit.
    Now I'm completely confused. It seems as if I've done all I know to get this to work, rebooted every time, yet when I unplug my laptop, the brightness remains the same.

  • Pm stuff or laptop-mode crazy?

    What happened? I updated my system awhile ago, then pm stuff or laptop-mode went bonkers. When I press power button, my laptop goes to sleep (as it should), after wake it powers off almost instantly.
    Here's some info on my system:
    $ inxi -xxxSM
    System: Host: Mieu Kernel: 3.3.7-1-ARCH x86_64 (64 bit, gcc: 4.7.0) Desktop: Awesome 3.4.11 Distro: Arch Linux
    Machine: System: Acer product: Aspire 1810TZ version: v1.3314
    Mobo: Acer model: JM11-MS Bios: INSYDE version: v1.3314 date: 08/31/2010
    $ pacman -Q laptop-mode-tools pm-utils
    laptop-mode-tools 1.61-1
    pm-utils 1.4.1-5
    $ lspci
    00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
    00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
    00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
    00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
    00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
    00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
    00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
    00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
    00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
    00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
    00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
    00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
    00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
    00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
    00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
    00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
    01:00.0 Ethernet controller: Atheros Communications Inc. AR8131 Gigabit Ethernet (rev c0)
    02:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000

    RedScare wrote:
    What is the real difference between these tools apart from the conveniences they have installed? My understanding is that ACPID runs scripts when the battery is plugged in and when not plugged in, and pm-utils and laptop-mode-tools just come with different sets of these scripts bundled with them.
    Is this view accurate or would there be a reason to install more than one of these?
    Thanks.
    ACPID - ACPI functions/auto-configuration.
    laptop-mode-tools - Lots of power-management scripts.
    pm-utils - Suspend/hibernate and some power-management scripts. Somewhat incompatible with laptop-mode-tools since 1.4.0.
    ACPID also allows you to set predefined actions when you close the lid on your laptop and when the power/sleep button is pressed. Before pm-utils 1.4.0, it was generally common to use all three of those tools together as they complimented each other. Now it's probably best to just use acpid/pm-utils together. I've opted to soley use pm-utils and have added this to my startup script:
    # Requires upower package.
    on_ac_power &
    Along with some key bindings to replicate what ACPID does, everything generally works without configuration. But as Coacher so obnoxiously said, it's a good idea to read their man pages as well.
    Tip:
    pacman -Ql package
    Edit: The wiki is slightly outdated regarding pm-utils.
    Last edited by Ledti (2010-08-07 07:08:37)

  • Laptop-mode-tools loops on lock_retry()

    I have been struggling with laptop-mode-tools for a while, so I am finally posting here.
    Short version:
    laptop-mode-tools never does anything on acpi events. Here is what happens in /var/log/everything.log when I unplug the ac adaptor:
    Jan 29 17:20:25 localhost laptop-mode: Determining power state from /sys/class/power_supply/ACAD/online.
    Jan 29 17:20:25 localhost laptop-mode: Not trying other options, already found a power supply.
    Jan 29 17:20:25 localhost laptop-mode: Battery level polling is disabled.
    Jan 29 17:20:25 localhost laptop-mode: Prelim lock acquisition on descriptor 8 with pid 8098
    Jan 29 17:20:25 localhost laptop-mode: Couldn't acquire prelim lock on descriptor 9 with pid 8098
    Jan 29 17:20:25 localhost laptop-mode: Now invoking lock_retry with arguments -- auto
    Jan 29 17:20:25 localhost kernel: [ 2961.821328] EXT4-fs (sda5): re-mounted. Opts: commit=300,commit=600
    Jan 29 17:20:26 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8098\n
    Jan 29 17:20:27 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8098\n
    Jan 29 17:20:28 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8098\n
    Jan 29 17:20:29 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8098\n
    Jan 29 17:20:30 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8098\n
    Jan 29 17:20:31 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8098\n
    Jan 29 17:20:32 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8098\n
    Jan 29 17:20:33 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8098\n
    Jan 29 17:20:34 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8098\n
    Jan 29 17:20:35 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8098\n
    Jan 29 17:20:35 localhost laptop-mode: Determining power state from /sys/class/power_supply/ACAD/online.
    Jan 29 17:20:35 localhost laptop-mode: Not trying other options, already found a power supply.
    Jan 29 17:20:35 localhost laptop-mode: Battery level polling is disabled.
    Jan 29 17:20:35 localhost laptop-mode: Prelim lock acquisition on descriptor 8 with pid 8188
    Jan 29 17:20:35 localhost laptop-mode: Couldn't acquire prelim lock on descriptor 9 with pid 8188
    Jan 29 17:20:35 localhost laptop-mode: Now invoking lock_retry with arguments -- auto
    Jan 29 17:20:36 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8188\n
    Jan 29 17:20:37 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8188\n
    Jan 29 17:20:38 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8188\n
    Jan 29 17:20:39 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8188\n
    Jan 29 17:20:40 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8188\n
    Jan 29 17:20:41 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8188\n
    Jan 29 17:20:42 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8188\n
    Jan 29 17:20:43 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8188\n
    Jan 29 17:20:44 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8188\n
    Jan 29 17:20:45 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 8188\n
    To obtain this log, I switched to 1 the variables VERBOSE_OUTPUT, LOG_TO_SYSLOG and DEBUG in /etc/laptop-mode/laptop-mode.conf
    long version:
    If I understand correctly, when the ac adapter is unplugged, the script /etc/acpi/events/lm_ac_adapter (which basically grabs every acpi events starting with ac_adapter), triggers the script /etc/acpi/actions/lm_ac_adapter.sh, and this action triggers the command '/usr/sbin/laptop_mode auto'
    I could check that acpid does its work correctly by modifying /etc/acpi/actions/lm_ac_adapter.sh and checking it is called immediately when I unplug the adapter, so I tried to manually call '/usr/sbin/laptop_mode auto' after unplugging the adapter, and I discovered that laptop_mode gets stuck in calling lock_retry() 10 times and then exists.
    See this paste: http://pastie.org/3276821
    Any idea how to fix that?
    Last edited by duquesnc (2012-01-29 17:26:05)

    lucke wrote:Perhaps you have a battery-level-polling.conf.pacnew file in /etc/laptop-mode/conf.d/ - merging the changes might help.
    No, this installation is brand new (I just got this laptop).
    Removing lmt-*.lock files from /var/lock/ after having stopped the laptop-mode "daemon" could (temporarily?) help.
    Trying to apply this advice, I realized something strange: calling 'rc.d stop laptop-mode' does not really stop laptop-mode:
    I first reboot the laptop in order to get rid of everything I could have done previously that could mess with the daemon. Then I check the lock files you mentionned exist:
    ls /var/lock/lmt-*.lock
    /var/lock/lmt-battpoll.lock /var/lock/lmt-invoc.lock /var/lock/lmt-req.lock
    Then, when calling
    rc.d stop laptop-mode
    I get in /var/log/everything.log:
    Jan 29 18:47:08 localhost laptop-mode: Now invoking lock_retry with arguments -- stop
    Jan 29 18:47:09 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20296\n
    Jan 29 18:47:10 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20296\n
    Jan 29 18:47:11 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20296\n
    Jan 29 18:47:12 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20296\n
    Jan 29 18:47:13 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20296\n
    Jan 29 18:47:14 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20296\n
    Jan 29 18:47:15 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20296\n
    Jan 29 18:47:16 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20296\n
    Jan 29 18:47:17 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20296\n
    Jan 29 18:47:18 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20296\n
    If I check /var/lock/lmt-*.lock after that, all the files are still there (they were not removed)
    ls /var/lock/lmt-*.lock
    /var/lock/lmt-battpoll.lock /var/lock/lmt-invoc.lock /var/lock/lmt-req.lock
    If I unplug the laptop after having stopped laptop-mode, I still get messages from laptop-mode in /var/log/everything.log!!!
    Jan 29 18:53:06 localhost laptop-mode: Determining power state from /sys/class/power_supply/ACAD/online.
    Jan 29 18:53:06 localhost laptop-mode: Not trying other options, already found a power supply.
    Jan 29 18:53:06 localhost laptop-mode: Battery level polling is enabled.
    Jan 29 18:53:06 localhost laptop-mode: Lock acquisition on descriptor 7 failed with pid 20828
    Jan 29 18:53:06 localhost laptop-mode: Prelim lock acquisition on descriptor 8 with pid 20828
    Jan 29 18:53:06 localhost laptop-mode: Couldn't acquire prelim lock on descriptor 9 with pid 20828
    Jan 29 18:53:06 localhost laptop-mode: Now invoking lock_retry with arguments -- auto
    Jan 29 18:53:06 localhost kernel: [ 8514.884884] EXT4-fs (sda5): re-mounted. Opts: commit=300,commit=600
    Jan 29 18:53:07 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20828\n
    Jan 29 18:53:08 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20828\n
    Jan 29 18:53:09 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20828\n
    Jan 29 18:53:10 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20828\n
    Jan 29 18:53:11 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20828\n
    Jan 29 18:53:12 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20828\n
    Jan 29 18:53:13 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20828\n
    Jan 29 18:53:14 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20828\n
    Jan 29 18:53:15 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20828\n
    Jan 29 18:53:16 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20828\n
    Jan 29 18:53:16 localhost laptop-mode: Determining power state from /sys/class/power_supply/ACAD/online.
    Jan 29 18:53:16 localhost laptop-mode: Not trying other options, already found a power supply.
    Jan 29 18:53:16 localhost laptop-mode: Battery level polling is enabled.
    Jan 29 18:53:16 localhost laptop-mode: Lock acquisition on descriptor 7 failed with pid 20920
    Jan 29 18:53:16 localhost laptop-mode: Prelim lock acquisition on descriptor 8 with pid 20920
    Jan 29 18:53:16 localhost laptop-mode: Couldn't acquire prelim lock on descriptor 9 with pid 20920
    Jan 29 18:53:16 localhost laptop-mode: Now invoking lock_retry with arguments -- auto
    Jan 29 18:53:17 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20920\n
    Jan 29 18:53:18 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20920\n
    Jan 29 18:53:19 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20920\n
    Jan 29 18:53:20 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20920\n
    Jan 29 18:53:21 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20920\n
    Jan 29 18:53:22 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20920\n
    Jan 29 18:53:23 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20920\n
    Jan 29 18:53:24 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20920\n
    Jan 29 18:53:25 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20920\n
    Jan 29 18:53:26 localhost laptop-mode: Couldn't acquire lock on descriptor 9 in lock_retry(). Retrying.... PID is 20920\n
    When I remove the files, I can stop laptop-mode for good, but when I restart it, it re-creates them and the problems start again after the next acpi event...
    Last edited by duquesnc (2012-01-29 18:10:23)

  • 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)

  • I fixed the LCD Brightness in my Samsung NP300 Laptop

    tl;dr: acpi_backlight=vendor to kernel at boot (add in grub configuration) + modprobe -r samsung_laptop && systemctl restart gdm. (i discovered it with pf-kernel, need to try in stock kernel)
    Well, i don't know if this is known, but i could not find it.
    Maybe its a bug to be fixed that im not aware of.
    Well, i had the common problem with the LCD brightness not responding. It used to decrease, but not increase. All of this running Gnome 3.
    After days of fight what i did was download pf-kernel and configure it. I selected the "samsung_laptop" module as my common sense told me, and in case it was needed the Q10 Samsung or something like that module too.
    I rebooted into the pf-kernel, with no luck, the same problem was still happening.
    I decided to stop gdm and use startx to try some things.
    First i modprobed the samsung_laptop module just in case, started X again, and it was the same.
    And then i did modprobe -r samsung_laptop, restarted X... AND IT WORKS.
    NOTE: The acpi_backlight=vendor is needed in the grub configuration to this to work.
    Oddly, without the samsung_laptop module.
    So i rebooted to try this again. Unloaded the module, did systemctl restart gdm, aand there it was working again.
    So, it may be a problem with that module, or maybe its not needed after all, im not sure.
    I'm kind of newbie in all of this, so if this is dumb or something im sorry but i think it may be helpful for somebody else in my situation.
    By googling i only found scripts to make this work that i did not like.
    Is neccesary that i place a bug report? Im not sure if that kernel module is made to fix this or if its for something else, so i dont know if the bug report makes sense.
    Last edited by nlabrad (2012-12-27 18:07:52)

    More history on what does what.
    At first, i could only decrease the brightness 1 step, from the max to one below.
    Then i put acpi_backlight=vendor in grub, and i could decrease the brightness to some value (which is not the real minimum), but could not increase it more than 2 steps over that minimum once decreased (like locked in the 2 lower values).
    To manually change the brightness i echoed values to /sys/class/backlight/intel_backlight/brightness. The other one did not work (samsung...), but it wasn't what i wanted.
    After changing kernel, unloading the kernel module samsung_laptop and restarting x it works.
    Not sure if the kernel has something to do.

  • [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 draws more power than no laptop-mode

    Hey all,
    I finally took the plunge and installed laptop-mode-tools. I edited the main configuration file to my liking and enabled those extra powersaving features I need. The other ones I have disabled. However, when I enable laptop-mode my battery is drained faster than without! I am pretty sure this is not what it should do
    I'm clueless as for where to look though, because I didn't change any critical setting (AFAIK) and I didn't enable any 'extra' features: i just enabled those found in /etc/laptop-mode/conf.d that I need and disabled those that I don't need. Can you help me pin-point which feature of laptop-mode-tools draws more power out of my battery?
    Here's the list of features I have enabled:
    auto-hibernate.conf
    dpms-standby.conf
    ethernet.conf
    intel-hda-powersave.conf
    intel-sata-powermgmt.conf
    lcd-brightness.conf
    nmi-watchdog.conf
    runtime-pm.conf
    sched-mc-power-savings.conf
    sched-smt-power-savings.conf
    terminal-blanking.conf
    usb-autosuspend.conf
    wireless-power.conf
    Those that I have disabled:
    ac97-powersave.conf
    battery-level-polling.conf
    bluetooth.conf
    configuration-file-control.conf
    cpufreq.conf
    eee-superhe.conf
    exec-commands.conf
    hal-polling.conf
    start-stop-programs.conf
    video-out.conf
    wireless-ipw-power.conf
    wireless-iwl-poweac97-powersave.conf
    battery-level-polling.conf
    bluetooth.conf
    configuration-file-control.conf
    cpufreq.conf
    eee-superhe.conf
    exec-commands.conf
    hal-polling.conf
    start-stop-programs.conf
    video-out.conf
    wireless-ipw-power.conf
    wireless-iwl-power.confr.conf
    Thanks in advance!
    PS: if you need any files, please tell me. As I said I am clueless what could cause this, so I could give you a list of all the laptop-mode files I have edited but I don't think this would help anything.
    EDIT: I have disabled the cpufreq one because I use cpupower and have that setup without any laptop-mode-tools interference. I use the on-demand governor all the time. An extra question: do I need those sched-{mc,smt} features in laptop-mode, if I have configured those in cpupower as well? For now I left them in, but I was gonna figure this one out still.
    Last edited by Unia (2012-04-20 17:55:51)

    Finally had the time to do some testing with powertop. The highest result I get are these:
    Top causes for wakeups:
    35,8% (309,7) [Rescheduling interrupts] <kernel IPI>
    28,8% (248,8) PS/2 toetsenbord/muis/touchpad interrupt
    The first I have also without laptop-mode, the second I don't have. However, it does seem to drain a little slower now. Anyway, any hints to persue to get those wakeups down?
    PS: powertop also suggested this:
    Suggestion: Enable the CONFIG_INOTIFY kernel configuration option.
    This option allows programs to wait for changes in files and directories
    instead of having to poll for these change
    Does the Arch kernel have that by default or do I have to build my own kernel for this?

  • 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.

  • Did something change for laptop-mode-tools last time?

    Hi,
    when I start laptop-mode daemon, I always get the following errors in my everything.log
    Jul 8 14:45:46 archbox laptop-mode: Considering /dev/sda.
    Jul 8 14:45:46 archbox laptop-mode: /dev/sda5 not found in PARTITIONS.
    Jul 8 14:45:46 archbox laptop-mode: /home not found in PARTITIONS.
    Jul 8 14:45:46 archbox laptop-mode: Checking /dev/sda5 against HD because PARTITIONS contains "auto".
    Jul 8 14:45:46 archbox laptop-mode: Considering /dev/sda.
    Jul 8 14:45:46 archbox laptop-mode: /dev/sda5 contains /dev/sda, which is in HD, so we will remount it.
    Jul 8 14:45:46 archbox laptop-mode: Original options: rw,commit=0
    Jul 8 14:45:46 archbox laptop-mode: Reducing file system type.
    Jul 8 14:45:46 archbox laptop-mode: No saved mount options, so apparently we never remounted this filesystem during this session.
    Jul 8 14:45:46 archbox laptop-mode: Not remounting.
    Jul 8 14:45:46 archbox laptop-mode: Executing: /sbin/blockdev --setfra 256 /dev/sda5
    Jul 8 14:45:46 archbox laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/lcd-brightness.
    Jul 8 14:45:46 archbox laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/sched-mc-power-savings.
    Jul 8 14:45:46 archbox laptop-mode: Scheduler power setting is disabled.
    Jul 8 14:45:46 archbox laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/start-stop-programs.
    Jul 8 14:45:46 archbox laptop-mode: START_SERVICES =
    Jul 8 14:45:46 archbox laptop-mode: STOP_SERVICES =
    Jul 8 14:45:46 archbox laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/syslog-conf.
    Jul 8 14:45:46 archbox laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/terminal-blanking.
    Jul 8 14:45:46 archbox laptop-mode: CONTROL_TERMINAL is disabled, skipping...
    Jul 8 14:45:46 archbox laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/usb-autosuspend.
    Jul 8 14:45:46 archbox laptop-mode: USB autosuspend is disabled.
    Jul 8 14:45:46 archbox laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/video-out.
    Jul 8 14:45:46 archbox laptop-mode: video-out module is disabled.
    Jul 8 14:45:46 archbox laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/wireless-ipw-power.
    Jul 8 14:45:46 archbox laptop-mode: Intel IPW Wireless power setting is disabled.
    Jul 8 14:45:46 archbox laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/wireless-iwl-power.
    Jul 8 14:45:46 archbox laptop-mode: Intel IWL Wireless power setting is disabled.
    Jul 8 14:45:46 archbox laptop-mode: Module /usr/local/lib/laptop-mode-tools/modules/* is not executable.
    Jul 8 14:45:46 archbox laptop-mode: Module /usr/local/share/laptop-mode-tools/modules/* is not executable.
    Jul 8 14:45:46 archbox laptop-mode: Module /etc/laptop-mode/modules/* is not executable.
    Where the scripts in /etc/laptop-mode/conf.d/  moved to /etc/laptop-mode/modules ??

    As far as I know, /etc/laptop-mode/conf.d did never contain modules/scripts, but configuration files for the different modules/scripts. Some releases ago, the longish, unique configuration file /etc/laptop-mode.conf has been partially splitted in these specific configuration files. The modules/scripts provided by upstream are in /usr/share/laptop-mode-tools/modules. The modules/scripts defined by the administrator should go in /etc/laptop-mode/modules. You haven't any of them.
    The only relevant novelty in the last release is that laptop mode tools now send logs to the system logger, so this is the reason why you did not see those messages before.
    Last edited by patroclo7 (2009-07-08 13:33:34)

Maybe you are looking for