mikus at bga.com
Thu Mar 11 13:13:04 EST 2010
>> XO-1.5 B2 (unmodified hardware). At ok prompt did 'flash u:\q3a35.rom';
>> after restart did 'fs-update u:\os112.zd'. That failed (with a message
>> about only 1 block being written).
> I've tested q3a35.rom with fs-update several times, with no problems.
Then it might be something peculiar about the hardware I'm using -- this
is the second time I've experienced this problem -- fs-update did not
work for me with q3a33l, but did work with q3a33o.
> You have to ensure that the firmware reflash actually occurred properly
> before continuing.
What I do is to wait while 'flash u:\q3a35.rom' steps through writing,
then steps through verifying, then restarts the XO-1.5. When the power
LED comes back on (automatically) I press the 'check' game button in
order to have the boot process recognize that I want to use the ok
prompt. I release the 'check' button, and once the chime sounds I press
<esc>. That brings me to the ok prompt, at which I type in 'fs-update
I believe the above actions are the "normal" ones to perform a firmware
reflash. When you say "you have to ensure" -- what more do you expect
from the user ?
> I can also verify that q3a34.rom should NOT work for you.
All I can say is that q3a34 *did* work for me, after q3a35 did not.
It takes me about half an hour to set up (customize) each new build that
I install. I've already done this with os112, and don't want to have to
do it again. So I'll wait until I have to re-customize anyway for the
next new build (or kernel version), before I do a thorough re-test of
what circumstances give me trouble with 'fs-update'.
More information about the Devel