Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm on Slackware-13.37 and need to update my ancient (Fedora or debian) acpi scripts which reference /proc/acpi, because as we would say here:There it is - gone!
This line that does a battery low check
Quote:
Next hopefully check the Battery is dead low
if grep -q critical /proc/acpi/battery/state
I tried leaving stuff out ( -->Instant hibernate) or replaced with
Quote:
# Next hopefully check the Battery is dead low
if grep -q critical /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/C1ED/status
And the thing stays on 'Discharging' until it dies. Yet the system knew what was going on, because I had this flashing orange light.
Where to pick it up?
and I have hunted here for some time before posting. Here's a listing:
Quote:
bash-4.1$ ls
alarm charge_now device/ power status type voltage_now
charge_full current_now manufacturer present subsystem uevent
charge_full_design cycle_count model_name serial_number technology voltage_min_design
The 'alarm' apparently occasionally flicks to 1 (It's normally 0) and I got nearly instant hibernate function when I tried watching that.
if grep -q 1 /sys/blah/alarm;
uevent has a line which is also in status which simply says discharging, until it's dead. The charge files have one six digit number (ľAh?). /proc/acpi is gone. Do I have to measure the value in charge now (currently 1267000) or something? How the <expletive deleted> would you do that in a bash script? (charge_now now 1200000).
Hmmm - I get a BAT0 that links back to that sysfs directory. As BAT0. Has all the content you'd expect (on Fedora 16 BTW, not Slack).
I thought I saw something similar reported. Fix was something about turning WMI off; needs a kernel recompile I think. Check the ACPI bugzilla.
I also see HP_WMI.
Time for you to make some decisions I guess - what do you want to be without the least ?. It's only a kernel build - try it and see.
This has been sorted as follows. I followed the Standard Procedure outlined to me from my days in R & D:
"If at first you don't succeed - give up!"
I preferred acpi over XFCE's Power Manager as I am capable of running sessions without X running at all, but I will settle for XFCE's Power Manager. I have configured it to act on battery critical instead of configuring it to play in the traffic. It talks to Hal - the aptly named hardware interface (For anyone who saw the film 2001) http://en.wikipedia.org/wiki/HAL_9000
Thanks, Guru, but what can the ordinary mortal who has a life to lead do?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.