[SOLVED] ACPI sensors & fan

Hello everyone.
Months ago, with Debian Squeeze, I tried to control the speed of my fans, but I had no luck: pwmconfig said There are no pwm-capable sensor modules installed. It's the same now with ArchLinux.
I'm using a custom kernel, compiled from the linux-ck AUR package, with ACPI enabled. The funny thing is that disabling ACPI in boot options (i.e. acpi=off) leaves the fan at its maximum speed; that way, the temperature is stable around 60 ºC. With ACPI enabled (both with and without the fan ACPI module) the fan is off until the temperature reaches 95ºC; then it starts at maximum, downgrades it to about 70ºC and offs again.
My question is the following: is ACPI needed in some way? I never suspend/hybernate the system. I don't need power management since -although it's a laptop- my computer is always connected to the AC without battery. I don't want CPU frequency scaling; I want my system to be full performance.
Or, if disabling ACPI is not recommended (as I have read somewhere), is there any way to tell the kernel to start with the fan when the temperature reaches a certain value?
My laptop is HP 6735s. The output of sensors is the following:
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +88.8°C (high = +70.0°C)
(crit = +100.0°C, hyst = +95.0°C)
The processor is an AMD Turion (tm)X2 Dual Core Mobile RM-70. I use the k10temp kernel module to fetch temperature information about it.
P.S.: With the core repo kernel, there are no such problems with the temperature, although I would still prefer the fan to be more active. I believe there's no problem with that, is there? I bet it's better having the fan working at full speed than burning the CPU or the graphics card (the hottest components of my PC).
Thanks in advance. Best regards,
Kalrish
EDIT:
I've just found this thread, very close to mine. So I have some files in /sys, that seem to define the limits and the behavior of the fan according to CPU temperature values. I've tried modifying them (as root, of course), but got Permission denied! Maybe that's not the way to go? How can I tell the kernel I want fan speed at maximum until the CPU is about 50ºC? Aren't there any tweaks, configuration files...?
Last edited by Kalrish (2013-04-03 15:44:23)

I have finally found the issue.
Con Kolivas suggests having no CPU frequency scaling and letting the BFS do all the stuff (I may have misunderstood something…). It's here (I followed several desktop configuration suggestions as I do not use the battery at all).
So I disabled everything related to the processor and frequency scaling: the cpufreq kernel architecture *and* the ACPI processor module, which, in fact, implicitly disables the [ACPI] thermal module. That module was responsible of creating a virtual device, whose output was the same as k10temp's.
With that 'device', the fan works "properly" (as I said, I'd like it to be more *active*). Without it… well, 95 celsius.
There must be a problem with k10temp. I thought the kernel was responsible of choosing the speed of the fan according to the temperature it read from the appropiate modules/drivers… or maybe it's ACPI!
I'm confused. For now, I'm going to check the source code and try to understand a bit (sensors outputs some limits related to the kernel module, that I tried to edit via /sys without luck).
Thanks to everyone!
P.S.: I just want my system to have the best performance it can offer. Of course, I don't want to damage it (no overclock. Never) but… is it harmful to let the processor run at its maximum frequency? I think not, with the appropiate cooling support.
Last edited by Kalrish (2013-04-01 15:53:47)

Similar Messages

[Solved] lm-sensors fan speeds and voltage.

After installing lm-sensors and running sensors-detect I have the following readings from sensors;
~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +42.0°C (crit = +80.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +47.0°C (high = +78.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +42.0°C (high = +78.0°C, crit = +100.0°C)
I am sure in the recent past I was able to retrieve fan speed and voltage readings from this machine;
|Abit FP-IN9 SLI | Intel(R) Core(TM)2 Duo CPU [email protected] | GeForce 9800 GT |
I suspect this is something that I am doing wrong (or is it a kernel issue??) as I have the same problem on a similar machine running Ubuntu 10.04.
Any ideas appreciated.
Last edited by ancleessen4 (2010-03-09 08:31:15)

Hi graysky,
You were spot on!
I followed the instructions in the wiki article to add
acpi_enforce_resources=lax
to /boot/grub/menu.lst
Reboot...
Voila!
[neil@archbox ~]$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +30.0°C (crit = +80.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +36.0°C (high = +78.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +34.0°C (high = +78.0°C, crit = +100.0°C)
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore: +1.12 V (min = +0.00 V, max = +1.74 V)
in1: +0.91 V (min = +0.51 V, max = +0.21 V) ALARM
AVCC: +3.30 V (min = +2.98 V, max = +3.63 V)
VCC: +3.30 V (min = +2.98 V, max = +3.63 V)
in4: +1.10 V (min = +0.00 V, max = +0.14 V) ALARM
in5: +1.20 V (min = +0.13 V, max = +0.00 V) ALARM
in6: +1.58 V (min = +0.02 V, max = +0.00 V) ALARM
3VSB: +3.23 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.01 V (min = +2.70 V, max = +3.30 V)
fan1: 0 RPM (min = 340 RPM, div = 128) ALARM
fan2: 811 RPM (min = 332 RPM, div = 16)
fan3: 0 RPM (min = 340 RPM, div = 128) ALARM
fan4: 0 RPM (min = 340 RPM, div = 128) ALARM
fan5: 0 RPM (min = 527 RPM, div = 128) ALARM
temp1: +28.0°C (high = +72.0°C, hyst = +0.0°C) sensor = thermistor
temp2: +29.0°C (high = +70.0°C, hyst = +65.0°C) sensor = diode
temp3: +38.5°C (high = +70.0°C, hyst = +65.0°C) sensor = thermistor
cpu0_vid: +0.000 V
[neil@archbox ~]$
:D

[SOLVED] Lm sensors and Toshiba 4090XCDT

Hi there,
I try to setup lm_sensors on a pretty old rig (Toshiba 4090XCDT) I own to no avail. I followed http://wiki.archlinux.org/index.php/Lm_sensors but all I get is (...)
[orange@arch ~]$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +20.0°C (crit = +95.0°C)
adm1021-i2c-0-4e
Adapter: SMBus PIIX4 adapter at fe70
temp1: +48.0°C (low = -55.0°C, high = +127.0°C)
temp2: +65.0°C (low = -65.0°C, high = +70.0°C)
My goal is to control the speed of the CPU fan that spins all the time at full speed following http://wiki.archlinux.org/index.php/Fan_speed_control
Does anyone have experiences with that particular laptop? Any suggestions I may try to get this running?
Thanks!
Last edited by orange (2009-11-22 21:40:14)

I solved this problem in the meantime by writing my own fan control script. Not sure if it might be useful for someone else, but I thought sharing it (at least) cannot harm (...)
[orange@arch ~]$ cat /usr/local/bin/fancontrol
#!/bin/sh
if [ "$(sensors | tail -n 3 | awk '/temp1/ {split($2, a, "."); split(a[1], b, "+"); print b[2]}')" -lt 65 ] && [ "$(awk '/running/ {print $2}' /proc/acpi/toshiba/fan)" -eq 1 ]; then
echo "force_on:1" > /proc/acpi/toshiba/fan
echo "force_on:0" > /proc/acpi/toshiba/fan
fi
if [ "$(sensors | tail -n 3 | awk '/temp1/ {split($2, a, "."); split(a[1], b, "+"); print b[2]}')" -gt 70 ] && [ "$(awk '/running/ {print $2}' /proc/acpi/toshiba/fan)" -eq 0 ]; then
echo "force_on:1" > /proc/acpi/toshiba/fan
fi
This fan control script gets executed every 30 seconds as cronjob.
Last edited by orange (2009-11-24 14:42:43)

[SOLVED] Thinkpad T61p fan

How do I know if my fan is working like it should? I have cpu scaling, and "acpi -t" gives
Battery 1: charged, 100%
Thermal 1: ok, 48.0 degrees C
Thermal 2: ok, 45.0 degrees C
the temperatures look ok, but I'm not really doing much, and it's quite a cold weather today.
Following the thinkwiki, I entered
modprobe thinkpad-acpi experimental=1 fan_control=1
, but what's the daemon or module for this to so that the fan starts up on bootup? does this modprobe thing last permanently or just for this session?
Last edited by zephyrus17 (2008-09-16 01:34:20)

Odd. the summary told me to run "lm_sensors". Anywho, these are the results from "sensors"
acpitz-virtual-0
Adapter: Virtual device
temp1: +49.0°C (crit = +127.0°C)
temp2: +46.0°C (crit = +100.0°C)
thinkpad-isa-0000
Adapter: ISA adapter
fan1: 2514 RPM
temp1: +49.0°C
temp2: +38.0°C
temp3: +33.0°C
temp4: +49.0°C
temp5: +33.0°C
ERROR: Can't get value of subfeature temp6_input: Can't read
temp6: +0.0°C
temp7: +31.0°C
ERROR: Can't get value of subfeature temp8_input: Can't read
temp8: +0.0°C
temp9: +34.0°C
temp10: +43.0°C
temp11: +46.0°C
ERROR: Can't get value of subfeature temp12_input: Can't read
temp12: +0.0°C
ERROR: Can't get value of subfeature temp13_input: Can't read
temp13: +0.0°C
ERROR: Can't get value of subfeature temp14_input: Can't read
temp14: +0.0°C
ERROR: Can't get value of subfeature temp15_input: Can't read
temp15: +0.0°C
ERROR: Can't get value of subfeature temp16_input: Can't read
temp16: +0.0°C
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +41.0°C (high = +100.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +39.0°C (high = +100.0°C, crit = +100.0°C)
is everything what it should be?

[SOLVED] Compaq 6510b fan control

Hi all !
I installed Arch a few days ago on my laptop, a HP Compaq 6510b. Almost everything is ok, but I have a little problem with my fan. I installed cpufreqd for frequency scaling, it's ok. Then I wanted a daemon to control the fan according to the temperature, so I searched in the Wiki and found a guide.
I first installed lm_sensors, and it detected no sensors but the CPU core temp sensors. I went to the lm_sensors website, and seen that it can't work on Compaq computers. No sensors, nothing but core temp returned by hwmon, no voltage... So the daemon from the guide can't be used.
So I looked in /proc/acpi, and played a little with what I found in it. There are five fans displayed in /proc/acpi/ : C3C1, C3C2, C3C3, C3C4, C3C5. They can be turned on and off, and the real and only fan will change it's speed according to the "highest" fan activated, eg :
C3C1 : speed 5 (max)
C3C2 : speed 4
C3C3 : speed 3
C3C4 : speed 2
C3C5 : speed 1 (min)
So, if I turn C3C1 and C3C3 on, the fan turns at speed 5, and when I turn C3C1 off, it falls down to speed 3. I wrote a little script and made a menu on my desktop so I can set in one click the speed of the fan. Is this normal ? Or is it just due to the Compaq hardware which is not very well understood by the kernel ? In the same way, I have a thermal zone, TZ5, which indicates the fan speed. 0 °C : fan speed < level 3, 100 °C : max speed. :-/
Sooo... Does anybody knows a fan managing daemon, which could be configured to read CPU's temp and
1. Turn on / off several fans ?
or
2. Call a script for each temp value ?
I think I could also write a script doing this, and configure cron to launch it every 10s or so. What do you think ?
Last edited by Vladislav IV (2008-06-24 10:45:53)

ibendiben wrote:stop! ho! what guide? The cpufreq daemon is not what you are looking for? Why not?
Yes, I use cpufreqd for CPU scaling, it works. But after that, I wanted to control the fan given the temperature, which is another problem. Even though I set up cpufreqd to speed up the fan when the CPU's hot, it don't satisfy me. There is more sense giving this particular job to another process, which will not be ruled by the processor scaling one.
ibendiben wrote:I don't like that, I have a Compaq myself: 6710b... but can you explain what daemon you are talking about here?
This guide : http://wiki.archlinux.org/index.php/Fan_control explains how to set up lm_sensors, then how to set up the fan controling system with pwmconfig.
The problem is that lm_sensors doesn't work on Compaq stuff (it doesn't detect any sensor but the core temp, but no fan speed, no voltage...), and the only way I can control the fan on my laptop is to turn on/off these five virtual fans. Look at the guide, it is written :
FCFANS= hwmon0/device/pwm1=hwmon0/device/fan1_input
The real problem is : if I look in the devices under hwmon0, there is no fan input ! So pwmconfig can't regulate the fan speed. That's why I looked for another solution.
Also, as I looked at the thermal zones, I found the one which is supposed to control the fan :
$ cat /proc/acpi/thermal_zone/TZ0/trip_points
critical (S5): 256 C
active[0]: 82 C: devices=C3C1
active[1]: 74 C: devices=C3C2
active[2]: 66 C: devices=C3C3
active[3]: 45 C: devices=C3C4
active[4]: 30 C: devices=C3C5
Given the critical temp (256 °C) I think it's the GPU sensor (but I think 256 °C is quite hot, even as critical, for that kind of GPU...). As you can see, it should increase the fan speed when this thermal sensor reach 30, 45, 66... But in fact, it's always < 50 °C, so the fan will keep turning slowly. Even if the CPU is at 65 °C So I thought it was not stupid to speed up the fan while looking at another thermal sensor (the CPU in my case).
I think I should also improve my script to make it look at several temperatures (CPU, GPU...) and adjust the fan speed to keep cool every component.
ibendiben wrote:Does every laptop (mine?) have several fans? The reason I'm interested is that my fan is blowing like hell and I can feel parts of the bottom are quite hot. So only when I use cpufreq scaling powersave to 1ghz the fan will rest in peace.
You're script is interesting and I could go and test it, but I'd like to know a little more first.
There are one or two fans, even three for the more powerful ones (with dedicated gaming 3D card), but in my case (6510b) there is only one. One physical, but under /proc/acpi/fan there are five fans, which correspond to the five speeds of the laptop's fan.
You can always install lm_sensors and a ressources monitor (I use gkrellm) to keep an eye open on all the temperatures and CPU usage. Then go under /proc/acpi/fan, and if you have four or five fans (like C3C1, C3C2, ..., C3C5), you can turn them on, one at a time, from the last to the first. You should hear your laptop's fan speed increase as you activate the different levels.
Oh, and as I said, in my case the thermal zone TZ5 is the fan speed. So don't panic if you see a thermal sensor going from 0 °C to 100 °C while you play with the fan

[SOLVED] ACPI power issues with Sony Vaio Pro 13

tl;dr backstory:
Sony VAIO Pro 13 (SVP13215CDB) laptop was working great (Win 8.1).
Installed Win10 Tech Preview. A week later, it started going to sleep randomly and on certain key-presses (perhaps after performing Sony Vaio Software updates. I'm not 100% sure). I wiped all partitions installing Win7 in legacy mode. It still went to sleep randomly.
I restored to factory default Win8.1 with Sony Vaio software up-to-date. It still went to sleep randomly.
Took it to an electronics repair shop, to see if they could fix it, and they said it can't be fixed in any way without replacing motherboard, but that's basically a new laptop.
So I turned to Arch Linux.
I have completed the basic install from the Wiki, and it no longer sleeps/shuts down randomly, but it will gracefully shutdown when certain events/keypresses occur.
I installed acpid and used "acpi_listen >> acpi.log" to determine what causes the system to perform a graceful shutdown. Here is the result of acpi.log (each line was a shutdown event):
button/power PBTN 00000080 00000000 # Unplugged power adapter.
button/power PBTN 00000080 00000000 # Running on battery and idle. Perhaps battery percent update caused this?
button/power PBTN 00000080 00000000 # Plugged in power adapter.
button/power PBTN 00000080 00000000 # Fn-F1 Touchpad Disable
button/power PBTN 00000080 00000000 # Fn-F5 Brightness Down
button/power PBTN 00000080 00000000 # Fn-F6 Brightness Up
button/power PBTN 00000080 00000000 # Fn-F7 LCD/External Display
button/power PBTN 00000080 00000000 # Fn-1 (Weird. It has no extra function).
As you can see, they all seem to trigger the same shutdown event.
I have seen on other posts that these ACPI signals can be disabled or assigned to other commands, which would be an acceptable workaround if it stops my laptop from erroneously shutting down. Is this doable?
Also, I was not able to reflash the Sony VAIO firmware when using Windows, as Sony's package software is amazing wouldn't allow flashing an equal or lesser firmware version. Perhaps there is a way in Arch to force a reflash if I can get my hands on the firmware blob?
Thanks .
Last edited by SafeToRemoveACPI (2014-11-25 22:55:55)

linux /boot/vmlinuz-linux root=UUID=<UUID here> rw quiet acpi=off
Like this?
I did that, and it disabled my laptop keyboard entirely. In doing so, it disables the key-presses that would normally shutdown the laptop, including the power button. So the only way to shut it down is a hard shutdown via long-press of the power button. Thanks, though.
Update: Issue Solved. I will update post tonight. Flashing the BIOS again resolved the ACPI issues.
Last edited by SafeToRemoveACPI (2014-11-25 22:54:13)

[SOLVED] acpi - Broadcom wireless- too many interrupts

Hi
I have an Ideapad U350:
Pentium SU4100
Chipset: GS40
My wireless card:
lspci -vnn | grep 14e4
03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:04ad]
08:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe [14e4:1692] (rev 01)
iwconfig
lo no wireless extensions.
eth1 no wireless extensions.
eth0 IEEE 802.11abg ESSID:"XXX"
Mode:Managed Frequency:2.462 GHz Access Point: XXX
Bit Rate=54 Mb/s Tx-Power=200 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=70/70 Signal level=-37 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
The problem is that i have too many interrupts from acpi:
cat /proc/interrupts
CPU0 CPU1
0: 59726 61956 IO-APIC-edge timer
1: 1111 1159 IO-APIC-edge i8042
8: 1 0 IO-APIC-edge rtc0
9: 34724550 34723449 IO-APIC-fasteoi acpi
12: 555976 555190 IO-APIC-edge i8042
16: 0 0 IO-APIC-fasteoi uhci_hcd:usb2
17: 103054 104287 IO-APIC-fasteoi eth0
18: 0 0 IO-APIC-fasteoi uhci_hcd:usb7
19: 84 68 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb4, uhci_hcd:usb6
21: 0 0 IO-APIC-fasteoi uhci_hcd:usb3
23: 1 1 IO-APIC-fasteoi uhci_hcd:usb5, ehci_hcd:usb8
46: 11776 11651 PCI-MSI-edge ahci
47: 400 405 PCI-MSI-edge snd_hda_intel
48: 137735 136131 PCI-MSI-edge i915
49: 2 1 PCI-MSI-edge eth1
NMI: 1661 1673 Non-maskable interrupts
LOC: 249956 280136 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 1661 1673 Performance monitoring interrupts
IWI: 0 0 IRQ work interrupts
RTR: 0 0 APIC ICR read retries
RES: 303961 261227 Rescheduling interrupts
CAL: 43 84 Function call interrupts
TLB: 9561 9373 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 14 14 Machine check polls
ERR: 0
MIS: 0
This is not a new issue, but till kernel 3.0 it could be resolved by compiling the broadcom sta driver (or using broadcom wl from AUR which is the same).
In kernel 3.0 and 3.1 the boot option 'pci=noacpi' had also to be added to minimize the interrupts.
My Laptop used to have idle power consumption of 8-9W and now it has 17W.
Because of the interrupts the CPU is never idle and the fan is constantly running.
Modules used:
lsmod|grep wl
wl 2557159 0
cfg80211 176889 1 wl
lib80211 3949 2 wl,lib80211_crypt_tkip
Powertop output:
Top causes for wakeups:
96.8% (17008.4) [acpi] <interrupt>
2.2% (387.0) PS/2 keyboard/mouse/touchpad interrupt
0.3% ( 47.7) [i915] <interrupt>
0.2% ( 29.8) swapper/1
0.1% ( 22.2) Xorg
0.1% ( 22.0) [Rescheduling interrupts] <kernel IPI>
0.1% ( 21.1) [eth0] <interrupt>
0.1% ( 18.9) swapper/0
0.1% ( 11.2) firefox
I have searched for weeks for a solution with kernel 3.3 and i have tried many boot options with acpi.
Turning acpi completely off leads to the same effect with software timer cosing the interrupts.
I have also tried the open source driver b43, which also worked but it had the same problem.
It would be great if anyone could help.
Last edited by Loch1985 (2012-05-06 19:22:47)

Yes! Thanks!
Solution:
add boot option:
acpi_os_name="Microsoft Windows NT"
REMOVE battery and boot
not sure if boot option is necessary because i removed it and its still ok....
Now it works with battery as well..

[solved] acpi - cannot load module

Hi,
I know that I'am not the only one with this problem, but I haven't found a clear solution yet. After doing a clean install with Gimmick, I tried to scale cpu-frequency. Thought I would follow the instructions in the French wiki page: http://wiki.archlinuxfr.org/doku.php?id=acpi_powernowd
I have installed acpi and powernow, of course. I have an AMB Sempron 2800+ processor, which supports powernow-k8. However, when I try "modprobe acpi", I receive this message:
FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.16-ARCH/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device
But the file manager tells me that this module might be found under exactly this path ...
Searching around I have found that someone apparently solved this problem by recompiling the kernel without SMP support. I am afraid that this is somewhat beyond my reach (i don't even a have clue what SMP is). Please let know if there is an easier way to get things done.
Best wishes, t.

Ooops - yes, I see ... Admittedly, my French isn't the best
It is running fine now with powernow-k8, cpufreq_userspace and powernowd.
Thanks for the hint, t.

SOLVED: GTX 770 Fan Speed Stuck at Full

Ever since I set up my GTX 770 in my computer, the fan speed appears to be set on full constantly. I have tried to use MSI Afterburner to solve the problem, but to no avail as adjusting the fan speed curve in Afterburner seems to do nothing. As soon as it boots, the fans ramp up to what sounds like max and stay like that. I was wondering if there was anyone else with this problem and if I can fix it.
Thanks in advance,
muddyducky
EDIT: Turns out it was actually every other fan in my computer running at 4000rpm that caused it - managed to turn it down in MSI Control Centre :P

Do you still have a question/problem?

KT4 Ultra (6590) - NB Chipset Sensor Fan

The KT4 Ultra have three Fan Power Connectors, how can i read in the manual:
"Fan Power Connectors: CFAN1/SFAN1/NBFAN1
The CFAN1 (processor fan), SFAN1 (system fan) and NBFAN1
(NorthBridge fan) support system cooling fan with +12V. It supports three pin
head connector."
The mobo have onboard a Winbond W83697HF sensor chipset.
With every software (PCAlert,Speedfan,Everest) i tried to read sensors statistics (Temp/Fan speed), i can read only two stats.
I have three fan connected:
1 for the CPU - CFAN1 (i can read Temp and Fan speed)
1 for the system - SFAN1 (i can read Temp and Fan speed)
1 for the NorthBridge - NBFAN1 (provided by the mobo itself and i can't read stats)
The NBFan is working and is three pin capable (three wires).
Every software show only two stats and not three with one all zero.
Now i have to change the fan or simple the mobo don't provide stats for the NB chipset?
someone with the same mobo can read this stats?
Thanks for every help.

Has it been like this for 5+ years? Probably the sensor is gone or damaged. Don't think so, but it is also possible the fan connection is damaged, so not all three reach the motherboard. (Upside down?)
If you have no problem I wouldn't worry about it. Once you start experiencing problems get a fanless heatsink, from Zalman for example. Think this will fit:
http://datorfixarna.com/catalog/product_info.php?cPath=28_96&products_id=5518&osCsid=cc705d4624a4078474841a9cf4109899

[SOLVED] ACPI problem - shutdown and battery error

Hi All,
I've installed Arch and it looks cool, but not everything work.
I can't get acpi related infos (like battery state), or turn off my laptop. I tried hard, but i couldn't solve it.
here are some info, if you could help me:
-actually I can reboot flawlessly
-i removed autodetect from the hooks list because its building lasted forever
-lshw : http://pastebin.com/Q6Cy9Ppy
-dmesg : http://pastebin.com/LdFTrmaC
systemctl status systemd-udevd :
● systemd-udevd.service - udev Kernel Device Manager
Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static)
Active: active (running) since cs 2014-11-27 15:49:17 CET; 57min ago
Docs: man:systemd-udevd.service(8)
man:udev(7)
Main PID: 136 (systemd-udevd)
CGroup: /system.slice/systemd-udevd.service
├─136 /usr/lib/systemd/systemd-udevd
├─137 /usr/lib/systemd/systemd-udevd
├─138 /usr/lib/systemd/systemd-udevd
├─139 /usr/lib/systemd/systemd-udevd
├─141 /usr/lib/systemd/systemd-udevd
├─142 /usr/lib/systemd/systemd-udevd
├─143 /usr/lib/systemd/systemd-udevd
├─144 /usr/lib/systemd/systemd-udevd
├─145 /usr/lib/systemd/systemd-udevd
└─146 /usr/lib/systemd/systemd-udevd
nov 27 15:49:17 Arch-AcerTM4500 systemd-udevd[136]: starting version 217
nov 27 15:50:19 Arch-AcerTM4500 systemd-udevd[136]: worker [140] /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/ACPI0001:00/ACPI0002:00 is taking a long time
nov 27 15:50:19 Arch-AcerTM4500 systemd-udevd[136]: worker [145] /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:09/PNP0C09:00/ACPI0001:00/ACPI0002:00 is taking a long time
nov 27 15:52:19 Arch-AcerTM4500 systemd-udevd[136]: worker [140] /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/ACPI0001:00/ACPI0002:00 timeout; kill it
nov 27 15:52:19 Arch-AcerTM4500 systemd-udevd[136]: seq 1138 '/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/ACPI0001:00/ACPI0002:00' killed
nov 27 15:52:19 Arch-AcerTM4500 systemd-udevd[136]: worker [145] /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:09/PNP0C09:00/ACPI0001:00/ACPI0002:00 timeout; kill it
nov 27 15:52:19 Arch-AcerTM4500 systemd-udevd[136]: seq 1060 '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:09/PNP0C09:00/ACPI0001:00/ACPI0002:00' killed
Sorry for my strange sentences, i didn't speak or write English a long time ago.
Last edited by vs22 (2015-02-13 09:13:17)

I don't know why, but now it works.
Possible reasons:
previously I installed my system from bootstrap and now from the iso
Arch updates
Now I use journaling in ext4 previously not (I've installed both time to usb flash)

Problem with Sensor fan 3 and 4 (P67A-GD65

Hi all :D.
I had buy 1 week ago a new P67A-GD65 motherboard but i have found a problem .
Today, i have connected my 4 fan in three different slot fan.
When i look with EFI the rpm of the fan,i can look only CPU_FAN SYS_Fan1 and SYS_FAN2 but not for SYS_Fan3.
Where is the problem? Sensor? Or what?
I had try to use AIDA64 and SPEEDfan but same problem

Not all Fan headers support fan monitoring & fan speed adjustion. That is not a bug but rather the lack of a feature.

[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

[SOLVED] ACPI daemon can't open display unless restarted

I'm trying to set up a machine to have X rotate the screen (using xrandr) on an ACPI event. (It's a tablet PC.)
The rotation script works fine, and gets called properly on the ACPI event, but when xrandr is called it outputs "Cannot open display" to stderr.
The odd thing is this: If I restart the acpi daemon, the whole thing works seamlessly, even after killing and restarting X. Does anybody have any idea why this would be so?
Last edited by tlawson (2009-01-25 12:40:07)

@anrxc: sorry to misdirect my criticism. no hard feelings?
@all: so, a little research reveals that these lines:
Jan 24 00:14:08 malachite acpid: client connected from 2315[0:1000]
Jan 24 00:14:08 malachite acpid: 1 client rule loaded
Jan 24 00:14:12 malachite acpid: client connected from 2096[82:82]
Jan 24 00:14:12 malachite acpid: 1 client rule loaded
mean that those processes are listening to /var/run/acpid.socket.
from 'man acpid':
In addition to rule files, acpid also accepts connections on a UNIX
domain socket (/var/run/acpid.socket by default). Any application may
connect to this socket. Once connected, acpid will send the text of
all ACPI events to the client. The client has the responsibility of
filtering for messages about which it cares.
this is neat, because the problem with your original 'xrandr' invocations from '/etc/acpid/handler.sh' is that they're run by root in acpid's environment, where XAUTHORITY and DISPLAY are unset. if they were called by some event handler operating *within* the x server's scope, there'd be no need for ugly hacks to get the DISPLAY. so the question is, how do you get x to listen for "ibm/hotkey HKEY 00000080 {00005009,0000500a}".
i haven't found a really good answer yet, but the last post in this thread has an interesting suggestion:
http://ubuntuforums.org/showthread.php?t=651248
if you could get it generate a keycode, and verify that x receives that with 'xev', then you can configure x or your wm to respond to. the advantage to having x respond directly is that you have the keycode bound in a system-wide x configuration so that you could have multiple x sessions running and they'd *all* respond to the swivel actions. and on the console, it would do... nothing! it might even make more sense to handle the event in '/etc/acpi/events/' than in the all-purpose handler.
and, i did some googling and found these for you, which i hope help:
http://www.krizka.net/2008/02/13/thinkp … der-linux/
http://ubuntuforums.org/showthread.php?t=604896
you did google "your-tablet swivel rotate x", right? :b

[solved] ACPI Info failed

Hi I'm having issues with my Arch installation on my laptop
I'm using i3wm with i3bar & i3status and have everything working fine except for one thing:
The i3status "gets stuck" meaning it doesn't update battery/clock stats. When I reset i3status it doesn't appear anymore either. When i run ACPI in the terminal, nothing shows up (just a blank screen). Same thing with htop. Top seems to work fine but viewing the date and time through the terminal command works fine.. It's just the battery stats screwing up. Htop reads battery life also so I figure that's why it hangs..
Here's a portion (most recent portion) of the dmesg output if it helps (there's some ACPI Error message I don't understand). This problem occurs randomly and is always fixed with a reboot.. but I'd rather not have to reboot.
[18610.212991] PM: Syncing filesystems ...
[18610.656035] done.
[18610.656042] PM: Preparing system for mem sleep
[18610.656551] Freezing user space processes ... (elapsed 0.001 seconds) done.
[18610.657874] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[18610.658951] PM: Entering mem sleep
[18610.659004] Suspending console(s) (use no_console_suspend to debug)
[18610.659488] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[18610.780306] sd 0:0:0:0: [sda] Stopping disk
[18611.846165] PM: suspend of devices complete after 1185.545 msecs
[18611.846376] PM: late suspend of devices complete after 0.208 msecs
[18611.849155] r8169 0000:0a:00.0: System wakeup enabled by ACPI
[18611.872922] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[18611.886402] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[18611.912844] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[18611.926214] PM: noirq suspend of devices complete after 79.745 msecs
[18611.926398] ACPI: Preparing to enter system sleep state S3
[18611.926548] PM: Saving platform NVS memory
[18611.927156] Disabling non-boot CPUs ...
[18611.928387] kvm: disabling virtualization on CPU1
[18612.029634] smpboot: CPU 1 is now offline
[18612.031067] kvm: disabling virtualization on CPU2
[18612.133067] smpboot: CPU 2 is now offline
[18612.134429] kvm: disabling virtualization on CPU3
[18612.236515] smpboot: CPU 3 is now offline
[18612.237630] ACPI: Low-level resume complete
[18612.237668] PM: Restoring platform NVS memory
[18612.238096] Enabling non-boot CPUs ...
[18612.238130] x86: Booting SMP configuration:
[18612.238131] smpboot: Booting Node 0 Processor 1 APIC 0x1
[18612.249751] kvm: enabling virtualization on CPU1
[18612.252084] Intel pstate controlling: cpu 1
[18612.252152] CPU1 is up
[18612.252168] smpboot: Booting Node 0 Processor 2 APIC 0x2
[18612.263702] kvm: enabling virtualization on CPU2
[18612.265943] Intel pstate controlling: cpu 2
[18612.265981] CPU2 is up
[18612.265997] smpboot: Booting Node 0 Processor 3 APIC 0x3
[18612.277526] kvm: enabling virtualization on CPU3
[18612.279786] Intel pstate controlling: cpu 3
[18612.279824] CPU3 is up
[18612.282987] ACPI: Waking up from system sleep state S3
[18612.348033] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[18612.374737] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
[18612.401442] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
[18612.441648] PM: noirq resume of devices complete after 117.195 msecs
[18612.441850] PM: early resume of devices complete after 0.176 msecs
[18612.441976] mei_me 0000:00:16.0: irq 46 for MSI/MSI-X
[18612.442200] snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X
[18612.484192] r8169 0000:0a:00.0: System wakeup disabled by ACPI
[18612.645265] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
[18612.699308] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[18612.699311] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[18612.781882] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[18612.791860] ata5.00: configured for UDMA/100
[18612.897396] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[18612.897399] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[18613.097651] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[18613.097654] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[18613.298206] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[18613.298209] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[18613.498078] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[18613.498081] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[18613.629818] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[18613.698271] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[18613.698274] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[18615.341478] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[18615.354081] ata1.00: configured for UDMA/133
[18615.365017] sd 0:0:0:0: [sda] Starting disk
[18616.047534] PM: resume of devices complete after 3601.561 msecs
[18616.048455] PM: Finishing wakeup.
[18616.048457] Restarting tasks ... done.
[18616.052792] usb 3-3: USB disconnect, device number 3
[18616.062188] video LNXVIDEO:00: Restoring backlight state
[18616.062194] video LNXVIDEO:01: Restoring backlight state
[18616.112293] systemd[1]: Service tlp-sleep.service is not needed anymore. Stopping.
[18616.179245] iwlwifi 0000:08:00.0: no hotplug settings from platform
[18616.179280] r8169 0000:0a:00.0: no hotplug settings from platform
[18616.333431] iwlwifi 0000:08:00.0: L1 Enabled; Disabling L0S
[18616.341035] iwlwifi 0000:08:00.0: Radio type=0x2-0x0-0x0
[18616.410512] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[18616.511451] r8169 0000:0a:00.0 eno1: link down
[18616.511491] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[18617.467805] wlo1: authenticate with 58:6d:8f:5a:72:e7
[18617.471308] wlo1: send auth to 58:6d:8f:5a:72:e7 (try 1/3)
[18617.474106] wlo1: authenticated
[18617.477162] wlo1: associate with 58:6d:8f:5a:72:e7 (try 1/3)
[18617.479695] wlo1: RX AssocResp from 58:6d:8f:5a:72:e7 (capab=0x401 status=0 aid=3)
[18617.482591] wlo1: associated
[18617.482643] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
[18617.482956] wlo1: deauthenticating from 58:6d:8f:5a:72:e7 by local choice (reason=2)
[18617.488654] wlo1: authenticate with 58:6d:8f:5a:72:e7
[18617.492128] wlo1: send auth to 58:6d:8f:5a:72:e7 (try 1/3)
[18617.492506] cfg80211: Calling CRDA to update world regulatory domain
[18617.497135] wlo1: authenticated
[18617.500529] wlo1: associate with 58:6d:8f:5a:72:e7 (try 1/3)
[18617.503124] wlo1: RX AssocResp from 58:6d:8f:5a:72:e7 (capab=0x401 status=0 aid=3)
[18617.506527] wlo1: associated
[18627.519113] wlo1: deauthenticating from 58:6d:8f:5a:72:e7 by local choice (reason=3)
[18627.527313] cfg80211: Calling CRDA to update world regulatory domain
[18628.104060] wlo1: authenticate with 58:6d:8f:5a:72:e7
[18628.107098] wlo1: send auth to 58:6d:8f:5a:72:e7 (try 1/3)
[18628.109889] wlo1: authenticated
[18628.112658] wlo1: associate with 58:6d:8f:5a:72:e7 (try 1/3)
[18628.115386] wlo1: RX AssocResp from 58:6d:8f:5a:72:e7 (capab=0x401 status=0 aid=3)
[18628.117992] wlo1: associated
[18711.915093] usb 3-3: new low-speed USB device number 4 using xhci_hcd
[18711.948946] usb 3-3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[18711.948955] usb 3-3: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
[18711.958851] input: Chicony USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/input/input29
[18711.959137] hid-generic 0003:04F2:0402.0007: input,hidraw0: USB HID v1.11 Keyboard [Chicony USB Keyboard] on usb-0000:00:14.0-3/input0
[18711.980686] input: Chicony USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.1/input/input30
[18711.981173] hid-generic 0003:04F2:0402.0008: input,hiddev0,hidraw1: USB HID v1.11 Device [Chicony USB Keyboard] on usb-0000:00:14.0-3/input1
[18725.987812] usb 3-2: new full-speed USB device number 5 using xhci_hcd
[18726.009897] logitech-djreceiver 0003:046D:C52B.000B: hiddev0,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-2/input2
[18769.731156] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.MMRD] (Node ffff8802538d1f50), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[18769.731169] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.RDMB] (Node ffff8802538d2938), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[18769.731175] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.RDMW] (Node ffff8802538d2960), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[18769.731180] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node ffff8802538d24d8), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[18769.731189] ACPI Exception: AE_AML_INFINITE_LOOP, Evaluating _BST (20131115/battery-473)
[18978.554233] input: Logitech Unifying Device. Wireless PID:1025 as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.2/0003:046D:C52B.000B/input/input31
[18978.554869] logitech-djdevice 0003:046D:C52B.000C: input,hidraw3: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1025] on usb-0000:00:14.0-2:1
[19207.166990] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.MMRD] (Node ffff8802538d1f50), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[19207.167004] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.RDMB] (Node ffff8802538d2938), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[19207.167010] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.RDMW] (Node ffff8802538d2960), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[19207.167015] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node ffff8802538d24d8), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[19207.167026] ACPI Exception: AE_AML_INFINITE_LOOP, Evaluating _BST (20131115/battery-473)
[19644.603035] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.MMRD] (Node ffff8802538d1f50), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[19644.603055] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.RDMB] (Node ffff8802538d2938), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[19644.603062] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.RDMW] (Node ffff8802538d2960), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[19644.603070] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node ffff8802538d24d8), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[19644.603083] ACPI Exception: AE_AML_INFINITE_LOOP, Evaluating _BST (20131115/battery-473)
[20082.062360] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.MMRD] (Node ffff8802538d1f50), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[20082.062398] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.RDMB] (Node ffff8802538d2938), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[20082.062405] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.RDMW] (Node ffff8802538d2960), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[20082.062410] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node ffff8802538d24d8), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[20082.062421] ACPI Exception: AE_AML_INFINITE_LOOP, Evaluating _BST (20131115/battery-473)
[20519.518413] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.MMRD] (Node ffff8802538d1f50), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[20519.518430] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.RDMB] (Node ffff8802538d2938), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[20519.518436] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.RDMW] (Node ffff8802538d2960), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[20519.518443] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node ffff8802538d24d8), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[20519.518455] ACPI Exception: AE_AML_INFINITE_LOOP, Evaluating _BST (20131115/battery-473)
Can anyone help me figure this out? This kind of problem happened on Ubuntu 13.10 also. Thanks in advance guys.
Edit:
I also have my kernel parameters set as this if it helps
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor acpi_osi='!Windows 2012'"
Edit: Fixed
So this error seems independent of i3status or anything else. It's dependent on ACPI info stuff and only fails while running on battery mode. I'm not too sure exactly what goes wrong except for that it goes in an Infinite Loop (from looking at dmesg)
The fix that seemed to work for me is adding
acpi_osi=Linux
to my kernel boot paramters.
My boot parameters in grub now looks like this
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor acpi_osi=Linux acpi_osi='!Windows 2012'"
Ran on battery mode for at least 5-6 hours total, suspending and resuming, etc and so far there has been no problems. Seems like this fixed it.
Last edited by xifuvo (2014-04-26 20:00:28)

Please edit your post.
When posting configs, code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through.

[SOLVED] ACPI sensors & fan

Similar Messages

Maybe you are looking for