From: Dan Williams <dcbw@redhat.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: power save settings for WiFi
Date: Mon, 04 Jan 2016 10:14:58 -0600 [thread overview]
Message-ID: <1451924098.8568.8.camel@redhat.com> (raw)
In-Reply-To: <CANUX_P3Wft5YhvckAzogXy-cV8Ngf8n+Y+6jn1Je3q7r-RDe_g@mail.gmail.com>
On Sun, 2016-01-03 at 12:17 +0200, Emmanuel Grumbach wrote:
> Hi Dan,
>
> I wanted to debug something with power save control and saw that NM
> disables power save by default. This was a complete surprise for me.
> This probably is because Ubuntu upgraded my NM version to 1.0.4.
Note that upstream NM 1.0.x does not support powersave, that was
apparently backported from NM 1.2.x by Ubuntu (?). So anything I'm
talking about here applies to NM 1.2...
> I tried to enabled power save with:
>
> nmcli c modify <MYSSID> 802-11-wireless.powersave 1
>
> That command returns 0, but power save is still disabled. Note that
This simply modifies the saved configuration, it doesn't modify the
runtime value. To change that, the connection must be bounced.
Upcoming NM versions will support live changes by reflecting what you
do with nmcli to the runtime state of the device (or IP
addresses/routes/etc). But not in 1.2 and lower.
So 'nmcli con up <MYSSID>' *should* enable powersave on the device.
> the decision to disable power save by default is a bit surprising.
> I understand that some device may not behave well with power save
> enabled, but then, I'd expect those (bad) devices to disable power
> save in the driver level.
When adding new features to NM (like powersave) we attempt to not
horribly break existing use-cases. Which, for users of devices where
powersave doesn't work very well, would mean breaking their connection
by enabling it by default. However, NM could have handled this better
by leaving the driver-default value enabled unless the user explicitly
sets the 'powersave' property. Which it should really do...
I've filed https://bugzilla.gnome.org/show_bug.cgi?id=760125 for that.
Dan
prev parent reply other threads:[~2016-01-04 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 10:17 power save settings for WiFi Emmanuel Grumbach
2016-01-04 16:14 ` Dan Williams [this message]
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=1451924098.8568.8.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).