#5418 NORM Never A: powersave mode non-functional.

[Zarro Boogs per Child]

#5418: powersave mode non-functional.
----------------------+-----------------------------------------------------
 Reporter:  dwmw2     |       Owner:  mbletsas      
     Type:  defect    |      Status:  new           
 Priority:  normal    |   Milestone:  Never Assigned
Component:  wireless  |     Version:                
 Keywords:            |    Verified:  0             
----------------------+-----------------------------------------------------
 Perhaps this is just because the access points in 1cc and my WRT54g at
 home don't support it, but enabling powersave mode ({{{iwconfig eth1 power
 on}}}) just seems to give an endless loop of:

 {{{
 [ 2633.189408] libertas host: CMD_RESP: response 0x8021, size 18, jiffies
 2333060
 [ 2633.196750] libertas host: CMD_RESP: PS_MODE cmd reply result 0x2,
 action 0x30
 [ 2633.204080] libertas host: CMD_RESP: PS command failed with 0x2
 [ 2633.210184] libertas host: EXEC_NEXT_CMD: cmdpendingq empty, go back to
 PS_SLEEP
 [ 2633.221601] libertas cmd: PS command:SubCode- Enter PS
 [ 2633.226881] libertas host: QUEUE_CMD: inserted command 0x0021 into
 cmdpendingq
 }}}

 What is result code 0x2? If it's really that the AP isn't letting us go
 into low-power mode, then I can fix the driver to give up, or at least
 keep attempting it in a much slower loop.

 I could also do with finding a setup where I can really test powersave
 mode.

-- 
Ticket URL: <http://dev.laptop.org/ticket/5418>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system