Deprecated /proc/acpi/

Hello,
Sorry, my english sucks.
Do you recommend to keep these options enabled in the kernel?
Deprecated /proc/acpi files
Deprecated power /proc/acpi directories
Deprecated /proc/acpi/event support
or the related acpi pkgs in Arch are updated for use /sys/ ?

Most acpi modules should have switched to sysfs by now but you'd have to read the documentation for the acpi-module you want to use.
I'd still keep it around. It doesn't hurt and it's shorter than /sys/devices/platform .

Similar Messages

No battery identified in /proc/acpi/

After the last couple of kernel updates, I no longer have a BATx folder inside /proc/acpi.
I used it to pipe the results to a little script I use on my statusbar, which keeps track of my memory usage, battery left, etc.
The strangest thing is that dmesg acknowledges the battery is there, and acpi returns the correct percentage and everything. It's just gone from /proc/acpi.
Anyone else had this one happen?
My laptop is an Acer TimeLine 1410.
dmesg | grep battery
[ 5.630145] ACPI: Battery Slot [BAT1] (battery present)
acpi -i
Battery 0: Full, 100%
Battery 0: design capacity 4400 mAh, last full capacity 4264 mAh = 96%
Last edited by Onyros (2011-10-10 13:34:01)

Using /proc to store ACPI information has been discouraged and deprecated since 2.6.24. The same data is available in /sys now and interested parties can (should) subscribe to ACPI events from the kernel via netlink.
https://bugs.archlinux.org/task/25845
acpitool upstream needs to fix this.

2.6.24 and /proc/acpi/battery

Hi,
Since the update to 2.6.24 (I now run it, pulled it in from testing) the procfs for acpi was deprecated. I think we should keep the two next options in the arch kernel.
# CONFIG_ACPI_PROCFS is not set
# CONFIG_ACPI_PROCFS_POWER is not set
I think the above should be set since quite some few applications depend on /proc/acpi/battery and /proc/acpi/ac
And even on 2.6.24 there still is a /proc/acpi directory filled with some things, so it's not so very "deprecated" if despite the fact CONFIG_ACPI_PROCFS is not set, there still exists such a directory.
Cheers!
ps. the app that is broken for me is kde's klaptopdaemon from kdeutils, 3.x.

cool, sorry, I completely forgot about the bugtracker. It's fixed now in -2 by tpowa. waiting for x86_64 testing to get bumped. can be closed! thanks
Last edited by imachine (2008-01-26 19:30:21)

[solved] /proc/acpi/thermal_zone/: No such file or directory

i want to monitor my laptop temperature with conky but i get
Conky: scandir for /proc/acpi/thermal_zone/: No such file or directory
does anyone know what i must install in order for it to work?
Last edited by red-guy (2011-03-21 17:05:00)

red-guy wrote:also, why do you even bother posting if it's not to help?
Because :
stlarch wrote:You are just expected to try to help yourself first. Then, when you've exhausted every effort ask. It's the Arch way. The wiki is your best friend.
And also because as forum moderator, we have to keep the boards as clean as possible. For you the problem might be new, but for many users here, they have seen these types of threads many times which have also been answered over and over again and also documented in the wiki. The wiki is a resource that has been created by the collective efforts of the Arch users - present and past. Make use of it.
As a general rule, if you have an issue, search the wiki, then the internet, then the forums for similar threads and if you still have problems then post a thread detailing what attempts you have made in order to fix the problem. That way, people don't give you options that you have already tried and know that they don't work.
In addition, please go through the forum rules to familiarize yourself with the basic rules and policies of the Arch forums.

Where is my /proc/acpi/video interface? Can't find it!

Hello!
I'm using a custom kernel. (2.6.23.8) For my xorg config I need a /proc/acpi/video interface (the nvidia driver need this interface).
I searched in the kernel config, but in Power Management / ACPI there isn't a "Video" Option.
How can I active this interface?
Thanks for your help!
Best regards,
Flasher

Hello,
I had the same problem a while back. You have to go into Device Drivers / Graphics Support, and turn on the first option, "Backlight & LCD device support". Under that option, choose "Lowlevel backlight controls". At this point, the video option should magically appear in the ACPI section.
Works for me. There may other dependencies I don't know about.
HTH,
peart.
Last edited by peart (2007-11-29 17:07:51)

Missing battery files in /proc/acpi/battery

I'm trying to employ this script:
http://mindspill.net/computing/linux-no … y-warning/
to get low battery warnings. It draws info from files like
BAT_STATE="/proc/acpi/battery/BAT1/state"
BAT_INFO="/proc/acpi/battery/BAT1/info"
but folder /proc/acpi/battery/ does not exist in my system. I do have /sys/class/power_supply/BAT0/ folder, but it does not containt 'state' or 'info' files.
What should I do to make this work?
Last edited by Lockheed (2012-06-06 10:49:13)

Maybe I am being a bit thick, but am not well versed in scripts.
I already modified the script to use notify-send rather than zenity
#!/bin/bash
# Location of acpi files.
BAT_STATE="/proc/acpi/battery/BAT1/state"
BAT_INFO="/proc/acpi/battery/BAT1/info"
# Minutes from the in-built warning level that measures should be taken to prevent loosing data.
BAT_ALERT_TIME=15
# Log to syslog & /var/log/acpid
LOGGER="/usr/bin/logger -t ACPID"
if grep -q discharging $BAT_STATE
then
BAT_REMAIN=`awk '/remaining/ { print $3 }' $BAT_STATE` # Remaining mAh.
BAT_DISCHARGE=`awk '/rate/ { print $3 }' $BAT_STATE` # Discharge rate in mA.
BAT_WARN=`awk '/warning/ { print $4 }' $BAT_INFO` # Warning level in mAh.
BAT_LOW=`awk '/low/ { print $4 }' $BAT_INFO` # Low level in mAh.
BAT_ALERT=$(( ( ( $BAT_DISCHARGE / 60 ) * $BAT_ALERT_TIME ) )) #+ $BAT_WARN )) # Work out the charge that will have been used in $BAT_ALERT_TIME minues (and add the warning level charge as a buffer zone).
#echo "BAT_REMAIN = $BAT_REMAIN"
#echo "BAT_ALERT = $BAT_ALERT"
# These environment variables are needed so that the script can post to the current display (using the zenity command). Change mention of steph to whatever your username is.
export XAUTHORITY=/home/steph/.Xauthority
export DISPLAY=:0
if
then
# Log the fact that the (critically) low level has been reached.
$LOGGER -p daemon.warn "Battery capacity is critically low, shutting down the system."
# Pop up critical warning.
/usr/bin/notify-send "Battery critically low." "HIBERNATING ($BAT_REMAIN)" &
# zenity --warning --title "Battery Critically Low" --text "Battery capacity is critically low, shutting down the system. (remain = $BAT_REMAIN)" &
# This is probably a good place to shut down the computer to make sure all data is written to disk. It may even be too late by now, in which case shut down the computer when it reaches the in-built warning level.
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate
elif
then
# Log the fact that the warning level has been reached.
$LOGGER -p daemon.warn "Battery capacity is low."
# Pop up warning.
/usr/bin/notify-send "Battery low." "(remain = $BAT_REMAIN)" &
# zenity --warning --title "Battery Low" --text "Battery capacity is low. (remain = $BAT_REMAIN)" &
elif
then
# Log this to let the system know that there's only a few minutes left of battery before it hit the warning level of the battery pack
$LOGGER -p daemon.info "Battery capacity alert."
# Pop up info.
/usr/bin/notify-send "Battery depleting." "(remain = $BAT_REMAIN)" &
# zenity --info --title "Battery Alert" --text "Battery capacity alert. (remain = $BAT_REMAIN)" &
fi
fi
However, I suppose changing it to use acpi -V would involve more in-depth modifications which I am not sure of.

/proc/acpi/event: Device or resource busy

Hi
ACPI has been working fine on my Acer Travelmate for a long time - but suddenly it broke. I can't start acpid deamon - I get the following error:
acpid: can't open /proc/acpi/event: Device or resource busy
Does anybody know how to fix it?

Hello, I have the same problem, but I think (not confirmed yet) that the solution of putting acpid before hald might work... (i can't restart this notebook right now...)
Just posting this because i used "lsof" to find what process uses the /proc/acpi/event file... so it would help you to find why you can't access it even when acpid starts before hald....
21:32:58°nanex@root:/home/noice$ /etc/rc.d/acpid restart
:: Stopping acpid [FAIL]
:: Starting acpid [BUSY]
acpid: can't open /proc/acpi/event: Device or resource busy
[FAIL]
21:33:00°nanex@root:/home/noice$ /etc/rc.d/acpid stop
:: Stopping acpid [FAIL]
21:37:27°nanex@root:/home/noice$ cat /proc/acpi/event
cat: /proc/acpi/event: Device or resource busy
21:37:34°nanex@root:/home/noice$ lsof /proc/acpi/event
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/noice/.gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
hald-addo 4193 hal 4r REG 0,3 0 4026531932 /proc/acpi/event
21:32:58°nanex@root:/home/noice$ /etc/rc.d/acpid restart
:: Stopping acpid [FAIL]
:: Starting acpid [BUSY] acpid: can't open /proc/acpi/event: Device or resource busy
[FAIL]
21:33:00°nanex@root:/home/noice$ /etc/rc.d/acpid stop
:: Stopping acpid [FAIL]
21:37:27°nanex@root:/home/noice$ cat /proc/acpi/event
cat: /proc/acpi/event: Device or resource busy
21:37:34°nanex@root:/home/noice$ lsof /proc/acpi/event
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/noice/.gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
hald-addo 4193 hal 4r REG 0,3 0 4026531932 /proc/acpi/event

Button/lid (no /proc/acpi/events?)

I must be missing something obvious but it seem that when I close my laptop's lid, the button/lid section of handler.sh is not triggered. I have acpi running fine, it even seems that other events are successfully triggered (like ac_adapter), but not button/lid. Essentially I'm trying to run 'powersave -u' when I close the lid.
Help please?

Thanks for the reply. It seems like this might be part of a bigger problem though, because I don't seem to have a /proc/acpi/event. What I have in /proc/acpi are ac_adapter, battery, button, embedded_controller, fan, power_resource, processor, thermal_zone, and video.
Also, when I start my computer, Arch says that the acpi daemon started successfully. But if I stop it (also successfully) and then try to start it again, it always fails with "acpid: can't open /proc/acpi/event: Device or resource busy".
Here's some sample output from /var/log/acpid which doesn't seem to be very useful. The exiting lines are probably me manually stopping acpid, although it never starts up again unless I reboot..
[Fri Feb 17 10:59:02 2006] starting up
[Fri Feb 17 10:59:02 2006] 2 rules loaded
[Fri Feb 17 10:59:07 2006] client connected from 2788[82:82]
[Fri Feb 17 10:59:07 2006] 1 client rule loaded
[Fri Feb 17 10:59:39 2006] exiting
[Fri Feb 17 11:01:34 2006] starting up
[Fri Feb 17 11:01:34 2006] 2 rules loaded
[Fri Feb 17 11:01:39 2006] client connected from 2729[82:82]
[Fri Feb 17 11:01:39 2006] 1 client rule loaded
[Fri Feb 17 11:02:12 2006] received event "thermal_zone C176 00000081 00000000"
[Fri Feb 17 11:02:12 2006] notifying client 2729[82:82]
[Fri Feb 17 11:02:12 2006] executing action "/etc/acpi/handler.sh thermal_zone C176 00000081 00000000"
[Fri Feb 17 11:02:12 2006] BEGIN HANDLER MESSAGES
cat: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq: No such file or directory
cat: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq: No such file or directory
[Fri Feb 17 11:02:12 2006] END HANDLER MESSAGES
[Fri Feb 17 11:02:12 2006] action exited with status 0
[Fri Feb 17 11:02:12 2006] executing action "/etc/acpi/handler.sh thermal_zone C176 00000081 00000000"
[Fri Feb 17 11:02:12 2006] BEGIN HANDLER MESSAGES
cat: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq: No such file or directory
cat: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq: No such file or directory
[Fri Feb 17 11:02:12 2006] END HANDLER MESSAGES
[Fri Feb 17 11:02:12 2006] action exited with status 0
[Fri Feb 17 11:02:12 2006] completed event "thermal_zone C176 00000081 00000000"
[Fri Feb 17 11:08:30 2006] exiting
Now I'm really confused.

/proc/acpi/video/* is gone [SOLVED]

Hello!
I noticed my precious directory was missing, when i tried manually set the LCD brightness with echo value > /proc/acpi/video/my/videoadapter. I have installed laptop-mode tools for managing the brightness when plugged in AC and when on battery.
Thanks.
Last edited by nybegynner (2011-02-13 20:56:50)

Thanks, buddy!
I'm now controlling the brightness with these settings:
BATT_BRIGHTNESS_COMMAND="echo 3"
LM_AC_BRIGHTNESS_COMMAND="echo 24"
NOLM_AC_BRIGHTNESS_COMMAND="echo 24"
BRIGHTNESS_OUTPUT="/sys/class/backlight/acpi_video0/brightness"
(Note: The levels of brightness goes from 0 (least bright) through 24 (most bright)

/proc/acpi/fan empty

Hey there...
I have been trying to get at least some of the Power Management working under Linux, but haven't been too successful. Most important for me:
Spin my fan down. The temperature seems to be at 22°C, so no cooling should be needed?
Unfortunately I don't have any entries in /proc/acpi/fan, does this mean, it can't spin down? Or do I need to load any specific modules for this?
Maybe related: There is only one "trip_point" defined in thermal zone:
[root@frank /]# cat /proc/acpi/thermal_zone/THRM/temperature
temperature: 22 C
[root@frank /]# cat /proc/acpi/thermal_zone/THRM/state
state: ok
[root@frank /]# cat /proc/acpi/thermal_zone/THRM/trip_points
critical (S5): 110 C
[root@frank /]# cat /proc/acpi/thermal_zone/THRM/cooling_mode
<setting not supported>
cooling mode: critical
Btw... the CPU is an AMD Turion64, and its frequency is scaled down by cpudyn.

yes - I have 3 machines that don't detect fan settings... the i2c+lm_sensors stuff should handle that, but I never bothered...

Klaptop using /proc/acpi/sleep instead of /sys/power/state

This is a problem in kde since it disables most of the features of klaptop. In other words for me at-least kde cpu frequency scaling, standby, suspend do not work through klaptop since it seems to use /proc/acpi/sleep instead of /sys/power/state which is the only thing available in the new kernel. I am not sure if this is a kde problem, my kernel problem, or just simply my particular problem.
Is there a way to fix this.
Thanks for the help,
Matt

It also seems kde is not reading the current cpu frequency correctly. It seems to use/proc/cpuinfo instead of /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq to get the current frequency. In addition when clicking setup helper applications under ACPI Config in klaptop I get:
The /opt/kde/bin/klaptop_acpi_helper application does not seem to have the same size or checksum as when it was compiled we do NOT recommend you proceed with making it setuid-root without further investigation
Are other people having these problems as well or is this unique to me.

/proc/acpi/button does not exist.

/proc/acpi/button does not exist. Any ideas?
or, anyone knows which module is the owner of /proc/acpi/button?
Thanks!

I am having the same problem, even with a stock kernel. There is no power button
device and therefore acpi_listen does not detect putton press events. I am on a
Thinkpad T420s, which used to work until a recent reinstall. Here are the
outputs that were originally requested (most of them look quite similar to
enicham's):
% lsmod | grep evdev
evdev 11784 27
% ls /dev/input
by-id event10 event14 event2 event6 mice
by-path event11 event15 event3 event7 mouse0
event0 event12 event16 event4 event8 mouse1
event1 event13 event17 event5 event9 mouse2
% cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd event0
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=046d Product=c52b Version=0111
N: Name="Logitech Unifying Device. Wireless PID:101b"
P: Phys=usb-0000:00:1a.0-1.2:1
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.2/0003:046D:C52B.0003/0003:046D:C52B.0004/input/input2
U: Uniq=
H: Handlers=mouse0 event1
B: PROP=0
B: EV=17
B: KEY=ffff0000 0 0 0 0
B: REL=143
B: MSC=10
I: Bus=0003 Vendor=046d Product=c52b Version=0111
N: Name="Logitech Unifying Device. Wireless PID:4002"
P: Phys=usb-0000:00:1a.0-1.2:2
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.2/0003:046D:C52B.0003/0003:046D:C52B.0005/input/input3
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=12001f
B: KEY=837fff072ff32d bf54444600000000 1 30f948b17c007 ffff73fad941dfff febeffdfffefffff fffffffffffffffe
B: REL=40
B: ABS=100000000
B: MSC=10
B: LED=1f
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input4
U: Uniq=
H: Handlers=event3
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input5
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=3
B: KEY=4000 0 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input7
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
I: Bus=0019 Vendor=17aa Product=5054 Version=4101
N: Name="ThinkPad Extra Buttons"
P: Phys=thinkpad_acpi/input0
S: Sysfs=/devices/platform/thinkpad_acpi/input/input8
U: Uniq=
H: Handlers=kbd rfkill event7
B: PROP=0
B: EV=33
B: KEY=18040000 0 10000000000000 0 1501b00102004 c000000001104000 e000000000000 0
B: MSC=10
B: SW=8
I: Bus=0003 Vendor=04f2 Product=b221 Version=0752
N: Name="Integrated Camera"
P: Phys=usb-0000:00:1a.0-1.6/button
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.0/input/input9
U: Uniq=
H: Handlers=kbd event8
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input10
U: Uniq=
H: Handlers=kbd event9
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0001 Vendor=14f1 Product=506e Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input12
U: Uniq=
H: Handlers=kbd event10
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input14
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input13
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
U: Uniq=
H: Handlers=event13
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
U: Uniq=
H: Handlers=event14
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
U: Uniq=
H: Handlers=event15
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input11
U: Uniq=
H: Handlers=mouse1 event16
B: PROP=9
B: EV=b
B: KEY=6420 30000 0 0 0 0
B: ABS=260800011000003
I: Bus=0011 Vendor=0002 Product=000a Version=0000
N: Name="TPPS/2 IBM TrackPoint"
P: Phys=synaptics-pt/serio0/input0
S: Sysfs=/devices/platform/i8042/serio1/serio2/input/input18
U: Uniq=
H: Handlers=mouse2 event17
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3
% pacman -Qi linux
Name : linux
Version : 3.14.5-1
Description : The Linux kernel and modules
Architecture : x86_64
URL : http://www.kernel.org/
Licenses : GPL2
Groups : base
Provides : kernel26=3.14.5
Depends On : coreutils linux-firmware kmod
mkinitcpio>=0.7
Optional Deps : crda: to set the correct wireless channels
of your country
Required By : nvidia
Optional For : None
Conflicts With : kernel26
Replaces : kernel26
Installed Size : 71950.00 KiB
Packager : Tobias Powalowski <[email protected]>
Build Date : Sun 01 Jun 2014 01:40:01 AM EDT
Install Date : Sat 07 Jun 2014 02:21:14 PM EDT
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature
% journalctl | grep dev/input
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event6 (Power Button)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event3 (Video Bus)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event4 (Lid Switch)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event5 (Sleep Button)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event7 (ThinkPad Extra Buttons)

[SOLVED] proc/acpi/button/power missing

I have been unable to trigger an event when the power button is pressed on my laptop.
# uname -a
Linux julia 3.0-ARCH #1 SMP PREEMPT Tue Aug 30 08:53:25 CEST 2011 x86_64 AMD Turion(tm) 64 X2 Mobile Technology TL-50 AuthenticAMD GNU/Linux
acpid version 2.0.10-2, started through rc.conf as daemon.
dbus is active, HAL is not installed.
# tail -f /var/log/messages.log
Sep 6 14:48:03 localhost -- MARK --
Sep 6 15:08:03 localhost -- MARK --
Sep 6 15:28:03 localhost -- MARK --
Sep 6 15:36:02 localhost acpid: client 1328[0:100] has disconnected
Sep 6 15:36:02 localhost acpid: client connected from 2084[0:100]
Sep 6 15:36:02 localhost acpid: 1 client rule loaded
Sep 6 15:48:03 localhost -- MARK --
Sep 6 16:08:03 localhost -- MARK --
Sep 6 16:28:03 localhost -- MARK --
Sep 6 16:48:03 localhost -- MARK --
Sep 6 16:59:43 localhost logger: PowerButton pressed: PWRF
# acpi_listen
button/power PWRF 00000080 00000002
That output indicates the power button is recognized by the kernel, but it have no idea what i should put in /etc/acpi/handler.sh to shutdown the laptop when the powerbutton is pressed.
Last edited by Lone_Wolf (2011-09-07 12:02:23)

button/power PWRF 00000080 00000002
These are the arguments passed to the handler script ($1 to $4).
handler.sh from acpid package:
case "$1" in
button/power)
#echo "PowerButton pressed!">/dev/tty5
case "$2" in
PBTN|PWRF) logger "PowerButton pressed: $2" ;;
*) logger "ACPI action undefined: $2" ;;
esac
Replace the logger "PowerButton [...]" command (which is responsible for the message.log line you quote) with a shutdown invocation.

[SOLVED] ACPI handler.sh no longer working (Thinkpad X60 Tablet)

Hello there,
I recently did a few updates on my system to reduce power usage and get hdaps working. For some reason one of these changes must have broken ACPID in some way so that what I wrote in handler.sh no longer has any effect when I e.g. press the configured buttons to lock my screen or shut down, but I have no clue which.
I'm not really familiar with where ACPI and ACPID keeps all their logs either, and which parts in there might mean something for me. I don't even know how I can check if ACPI is running properly and just ACPID isn't, for instance (both are running thought, confirmed with ps -A).
Here's what I can remember of what I did:
-full system update
-install cpufreq to redcude power usage with acpi_cpufreq
-install HDAPS with Thinkpad driver, as described on the Wiki
-tweak my laptop-mode settings, e.g. disable VGA output when in laptop mode
-enable AHCI for my hard drive in kernel image and BIOS
Would be great if you could help me troubleshoot this somehow, as I really don't have a clue on how to fix this. Here's some output that might be helpful for starters:
cat /etc/acpi/handler.sh
#!/bin/sh
set $*
case "$1" in
button/power)
#echo "PowerButton pressed!">/dev/tty5
case "$2" in
PWRF)
#Power off
shutdown -h now
logger "ACPI action undefined: $2"
esac
ibm/hotkey)
#echo "Display swiveled">/dev/tty5
case "$2" in
HKEY)
case "$4" in
00005009)
#Swiveling down
/bin/sh /etc/acpi/actions/swivel-down
0000500a)
#Swiveling up
/bin/sh /etc/acpi/actions/swivel-up
00001002)
#Lock screen
xscreensaver-command -lock
#run_once xtrlock &
00001004)
#Standby button
xscreensaver-command -lock ; s2ram
00001005)
#Network button
/etc/rc.d/net-auto-wireless restart
00001009)
#Reboot
shutdown -r now
00007000)
#WLan button switched
/etc/rc.d/net-auto-wireless restart
fi
esac
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)
#laptop mode should take care of this alone!
#/etc/rc.d/laptop-mode start
00000001)
#/etc/rc.d/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
case "$2" in
LID)
if [[ `cat /proc/acpi/button/lid/LID/state | awk '{print $2}'` = "closed" ]]
then
#run_once xtrlock &
xscreensaver-command -lock
fi
esac
logger "ACPI group/action undefined: $1 / $2"
esac
dmesg | grep acpi
BIOS-e820: 000000007f6d0000 - 000000007f6df000 (ACPI data)
BIOS-e820: 000000007f6df000 - 000000007f700000 (ACPI NVS)
modified: 000000007f6d0000 - 000000007f6df000 (ACPI data)
modified: 000000007f6df000 - 000000007f700000 (ACPI NVS)
ACPI: RSDP 000f67c0 00024 (v02 LENOVO)
ACPI: XSDT 7f6d11e8 0008C (v01 LENOVO TP-7J 00001140 LTP 00000000)
ACPI: FACP 7f6d1300 000F4 (v03 LENOVO TP-7J 00001140 LNVO 00000001)
ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 (20090903/tbfadt-526)
ACPI Warning: Optional field Gpe1Block has zero address or length: 000000000000102C/0 (20090903/tbfadt-557)
ACPI: DSDT 7f6d1690 0D56F (v01 LENOVO TP-7J 00001140 MSFT 0100000E)
ACPI: FACS 7f6f4000 00040
ACPI: SSDT 7f6d14b4 001DC (v01 LENOVO TP-7J 00001140 MSFT 0100000E)
ACPI: ECDT 7f6debff 00052 (v01 LENOVO TP-7J 00001140 LNVO 00000001)
ACPI: TCPA 7f6dec51 00032 (v02 LENOVO TP-7J 00001140 LNVO 00000001)
ACPI: APIC 7f6dec83 00068 (v01 LENOVO TP-7J 00001140 LNVO 00000001)
ACPI: MCFG 7f6deceb 0003C (v01 LENOVO TP-7J 00001140 LNVO 00000001)
ACPI: HPET 7f6ded27 00038 (v01 LENOVO TP-7J 00001140 LNVO 00000001)
ACPI: SLIC 7f6dee62 00176 (v01 LENOVO TP-7J 00001140 LTP 00000000)
ACPI: BOOT 7f6defd8 00028 (v01 LENOVO TP-7J 00001140 LTP 00000001)
ACPI: SSDT 7f6f2603 0025F (v01 LENOVO TP-7J 00001140 INTL 20050513)
ACPI: SSDT 7f6f2862 000A6 (v01 LENOVO TP-7J 00001140 INTL 20050513)
ACPI: SSDT 7f6f2908 004F7 (v01 LENOVO TP-7J 00001140 INTL 20050513)
ACPI: SSDT 7f6f2dff 001D8 (v01 LENOVO TP-7J 00001140 INTL 20050513)
ACPI: Local APIC address 0xfee00000
ACPI: PM-Timer IO Port: 0x1008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
ACPI: Core revision 20090903
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI: bus type pci registered
ACPI: EC: EC description table is found, configuring boot EC
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE = 0x1c, I/O: command/status = 0x66, data = 0x62
ACPI: Power Resource [PUBS] (on)
ACPI: ACPI Dock Station Driver: 3 docks/bays found
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:1f.0: quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11)
PCI: Using ACPI for IRQ routing
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 11 devices
ACPI: ACPI bus type pnp unregistered
acpi device:01: registered as cooling_device0
ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
ACPI: Lid Switch [LID]
ACPI: Sleep Button [SLPB]
ACPI: Power Button [PWRF]
i915 0000:00:02.0: power state changed by ACPI to D0
ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ACPI: SSDT 7f6f1ccc 001FE (v01 PmRef Cpu0Ist 00000100 INTL 20050513)
ACPI: SSDT 7f6f1f4f 006B4 (v01 PmRef Cpu0Cst 00000100 INTL 20050513)
ACPI: SSDT 7f6f1c04 000C8 (v01 PmRef Cpu1Ist 00000100 INTL 20050513)
ACPI: SSDT 7f6f1eca 00085 (v01 PmRef Cpu1Cst 00000100 INTL 20050513)
ehci_hcd 0000:00:1d.7: power state changed by ACPI to D0
uhci_hcd 0000:00:1d.0: power state changed by ACPI to D0
uhci_hcd 0000:00:1d.2: power state changed by ACPI to D0
ACPI: Thermal Zone [THM0] (56 C)
ACPI: Thermal Zone [THM1] (59 C)
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery present)
thinkpad_acpi: ThinkPad ACPI Extras v0.23
thinkpad_acpi: http://ibm-acpi.sf.net/
thinkpad_acpi: ThinkPad BIOS 7JET29WW (1.14 ), EC 7JHT13WW-1.04
thinkpad_acpi: Lenovo ThinkPad X60 Tablet, model 6363WDK
thinkpad_acpi: WARNING: Outdated ThinkPad BIOS/EC firmware
thinkpad_acpi: WARNING: This firmware may be missing critical bug fixes and/or important features
thinkpad_acpi: ACPI backlight control delay disabled
thinkpad_acpi: radio switch found; radios are enabled
thinkpad_acpi: possible tablet mode switch found; ThinkPad in laptop mode
thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
Registered led device: tpacpi::thinklight
Registered led device: tpacpi::power
Registered led device: tpacpi::standby
Registered led device: tpacpi::thinkvantage
thinkpad_acpi: Standard ACPI backlight interface available, not loading native one.
ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
cat /var/log/acpid.log
Feb 28 13:19:28 damnation acpid: exiting
Mar 1 12:48:43 damnation acpid: starting up
Mar 1 12:48:43 damnation acpid: 4 rules loaded
Mar 1 12:48:43 damnation acpid: waiting for events: event logging is off
Mar 1 12:48:44 damnation acpid: client connected from 1737[82:82]
Mar 1 12:48:44 damnation acpid: 1 client rule loaded
Mar 1 12:49:39 damnation acpid: client connected from 2523[0:0]
Mar 1 12:49:39 damnation acpid: 1 client rule loaded
Mar 1 12:49:56 damnation acpid: exiting
Mar 1 12:49:56 damnation acpid: starting up
Mar 1 12:49:56 damnation acpid: 4 rules loaded
Mar 1 12:49:56 damnation acpid: waiting for events: event logging is off
Mar 1 12:49:57 damnation acpid: client connected from 2523[0:0]
Mar 1 12:49:57 damnation acpid: 1 client rule loaded
Mar 1 12:50:01 damnation acpid: client connected from 1737[82:82]
Mar 1 12:50:01 damnation acpid: 1 client rule loaded
Mar 2 10:23:50 damnation acpid: client 2523[0:0] has disconnected
Mar 2 10:23:50 damnation acpid: client connected from 2523[0:0]
Mar 2 10:23:50 damnation acpid: 1 client rule loaded
Mar 2 10:52:18 damnation acpid: client 2523[0:0] has disconnected
Mar 2 10:52:18 damnation acpid: client connected from 2523[0:0]
Mar 2 10:52:18 damnation acpid: 1 client rule loaded
Mar 2 17:00:21 damnation acpid: client 2523[0:0] has disconnected
Mar 2 17:00:21 damnation acpid: client connected from 2523[0:0]
Mar 2 17:00:21 damnation acpid: 1 client rule loaded
Mar 3 09:54:32 damnation acpid: client 2523[0:0] has disconnected
Mar 3 09:54:32 damnation acpid: client connected from 2523[0:0]
Mar 3 09:54:32 damnation acpid: 1 client rule loaded
Mar 3 10:28:14 damnation acpid: exiting
Mar 3 10:28:14 damnation acpid: starting up
Mar 3 10:28:14 damnation acpid: 4 rules loaded
Mar 3 10:28:14 damnation acpid: waiting for events: event logging is off
Mar 3 10:28:15 damnation acpid: client connected from 2523[0:0]
Mar 3 10:28:15 damnation acpid: 1 client rule loaded
Mar 3 10:28:19 damnation acpid: client connected from 1737[82:82]
Mar 3 10:28:19 damnation acpid: 1 client rule loaded
Mar 3 10:37:44 damnation acpid: exiting
Mar 3 10:37:44 damnation acpid: starting up
Mar 3 10:37:44 damnation acpid: 4 rules loaded
Mar 3 10:37:44 damnation acpid: waiting for events: event logging is off
Mar 3 10:37:45 damnation acpid: client connected from 2523[0:0]
Mar 3 10:37:45 damnation acpid: 1 client rule loaded
Mar 3 10:37:49 damnation acpid: client connected from 1737[82:82]
Mar 3 10:37:49 damnation acpid: 1 client rule loaded
Mar 3 12:22:44 damnation acpid: exiting
Mar 3 12:23:44 damnation acpid: starting up
Mar 3 12:23:45 damnation acpid: 4 rules loaded
Mar 3 12:23:45 damnation acpid: waiting for events: event logging is off
Mar 3 12:23:46 damnation acpid: client connected from 3417[82:82]
Mar 3 12:23:46 damnation acpid: 1 client rule loaded
Mar 3 12:24:40 damnation acpid: client connected from 4287[0:0]
Mar 3 12:24:40 damnation acpid: 1 client rule loaded
Mar 3 12:24:55 damnation acpid: exiting
Mar 3 12:24:55 damnation acpid: starting up
Mar 3 12:24:55 damnation acpid: 4 rules loaded
Mar 3 12:24:55 damnation acpid: waiting for events: event logging is off
Mar 3 12:24:56 damnation acpid: client connected from 4287[0:0]
Mar 3 12:24:56 damnation acpid: 1 client rule loaded
Mar 3 12:25:00 damnation acpid: client connected from 3417[82:82]
Mar 3 12:25:00 damnation acpid: 1 client rule loaded
Mar 3 12:40:54 damnation acpid: exiting
Mar 3 12:49:47 damnation acpid: starting up
Mar 3 12:49:47 damnation acpid: 4 rules loaded
Mar 3 12:49:47 damnation acpid: waiting for events: event logging is off
Mar 3 12:49:49 damnation acpid: client connected from 3396[82:82]
Mar 3 12:49:49 damnation acpid: 1 client rule loaded
Mar 3 12:50:12 damnation acpid: client connected from 5224[0:0]
Mar 3 12:50:12 damnation acpid: 1 client rule loaded
Mar 3 12:50:59 damnation acpid: exiting
Mar 3 12:50:59 damnation acpid: starting up
Mar 3 12:50:59 damnation acpid: 4 rules loaded
Mar 3 12:50:59 damnation acpid: waiting for events: event logging is off
Mar 3 12:51:00 damnation acpid: client connected from 5224[0:0]
Mar 3 12:51:00 damnation acpid: 1 client rule loaded
Mar 3 12:51:04 damnation acpid: client connected from 3396[82:82]
Mar 3 12:51:04 damnation acpid: 1 client rule loaded
Mar 3 13:21:42 damnation acpid: exiting
Mar 3 13:21:42 damnation acpid: starting up
Mar 3 13:21:42 damnation acpid: 4 rules loaded
Mar 3 13:21:42 damnation acpid: waiting for events: event logging is off
Mar 3 13:21:43 damnation acpid: client connected from 5224[0:0]
Mar 3 13:21:43 damnation acpid: 1 client rule loaded
Mar 3 13:21:47 damnation acpid: client connected from 3396[82:82]
Mar 3 13:21:47 damnation acpid: 1 client rule loaded
Mar 3 13:22:21 damnation acpid: exiting
Mar 3 13:22:21 damnation acpid: starting up
Mar 3 13:22:21 damnation acpid: 4 rules loaded
Mar 3 13:22:21 damnation acpid: waiting for events: event logging is off
Mar 3 13:22:22 damnation acpid: client connected from 5224[0:0]
Mar 3 13:22:22 damnation acpid: 1 client rule loaded
Mar 3 13:22:26 damnation acpid: client connected from 3396[82:82]
Mar 3 13:22:26 damnation acpid: 1 client rule loaded
Mar 3 13:23:03 damnation acpid: client 5224[0:0] has disconnected
Mar 3 13:23:03 damnation acpid: client connected from 5224[0:0]
Mar 3 13:23:03 damnation acpid: 1 client rule loaded
Mar 3 13:25:00 damnation acpid: exiting
Mar 3 13:25:00 damnation acpid: starting up
Mar 3 13:25:00 damnation acpid: 4 rules loaded
Mar 3 13:25:00 damnation acpid: waiting for events: event logging is off
Mar 3 13:25:01 damnation acpid: client connected from 5224[0:0]
Mar 3 13:25:01 damnation acpid: 1 client rule loaded
Mar 3 13:25:05 damnation acpid: client connected from 3396[82:82]
Mar 3 13:25:05 damnation acpid: 1 client rule loaded
Mar 3 13:29:52 damnation acpid: client connected from 21588[1000:100]
Mar 3 13:29:52 damnation acpid: 1 client rule loaded
Mar 3 13:30:27 damnation acpid: client 21588[1000:100] has disconnected
Mar 3 13:36:15 damnation acpid: exiting
Mar 3 13:37:54 damnation acpid: starting up
Mar 3 13:37:54 damnation acpid: 4 rules loaded
Mar 3 13:37:54 damnation acpid: waiting for events: event logging is off
Mar 3 13:37:56 damnation acpid: client connected from 3419[82:82]
Mar 3 13:37:56 damnation acpid: 1 client rule loaded
Mar 3 13:38:28 damnation acpid: client connected from 4292[0:0]
Mar 3 13:38:28 damnation acpid: 1 client rule loaded
Mar 3 13:39:24 damnation acpid: exiting
Mar 3 13:39:24 damnation acpid: starting up
Mar 3 13:39:24 damnation acpid: 4 rules loaded
Mar 3 13:39:24 damnation acpid: waiting for events: event logging is off
Mar 3 13:39:25 damnation acpid: client connected from 4292[0:0]
Mar 3 13:39:25 damnation acpid: 1 client rule loaded
Mar 3 13:39:29 damnation acpid: client connected from 3419[82:82]
Mar 3 13:39:29 damnation acpid: 1 client rule loaded
Mar 3 13:44:09 damnation acpid: client connected from 4488[1000:100]
Mar 3 13:44:09 damnation acpid: 1 client rule loaded
Mar 3 13:45:42 damnation acpid: client 4488[1000:100] has disconnected
Mar 3 13:58:17 damnation acpid: exiting
Mar 3 13:58:17 damnation acpid: starting up
Mar 3 13:58:17 damnation acpid: 4 rules loaded
Mar 3 13:58:17 damnation acpid: waiting for events: event logging is off
Mar 3 13:58:18 damnation acpid: client connected from 4292[0:0]
Mar 3 13:58:18 damnation acpid: 1 client rule loaded
Mar 3 13:58:22 damnation acpid: client connected from 3419[82:82]
Mar 3 13:58:22 damnation acpid: 1 client rule loaded
(are all these "client has disconnected" messages normal?)
Last edited by Natanji (2010-03-07 11:03:54)

I don't know if it works for everyone but i have just fixed the acpi rotate for my x60t
/usr/bin/xrotate
#!/bin/sh
output=LVDS1
if [ "$XROT_OUTPUT" ]
then
output=$XROT_OUTPUT;
fi
devices="stylus eraser"
geomnbr=0
xrandr=normal
wacom=normal
if [ "$1" == "-" ] || [ "$1" == "+" ] || ! [ "$1" ];
then
operator="$1";
[ "$1" ] || operator='+';
case `xrandr --verbose | grep "^$output " | sed "s/^[^ ]* [^ ]* [^ ]* ([^(]*) $[a-z]*$.*/\1/"` in
normal) geom=0;;
left) geom=1;;
inverted) geom=2;;
right) geom=3;;
esac
let geom=${geom}${operator}1+4
let geom=${geom}%4
else
geom="$1"
fi
case $geom in
1) wacom=CCW; xrandr=left ;;
2) wacom=HALF; xrandr=inverted ;;
3) wacom=CW; xrandr=right ;;
*) wacom=NONE; xrandr=normal ;;
esac
echo "xrandr to $xrandr, xsetwacom to $wacom" >&2
if xrandr --output "$output" --rotate "$xrandr"; then
for device in $devices
do
xsetwacom set "$device" Rotate "$wacom"
done
fi
#workaround for linuxwacom bug
if [ "`xsetwacom get stylus Mode`" == '1' ]; then
for decive in $devices
do
xsetwacom set stylus CoreEvent "off"
xsetwacom set stylus Mode "off"
done
{ sleep 1;
for device in $devices
do
xsetwacom set stylus Mode "on"
xsetwacom set stylus CoreEvent "on"
done; } &
fi
/etc/acpi/thinkpad-swivel-up.sh
#!/bin/bash
XAUTHORITY=/var/lib/gdm/\:0.Xauth DISPLAY=:0.0 /usr/bin/xrotate 0
/etc/acpi/thinkpad-swivel-down.sh
#!/bin/bash
XAUTHORITY=/var/lib/gdm/\:0.Xauth DISPLAY=:0.0 /usr/bin/xrotate 1
The problem was that my acpid starts long before xorg.
System:
Thinkpad x60 tablet
xorg 1.8
acpid 1.0.10

LCD Panel not supported (acpi brightness)

Hi all,
This is my first post, Hello! I have used several distros but this is my first time using Arch.
I have a dell d420 (dual core / intel graphics). I have installed Arch with lxde / compiz.
Things have been going pretty well so far, I really like the distro. However, I am having problems with laptop-tools and adjusting the brightness of my lcd on AC acpi events.
Basically, I have /etc/laptop-mode/conf.d/lcd-brightness.conf configured as follows:
# Should laptop mode tools control LCD brightness?
CONTROL_BRIGHTNESS=1
# Commands to execute to set the brightness on your LCD
BATT_BRIGHTNESS_COMMAND="echo 20"
LM_AC_BRIGHTNESS_COMMAND="echo 70"
NOLM_AC_BRIGHTNESS_COMMAND="echo 100"
BRIGHTNESS_OUTPUT="/proc/acpi/video/VID/LCD/brightness"
Further, laptop-mode is running and set up as a daemon.
The problem is when I plug/unplug the power cable the brightness of the panel does not change in the way I would expect it to. Sometimes it does not change at all, sometimes it gets brighter on battery than it does on AC!!! The brightness keys on my laptop work fine (however, they are I believe prgrammed into the bios and rely on no software to adjust the panel.)
Things I have installed / setup:
acpid
acpi
laptop-tools
I have noticed that there seems to be a problem recognising my panel, when I do a
cat /proc/acpi/video/VID/LCD/brightness
I get the response:
<not supported>
Also:
cat /proc/acpi/video/VID/LCD/info
device_id: 0x0400
type: UNKNOWN
known by bios: no
I think this is the problem, as laptop-tools and acpi seem to be configured correclty apart from this issue. Any thoughts?
Many, thanks.
Last edited by e-dard (2008-10-25 16:11:37)

OK, it looks like others have had a similar issue with the NVS 3100M adapter. I found this prior post:
I followed the advice there and installed the 32 bit A08 driver that I found here:
Now the backlight works fine on startup. Unfortunately my system has lost some other small functions and seems a bit slower, however, at least I can now work while I travel.
It's a bit disappointing that newer drivers seem to break my computer. I'd very much like for that not to happen.
Some steps of this, like updating the BIOS and installing the driver were a bit complicated, so I'm happy to give advice on how to do that if anyone needs. In the meantime if anyone has a better way to fix this, I'm keen to find out.

Deprecated /proc/acpi/

Similar Messages

Maybe you are looking for