[Solved]Laptop lid question

Hello,
I am really happy with arch on my laptop. Suspend2Disk works (although the light on my wlan-button stays off after wake up, but since the network itself works I am fine with that), suspend2ram works to.. and those two are crucial.
Even the Sleep-Button works and that is awesome!
But I would like the Laptop to go to suspend2disk when I close the lid, and honestly I am confused about how to do that.
I use acpid for the sleep button, which calls its own suspend2ram (works better then PM-utils for me btw). I call pm-hibernate by myself when I need it.
I read probably every article in the wiki but I can not put the puzzle pieces together.
acpid reacts on closing the lid, it does something with the ati-driver, probably to shut the screen of, or some.
But how can I change that to execute pm-hibernate?
BTW: it's Samsung P35, should that help.
Last edited by thom_raindog (2008-05-17 20:17:20)

Run acpi_listen and close the lid to get the relevant event. If you get the same event for closing and opening the lid (I do) you can use something like
grep open /proc/acpi/button/lid/LID/state || hibernate -F /etc/hibernate/ususpend-ram.conf
Of courseyou might need to change the path of the state file and the hibernate command as this is pasted from my handler.sh.

Similar Messages

  • [SOLVED] Laptop Lid Close

    I've been using arch on my laptop for a while now and have been having problems when I close the lid on my laptop. What I want my a laptop to do is nothing except simply turn the screen off when the lid is shut. However, at the moment when I close the lid, it doesn't suspend or sleep or anything, the screen turns off, but when I open the lid, I am presented with a black screen(lit up). I have to turn my laptop on and off to use it again, or change tty and then restart the x-screen. Any help would be much appreciated. Thanks in advance.
    Last edited by compty (2013-12-30 08:15:22)

    Thanks,
    I'm using acpid to handle the event and in the /etc/systemd/logind.conf I have only the following line uncommented:
    HandleLidSwitch=ignore
    Which to my understanding should prevent systemd from controlling the event yes?
    And at the moment I currently have the default acpi setup,
    so the anything event:
    # Pass all events to our one handler script
    event=.*
    action=/etc/acpi/handler.sh %e
    And the following hander.sh:
    #!/bin/bash
    # Default acpi script that takes an entry for all actions
    case "$1" in
    button/power)
    case "$2" in
    PBTN|PWRF)
    logger 'PowerButton pressed'
    logger "ACPI action undefined: $2"
    esac
    button/sleep)
    case "$2" in
    SLPB|SBTN)
    logger 'SleepButton pressed'
    logger "ACPI action undefined: $2"
    esac
    ac_adapter)
    case "$2" in
    AC|ACAD|ADP0)
    case "$4" in
    00000000)
    logger 'AC unpluged'
    00000001)
    logger 'AC pluged'
    esac
    logger "ACPI action undefined: $2"
    esac
    battery)
    case "$2" in
    BAT0)
    case "$4" in
    00000000)
    logger 'Battery online'
    00000001)
    logger 'Battery offline'
    esac
    CPU0)
    *) logger "ACPI action undefined: $2" ;;
    esac
    button/lid)
    case "$3" in
    close)
    logger 'LID closed'
    open)
    logger 'LID opened'
    logger "ACPI action undefined: $3"
    esac
    logger "ACPI group/action undefined: $1 / $2"
    esac
    # vim:set ts=4 sw=4 ft=sh et:
    I know I need to add the commands etc to perform the various functions, but I thought that this handler.sh would do nothing?
    I'm also using xfce. My laptop is a Dell Inspiron 7720.
    Any advice on what I might be doing wrong?

  • [SOLVED] Laptop action ignore close lid settings

    I run gnome 3.4.2 and my laptop goes to sleep even though I set the laptop lid close action to "blank." I used gnome-tweak
    Last edited by tancrackers (2012-10-14 07:04:19)

    Are you using systemd? https://wiki.archlinux.org/index.php/Sy … th_systemd

  • [SOLVED] Power button and laptop lid close rules not followed (KDE)

    I'm using KDE 4.9.1, and the rules I set for the power button and lid close events in the KDE power management settings are not followed.
    Currently, I have the power button press event set to trigger hibernation, and the lid close event set to turn off the display. Instead, the power button causes the laptop to power down immediately, as if the 'poweroff' command was issued. Closing the lid causes the system to suspend to ram.
    This problem seemed to have started when I installed 'laptop-mode-tools' and 'acpid'. The problem persisted even when I uninstalled the said packages from the system. Most solutions on the internet involve adjusting the contents of files in /etc/acpi/, but that directory does not exist on my system. I also tried deleting the power management configuration files in the ~/.kde4/share/config directory, but that didn't fix the problem either.
    Hibernation works if I choose 'hibernate' from the KDE menu.
    Thanks for any help.
    Last edited by rb3 (2012-09-28 05:46:56)

    That's not a good solution.
    Changes in systemd default behaviour are reasonable. It guarantees that if your graphical enviroment has no suspend support, it will still suspend when the lid is closed.
    For example, closing the laptop lid at KDM login screen will now suspend the laptop. I remember a topic when someone nearly killed his notebook battery with overheat in that situation (the laptop did not suspend when the lid was closed at kdm screen).
    This change also brings native (non-acpid) suspend support to lighweight desktop enviroments.
    The source of the «double suspend» problem is in acynchronized update of systemd and KDE.
    Updating KDE to 4.9.2 (which will be released in several days) will fix this without editing the config file.
    Make sure you restore the original logind.conf after updating to KDE 4.9.2.
    See:
    http://lists.freedesktop.org/archives/s … 06604.html
    https://bugs.kde.org/show_bug.cgi?id=307412
    https://git.reviewboard.kde.org/r/106533/

  • Time machine disk failure after closing laptop lid

    I have a Seagate 1.5 TB disk that I'm using for a time machine backup (USB).  For a long time, I had the disk formatted wrong and had this problem, but I re-formatted it (per Apple's instructions) and have been trying again.  Now, with it correctly formatted, I still have the same problem.
    This is a laptop, so I don't leave the Time Machine application on, nor do I leave the TM disk connected all the time.  If I plug in the drive, run TM, and eject the disk before closing the laptop lid, I do not have any issues.  If, however, the laptop lid is shut at any point after TM completes, I have can never seem to eject nor unmount the TM disk.  For example, last night I ran TM and left the machine open overnight.  In the morning, the machine was used and shut per usual routine, except the drive was still connected.  Now there is a critical failure on the drive (Disk Utility can do nothing to repair the drive and suggests re-formatting).  Last night, the computer was plugged in and went to sleep after 15 minutes.  I have changed no settings regarding what the computer does on lid shutdown.
    What used to work to eject/unmount the drive is to shutdown the computer.  Then I would unplug the drive before re-starting.  Now, however, I had errors with the drive (Disk Utility) and went ahead with a force eject.  That worked, and the drive still had errors that Disk Utility could not address.
    I have a Macbook Pro (13-inch, mid 2012) running Mac OS X Version 10.9.2 (13C64); processor 2.9 GHz Intel Core i7 with 8 GB 1600 MHz DDR3 memory.  My main drive is 750 GB (Macintosh HD).  I also backup a firewire 400 drive to this TM drive, capacity 250 GB.
    So, first question: why is this happening over and over and over?  Is there anything I can do, apart from immediate removal of the TM drive after the backup completes, to ensure that it doesn't happen in the future?  Should I be concerned that the disk is failing mechanically?
    Thanks

    I don't think you quite understand how Time Machine really works. But then hardly anyone does. Time Machine is intended to be left enabled always whether a backup drive is connected or not. What Time Machine cannot handle properly is a situation where the backup drive loses power for whatever reason. Time Machine treats this, as does the OS, as an improper disconnect of an external drive without being properly ejected. This in turn throws Time Machine a little bit of a loop.
    For you I would suggest not using Time Machine. Instead use a third-party backup utility that you can either schedule or run manually as you wish. They will work with the same drive you have used for Time Machine, but you will need to first erase the Time Machine drive using Disk Utility. Please DO NOT try dragging the Time Machine backups to the Trash.
    Here are some good backup utilities you can try:
    Suggested Backup Software
      1. Carbon Copy Cloner
      2. Get Backup
      3. Deja Vu
      4. SuperDuper!
      5. Synk Pro
      6. Tri-Backup
    Others may be found at MacUpdate. Each one can be used for a trial period. No need to pay for one until you've decided on which one you like best. I, for example, use Carbon Copy Cloner but please don't take that as a recommendation over the others. It's just my preference. All can be operated manually or can be set up to backup on a schedule you determine. Some can even be set up to backup as soon as the backup drive is connected.
    Visit The XLab FAQs and read the FAQ on backup and restore.  Also read How to Back Up and Restore Your Files.

  • Power up Macbook Pro with 23" Cinema Display without opening Laptop lid?

    Hi there,
    I've just bought an Apple 23" Cinema display to use with my Macbook Pro.
    I just have a quick question for working this setup. I'd like work with just the 23" display in use (i.e. laptop lid closed, due to desk space), but can't figure out how to turn on the Macbook Pro without opening the lid to the laptop for the power button!
    This may sound like a silly question and I may be overlooking something as I've only had the setup for a hour, but it'd be a major pain in the ar*e if I had to open the laptop to turn it on every day, then close the lid again (and possibly go through the 'Are you sure you want to go into sleep mode...' process each time).
    Can I avoid opening the laptop when connected to the 23" display? There is a power button on the display, but it only seems to put the Mac into sleep mode when it's already on, i.e. it didn't seem to work when I tried to use it to turn the Mac on from being off.
    Thanks for any advice on this.
    Ste

    These Apple tech notes may help:
    How to use your PowerBook G4, MacBook Pro or MacBook with the display closed
    How to use your PowerBook G4, MacBook or MacBook Pro with the display closed and a Bluetooth keyboard or mouse
    Just a final question about Sleep mode - does this have any negative effects on the life or performance of the laptop? I'm so used to Shutting down the laptop each day that I worry about Sleep mode having some sort of drain on the components or something.
    There are only two practical differences between Sleep and Shut Down:
    1. Sleep will wake instantly, so you don't have to wait for startup.
    2. Sleep will drain a new, fully charged battery after several days without being woken or plugged in. If you shut down, the battery charge lasts much longer. Obviously, if you only sleep it overnight, you'll still have plenty of battery left in the morning.
    Don't sleep it more frequently than necessary, though. Frequently turning the backlight and hard drive off and on can shorten their life. Just do what's reasonable. I usually leave mine awake until I have to transport it in a bag, along with sleeping it overnight. On battery, I'll sleep it more often to preserve battery.

  • Kernel 2.6.32.2-2 black screen after closing laptop lid (intel + KMS)

    Today I updated my laptop with the new 2.6.32.2-2 kernel from core. Previous update of my system was just a few days back, so there are no massive changes to other packages and I also don't use testing packages.
    Since the update, after closing the laptop lid (which just blanks my screen) and I want to continue working I just have a black screen (no backlight) and the screen won't respond to mouse or keyboard input. I have to reboot (ctr-alt-del or pushing my power button) or switch to VT1 and back to VT7 to get my screen back. I'm absolutely positive that this was not a problem before, it worked fine with 2.6.30 and 2.6.31 kernels with my same configuration.
    HP 6730b laptop
    Intel GMA 4500 (Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07))
    Intel driver 2.9.1-1 using KMS with early start (modprobe.conf) and I rebuilt my initcpio to the new 2.6.32.2-2 kernel
    Gnome 2.28.2
    Can anyone confirm this behaviour? Should I file a bug somewhere? I read about lots of upgrade problems with this new kernel, but for the rest everything else works fine so far.
    Thanks for your feedback.
    Ulukai

    moose jaw wrote:
    ulukai wrote:@ Moose Jaw: I also looked into pm-suspend, but i guess it is only usefull for suspending and resuming sessions (something I never do)? Is there a command you know for simulating closing the lid and reopening it again?
    Isn't suspending and resuming a session exactly what you're doing (or hoping to do) when you close your lid and then open it up again?  I.e., putting the machine into a low-power sleep state and then having everything come back to where you were when you wake it up?  You mentioned that the Gnome power management tools depend on pm-utils, which suggests that somewhere in there "pm-suspend" is getting called.  If you can find out where it's getting called (i.e., in some script that Gnome power manager uses), and try changing it to "pm-suspend --quirk-vbestate-restore" (or one of the other quirks, perhaps), then that may bring your screen back on wakeup.
    Hehe, nope I don't hope to suspend :-) I just close the lid to save the display (and some power) but want my machine to keep running (when downloading torrents or when I'm going to eat etc...) Also it keeps the dust from entering the keyboard ;-)
    I also took a look at the post where there should be a patch present, but I think it's for another problem: flickering screens.
    For me it's a bug in intel driver or kernel, but still it's strange that KDE doesn't suffer from this!

  • Power on laptop connected to Thunderbolt display without opening laptop lid?

    I have a Macbook Pro (2.7 GHz Intel Core i7) running Lion connected to a 27" Thunderbolt display. Is there any way to power on my computer without having to open the laptop lid?
    Thanks for your time.
    Best regards,
    Erin

    I have a Macbook Pro (2.7 GHz Intel Core i7) running Lion connected to a 27" Thunderbolt display. Is there any way to power on my computer without having to open the laptop lid?
    Thanks for your time.
    Best regards,
    Erin

  • Challenging question! (Does anyone how to solve this Javabat question?)

    Does anyone how to solve this Javabat question?
    Here is the link:
    http://www.javabat.com/prob?id=Array3.linearIn

    I'm a little surprised by the implied rating of this problem... it's a plain to-way merge. You can use the same template as for the merging step in merge sort:
    public boolean linearIn(int[] outer, int[] inner) {
      int i = 0;
      int j = 0;
      while (i < outer.length || j < inner.length) {
          if (j < inner.length && (i == outer.length || inner[j] < outer)) {
    // inner[j] smallest
    return false;
    else if (i < outer.length && (j == inner.length || outer[i] < inner[j])) {
    // outer[i] smallest
    i++;
    else {
    // inner[j] == outer[i]
    i++; j++;
    return true;

  • Want to listen to music with laptop lid closed

    I want to listen to my music with the laptop lid closed but ipod pauses every time I close the lid. Never have this problem when I play music on the window media player...
    Any fix?

    http://manuals.info.apple.com/enUS/iPhone_UserGuide.pdf

  • The grip between the screen and the laptop lid?

    The grip that seperates the screen from the laptop lid is what I'm talking about... but basically I just noticed (not from my doing) that on a tiny section of the screen, you can see the grip not attached properly like the rest of the laptop is. Would this even be something to bring up to the Apple store?

    Dear god it does.

  • Firefox locks up when I reopen the laptop lid.

    I have W7 on my A505 Toshiba. I have Fox News (home page), Comcast home page and Comcast mail tabs displayed. I close the laptop lid. Reopen several hours later and performance is slow. X out of mail, Comcast, and then try to X out of Fox and computer hangs up. This has started within the last couple weeks. During that time, I downloaded an Adobe update only.

    Hi,
    You can try to [https://www.mozilla.org/en-US/firefox/new/ updating Firefox] and check. If the problem persists, you can also try to '''Disable''' suspicious '''Plugins''' in '''Tools '''('''Alt '''+ '''T''') > '''Add-ons'''. Please note that this may also happen if the laptop close lid action was changed from sleep to hibernate because Windows would take more time to restore the saved state from disk.

  • [SOLVED] Laptop doesn't suspend anymore when closing lid [GNOME 3]

    Hi there!
    Since I upgraded to GNOME 3 recently, my laptop (Acer Aspire TimelineX 3820TG) doesn't suspend anymore when I close the lid. Instead, it just turns off the screen. If I choose suspend from the menu, it does suspend properly.
    I googled a bit and found out that the option what to do on closing the lid was dropped in GNOME 3, setting suspend as default action. That's exactly what I want...
    Also, I checked that option via gnome-tweak-tool and dconf-editor, and (surprise!) it was set to 'suspend'.
    Anyone got an idea what to do to make it suspend again on closing the lid?
    Last edited by perpetrator (2011-10-17 14:25:26)

    Sorry to bother you again, but for some reason it doesn't work anymore...
    Somehow it can't lock the GNOME session, because when I enter the above line from /etc/acpi/handler.sh manually as root in TTY1, I get this error:
    ** Message: Failed to get session bus: Befehlszeile »dbus-launch --autolaunch=c9375f4ea0008d92177b28db000009ae --binary-syntax --close-stderr« brach mit von Null verschiedenem Beenden-Status 1 ab: No protocol specified\nAutolaunch error: X11 initialization failed.\n
    If I enter this command inside GNOME, everything works just fine, it locks the screen and suspends.
    EDIT:
    Setting the XAUTHORITY environment variable properly did the trick. Therefore, I borrowed some lines from here: https://wiki.archlinux.org/index.php/Su … losing_lid
    Thread marked as SOLVED again.
    Last edited by perpetrator (2011-10-17 14:25:11)

  • [SOLVED] XFCE 4.12 - laptop lid ignores power-manager settings

    I just fresh installed Arch w/ XFCE 4.12
    In power manager, I set the lid switch to suspend on battery, lock on ac.  The setting worked initially, but after the first suspend, or a reboot, the lid switch triggers suspend no matter what.
    I tried setting HandleLidSwitch=ignore in /etc/systemd/logind.conf, as suggested in numerous online sources, but it didn't help
    I tried rm -rf .config/xfce4/xfconf/xfce-perchannel-xml/xfce4-power-manager.xml, which makes it work temporarily again, until a suspend or a reboot
    Does anyone know of a fix for this?  It's not a deal-breaker but it's a pain in the ass.
    Last edited by madscience (2015-04-13 03:10:33)

    I may have solved it.
    I edited the xml file directly and set <property name="logind-handle-lid-switch" type="bool" value="false"/>
    Now the options seem to work as intended.  I also noticed that if you launch the settings applet, it changes that key back to true every time it's opened.  The change can also be made through the settings editor.
    I'll test for 24 hours and mark as solved if it works.
    EDIT:
    That didn't work permanently, I'm back to suspending on lid close on AC.  I'm using TLP with battery thresholds enabled, and I'm starting to wonder if xfce-power-manager is reading the charge state of the battery instead of the power source directly.  When my battery is below the start charging threshold and is actually charging, it seems to be working as intended.  If my laptop is on AC but the battery is not actually charging, it acts like it's on battery.  I might be wrong, it's just a theory.
    Last edited by madscience (2015-04-13 02:44:48)

  • [SOLVED] how to prevent suspending/sleeping when closing laptop lid

    Hi all,
    My laptop, a Lenovo Thinkpad T430u, suspends whenever I close the lid. It's been doing this since I first installed Arch.  I want to turn this feature off.  How can I do it?
    Relevant information:
    acpid is installed
    the configuration file /etc/acpi/handler.sh
    #!/bin/bash
    # Default acpi script that takes an entry for all actions
    case "$1" in
    button/power)
    case "$2" in
    PBTN|PWRF)
    logger 'PowerButton pressed'
    logger "ACPI action undefined: $2"
    esac
    button/sleep)
    case "$2" in
    SLPB|SBTN)
    logger 'SleepButton pressed'
    logger "ACPI action undefined: $2"
    esac
    ac_adapter)
    case "$2" in
    AC|ACAD|ADP0)
    case "$4" in
    00000000)
    logger 'AC unpluged'
    00000001)
    logger 'AC pluged'
    esac
    logger "ACPI action undefined: $2"
    esac
    battery)
    case "$2" in
    BAT0)
    case "$4" in
    00000000)
    logger 'Battery online'
    00000001)
    logger 'Battery offline'
    esac
    CPU0)
    *) logger "ACPI action undefined: $2" ;;
    esac
    button/lid)
    case "$3" in
    close)
    logger 'LID closed'
    open)
    logger 'LID opened'
    logger "ACPI action undefined: $3"
    esac
    case $(cat /proc/acpi/button/lid/LID0/state | awk '{print $2}') in
    closed) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force off ;;
    open) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force on ;;
    esac
    logger "ACPI group/action undefined: $1 / $2"
    esac
    # vim:set ts=4 sw=4 ft=sh et:
    dmesg output:
    [ 1530.790532] PM: Syncing filesystems ... done.
    [ 1530.805678] PM: Preparing system for mem sleep
    [ 1530.844445] Freezing user space processes ... (elapsed 0.01 seconds) done.
    [ 1530.856658] Freezing remaining freezable tasks ... (elapsed 0.10 seconds) done.
    [ 1530.963435] PM: Entering mem sleep
    [ 1530.963572] Suspending console(s) (use no_console_suspend to debug)
    [ 1531.123543] iwlwifi 0000:03:00.0: iwl_pcie_cmdq_reclaim: Read index for DMA queue txq id (9), index 207 is out of range [0-256] 208 208.
    [ 1531.124216] sd 0:0:0:0: [sda] Synchronizing SCSI cache
    [ 1531.124579] sd 0:0:0:0: [sda] Stopping disk
    [ 1531.360682] mei 0000:00:16.0: suspend
    [ 1531.440517] ahci 0000:00:1f.2: power state changed by ACPI to D3hot
    [ 1531.687309] PM: suspend of devices complete after 722.490 msecs
    [ 1531.687784] PM: late suspend of devices complete after 0.469 msecs
    [ 1531.688232] pcieport 0000:00:1c.3: System wakeup enabled by ACPI
    [ 1531.714222] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
    [ 1531.727619] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
    [ 1531.754015] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
    [ 1531.767422] PM: noirq suspend of devices complete after 79.565 msecs
    [ 1531.768301] ACPI: Preparing to enter system sleep state S3
    [ 1531.797647] PM: Saving platform NVS memory
    [ 1531.799282] Disabling non-boot CPUs ...
    [ 1531.900721] smpboot: CPU 1 is now offline
    [ 1532.004162] smpboot: CPU 2 is now offline
    [ 1532.107554] smpboot: CPU 3 is now offline
    I have pmutils and tlpinstalled
    tlp config
    # tlp - Parameters for power save
    # Hint: some features are disabled by default, remove the leading # to enable them
    # Set to 0 to disable/1 to enable TLP
    TLP_ENABLE=1
    # Seconds laptop mode has to to wait after the disk goes idle before doing a sync.
    # Non-zero value enables, zero disables laptop mode.
    DISK_IDLE_SECS_ON_AC=0
    DISK_IDLE_SECS_ON_BAT=2
    # Dirty page values (timeouts in secs).
    MAX_LOST_WORK_SECS_ON_AC=15
    MAX_LOST_WORK_SECS_ON_BAT=60
    # Select a cpu frequency scaling governor: ondemand/powersave/performance/conservative
    # Important:
    # - You *must* disable your distribution's governor settings or conflicts will occur
    # - ondemand is sufficient for *almost all* workloads, you should know what you're doing!
    #CPU_SCALING_GOVERNOR_ON_AC=ondemand
    #CPU_SCALING_GOVERNOR_ON_BAT=ondemand
    # Set the min/max frequency available for the scaling governor.
    # Possible values strongly depend on your cpu. For available frequencies see
    # tlp-stat output, Section "+++ Processor".
    # Hint: Parameters are disabled by default, remove the leading # to enable them,
    # otherwise kernel default values are used.
    #CPU_SCALING_MIN_FREQ_ON_AC=0
    #CPU_SCALING_MAX_FREQ_ON_AC=0
    #CPU_SCALING_MIN_FREQ_ON_BAT=0
    #CPU_SCALING_MAX_FREQ_ON_BAT=0
    # Set the cpu "turbo boost" feature: 0=disable / 1=allow
    # Requires an Intel Core i processor and kernel 3.7 or later.
    # Important:
    # - This may conflict with your distribution's governor settings
    # - A value of 1 does *not* activate boosting, it just allows it
    #CPU_BOOST_ON_AC=1
    #CPU_BOOST_ON_BAT=0
    # Minimize number of used cpu cores/hyper-threads under light load conditions
    SCHED_POWERSAVE_ON_AC=0
    SCHED_POWERSAVE_ON_BAT=1
    # Kernel NMI Watchdog
    # 0=disable (default, saves power) / 1=enable (for kernel debugging only)
    NMI_WATCHDOG=0
    # Change CPU voltages aka "undervolting" - Kernel with PHC patch required
    # Freq:voltage pairs are written to /sys/devices/system/cpu/cpu0/cpufreq/phc_controls
    # CAUTION: only use this, if you thoroughly understand what you are doing!
    #PHC_CONTROLS="F:V F:V F:V F:V"
    # Hard disk devices, separate multiple devices with spaces (default: sda).
    # Devices can be specified by disk id too (lookup with: tlp diskid).
    DISK_DEVICES="sda sdb"
    # Hard disk advanced power management level: 1(max saving)..254(off)
    # Levels 1..127 may spin down the disk.
    # Separate values for multiple devices with spaces.
    DISK_APM_LEVEL_ON_AC="254 254"
    DISK_APM_LEVEL_ON_BAT="128 128"
    # Hard disk spin down timeout:
    # 0: spin down disabled
    # 1..240: timeouts from 5s to 20min (in units of 5s)
    # 241..251: timeouts from 30min to 5.5 hours (in units of 30min)
    # (see 'man hdparm' for details)
    #DISK_SPINDOWN_TIMEOUT_ON_AC="0 0"
    #DISK_SPINDOWN_TIMEOUT_ON_BAT="0 0"
    # Select io scheduler for the disk devices: noop/deadline/cfq (Default: cfq)
    # Separate values for multiple devices with spaces.
    #DISK_IOSCHED="cfq cfq"
    # SATA aggressive link power management (ALPM):
    # min_power/medium_power/max_performance
    SATA_LINKPWR_ON_AC=max_performance
    SATA_LINKPWR_ON_BAT=min_power
    # PCI Express Active State Power Management (PCIe ASPM):
    # default/performance/powersave
    # Hint: needs kernel boot option pcie_aspm=force on some machines
    PCIE_ASPM_ON_AC=performance
    PCIE_ASPM_ON_BAT=powersave
    # Radeon graphics clock speed (profile method): low/mid/high/auto/default
    # auto = mid on BAT, high on AC; default = use hardware defaults
    # (Kernel >= 2.6.35 only, not with fglrx driver!)
    RADEON_POWER_PROFILE_ON_AC=high
    RADEON_POWER_PROFILE_ON_BAT=low
    # WiFi power saving mode: 1=disable/5=enable
    # (Linux 2.6.32 and later, some adapters only!)
    WIFI_PWR_ON_AC=1
    WIFI_PWR_ON_BAT=5
    # Disable wake on lan: Y/N
    WOL_DISABLE=Y
    # Enable audio power saving for Intel HDA, AC97 devices (timeout in secs).
    # A value of 0 disables / >=1 enables power save.
    SOUND_POWER_SAVE=1
    # Disable controller too (HDA only): Y/N
    SOUND_POWER_SAVE_CONTROLLER=Y
    # Set to 1 to power off optical drive in UltraBay (ThinkPads only)
    # when running on battery. A value of 0 disables this Feature (Default).
    # Drive can be powered on again by releasing (and reinserting) the
    # eject lever or by pressing the disc eject button on newer models.
    # Note: an UltraBay hard disk is never powered off.
    BAY_POWEROFF_ON_BAT=0
    # Optical drive device to power off (default sr0)
    BAY_DEVICE="sr0"
    # Runtime Power Management for pci(e) bus devices
    # (Kernel >= 2.6.35 only): on=disable/auto=enable
    RUNTIME_PM_ON_AC=on
    RUNTIME_PM_ON_BAT=auto
    # Runtime PM for *all* pci(e) bus devices: 0=disable / 1=enable
    # Warning: experimental option, could cause system instabilities
    RUNTIME_PM_ALL=0
    # Set to 0 to disable/1 to enable usb autosuspend feature
    USB_AUTOSUSPEND=1
    # Devices from the following list are excluded from usb autosuspend
    # (separate with spaces). Use lsusb to get the id's.
    # Note: input devices (usbhid) are excluded automatically
    #USB_BLACKLIST="1111:2222 3333:4444"
    # Set to 1 to disable autosuspend before shutdown/0 to do nothing
    # (workaround for usb devices that cause shutdown problems)
    #USB_AUTOSUSPEND_DISABLE_ON_SHUTDOWN=1
    # Restore radio device state (bluetooth, wifi, wwan) from previous shutdown
    # on system startup: 0=disable/1=enable
    # Hint: the parameters DEVICES_TO_DISABLE/ENABLE_ON_STARTUP/SHUTDOWN below
    # are ignored when this is enabled!
    RESTORE_DEVICE_STATE_ON_STARTUP=0
    # Radio devices to disable on startup: bluetooth wifi wwan
    #DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
    # Radio devices to enable on startup: bluetooth wifi wwan
    #DEVICES_TO_ENABLE_ON_STARTUP="wifi"
    # Radio devices to disable on shutdown: bluetooth wifi wwan
    # (workaround for devices that are blocking shutdown)
    #DEVICES_TO_DISABLE_ON_SHUTDOWN="bluetooth wifi wwan"
    # Radio devices to enable on shutdown: bluetooth wifi wwan
    # (to prevent other operating systems from missing radios)
    #DEVICES_TO_ENABLE_ON_SHUTDOWN="wwan"
    # Radio devices to enable when wireless radio switch is turned on:
    # bluetooth wifi wwan (Ubuntu + ThinkPad only)
    #DEVICES_TO_ENABLE_ON_RADIOSW="wifi wwan"
    # Battery charge thresholds (ThinkPad only, tp-smapi or acpi-call kernel module required)
    # Charging starts when the remaining capacity falls below the START_CHARGE_TRESH
    # value and stops when exceeding the STOP_CHARGE_TRESH value.
    # Main battery (values in %)
    #START_CHARGE_THRESH_BAT0=75
    #STOP_CHARGE_THRESH_BAT0=80
    # Ultrabay or slice battery (values in %)
    #START_CHARGE_THRESH_BAT1=75
    #STOP_CHARGE_THRESH_BAT1=80
    # Set to 1 to disable use of tpacpi-bat on Sandy Bridge or newer Thinkpads
    # and force usage of tp-smapi instead
    #DISABLE_TPACPIBAT=1
    # tlp-rdw - Parameters for the radio device wizard
    # Possible devices: bluetooth/wifi/wwan
    # Hint: parameters are disabled by default, remove the leading # to enable them
    # Radio devices to disable on connect
    DEVICES_TO_DISABLE_ON_LAN_CONNECT="wifi wwan"
    DEVICES_TO_DISABLE_ON_WIFI_CONNECT="wwan"
    DEVICES_TO_DISABLE_ON_WWAN_CONNECT="wifi"
    # Radio devices to enable on disconnect
    DEVICES_TO_ENABLE_ON_LAN_DISCONNECT="wifi wwan"
    #DEVICES_TO_ENABLE_ON_WIFI_DISCONNECT=""
    #DEVICES_TO_ENABLE_ON_WWAN_DISCONNECT=""
    # Radio devices to enable/disable when docked
    #DEVICES_TO_ENABLE_ON_DOCK=""
    #DEVICES_TO_DISABLE_ON_DOCK=""
    # Radio devices to enable/disable when undocked
    #DEVICES_TO_ENABLE_ON_UNDOCK="wifi"
    #DEVICES_TO_DISABLE_ON_UNDOCK=""
    thanks guys
    I love arch
    Last edited by beitme (2013-06-08 10:05:37)

    @ Karol, done
    @ 65kid, here's my logind.conf
    [Login]
    #NAutoVTs=6
    #ReserveVT=6
    #KillUserProcesses=no
    #KillOnlyUsers=
    #KillExcludeUsers=root
    #Controllers=
    #ResetControllers=cpu
    #InhibitDelayMaxSec=5
    #HandlePowerKey=poweroff
    #HandleSuspendKey=suspend
    #HandleHibernateKey=hibernate
    #HandleLidSwitch=ignore
    #PowerKeyIgnoreInhibited=no
    #SuspendKeyIgnoreInhibited=no
    #HibernateKeyIgnoreInhibited=no
    #LidSwitchIgnoreInhibited=yes
    #IdleAction=ignore
    #IdleActionSec=30min

Maybe you are looking for

  • Can't install ATI Catalyst

    Hate to ask for help, but can't find anything from google.  Also sorry if this is the wrong place to post it.  Anywho, I'm having trouble installing ATI Catalyst.  When I installed Arch I installed the oss drivers, but I can't play any resource heavy

  • Can we create pl/sql code over database link?

    Hi All, We are using Oracle 9i database. I want to know if we can create or modify pl/sql code (procedue, package, etc) over the database link? That means - can we create a procedure in remote database using the db link? Thanks, Dnyanesh

  • Help Setting Up Some Hardcore Actions

    Hey Peeps I'm currently trying to set up a action to take a .svg generated in html5 to a print ready eps with a spot knifeline So I'm running into 2 problems First is that I need to lock a few items so when I run a select all there not selected, but

  • Contacts Names Don't Show Up On Visual Voicemail

    Ever since I shifted to Exchange as my contacts account, the names of my contacts don't show up in visual voicemail, or for most incoming calls. I don't want to keep duplicates in the "On My Iphone" account, since then I get duplicate when I sync. I

  • Problem in viewing the synonym

    Hi, I have created a synonym as below, create synonym     PCS_TARGET.C$_0BLOB_TARGET for           PCS_MASTER_INT.C$_0BLOB_TARGET@PCBID But when i try to view this, its throwing an error as ORA-00942: table or view does not exist It doesn't consider