#7690 NORM 8.2.0 (: msh0 device does not come back up (nor NM/Sugar notified once it does) after power cycling radio via /sys/power/wlan_enabled
Zarro Boogs per Child
bugtracker at laptop.org
Fri Aug 8 16:36:29 EDT 2008
#7690: msh0 device does not come back up (nor NM/Sugar notified once it does)
after power cycling radio via /sys/power/wlan_enabled
----------------------------+-----------------------------------------------
Reporter: mtd | Owner:
Type: defect | Status: new
Priority: normal | Milestone: 8.2.0 (was Update.2)
Component: not assigned | Version: Development build as of this date
Resolution: | Keywords: blocks?:8.2.0
Next_action: diagnose | Verified: 0
Blockedby: 7740 | Blocking:
----------------------------+-----------------------------------------------
Comment(by gnu):
Aha, I think I understand. Eben modified his design with this comment
buried in another bug: http://dev.laptop.org/ticket/5459#comment:10
The problem with eliminating the "mesh off" button is that we lose huge
power saving opportunities.
I don't think Eben realized that when he made that design choice. See the
comments in #5144. With the mesh off and an access point on, we save
small or medium amounts of power -- and have an opportunity to power down
the WiFi chip when the lid is closed, which saves major amounts of power
while suspended (basically the laptop lasts much more than 8 hours in
suspend). With both the mesh and the access point off, the WiFi chip can
also be powered down during suspend -- or all the time.
In Eben's modified design, the only way to turn off the mesh is to turn on
an access point. That's counter-intuitive, and if there is no access
point visible, there is no way to turn off the mesh at all -- which means
we burn full power all the time. The "Turn off" mesh action from the
original design should be reinstated.
--
Ticket URL: <http://dev.laptop.org/ticket/7690#comment:7>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list