Hot answers tagged acpi
11
Edit /etc/systemd/logind.conf and make sure you have,
HandleLidSwitch=ignore
which will make it ignore the lid being closed. (You may need to also undo the other changes you've made).
Full details over at the archlinux Wiki.
4
The program powertop should help you identify the problem.
$ sudo yum -y install powertop
$ sudo powertop
Look at the various output, and then arrow-key over to the rightmost "tab", Tunables. Look at the things which are "bad", and press enter to fix them.
Also, on the first Overview screen, look for any egregiously bad processes that might be ...
4
Analyzing the code you posted as well ass acpi_call leads me to the the conclusion that most probable candidates should be:
echo '\_SB.PCI0.PEG0.PEGP._OFF' > /proc/acpi/call
to turn the card off and
echo '\_SB.PCI0.PEG0.PEGP._ON' > /proc/acpi/call
to turn it back on again.
You should be safe to test those, as the README for acpi_call states:
...
4
With the help of the guys who commented on my question, I figured out what was wrong and fixed it in the script.
Here now the updated routines how to get automatic screen switching with your laptop to work. You need acpid, kms and udev.
Create the following rules for acpi and udev
/etc/acpi/events/lidclose
# Pass all events to our one handler script
...
4
ACPI is tied to the hardware which has changed dramatically in the last 15 years. Dual core processors which never existed (or where extremely expensive in '97) are now standard. Modern GPUs are now so power hungry that they may need their own thermal monitors. The cost of adding thermal monitors is now cheap enough other devices may also have thermal ...
3
The thermal zones temperatures for each core are available from /sys/class/thermal/thermal_zone?/temp on kernel versions > 3.x.
Your desire to seed mt_rand() using your CPU temperature makes no sense. According to the mt_rand() documentation, seeding the PRNG is done automatically in PHP versions 4.2.0+. Even if you want to seed it manually using ...
3
According to this post in the Linux kernel mailing-list, it should not mean a problem:
Unless you need to use anything on SMBus (hardware sensors, essentially) you don't have to worry about that one. It means that the kernel has detected that the BIOS may potentially access the SMBus controller which may conflict with usage of the controller from within ...
3
It might not be possible. At least there is nothing in the documentation of thinkpad-acpi, nothing in the release notes, nothing in the thinkpad-acpi thinkwiki page and no mentioning of tp_smapi being obsolete in the tp_smapi thinkwiki page.
3
I would look at the sys devices directory. For example, in Sony Vaio laptops, you can turn on the fan to max speed with this command:
while [ 1 ] ; do echo "255" > /sys/devices/platform/sony-laptop/fanspeed; sleep 0.1; done
In your laptop, try doing a:
find /sys/devices/platform/ -name "*fan*"
or manually inspect the directory using tree, looking ...
3
The fujitsu_laptop module dans control acpi for Fujitsu-Siemens laptops does not appear to have fan control code (as of today) see:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/platform/x86/fujitsu-laptop.c
(You can look at the thinkpad acpi code in the same directory, it has a fan subdriver)
I don't think it's ...
2
Well, usually you can set this temperature in the BIOS settings and it depends on the CPU type - I presume your CPU is getting hot, not some other hardware part.
If you are running linux, you can always construct some script reading out temperatures from /proc/acpi/... files - you can find temperature information there on some systems.
Or you can use ...
2
Before you go into the hassle of custom-built kernel (which might do you good anyway), you can try some more boot options to either debug the problem or maybe even boot successfully. Here are some that I'd try: acpi=noirq, acpi=strict, pci=noacpi.
One simple trick you might use is to just run your Mint on the Gentoo kernel. To do that, you must copy files ...
2
Generally this is caused by broken acpi bios, however, if you can identify a specific kernel version where it works without acpi=off, and one where it breaks, then you can start bisecting to narrow down exactly what change caused it. That could lead to finding a kernel bug that would need fixed, or possibly understanding the nature of the bug in your bios, ...
2
I'm pretty sure that your lid callback is going to be called every time the lid is closed as well as opened.
The sleep.sh file here states:
# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0
the "lid open" scenario is one your script is not ...
2
The fan gets usually controlled not by the CPU and OS, but by the System Managagement controller. This way it works even if the OS is failing.
Unfortunately this means that "fan off" errors ususally are hardware problems. Read: The fan (assembly) needs replacement.
The only exception would be a very broken ACPI implementation that can shut down the fan. ...
1
You can have a look at some stuff in /proc and /sys and see what happens; the brightness widget or whatever in your DE (you did not say which one) uses some interface to something there. /proc and /sys do not exist on disk; the files they contain are special interfaces to the kernel. Many of the files can be written to to control various things.
For ...
1
What you should do is modify the brightness manually, while checking which brightness file is modified.
e.g.
$ ls -l
total 0
lrwxrwxrwx 1 root root 0 Feb 24 14:02 dell_backlight -> ../../devices/platform/dell-laptop/backlight/dell_backlight
lrwxrwxrwx 1 root root 0 Feb 24 14:02 intel_backlight -> ...
1
Powertop is intended to be primarily a diagnostic tool, and the Tunables tab is there to support that.
The idea seems to be that these are hints to distributors about potential settings they could be change in their defaults, rather than hints to end users about to configure their system.
A discussion on the project's mailing list suggests that these are ...
1
You will need to install archlinux-keyring package to have all needed public key.
pacman -S archlinux-keyring
More information here.
Also you should lock first, suspend later:
button/lid)
case $3 in
close)
#echo "LID switched!">/dev/tty5
DISPLAY=:0.0 su -c - username /usr/bin/slimlock &
...
1
Follow this: https://wiki.archlinux.org/index.php/Pacman
Being new to Linux and going directly to Arch is not a good idea. Take a look at Fedora/Ubuntu or Debian.
Ps: You need to generate the PGP keys for arch linux so you can add them.
1
Since this is a keyboard malfunction, I'd favor blocking the keys at the keyboard level.
A simple way to do this is to reassign the keys to do nothing. You can do it with the following shell snippet:
#!/bin/sh
xmodmap - <<EOF
keysym XF86WLAN = NoSymbol
keysym XF86Bluetooth = NoSymbol
EOF
Write this script to a file, make it executable (chmod +x ...
1
Searching GMANE (a mailing list archive service) seems helpful, it yields (among others) gmane.linux.acpi.devel, the Linux ACPI Development Discussion List. While I'm not sure if it's where you'll find the developers of acpid, it is mentioned there, so it might be worth a try.
Edit Looking at Debian's packages for the homepage of some project is often ...
1
On top of pcie_aspm=force, there are a small handful of extra parameters you can add that have a marginal impact on the power consumption of your Intel on-chip GPU.
i915.i915_enable_fbc=1 will enable frame-buffer compression, which wont directly reduce power consumption, but will reduce the memory bandwidth required to draw the screen - reducing the power ...
1
On the shell try
$ ps -A r
if you see some daemons running in an abnormal behavior kill it and restart the service if it is a needed service.
In the computer I observed that, I reinstalled the daemons (2) removing in full first. After that problem is gone.
1
Gnome-shell will not reduce your battery life to half. I think you have a CPU-intensive application running all time.
Charge your battery to full charge and restart the computer. Don't open nothing and review your battery life.
Charge again the battery to full charge. Open a terminal and run "top" in this. Open your browser and use normally. Check all your ...
1
ACPI wakeup from keyboard/mouse via /proc/acpi/wakeup after suspend. How to find the correct device?
grep `ls /dev/input/by-path/*-mouse | head -1 | cut -d- -f 3` /proc/acpi/wakeup | gawk '{print $1}'
This finds the input device for your mouse, then looks up the PCI ID in /proc/acpi/wakeup to give you the name. In fact, you could just redirect the output of that command back to /proc/acpi/wakeup in order to enable wakeups from that device.
1
ACPI wakeup from keyboard/mouse via /proc/acpi/wakeup after suspend. How to find the correct device?
Ok, I've found a way, though it does not look very clean ;)
I'll start from the end - running this one-liner will tell you the truth:
grep "USB.*pci" /proc/acpi/wakeup | cut -d ':' -f 2- | while read aaa; do find /dev/.udev -name "*$aaa*" -print -exec grep "$aaa" /proc/acpi/wakeup \; -exec echo \; ; done
Nice, isn't it? And here is, how it works:
The ...
1
This can probably be solved in BIOS configuration. If there is a newer BIOS for your machine, you should use it.
Other than that, try booting with pci=noacpi option. If this results in loosing some capabilities you desire, whereas presently everything works fine despite the acpi warning, you might just disable kernel warnings using loglevel=3 boot option. ...
1
Directly calling _ON and _OFF is not recommended. I have analysed many ACPI tables for the "correct" ACPI methods that allow you to toggle the power state and have concluded that there are two generic methods that do disable the Nvidia card.
Your laptop seems to support both methods according to SSDT4 file on Launchpad. Performing ACPI method calls using ...
Only top voted, non community-wiki answers of a minimum length are eligible
