3x+ battery life

webspider · 2012-08-25 19:53:11

1: I guess this i915 option made quite nice battery life gains possible, if it doesn't work for you, feel free to remove the option. This applies to all tweaks in general, these are more of an inspiration for you than something that will work out of the box for everyone. And yes, I'm afraid it will only work with certain intel chipsets.
2: This gets executed at start. If your cable was unplugged on start, it starts with powerdown active, if it wasn't, powerup gets activated. In case it doesn't work for you, feel free to debug it for your system and fixing the error.
3: Dunno, might be something else specific to your laptop.
4: I guess it doesn't, but I wouldn't be too sure, since the author set the swap file for this to 2GB. Test it for science if you dare

taylorchu · 2012-08-25 20:25:11

@everyone
1. if powerdown does not detect i915 chipset, it does not do anything
2. pmutils-related stuff is intended for kde, so you dont have to configure at all.

3. do you use kde? kde power management will also dim your screen.
4. it uses kernel builtin hibernate, and it compresses by default.

Lockheed · 2012-08-26 09:37:42

1. So if I am running Intel 965/82801H ICH8 Family chipset, I should remove the extra grub parameter related to i915?

2. I am running xfce. I removed pm-utils (conflict with your package) and now I think I have no way of running powerup/down automatically upon powers state change. And even if I had, that still does not answer the question will it take effect if power state changes while computer is hibernated/suspended. I am guessing that no...?

3. I am running xfce

4. I have TuxOnIce setup working at the moment so I will stick to that, but out of curiosity - what compression method is this?

Last edited by Lockheed (2012-08-26 09:39:50)

Marvell · 2012-08-27 10:09:25

Hello, I have an issue with powerdown. I can't start X after running powerdown. When I start X and then run powerdown everything is ok. I don't use nvidia driver, I use nouveau.

Xorg.0.log:

...
[    76.426] (==) ModulePath set to "/usr/lib/xorg/modules"
[    76.426] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    76.426] (II) Loader magic: 0x7c8b00
[    76.426] (II) Module ABI versions:
[    76.426] 	X.Org ANSI C Emulation: 0.4
[    76.426] 	X.Org Video Driver: 12.1
[    76.426] 	X.Org XInput driver : 16.0
[    76.426] 	X.Org Server Extension : 6.0
[    76.427] (--) PCI:*(0:2:0:0) 10de:0a29:144d:c06a rev 162, Mem @ 0xdc000000/16777216, 0xe0000000/268435456, 0xde000000/33554432, I/O @ 0x00002000/128, BIOS @ 0x????????/524288
[    76.427] (II) Open ACPI successful (/var/run/acpid.socket)
[    76.427] (II) LoadModule: "extmod"
[    76.427] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[    76.427] (II) Module extmod: vendor="X.Org Foundation"
[    76.427] 	compiled for 1.12.3.901, module version = 1.0.0
[    76.427] 	Module class: X.Org Server Extension
[    76.427] 	ABI class: X.Org Server Extension, version 6.0
[    76.427] (II) Loading extension MIT-SCREEN-SAVER
[    76.427] (II) Loading extension XFree86-VidModeExtension
[    76.427] (II) Loading extension XFree86-DGA
[    76.427] (II) Loading extension DPMS
[    76.427] (II) Loading extension XVideo
[    76.427] (II) Loading extension XVideo-MotionCompensation
[    76.427] (II) Loading extension X-Resource
[    76.427] (II) LoadModule: "dbe"
[    76.427] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[    76.427] (II) Module dbe: vendor="X.Org Foundation"
[    76.427] 	compiled for 1.12.3.901, module version = 1.0.0
[    76.427] 	Module class: X.Org Server Extension
[    76.427] 	ABI class: X.Org Server Extension, version 6.0
[    76.427] (II) Loading extension DOUBLE-BUFFER
[    76.427] (II) LoadModule: "glx"
[    76.427] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    76.427] (II) Module glx: vendor="X.Org Foundation"
[    76.427] 	compiled for 1.12.3.901, module version = 1.0.0
[    76.427] 	ABI class: X.Org Server Extension, version 6.0
[    76.427] (==) AIGLX enabled
[    76.427] (II) Loading extension GLX
[    76.427] (II) LoadModule: "record"
[    76.428] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[    76.428] (II) Module record: vendor="X.Org Foundation"
[    76.428] 	compiled for 1.12.3.901, module version = 1.13.0
[    76.428] 	Module class: X.Org Server Extension
[    76.428] 	ABI class: X.Org Server Extension, version 6.0
[    76.428] (II) Loading extension RECORD
[    76.428] (II) LoadModule: "dri"
[    76.428] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[    76.428] (II) Module dri: vendor="X.Org Foundation"
[    76.428] 	compiled for 1.12.3.901, module version = 1.0.0
[    76.428] 	ABI class: X.Org Server Extension, version 6.0
[    76.428] (II) Loading extension XFree86-DRI
[    76.428] (II) LoadModule: "dri2"
[    76.428] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[    76.428] (II) Module dri2: vendor="X.Org Foundation"
[    76.428] 	compiled for 1.12.3.901, module version = 1.2.0
[    76.428] 	ABI class: X.Org Server Extension, version 6.0
[    76.428] (II) Loading extension DRI2
[    76.428] (==) Matched nouveau as autoconfigured driver 0
[    76.428] (==) Matched nvidia as autoconfigured driver 1
[    76.428] (==) Matched nv as autoconfigured driver 2
[    76.428] (==) Matched vesa as autoconfigured driver 3
[    76.428] (==) Matched fbdev as autoconfigured driver 4
[    76.428] (==) Assigned the driver to the xf86ConfigLayout
[    76.428] (II) LoadModule: "nouveau"
[    76.428] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[    76.428] (II) Module nouveau: vendor="X.Org Foundation"
[    76.428] 	compiled for 1.12.2, module version = 1.0.1
[    76.428] 	Module class: X.Org Video Driver
[    76.428] 	ABI class: X.Org Video Driver, version 12.0
[    76.428] (II) LoadModule: "nvidia"
[    76.429] (WW) Warning, couldn't open module nvidia
[    76.429] (II) UnloadModule: "nvidia"
[    76.429] (II) Unloading nvidia
[    76.429] (EE) Failed to load module "nvidia" (module does not exist, 0)
[    76.429] (II) LoadModule: "nv"
[    76.429] (WW) Warning, couldn't open module nv
[    76.429] (II) UnloadModule: "nv"
[    76.429] (II) Unloading nv
[    76.429] (EE) Failed to load module "nv" (module does not exist, 0)
[    76.429] (II) LoadModule: "vesa"
[    76.429] (WW) Warning, couldn't open module vesa
[    76.429] (II) UnloadModule: "vesa"
[    76.429] (II) Unloading vesa
[    76.429] (EE) Failed to load module "vesa" (module does not exist, 0)
[    76.429] (II) LoadModule: "fbdev"
[    76.429] (WW) Warning, couldn't open module fbdev
[    76.429] (II) UnloadModule: "fbdev"
[    76.429] (II) Unloading fbdev
[    76.429] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    76.429] (II) NOUVEAU driver 
[    76.429] (II) NOUVEAU driver for NVIDIA chipset families :
[    76.429] 	RIVA TNT        (NV04)
[    76.429] 	RIVA TNT2       (NV05)
[    76.429] 	GeForce 256     (NV10)
[    76.429] 	GeForce 2       (NV11, NV15)
[    76.429] 	GeForce 4MX     (NV17, NV18)
[    76.429] 	GeForce 3       (NV20)
[    76.429] 	GeForce 4Ti     (NV25, NV28)
[    76.429] 	GeForce FX      (NV3x)
[    76.429] 	GeForce 6       (NV4x)
[    76.429] 	GeForce 7       (G7x)
[    76.429] 	GeForce 8       (G8x)
[    76.429] 	GeForce GTX 200 (NVA0)
[    76.429] 	GeForce GTX 400 (NVC0)
[    76.429] (--) using VT number 7

[    76.430] drmOpenDevice: node name is /dev/dri/card0
[    76.431] drmOpenDevice: open result is -1, (No such device)
[    76.431] drmOpenByBusid: Searching for BusID pci:0000:02:00.0
[    76.431] drmOpenDevice: node name is /dev/dri/card0
[    76.431] drmOpenDevice: open result is -1, (No such device)
[    76.431] drmOpenByBusid: drmOpenMinor returns -19
[    76.431] drmOpenDevice: node name is /dev/dri/card1
[    76.435] drmOpenByBusid: drmOpenMinor returns -1
[    76.435] drmOpenDevice: node name is /dev/dri/card2
[    76.439] drmOpenByBusid: drmOpenMinor returns -1
[    76.439] drmOpenDevice: node name is /dev/dri/card3
[    76.443] drmOpenByBusid: drmOpenMinor returns -1
[    76.443] drmOpenDevice: node name is /dev/dri/card4
[    76.447] drmOpenByBusid: drmOpenMinor returns -1
[    76.447] drmOpenDevice: node name is /dev/dri/card5
[    76.451] drmOpenByBusid: drmOpenMinor returns -1
[    76.451] drmOpenDevice: node name is /dev/dri/card6
[    76.456] drmOpenByBusid: drmOpenMinor returns -1
[    76.456] drmOpenDevice: node name is /dev/dri/card7
[    76.460] drmOpenByBusid: drmOpenMinor returns -1
[    76.460] drmOpenDevice: node name is /dev/dri/card8
[    76.464] drmOpenByBusid: drmOpenMinor returns -1
[    76.464] drmOpenDevice: node name is /dev/dri/card9
[    76.468] drmOpenByBusid: drmOpenMinor returns -1
[    76.468] drmOpenDevice: node name is /dev/dri/card10
[    76.473] drmOpenByBusid: drmOpenMinor returns -1
[    76.473] drmOpenDevice: node name is /dev/dri/card11
[    76.477] drmOpenByBusid: drmOpenMinor returns -1
[    76.477] drmOpenDevice: node name is /dev/dri/card12
[    76.481] drmOpenByBusid: drmOpenMinor returns -1
[    76.481] drmOpenDevice: node name is /dev/dri/card13
[    76.485] drmOpenByBusid: drmOpenMinor returns -1
[    76.485] drmOpenDevice: node name is /dev/dri/card14
[    76.490] drmOpenByBusid: drmOpenMinor returns -1
[    76.490] drmOpenDevice: node name is /dev/dri/card15
[    76.494] drmOpenByBusid: drmOpenMinor returns -1
[    76.494] drmOpenDevice: node name is /dev/dri/card0
[    76.494] drmOpenDevice: open result is -1, (No such device)
[    76.494] drmOpenDevice: node name is /dev/dri/card0
[    76.494] drmOpenDevice: open result is -1, (No such device)
[    76.494] drmOpenDevice: node name is /dev/dri/card1
[    76.498] drmOpenDevice: node name is /dev/dri/card2
[    76.502] drmOpenDevice: node name is /dev/dri/card3
[    76.507] drmOpenDevice: node name is /dev/dri/card4
[    76.511] drmOpenDevice: node name is /dev/dri/card5
[    76.515] drmOpenDevice: node name is /dev/dri/card6
[    76.519] drmOpenDevice: node name is /dev/dri/card7
[    76.524] drmOpenDevice: node name is /dev/dri/card8
[    76.528] drmOpenDevice: node name is /dev/dri/card9
[    76.532] drmOpenDevice: node name is /dev/dri/card10
[    76.537] drmOpenDevice: node name is /dev/dri/card11
[    76.541] drmOpenDevice: node name is /dev/dri/card12
[    76.545] drmOpenDevice: node name is /dev/dri/card13
[    76.549] drmOpenDevice: node name is /dev/dri/card14
[    76.553] drmOpenDevice: node name is /dev/dri/card15
[    76.558] (EE) [drm] failed to open device
[    76.558] (EE) No devices detected.
[    76.558] 
Fatal server error:
[    76.558] no screens found
[    76.558] 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    76.558] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    76.558]

What should I do with this?

Lockheed · 2012-08-27 10:13:04

You should add to the wiki a mention that upowerd has to be run in order to automatically detect powerstate changes. If this does not happen automatically, add
"upower -e"
to your .xinitrc.

Last edited by Lockheed (2012-08-27 10:20:33)

zenlord · 2012-08-27 10:40:29

Lockheed wrote:

You should add to the wiki [...]

You know that a wiki can be edited by anyone, right?

You seem to have raised some very good points regarding powerdown - they are very helpful, but once this thread has moved along for a page or two, no-one will read your post and your knowledge will be lost. Posting it to the wiki is the right thing to do

Lockheed · 2012-08-27 10:45:01

zenlord wrote:

Lockheed wrote:
You should add to the wiki [...]
You know that a wiki can be edited by anyone, right?
You seem to have raised some very good points regarding powerdown - they are very helpful, but once this thread has moved along for a page or two, no-one will read your post and your knowledge will be lost. Posting it to the wiki is the right thing to do

I can't because I have no wiki account. And I cannot create one because the security question is
"What is the output of "date -u +%W`uname`|sha256sum|sed 's/\W//g'"?"

Unia · 2012-08-27 10:50:39

Just open a terminal and paste the command in there. Then paste the output back in the account creation page.

zenlord · 2012-08-27 10:50:43

Lockheed wrote:

I can't because I have no wiki account. And I cannot create one because the security question is
"What is the output of "date -u +%W`uname`|sha256sum|sed 's/\W//g'"?"

And the problem with this question is?

230b7bc53e09a4291937f0226d9a54d71b1f335bd74b959ce294ce086be7f039

Lockheed · 2012-08-27 10:55:02

zenlord wrote:

And the problem with this question is?

The answer. If executing the question in a terminal produces no result, then the only other a user can try is to guess it. And it is rather hard to guess it.

zenlord · 2012-08-27 11:07:03

Lockheed wrote:

zenlord wrote:
And the problem with this question is?
The answer. If executing the question in a terminal produces no result, then the only other a user can try is to guess it. And it is rather hard to guess it.

Lol. I provided the answer so you can memorize it. Beats guessing

OdinEidolon · 2012-09-04 17:49:52

zenlord wrote:

taylorchu wrote:
did you enable pcie_aspm in grub, syslinux? It gives you 1 more hours.
Just checking - I thought this measure wasn't needed anymore since the patches for the infamous power regression made it into the kernel since v3.3?

No reply to this question?

taylorchu · 2012-09-05 04:58:20

@OdinEidolon
kernel still honors BIOS settings, so PCIE powersave might not be turned on.
If you think it is safe, you need to "force" it to be on.

OdinEidolon · 2012-09-05 07:07:42

taylorchu wrote:

@OdinEidolon
kernel still honors BIOS settings, so PCIE powersave might not be turned on.
If you think it is safe, you need to "force" it to be on.

I see, so you think it is needed to force this:

opt /sys/module/pcie_aspm/parameters/policy powersave

Is this exactly the same as the kernel boot line

pcie_aspm=force

?

Or you need BOTH to work?

In my sytem

cat  /sys/module/pcie_aspm/parameters/policy

gives

[default] performance powersave

Phoronix tests and others iirc reported WORSE power consumption with the forcing option after the kernel patch.

Not criticizing at all, just trying to understand. How can I see if pcie_aspm is enabled without forcing it in the kernel boot line?

Unia · 2012-09-05 09:51:37

OdinEidolon wrote:

How can I see if pcie_aspm is enabled without forcing it in the kernel boot line?

Just try to apply the powersave setting from powerdown. If it's enabled, it'll work. If not, it'll throw an error.

OdinEidolon · 2012-09-05 10:04:21

Unia wrote:

OdinEidolon wrote:
How can I see if pcie_aspm is enabled without forcing it in the kernel boot line?
Just try to apply the powersave setting from powerdown. If it's enabled, it'll work. If not, it'll throw an error.

powerdown just does this:

opt /sys/module/pcie_aspm/parameters/policy powersave

If I do it manually:

sudo opt /sys/module/pcie_aspm/parameters/policy powersave
opt: Too many positional arguments specified!
Can specify at most 1 positional arguments: See: opt -help

Unia · 2012-09-05 10:24:51

Check one of the other Powerdown files to see what opt does

EDIT: powerdown-functions:

# turn on kernel options
opt() {
  [[ -w $1 && -r $1 ]] || return
  echo $2 | tee $1 &>/dev/null || echo "[powerdown] cannot write $2 to $1"

Last edited by Unia (2012-09-05 10:25:34)

Earnestly · 2012-09-05 10:29:42

OdinEidolon wrote:

If I do it manually:

opt is the LLVM optimizer.

The opt you see is defined in the functions file included with the powerdown script.

Edit: 'echo | tee'? You can use: 'tee $1 <<< $2 &> /dev/null' instead.

Last edited by Earnestly (2012-09-05 10:35:41)

OdinEidolon · 2012-09-06 09:24:55

Kaustic wrote:

OdinEidolon wrote:
If I do it manually:
opt is the LLVM optimizer.
The opt you see is defined in the functions file included with the powerdown script.
Edit: 'echo | tee'? You can use: 'tee $1 <<< $2 &> /dev/null' instead.

Whoops.

Any idea why if I try to install powerdown I get this now:

[adriano@M735T ~]  yaourt -S powerdown
==> Installing from a package list
sed: -e expression #1, char 0: no previous regular expression
Recent ML chatter: 
error: target not found: (standard_in)

(mind the "sed:..." and "Recent..." lines always appear for some reason on my system and do not seem to harm)

Last edited by OdinEidolon (2012-09-06 09:26:14)

taylorchu · 2012-09-06 18:44:03

@OdinEidolon
you need BOTH. After that run "sudo powernow". you should see

 -> /sys/module/pcie_aspm/parameters/policy: default performance [powersave]

About sed problem: I think it is a bug in yaourt, but you should check.

OdinEidolon · 2012-09-06 18:53:53

taylorchu wrote:

@OdinEidolon
you need BOTH. After that run "sudo powernow". you should see
 -> /sys/module/pcie_aspm/parameters/policy: default performance [powersave] 
About sed problem: I think it is a bug in yaourt, but you should check.

The problem installing powerdown is NOT related to the sed line, but to the line

error: target not found: (standard_in)

I still cannot install it!

I do not understand. If aspm was fixed in the kernel, how is it possible that I now need to force the kernel parameter? Was it fixed or not fixed? From what I understand [default] means ACTIVE if the kenel has this option enabled, which is since 3.3. Where am I wrong?

OdinEidolon · 2012-09-09 09:03:37

Anyone can help me out on this one?

OdinEidolon · 2012-09-11 17:28:12

OdinEidolon wrote:

Anyone can help me out on this one?

Now it works.
Question [KDE], how do I let KDE run the powerdown script when loading the module, without the need for ROOT permissions? And possibly without editing sudoers?

Uranium · 2012-09-13 21:41:36

Script works well except for the fact that my laptop won't shutdown completely when Powerdown is active. It shuts everything down, hangs at the end, and I get the following message:

[  45656.5984714] Power down.

The numbers change every time I try to shutdown.

I found out that commenting out the "bus" line in /usr/bin/powerdown fixes this.

# bus
# for i in /sys/bus/*/devices/*/power/control; do opt $i auto; done

I would prefer to keep the bus power saving option enabled of course. Any ideas on how to resolve this?

Last edited by Uranium (2012-09-13 21:47:39)

zenlord · 2012-09-13 21:53:55

Uranium wrote:

The numbers change every time I try to shutdown.

That's because it is a timestamp

Welcome. Greets from Erembodegem (BE).

Arch Linux

#201 2012-08-25 19:53:11

Re: 3x+ battery life

#202 2012-08-25 20:25:11

Re: 3x+ battery life

#203 2012-08-26 09:37:42

Re: 3x+ battery life

#204 2012-08-27 10:09:25

Re: 3x+ battery life

#205 2012-08-27 10:13:04

Re: 3x+ battery life

#206 2012-08-27 10:40:29

Re: 3x+ battery life

#207 2012-08-27 10:45:01

Re: 3x+ battery life

#208 2012-08-27 10:50:39

Re: 3x+ battery life

#209 2012-08-27 10:50:43

Re: 3x+ battery life

#210 2012-08-27 10:55:02

Re: 3x+ battery life

#211 2012-08-27 11:07:03

Re: 3x+ battery life

#212 2012-09-04 17:49:52

Re: 3x+ battery life

#213 2012-09-05 04:58:20

Re: 3x+ battery life

#214 2012-09-05 07:07:42

Re: 3x+ battery life

#215 2012-09-05 09:51:37

Re: 3x+ battery life

#216 2012-09-05 10:04:21

Re: 3x+ battery life

#217 2012-09-05 10:24:51

Re: 3x+ battery life

#218 2012-09-05 10:29:42

Re: 3x+ battery life

#219 2012-09-06 09:24:55

Re: 3x+ battery life

#220 2012-09-06 18:44:03

Re: 3x+ battery life

#221 2012-09-06 18:53:53

Re: 3x+ battery life

#222 2012-09-09 09:03:37

Re: 3x+ battery life

#223 2012-09-11 17:28:12

Re: 3x+ battery life

#224 2012-09-13 21:41:36

Re: 3x+ battery life

#225 2012-09-13 21:53:55

Re: 3x+ battery life

Board footer