linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* power save settings for WiFi
@ 2016-01-03 10:17 Emmanuel Grumbach
  2016-01-04 16:14 ` Dan Williams
  0 siblings, 1 reply; 2+ messages in thread
From: Emmanuel Grumbach @ 2016-01-03 10:17 UTC (permalink / raw)
  To: Dan Williams; +Cc: linux-wireless

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.
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
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.

Any advice on how can I re-allow power save by default since the
command above didn't help?

thanks.

Emmanuel Grumbach
egrumbach@gmail.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: power save settings for WiFi
  2016-01-03 10:17 power save settings for WiFi Emmanuel Grumbach
@ 2016-01-04 16:14 ` Dan Williams
  0 siblings, 0 replies; 2+ messages in thread
From: Dan Williams @ 2016-01-04 16:14 UTC (permalink / raw)
  To: Emmanuel Grumbach; +Cc: linux-wireless

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-01-04 16:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-03 10:17 power save settings for WiFi Emmanuel Grumbach
2016-01-04 16:14 ` Dan Williams

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).