3x+ battery life

Unia · 2012-06-07 09:02:28

I decided to go for the pm-utils way, but I rebuild upower without idevice support so it doesn't need additional dependencies. If you want to do the same, use this PKGBUILD:

pkgname=upower
pkgver=0.9.16
pkgrel=1
pkgdesc="Abstraction for enumerating power devices, listening to device events and querying history and statistics"
arch=('i686' 'x86_64')
url="http://upower.freedesktop.org"
license=('GPL')
depends=('udev' 'libusb' 'polkit' 'pm-utils' 'dbus-glib')
makedepends=('intltool' 'gobject-introspection' 'docbook-xsl')
options=('!libtool')
source=($url/releases/$pkgname-$pkgver.tar.xz)
sha256sums=('eb9a3d39a8cb62970fd612e333bc7a43437ab0e7890303578b0a7e3c67c8c212')

build() {
  cd "$pkgname-$pkgver"

  # put udev files in /usr/lib
  sed -i "/slashlibdir=/s#/lib#/usr/lib#" configure

  ./configure --prefix=/usr --sysconfdir=/etc \
      --localstatedir=/var \
      --libexecdir=/usr/lib/upower \
      --with-systemdsystemunitdir=/usr/lib/systemd/system \
      --disable-static \
      --without-idevice
  make
}

package() {
  cd "$pkgname-$pkgver"
  make DESTDIR="$pkgdir" install
}

nierro · 2012-06-07 10:39:17

I found easier anyway to use acpid, and put a line in rc.local (or creating a systemd unit, as i did) .
Read here to understand my problem with pm-utils and upowerd -> https://bugs.archlinux.org/task/29974
Yeah it is very long

Zucca · 2012-06-07 15:43:38

Unia wrote:

Hm, here's a disadvantage of using handler.sh: it will only switch power states when you (un)plug the power. When you boot with power unplugged, it will not automatically trigger powerdown.

That problem can be solved by adding few lines to rc.local for example.

Unia · 2012-06-07 17:11:58

Zucca wrote:

Unia wrote:
Hm, here's a disadvantage of using handler.sh: it will only switch power states when you (un)plug the power. When you boot with power unplugged, it will not automatically trigger powerdown.
That problem can be solved by adding few lines to rc.local for example.

Such as?

nierro · 2012-06-07 17:20:40

it depends: do you want to use acpid with pm-utils or acpid with powerdown and powerup script?
In the first case you only must put "pm-powersave" in rc.local.
In the second

if cat /sys/class/power_supply/AC0/online | grep 0 > /dev/null 2>&1
then
powerdown
else 
powerup
fi

Last edited by nierro (2012-06-07 17:20:49)

Unia · 2012-06-09 21:53:07

For those of you looking for the pm-utils way of doing things, you can find my script here:
https://github.com/Unia/Powersave

Thought it might come in handy for some of you. All credit goes to Taylorchu for his initial work on this!

TheImmortalPhoenix · 2012-06-09 22:47:02

Your script looks great dear Unia, i'm using it, i think it's confortable...I've just a problem with setting brightness...when i'm in 'powersave' mode, it is correctly set to '0', but when i return to 'normal' mode, it's not set back to '9' but remains to '0'
I tried to edit file manually but i got this error:

"/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/brightness" E667: Fsync failed

Can anyone help me to solve this issue?

EDIT: I don't know why but now the problem seems to be solved...

Last edited by TheImmortalPhoenix (2012-06-09 22:52:07)

Unia · 2012-06-09 22:55:02

TheImmortalPhoenix wrote:

Your script looks great dear Unia, i'm using it, i think it's confortable...I've just a problem with setting brightness...when i'm in 'powersave' mode, it is correctly set to '0', but when i return to 'normal' mode, it's not set back to '9' but remains to '0'
I tried to edit file manually but i got this error:
"/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/brightness" E667: Fsync failed
Can anyone help me to solve this issue?
EDIT: I don't know why but now the problem seems to be solved...

Just to be clear; did you notice the README I made? It says you have to edit the variable there, as it differs per manufacturer and even model.

TheImmortalPhoenix · 2012-06-09 23:11:48

I did...My maximum number is 10

Last edited by TheImmortalPhoenix (2012-06-09 23:14:25)

Unia · 2012-06-09 23:14:02

TheImmortalPhoenix wrote:

I did...Ma maximum number is 10

Then I don't know Glad it works for you now, though!

hesse · 2012-06-10 02:46:56

Cool project! I'm trying this script out together with /etc/acpi/handler.sh. By the way, what's the basic difference between

echo -n mem > /sys/power/state

and

pm-suspend

?

Unia · 2012-06-10 11:15:14

hesse wrote:

Cool project! I'm trying this script out together with /etc/acpi/handler.sh. By the way, what's the basic difference between
echo -n mem > /sys/power/state 
and
pm-suspend
?

According to the pm-utils Wiki, pm-utils (thus pm-suspend) is a more robust tool than just echoing the state into the kernel (?). In this case, more robust means that it works well with for example proprietary drivers such as Catalyst. For this reason, I am using pm-utils instead of echoing the state.

I have to say though, that I have never used the echoing way of doing it so it might just work perfect for you. Also, I'm not sure if there are any other differences.

hesse · 2012-06-10 16:36:51

I have to say though, that I have never used the echoing way of doing it so it might just work perfect for you. Also, I'm not sure if there are any other differences.

I replaced my pm-suspend line with echo -n 'mem' > /sys/power/state in my handler.sh and it's working great. Also I made a small addition (some may call it bloat) to my /usr/lib/powerdown-utils to make it easier to see who is using its functions in the error messages:

# log as myself
test -n "$1" && me="$1" || me="powerdown-utils"

# turn on kernel options
opt() {
  echo $2 | tee $1 &>/dev/null
  [[ $? != 0 ]] && echo "[${me}] cannot enable option $1"
}
...

# powerdown - powersave script
source /usr/lib/powerdown-utils "powerdown" 
...

# powerdown - powerup
source /usr/lib/powerdown-utils "powerup" 
...

So the output from plugging in and unplugging AC adapter is now logged as:

[powerup] cannot enable option /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
[powerdown] cannot enable option /sys/devices/system/cpu/sched_smt_power_savings
[powerdown] cannot enable option /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
[powerdown] cannot enable option /sys/module/snd_ac97_codec/parameters/power_save
[powerdown] cannot enable option /sys/module/i915/parameters/i915_enable_rc6

Last edited by hesse (2012-06-10 16:37:46)

unikum · 2012-06-15 21:41:36

Seems script should be updated:

# powerdown 
[powerdown] cannot enable option /sys/devices/system/cpu/sched_smt_power_savings
[powerdown] cannot enable option /sys/devices/system/cpu/sched_mc_power_savings
[powerdown] cannot enable option /sys/module/pcie_aspm/parameters/policy
[powerdown] cannot enable option /sys/class/scsi_host/host*/link_power_management_policy
[powerdown] cannot enable option /sys/module/snd_ac97_codec/parameters/power_save
[powerdown] cannot run iwconfig wlan0 power on
[powerdown] cannot enable option /sys/module/i915/parameters/i915_enable_rc6
[powerdown] cannot enable option /sys/module/i915/parameters/i915_enable_fbc
[powerdown] cannot unload module uvcvideo
[powerdown] cannot unload module videodev
[powerdown] cannot unload module btusb
[powerdown] cannot unload module bluetooth

Unia · 2012-06-15 21:43:39

unikum wrote:

Seems script should be updated:

# powerdown 
[powerdown] cannot enable option /sys/devices/system/cpu/sched_smt_power_savings
[powerdown] cannot enable option /sys/devices/system/cpu/sched_mc_power_savings
[powerdown] cannot enable option /sys/module/pcie_aspm/parameters/policy
[powerdown] cannot enable option /sys/class/scsi_host/host*/link_power_management_policy
[powerdown] cannot enable option /sys/module/snd_ac97_codec/parameters/power_save
[powerdown] cannot run iwconfig wlan0 power on
[powerdown] cannot enable option /sys/module/i915/parameters/i915_enable_rc6
[powerdown] cannot enable option /sys/module/i915/parameters/i915_enable_fbc
[powerdown] cannot unload module uvcvideo
[powerdown] cannot unload module videodev
[powerdown] cannot unload module btusb
[powerdown] cannot unload module bluetooth

And it worked before?

taylorchu · 2012-06-16 01:24:05

something to check:
1. root privileges
2. acpi-cpufreq is loaded
3. the module is used on your machine

dartfira · 2012-06-24 19:29:09

[powerdown] cannot enable option /sys/module/snd_ac97_codec/parameters/power_save
[powerdown] cannot enable option /sys/module/i915/parameters/i915_enable_rc6
[powerdown] cannot unload module uvcvideo
[powerdown] cannot unload module videodev
[powerdown] cannot unload module btusb
[powerdown] cannot unload module bluetooth

Mine, but I has no bluetooth hardware.
Still get 2.23 hours as laptop-mode.

TheImmortalPhoenix · 2012-06-24 20:32:23

Simply remove those lines if a module cannot be unloaded it means that it's not loaded at all, so you don't need those lines...

dartfira · 2012-07-07 14:26:53

Ok but what about the times?

taylorchu · 2012-07-07 22:48:18

@everyone
the latest version includes existence checks, so all error messges are relevant now.

fredmorcos · 2012-07-09 14:49:24

Would anyone be interested in contributing to sysconf?

https://bbs.archlinux.org/viewtopic.php?id=144507

Also, I am open to merging projects towards a single complete solution for this problem.

From what I found in this thread (a quick skim) that is missing in sysconf would be:

1. pm-utils integration scripts.
2. Screen brightness control.
3. Curses/dialog UI for creating/editing profiles.
4. Check the README for some TODO items.

Cheers,
Fred

patroclo7 · 2012-07-09 15:01:28

I am experimenting with a slightly personalized powerdown script and I enjoy it a lot. Thanks for this.

In the load function in /usr/lib/powerdown-utils there is the following line:

[[ $(lsmod | grep $1) == "" ]] || return

When I run powerup from an interactive shell I always get exit code 1. If I change that line to how it is in the unload function:

[[ $(lsmod | grep $1) == "" ]] && return

then I get exit code 0 (success).
Please note that in both cases the modules that should be loaded are actually loaded, so I think that it succeeds.
Am I missing something?

taylorchu · 2012-07-11 01:45:04

@fred
Sorry, I was not sure about your future plan. Could you talk about it?

@patroclo7
these lines just grep lsmod info and see whether it can grep something. If it can, it means the module is loaded, so unload.

patroclo7 · 2012-07-11 10:47:52

@taylorchu: Yes, I understand. My only problem is that as a result of that specific line powerup always exits with an error code (it does not matter if the modules are already loaded or not), although it loads the modules as expected. Not sure if this has something to do with zsh being my default shell.

Last edited by patroclo7 (2012-07-11 10:53:58)

taylorchu · 2012-07-12 00:44:39

[[ $(lsmod | grep $1) = "" ]]
can you confirm that this have different result if the module is loaded or not?

Arch Linux

#151 2012-06-07 09:02:28

Re: 3x+ battery life

#152 2012-06-07 10:39:17

Re: 3x+ battery life

#153 2012-06-07 15:43:38

Re: 3x+ battery life

#154 2012-06-07 17:11:58

Re: 3x+ battery life

#155 2012-06-07 17:20:40

Re: 3x+ battery life

#156 2012-06-09 21:53:07

Re: 3x+ battery life

#157 2012-06-09 22:47:02

Re: 3x+ battery life

#158 2012-06-09 22:55:02

Re: 3x+ battery life

#159 2012-06-09 23:11:48

Re: 3x+ battery life

#160 2012-06-09 23:14:02

Re: 3x+ battery life

#161 2012-06-10 02:46:56

Re: 3x+ battery life

#162 2012-06-10 11:15:14

Re: 3x+ battery life

#163 2012-06-10 16:36:51

Re: 3x+ battery life

#164 2012-06-15 21:41:36

Re: 3x+ battery life

#165 2012-06-15 21:43:39

Re: 3x+ battery life

#166 2012-06-16 01:24:05

Re: 3x+ battery life

#167 2012-06-24 19:29:09

Re: 3x+ battery life

#168 2012-06-24 20:32:23

Re: 3x+ battery life

#169 2012-07-07 14:26:53

Re: 3x+ battery life

#170 2012-07-07 22:48:18

Re: 3x+ battery life

#171 2012-07-09 14:49:24

Re: 3x+ battery life

#172 2012-07-09 15:01:28

Re: 3x+ battery life

#173 2012-07-11 01:45:04

Re: 3x+ battery life

#174 2012-07-11 10:47:52

Re: 3x+ battery life

#175 2012-07-12 00:44:39

Re: 3x+ battery life

Board footer