Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#7141 closed defect (fixed)

OFW secure reflash claims it's erasing when it's actually reflashing

Reported by: cscott Owned by: wmb@…
Priority: normal Milestone:
Component: ofw - open firmware Version: Update.1
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed:
Verified: no

Description

During secure reflash, the text below the "lots of rectangles display" never switches from "erasing" to (presumably) "reflashing", even though the color of the drawn rectangles changes from black to green. (q2d14)

Change History (5)

comment:1 Changed 6 years ago by wmb@…

  • Resolution set to fixed
  • Status changed from new to closed

svn 831

I added a "Writing" message to show that erasing is done and writing has commenced.
I also added "Your USB key may be bad. Please try a different one" after the "Bad hash for eblock# N" message.

The fix will appear in Q2D17.

comment:2 Changed 6 years ago by cscott

Oddly enough, the new trend I'm noticing is that people "fix" the bad USB key syndrome by copying the damaged file from the old USB key onto a new USB key, and then complain that it still doesn't work.

I have no idea how to better address this. Maybe, "The file on your USB key may be corrupt because your USB key is damaged. Please redownload the file into a different USB key."?

<sigh>

comment:3 Changed 6 years ago by wmb@…

That seems unlikely to help much. In my experience, people rarely read things carefully. I don't see how to convey it clearly enough in a short message.

Perhaps the message should point to a wiki troubleshooting page in addition to the brief message.

comment:4 Changed 6 years ago by cscott

That sounds like a good idea: the wiki allows for translation as well. Trade off is that connectivity is required. http://wiki.laptop.org/go/Bad_hash ?

comment:5 Changed 6 years ago by gregorio

  • Milestone Never Assigned deleted

Milestone Never Assigned deleted

Note: See TracTickets for help on using tickets.