all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Does Linux 4.16.1 blast out battery time? (9h+ -> 3h+)
Date: Tue, 24 Apr 2018 10:37:26 +0200	[thread overview]
Message-ID: <87k1sx2e61.fsf@gnu.org> (raw)
In-Reply-To: <871sfjtnuy.fsf@gmail.com> (Pierre Neidhardt's message of "Fri, 13 Apr 2018 15:44:13 +0530")

Hello,

Pierre Neidhardt <ambrevar@gmail.com> skribis:

> With a bit of tweaking, I figured that enabling power management on
> on "Audio codec":
>
> 	echo '1' > '/sys/module/snd_hda_intel/parameters/power_save';
>
> helped a little bit.  But not that much.  Now on 4.14.33, I get 10h,
> while on 4.16.1 I get 5h.
>
> There is something else.

That sounds worrying.  Could you report it upstream?

> By the way, how do I make the above /sys/ tweak permanent on GuixSD?

You could do something like:

  (simple-service 'my-/sys-tweaks activation-service-type
                  #~(call-with-output-file "/sys/…"
                      (lambda (port)
                        (display "1" port))))

That said, we should probably build a higher-level
‘/sys-tweaks-service-type’ where we could directly pass pairs of file
name/values.

Would you like to give it a try?

Thanks,
Ludo’.

  reply	other threads:[~2018-04-24  8:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13  6:06 Does Linux 4.16.1 blast out battery time? (9h+ -> 3h+) Pierre Neidhardt
2018-04-13  6:50 ` Tomáš Čech
2018-04-13  7:33   ` Pierre Neidhardt
2018-04-13 10:14     ` Pierre Neidhardt
2018-04-24  8:37       ` Ludovic Courtès [this message]
2018-04-24 13:17         ` Pierre Neidhardt
2018-05-03  6:45           ` Pierre Neidhardt
2018-05-08 21:11             ` Nils Gillmann
2018-05-09  7:20               ` Pierre Neidhardt
2018-05-09  8:19                 ` Nils Gillmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k1sx2e61.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=ambrevar@gmail.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.