#5422 NORM Update.: Pending firmware update apparently prevents boot until AC power is applied

[Zarro Boogs per Child]

#5422: Pending firmware update apparently prevents boot until AC power is applied
----------------------------------+-----------------------------------------
  Reporter:  gnu                  |       Owner:  wmb at firmworks.com
      Type:  defect               |      Status:  new              
  Priority:  normal               |   Milestone:  Update.1         
 Component:  ofw - open firmware  |     Version:                   
Resolution:                       |    Keywords:                   
  Verified:  0                    |    Blocking:                   
 Blockedby:                       |  
----------------------------------+-----------------------------------------

Comment(by gnu):

 The team is agreed on a desired resolution, but it isn't implemented yet:

 <jg> When I was in au, I found that OFW wouldn't continue to try to boot
 if it wasn't on power and the firmware needed updating....
 <jg> did this get resolved?
 <jg> it was logistically a PITA to have to plug in machines to get them
 fully upgraded.

 <cjb> hm, it certainly got to Mitch, who was convinced that the status quo
 wouldn't work.
 <cjb> smithbone_: any idea on that?
 <cjb> I don't see anything likely in the SVN log for OFW.

 <smithbone_> cjb: I think it was me who actually had the most resistance.

 <gnu{-> jg:  not fixed yet.  It's http://dev.laptop.org/ticket/5422

 <smithbone_> If you allow re-flashing without power then you will get
 bricks
 <smithbone_> redundant power that is.

 <cjb> smithbone_: so let's not do that, but let's not *refuse to boot*
 when there is an update pending and we don't have power.

 <jg> that's my point.

 <smithbone_> cjb: Yes.  I supported that.  I think thats already in OFW
 head.

 <cjb> I thought that was the consensus view we came up with.  Failing to
 apply an update and booting anyway is less bad than trying to apply an
 update on bad power.

 <cjb> smithbone_: ok.  we need it in a release.  also, I don't see it in
 the SVN log.

 <jg> the first time the system is booted on power, it gets reflashed.

 <smithbone_> Hmm...

 <jg> smithbone_: can you follow up with Mitch?

 <smithbone_> jg: I will.

 <cjb> jg: Thanks for remembering about that.

 <jg> 'cause I found that a real headache just updating 100 machines; much
 less 40K.
 <jg> of course, with 40k you can afford to set up updating stations, so it
 may not be all that bad.
 <jg> not as  bad as I experienced.
 <jg> so I don't think we should hold things up on this change, but we
 should see it gets done soon.

 <smithbone_> If we accept that fact that unsafe flashing can brick then we
 can remove the hard requirement.  But I think the current view was that if
 it save's one childs laptop from getting bricked then its worth the extra
 work.

 <jg> smithbone_: no, we just delay the reflash until you boot on power.
 <jg> of course, some of our stuff really wants the later firmware.

 <cjb> smithbone_: We were all convinced by your argument that is in
 unsafe.  That's your call.  What's up for debate is what happens when
 there is an update pending and we don't have power -- do we boot anyway,
 or do we crash to the ok prompt.
 <cjb> And I heard everyone agreeing that we boot anyway.

 <jg> boot anyway.
 <jg> yes.

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