Ticket #10575 (closed task: fixed)

Opened 4 years ago

Last modified 2 years ago

Network Manager should manage rfkill

Reported by: martin.langhoff Owned by: dsd
Priority: normal Milestone: Future Release
Component: network manager Version: 1.5/1.0 Software Build os852 aka 10.1.2
Keywords: Cc: sascha_silbe
Action Needed: design Verified: no
Deployments affected: Blocked By:
Blocking:

Description

Currently NM reads rfkill state but does not manage rkill.

This is true for the NM we ship (v0.7.2.x), and for the latest release of NM today (v0.8.1)

Desired behaviour:

  • When wireless is switched to disabled, directoy or via networking switched to disabled, NM must issue 'rfkill block wifi'.
  • When wireless is switched to enabled, directly or indirectly via networking switched to enabled, NM must issue 'rfkill unblock wifi'.

This achieves significant power savings -- at least with our chipset -- and allows us to remove a pile of workarounds discussed in #10532

Change History

Changed 4 years ago by martin.langhoff

Once this is fixed in NM

  • Remove workarounds in olpc-utils
  • Remove workarounds in sugar's cpsection/network/model.py

Changed 4 years ago by martin.langhoff

  • milestone changed from Future Release to 11.2.0-M3

Posted to NM's mailing list & Dan Williams to see status of this in NM-0.8.1/F14 .

Changed 3 years ago by dsd

  • milestone changed from 11.2.0-M3 to Future Release

Not ready in time for 11.2.0; very welcome in a future development window.

Changed 3 years ago by sascha_silbe

  • cc sascha_silbe added

Changed 2 years ago by pgf

  • status changed from new to closed
  • resolution set to fixed

closing, old bug. i think the NM support has landed in recent releases, and whatever workarounds we may or may not have removed need to be replaced with something else anyway, since rfkill no longer does what we wanted: it only turns off the transmitter, and not the entire card.

Note: See TracTickets for help on using tickets.