You are not logged in.

Pages: 1 … 15 16 17 18 19 … 24

#401 2013-02-09 23:16:36

taylorchu
Member
Registered: 2010-08-09
Posts: 405

Re: 3x+ battery life

@everyone
1. the line for loading cpu module is removed
2. powernow cleanup and fix a issue if the user does not have wireless interface

@kozaki
the latest powerdown should skip hid. please update and see.

"After you do enough distro research, you will choose Arch."

Offline

#402 2013-02-09 23:21:24

nierro
Member
From: Milan, Italy
Registered: 2011-09-02
Posts: 849

Re: 3x+ battery life

Keep up the great job smile

Offline

#403 2013-02-09 23:43:23

Jristz
Member
From: America/Santiago
Registered: 2011-06-11
Posts: 1,022

Re: 3x+ battery life

taylorchu wrote:

@everyone
1. the line for loading cpu module is removed
2. powernow cleanup and fix a issue if the user does not have wireless interface

@kozaki
the latest powerdown should skip hid. please update and see.


But I use the 3.0 LTS and the autoload is for 3.4

You know any workaround thatnot imply parch or edit the code???

Well, I suppose that this is somekind of signature, no?

Offline

#404 2013-02-10 00:25:25

taylorchu
Member
Registered: 2010-08-09
Posts: 405

Re: 3x+ battery life

https://wiki.archlinux.org/index.php/Modprobe.d#Loading

"After you do enough distro research, you will choose Arch."

Offline

#405 2013-02-10 01:02:12

Jristz
Member
From: America/Santiago
Registered: 2011-06-11
Posts: 1,022

Re: 3x+ battery life

taylorchu wrote:

no comments *facepalm*


but ok I like this script, but I ask: in any ponit you going to ad a comfigurable .conf file???

Well, I suppose that this is somekind of signature, no?

Offline

#406 2013-02-10 12:20:12

mityukov
Member
Registered: 2010-10-10
Posts: 66

Re: 3x+ battery life

I've added the following line to the powerdown:

ethtool -s eth0 wol d

(it was suggested on "Tunables" tab of PowerTop's HTML report)

Now, I need to add something "reversing" to the powerup, but don't know what flags should be there by default for "ethtool -s eth0 wol ..."?

Another issue: when I run powerdown, it says the following:

[powerdown] cannot run mount -o remount,noatime /dev/sda5

I have NTFS volume on /dev/sda5, is that a problem? Also, it's mounted on boot (via /etc/fstab):

# /dev/sda5 ("Drive D:")
UUID=40F616A1F616976E               /media/drive_d  ntfs-3g     defaults    0 0

Offline

#407 2013-02-10 12:39:06

mityukov
Member
Registered: 2010-10-10
Posts: 66

Re: 3x+ battery life

nierro wrote:

I guess it's because you need to lauch that from your user. Try 

su yourusername -c "qdbus org.ktorrent.ktorrent /core setSuspended true"

If it won't work, read here: https://wiki.archlinux.org/index.php/Pm … or_suspend . Read carefully the first script, then you'll know what to do smile

Well, neither worked for me. I've even tried to go a bit further and to adapt the 3rd script, so, now I have the following:

#!/bin/sh

DBUS=$(ps aux | grep 'dbus-launch' | grep -v root)
if [[ ! -z $DBUS ]];then
    USER=$(echo $DBUS | awk '{print $1}')
    USERHOME=$(getent passwd $USER | cut -d: -f6)
    export XAUTHORITY="$USERHOME/.Xauthority"
    for x in /tmp/.X11-unix/*; do
        DISPLAYNUM=$(echo $x | sed s#/tmp/.X11-unix/X##)
        if [[ -f "$XAUTHORITY" ]]; then
            export DISPLAY=":$DISPLAYNUM"
        fi
    done
else
    USER=pilat
    USERHOME=/home/pilat
    export XAUTHORITY="$USERHOME/.Xauthority"
    export DISPLAY=":0"
fi

case "$1" in
    yes|true|on)
        su $USER -c "qdbus org.ktorrent.ktorrent /core setSuspended true" &
        ;;
    no|false|off)
        su $USER -c "qdbus org.ktorrent.ktorrent /core setSuspended false" &
        ;;
    *) exit $NA
        ;;
esac

, but it fails to work. Here's the output:

$ sudo -s
# bin/suspent_ktorrent.sh off
: Cannot find '.setSuspended' in object /core at org.ktorrent.ktorrent

So, there must be something special to do, when sending DBus messages from system scripts...

Offline

#408 2013-02-10 13:02:56

jakob
Member
From: Berlin
Registered: 2005-10-27
Posts: 419

Re: 3x+ battery life

mityukov wrote:

I've added the following line to the powerdown:

ethtool -s eth0 wol d

(it was suggested on "Tunables" tab of PowerTop's HTML report)

Now, I need to add something "reversing" to the powerup, but don't know what flags should be there by default for "ethtool -s eth0 wol ..."?

man ethtool

and if you don't know what's the default you're probably not using WOL, ergo no need to reverse the setting, right?

Last edited by jakob (2013-02-10 13:03:51)

Offline

#409 2013-02-10 13:08:28

nierro
Member
From: Milan, Italy
Registered: 2011-09-02
Posts: 849

Re: 3x+ battery life

mityukov wrote:
$ sudo -s
# bin/suspent_ktorrent.sh off
: Cannot find '.setSuspended' in object /core at org.ktorrent.ktorrent

I think it's trying to say that setSuspended is not the right command.
Try to change

su $USER -c "qdbus org.ktorrent.ktorrent /core setSuspended true" &

in 

su $USER -c "qdbus org.ktorrent.ktorrent /core org.ktorrent.core.setSuspended true" &

Offline

#410 2013-02-10 20:06:57

mityukov
Member
Registered: 2010-10-10
Posts: 66

Re: 3x+ battery life

nierro wrote:
su $USER -c "qdbus org.ktorrent.ktorrent /core org.ktorrent.core.setSuspended true" &

Does not work: "Cannot find 'org.ktorrent.core.setSuspended' in object /core at org.ktorrent.ktorrent"

I should mention that the command itself, that I'm trying to run (`qdbus org.ktorrent.ktorrent /core setSuspended true`) -- it works just fine if I run it under the user...

Offline

#411 2013-02-10 20:21:07

mityukov
Member
Registered: 2010-10-10
Posts: 66

Re: 3x+ battery life

There might be a need to pass $DBUS_SESSION_BUS_ADDRESS value to the qdbus. Is there a way I can read environment variable name from a running user session (being root myself)?

Offline

#412 2013-02-10 20:22:25

nierro
Member
From: Milan, Italy
Registered: 2011-09-02
Posts: 849

Re: 3x+ battery life

I found this, right now: http://forum.kde.org/viewtopic.php?f=23 … 75#p244543 . May be it can be useful someway.

Offline

#413 2013-02-11 06:48:53

mityukov
Member
Registered: 2010-10-10
Posts: 66

Re: 3x+ battery life

nierro wrote:

I found this, right now: http://forum.kde.org/viewtopic.php?f=23 … 75#p244543 . May be it can be useful someway.

same error here.. sad I think I'll need to file another ticket on this DBus question anyway. Thank you all!

Offline

#414 2013-02-12 09:02:20

mityukov
Member
Registered: 2010-10-10
Posts: 66

Re: 3x+ battery life

Finally, got it to work! smile
https://bbs.archlinux.org/viewtopic.php … 7#p1230507

Offline

#415 2013-02-12 09:04:04

nierro
Member
From: Milan, Italy
Registered: 2011-09-02
Posts: 849

Re: 3x+ battery life

And it was a script I used to export $DBUS_SESSION_BUS_ADDRESS...damn, sorry man, i forgot about it wink

Offline

#416 2013-02-13 14:41:07

kozaki
Member
From: London >. < Paris
Registered: 2005-06-13
Posts: 673
Website

Re: 3x+ battery life

Hi, thank you nierro, dura and taylorchu. Interestingly I could reproduce the freeze even today.

taylorchu wrote:

@kozaki
the latest powerdown should skip hid. please update and see.

Same freeze happened today on the Core i3 after I reinstalled powerdown, and commented out the usb autosuspend / usbpowersave following nierro's advice
@dura I didn't find the reference about delaying it, sorry.

Results with a bit more details this time

1. installed powerdown 20130213-1 commented out the usb autosuspend 2 lines, and set hdparm -B to 254, then launched it.
For an instant, everything seemed to be fine e.g. I could launch powernow, read its output; then I released the desk (coffee time smile)

2. Coming back to my desk after less than a minute, the system had froze: Tapping on the keyboard, moving, left/right clickin the mice didn't help, i3-wm clock was frozen :-/
Now, really weird (at least to me):
- pressing the sysrq Keys (that I enabled through sysctl and tested yesterday it worked, /proc/sys/kernel/sysrq shows "1") did nothing.
- same for the PC's reset button that I pressed once... ... then after a good 10 seconds with no further action, it suddently rebooted. booh.

The kernel is slightly different, compiled linux-ck from AUR replacing Grayski's linux-ck-ivybridge.
No logs that I can find. journalctl logs for the time freeze happened are empty

EDIT: added version.

Last edited by kozaki (2013-02-13 14:41:51)

Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery smile) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9

Offline

#417 2013-02-13 15:26:24

eruditorum
Member
Registered: 2012-11-12
Posts: 130

Re: 3x+ battery life

use udev, people!

Offline

#418 2013-02-13 19:20:48

taylorchu
Member
Registered: 2010-08-09
Posts: 405

Re: 3x+ battery life

please do not comment out any line, and try again.

"After you do enough distro research, you will choose Arch."

Offline

#419 2013-02-13 21:08:52

kozaki
Member
From: London >. < Paris
Registered: 2005-06-13
Posts: 673
Website

Re: 3x+ battery life

@taylorchu, have done that. And i kept working on it this time.
System hung up about a minute after I started powerdown. Same than previous, i.e. total freeze, music (mplayer) loop.
Log:

-- Logs begin at mar. 2013-01-29 22:17:25 CET, end at mer. 2013-02-13 22:01:58 CET. --
févr. 13 21:51:02 llewellyn CROND[9907]: pam_unix(crond:session): session closed for user root
févr. 13 21:53:34 llewellyn kernel: ehci_hcd 0000:00:1d.0: setting latency timer to 64
-- Reboot --
févr. 13 22:01:34 llewellyn systemd-journal[193]: Allowing runtime journal files to grow to 182.2M.

Last edited by kozaki (2013-02-14 09:44:55)

Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery smile) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9

Offline

#420 2013-02-13 23:23:56

adam777
Member
Registered: 2012-05-28
Posts: 161

Re: 3x+ battery life

I hope I'm not violating any forum rule by this cross-reference, and if so I apologize.
Perhaps you could help me with this issue I'm having with monitor DPMS, after switching to powerdown.
https://bbs.archlinux.org/viewtopic.php?id=158041

Offline

#421 2013-02-15 19:42:04

taylorchu
Member
Registered: 2010-08-09
Posts: 405

Re: 3x+ battery life

for i in /sys/bus/*/devices/*/power/control; do echo $i $(cat $i); done
can you paste what the status of bus? I think it might be the problem.

"After you do enough distro research, you will choose Arch."

Offline

#422 2013-02-16 21:45:23

kozaki
Member
From: London >. < Paris
Registered: 2005-06-13
Posts: 673
Website

Re: 3x+ battery life

taylorchu wrote:

for i in /sys/bus/*/devices/*/power/control; do echo $i $(cat $i); done
can you paste what the status of bus? I think it might be the problem.

Here's the output without powerdown installed (I apologize in case taylorchu's advice wasn't meant for this issue). Every single line shows "control auto":

for i in /sys/bus/*/devices/*/power/control; do echo $i $(cat $i); done
/sys/bus/acpi/devices/INT0800:00/power/control auto
/sys/bus/acpi/devices/INT3F0D:00/power/control auto
/sys/bus/acpi/devices/LNXCPU:00/power/control auto
/sys/bus/acpi/devices/LNXCPU:01/power/control auto
/sys/bus/acpi/devices/LNXCPU:02/power/control auto
/sys/bus/acpi/devices/LNXCPU:03/power/control auto
/sys/bus/acpi/devices/LNXCPU:04/power/control auto
/sys/bus/acpi/devices/LNXCPU:05/power/control auto
/sys/bus/acpi/devices/LNXCPU:06/power/control auto
/sys/bus/acpi/devices/LNXCPU:07/power/control auto
/sys/bus/acpi/devices/LNXPWRBN:00/power/control auto
/sys/bus/acpi/devices/LNXSYBUS:00/power/control auto
/sys/bus/acpi/devices/LNXSYBUS:01/power/control auto
/sys/bus/acpi/devices/LNXSYSTM:00/power/control auto
/sys/bus/acpi/devices/LNXVIDEO:00/power/control auto
/sys/bus/acpi/devices/PNP0000:00/power/control auto
/sys/bus/acpi/devices/PNP0100:00/power/control auto
/sys/bus/acpi/devices/PNP0103:00/power/control auto
/sys/bus/acpi/devices/PNP0200:00/power/control auto
/sys/bus/acpi/devices/PNP0303:00/power/control auto
/sys/bus/acpi/devices/PNP0A08:00/power/control auto
/sys/bus/acpi/devices/PNP0B00:00/power/control auto
/sys/bus/acpi/devices/PNP0C01:00/power/control auto
/sys/bus/acpi/devices/PNP0C01:01/power/control auto
/sys/bus/acpi/devices/PNP0C02:00/power/control auto
/sys/bus/acpi/devices/PNP0C02:01/power/control auto
/sys/bus/acpi/devices/PNP0C02:02/power/control auto
/sys/bus/acpi/devices/PNP0C02:03/power/control auto
/sys/bus/acpi/devices/PNP0C04:00/power/control auto
/sys/bus/acpi/devices/PNP0C0C:00/power/control auto
/sys/bus/acpi/devices/PNP0C0F:00/power/control auto
/sys/bus/acpi/devices/PNP0C0F:01/power/control auto
/sys/bus/acpi/devices/PNP0C0F:02/power/control auto
/sys/bus/acpi/devices/PNP0C0F:03/power/control auto
/sys/bus/acpi/devices/PNP0C0F:04/power/control auto
/sys/bus/acpi/devices/PNP0C0F:05/power/control auto
/sys/bus/acpi/devices/PNP0C0F:06/power/control auto
/sys/bus/acpi/devices/PNP0C0F:07/power/control auto
/sys/bus/acpi/devices/device:00/power/control auto
/sys/bus/acpi/devices/device:01/power/control auto
/sys/bus/acpi/devices/device:02/power/control auto
/sys/bus/acpi/devices/device:03/power/control auto
/sys/bus/acpi/devices/device:04/power/control auto
/sys/bus/acpi/devices/device:05/power/control auto
/sys/bus/acpi/devices/device:06/power/control auto
/sys/bus/acpi/devices/device:07/power/control auto
/sys/bus/acpi/devices/device:08/power/control auto
/sys/bus/acpi/devices/device:09/power/control auto
/sys/bus/acpi/devices/device:0a/power/control auto
/sys/bus/acpi/devices/device:0b/power/control auto
/sys/bus/acpi/devices/device:0c/power/control auto
/sys/bus/acpi/devices/device:0d/power/control auto
/sys/bus/acpi/devices/device:0e/power/control auto
/sys/bus/acpi/devices/device:0f/power/control auto
/sys/bus/acpi/devices/device:10/power/control auto
/sys/bus/acpi/devices/device:11/power/control auto
/sys/bus/acpi/devices/device:12/power/control auto
/sys/bus/acpi/devices/device:13/power/control auto
/sys/bus/acpi/devices/device:14/power/control auto
/sys/bus/acpi/devices/device:15/power/control auto
/sys/bus/acpi/devices/device:16/power/control auto
/sys/bus/acpi/devices/device:17/power/control auto
/sys/bus/acpi/devices/device:18/power/control auto
/sys/bus/acpi/devices/device:19/power/control auto
/sys/bus/acpi/devices/device:1a/power/control auto
/sys/bus/acpi/devices/device:1b/power/control auto
/sys/bus/acpi/devices/device:1c/power/control auto
/sys/bus/acpi/devices/device:1d/power/control auto
/sys/bus/acpi/devices/device:1e/power/control auto
/sys/bus/acpi/devices/device:1f/power/control auto
/sys/bus/acpi/devices/device:20/power/control auto
/sys/bus/acpi/devices/device:21/power/control auto
/sys/bus/acpi/devices/device:22/power/control auto
/sys/bus/acpi/devices/device:23/power/control auto
/sys/bus/acpi/devices/device:24/power/control auto
/sys/bus/acpi/devices/device:25/power/control auto
/sys/bus/acpi/devices/device:26/power/control auto
/sys/bus/acpi/devices/device:27/power/control auto
/sys/bus/acpi/devices/device:28/power/control auto
/sys/bus/acpi/devices/device:29/power/control auto
/sys/bus/acpi/devices/device:2a/power/control auto
/sys/bus/acpi/devices/device:2b/power/control auto
/sys/bus/acpi/devices/device:2c/power/control auto
/sys/bus/acpi/devices/device:2d/power/control auto
/sys/bus/acpi/devices/device:2e/power/control auto
/sys/bus/acpi/devices/device:2f/power/control auto
/sys/bus/acpi/devices/device:30/power/control auto
/sys/bus/acpi/devices/device:31/power/control auto
/sys/bus/acpi/devices/device:32/power/control auto
/sys/bus/acpi/devices/device:33/power/control auto
/sys/bus/acpi/devices/device:34/power/control auto
/sys/bus/acpi/devices/device:35/power/control auto
/sys/bus/acpi/devices/device:36/power/control auto
/sys/bus/acpi/devices/device:37/power/control auto
/sys/bus/acpi/devices/device:38/power/control auto
/sys/bus/acpi/devices/device:39/power/control auto
/sys/bus/acpi/devices/device:3a/power/control auto
/sys/bus/acpi/devices/device:3b/power/control auto
/sys/bus/acpi/devices/device:3c/power/control auto
/sys/bus/acpi/devices/device:3d/power/control auto
/sys/bus/acpi/devices/device:3e/power/control auto
/sys/bus/acpi/devices/device:3f/power/control auto
/sys/bus/acpi/devices/device:40/power/control auto
/sys/bus/acpi/devices/device:41/power/control auto
/sys/bus/acpi/devices/device:42/power/control auto
/sys/bus/acpi/devices/device:43/power/control auto
/sys/bus/acpi/devices/device:44/power/control auto
/sys/bus/acpi/devices/device:45/power/control auto
/sys/bus/acpi/devices/device:46/power/control auto
/sys/bus/acpi/devices/device:47/power/control auto
/sys/bus/clocksource/devices/clocksource0/power/control auto
/sys/bus/cpu/devices/cpu0/power/control auto
/sys/bus/cpu/devices/cpu1/power/control auto
/sys/bus/cpu/devices/cpu2/power/control auto
/sys/bus/cpu/devices/cpu3/power/control auto
/sys/bus/event_source/devices/breakpoint/power/control auto
/sys/bus/event_source/devices/cpu/power/control auto
/sys/bus/event_source/devices/software/power/control auto
/sys/bus/event_source/devices/tracepoint/power/control auto
/sys/bus/hid/devices/0003:045E:008C.0001/power/control auto
/sys/bus/i2c/devices/i2c-0/power/control auto
/sys/bus/i2c/devices/i2c-1/power/control auto
/sys/bus/i2c/devices/i2c-2/power/control auto
/sys/bus/i2c/devices/i2c-3/power/control auto
/sys/bus/i2c/devices/i2c-4/power/control auto
/sys/bus/i2c/devices/i2c-5/power/control auto
/sys/bus/i2c/devices/i2c-6/power/control auto
/sys/bus/i2c/devices/i2c-7/power/control auto
/sys/bus/machinecheck/devices/machinecheck0/power/control auto
/sys/bus/machinecheck/devices/machinecheck1/power/control auto
/sys/bus/machinecheck/devices/machinecheck2/power/control auto
/sys/bus/machinecheck/devices/machinecheck3/power/control auto
/sys/bus/memory/devices/memory0/power/control auto
/sys/bus/memory/devices/memory1/power/control auto
/sys/bus/memory/devices/memory10/power/control auto
/sys/bus/memory/devices/memory11/power/control auto
/sys/bus/memory/devices/memory12/power/control auto
/sys/bus/memory/devices/memory13/power/control auto
/sys/bus/memory/devices/memory14/power/control auto
/sys/bus/memory/devices/memory15/power/control auto
/sys/bus/memory/devices/memory16/power/control auto
/sys/bus/memory/devices/memory17/power/control auto
/sys/bus/memory/devices/memory18/power/control auto
/sys/bus/memory/devices/memory19/power/control auto
/sys/bus/memory/devices/memory2/power/control auto
/sys/bus/memory/devices/memory20/power/control auto
/sys/bus/memory/devices/memory21/power/control auto
/sys/bus/memory/devices/memory22/power/control auto
/sys/bus/memory/devices/memory23/power/control auto
/sys/bus/memory/devices/memory24/power/control auto
/sys/bus/memory/devices/memory25/power/control auto
/sys/bus/memory/devices/memory3/power/control auto
/sys/bus/memory/devices/memory32/power/control auto
/sys/bus/memory/devices/memory33/power/control auto
/sys/bus/memory/devices/memory34/power/control auto
/sys/bus/memory/devices/memory35/power/control auto
/sys/bus/memory/devices/memory4/power/control auto
/sys/bus/memory/devices/memory5/power/control auto
/sys/bus/memory/devices/memory6/power/control auto
/sys/bus/memory/devices/memory7/power/control auto
/sys/bus/memory/devices/memory8/power/control auto
/sys/bus/memory/devices/memory9/power/control auto
/sys/bus/pci/devices/0000:00:00.0/power/control auto
/sys/bus/pci/devices/0000:00:02.0/power/control auto
/sys/bus/pci/devices/0000:00:16.0/power/control auto
/sys/bus/pci/devices/0000:00:1a.0/power/control auto
/sys/bus/pci/devices/0000:00:1b.0/power/control auto
/sys/bus/pci/devices/0000:00:1c.0/power/control auto
/sys/bus/pci/devices/0000:00:1c.1/power/control auto
/sys/bus/pci/devices/0000:00:1c.2/power/control auto
/sys/bus/pci/devices/0000:00:1d.0/power/control auto
/sys/bus/pci/devices/0000:00:1e.0/power/control auto
/sys/bus/pci/devices/0000:00:1f.0/power/control auto
/sys/bus/pci/devices/0000:00:1f.2/power/control auto
/sys/bus/pci/devices/0000:00:1f.3/power/control auto
/sys/bus/pci/devices/0000:02:00.0/power/control auto
/sys/bus/pci/devices/0000:03:00.0/power/control auto
/sys/bus/pci_express/devices/0000:00:1c.0:pcie01/power/control auto
/sys/bus/pci_express/devices/0000:00:1c.1:pcie01/power/control auto
/sys/bus/pci_express/devices/0000:00:1c.2:pcie01/power/control auto
/sys/bus/platform/devices/alarmtimer/power/control auto
/sys/bus/platform/devices/coretemp.0/power/control auto
/sys/bus/platform/devices/efifb.0/power/control auto
/sys/bus/platform/devices/i8042/power/control auto
/sys/bus/platform/devices/iTCO_wdt/power/control auto
/sys/bus/platform/devices/microcode/power/control auto
/sys/bus/platform/devices/pcspkr/power/control auto
/sys/bus/platform/devices/serial8250/power/control auto
/sys/bus/pnp/devices/00:00/power/control auto
/sys/bus/pnp/devices/00:01/power/control auto
/sys/bus/pnp/devices/00:02/power/control auto
/sys/bus/pnp/devices/00:03/power/control auto
/sys/bus/pnp/devices/00:04/power/control auto
/sys/bus/pnp/devices/00:05/power/control auto
/sys/bus/pnp/devices/00:06/power/control auto
/sys/bus/pnp/devices/00:07/power/control auto
/sys/bus/pnp/devices/00:08/power/control auto
/sys/bus/pnp/devices/00:09/power/control auto
/sys/bus/pnp/devices/00:0a/power/control auto
/sys/bus/pnp/devices/00:0b/power/control auto
/sys/bus/pnp/devices/00:0c/power/control auto
/sys/bus/pnp/devices/00:0d/power/control auto
/sys/bus/scsi/devices/0:0:0:0/power/control on
/sys/bus/scsi/devices/2:0:0:0/power/control on
/sys/bus/scsi/devices/6:0:0:0/power/control on
/sys/bus/scsi/devices/host0/power/control auto
/sys/bus/scsi/devices/host1/power/control auto
/sys/bus/scsi/devices/host2/power/control auto
/sys/bus/scsi/devices/host3/power/control auto
/sys/bus/scsi/devices/host4/power/control auto
/sys/bus/scsi/devices/host5/power/control auto
/sys/bus/scsi/devices/host6/power/control auto
/sys/bus/scsi/devices/host7/power/control auto
/sys/bus/scsi/devices/target0:0:0/power/control auto
/sys/bus/scsi/devices/target2:0:0/power/control auto
/sys/bus/scsi/devices/target6:0:0/power/control auto
/sys/bus/serio/devices/serio0/power/control auto
/sys/bus/usb/devices/1-1/power/control auto
/sys/bus/usb/devices/2-1.5/power/control auto
/sys/bus/usb/devices/2-1/power/control auto
/sys/bus/usb/devices/usb1/power/control auto
/sys/bus/usb/devices/usb2/power/control auto

Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery smile) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9

Offline

#423 2013-02-19 18:38:57

I-sty
Member
From: Romania
Registered: 2012-11-30
Posts: 60
Website

Re: 3x+ battery life

Hi
the powerdown command say:

[root@localhost i-sty]# powerdown 
[powerdown] cannot write powersave to /sys/module/pcie_aspm/parameters/policy
[powerdown] cannot run iw dev wlan0 set power_save on
[powerdown] cannot write 1 to /sys/module/i915/parameters/i915_enable_rc6
[root@localhost i-sty]#

And with wifi and 200 brightness my battery long is 3h 17m. This is very short.
Can you help me?


____________________________________
I edited my powerdown script with this code:

# net
run iw dev wlp2s0 set power_save on

# screen
echo "200" > /sys/class/backlight/intel_backlight/brightness

This help with several minutes.
Now, I have the i915 error.

Last edited by I-sty (2013-02-19 18:50:25)

Offline

#424 2013-02-19 21:41:31

nierro
Member
From: Milan, Italy
Registered: 2011-09-02
Posts: 849

Re: 3x+ battery life

You can append that to the grub line: 

i915.i915_enable_rc6="x"

. Remember to comment that line in powerdown script!
Ps: "x" is your preferred value wink

Last edited by nierro (2013-02-19 21:42:11)

Offline

#425 2013-02-21 03:51:04

Jristz
Member
From: America/Santiago
Registered: 2011-06-11
Posts: 1,022

Re: 3x+ battery life

I reseive thi error when I run powerown

➜  ~  sudo LANG=C powerdown
[powerdown] cannot write powersave to /sys/module/pcie_aspm/parameters/policy
[powerdown] cannot run iw dev wlan0 set power_save on
cat: /sys/class/backlight/acpi_video0/max_brightness: No such file or directory
(standard_in) 1: parse error
/usr/lib/powerdown-functions: line 37: * 1 : syntax error: operand expected (error token is "* 1 ")

and I notice that the pathsremain to the old wlan0 in powernow

Well, I suppose that this is somekind of signature, no?

Offline

Pages: 1 … 15 16 17 18 19 … 24

Board footer

Powered by FluxBB