>> Again - please tell me WHAT MORE a user performing a firmware reflash
>> can do "to ensure that the firmware reflash actually occurred" ?
>
> On reboot press the x key (esc) to get to open firmware and check the
> ofw banner at the top of the screen.
My normal practice is to press the 'check'
reuben k caron wrote:
>
>
> On Mar 12, 2010, at 12:52 AM, Mikus Grinbergs wrote:
>
> >
> > You also said "If the firmware update wasn't happening (say, due to no
> > DC input)". But what I posted to you in this thread was: "What I do
> > is
> > to wait while 'flash u:\q3a35.rom' ste
On Mar 12, 2010, at 12:52 AM, Mikus Grinbergs wrote:
You have to ensure that the firmware reflash actually occurred
properly
before continuing.
>>>
>>> ...
>>> I believe the above actions are the "normal" ones to perform a
>>> firmware
>>> reflash. When you say "you have to
>>> You have to ensure that the firmware reflash actually occurred properly
>>> before continuing.
>>
>> ...
>> 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 ?
>
> Yep. If the firm
On Mar 11, 2010, at 1:13 PM, Mikus Grinbergs wrote:
>>> 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-updat
On 03/11/2010 01:13 PM, Mikus Grinbergs wrote:
> 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
>> 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 peculia
I've tested q3a35.rom with fs-update several times, with no problems.
You have to ensure that the firmware reflash actually occurred properly
before continuing.
I can also verify that q3a34.rom should NOT work for you.
It has serious fs-update problems and should not be used.
Cheers,
wad
On Mar
(dropping Fedora list)
Yes, it worked for me, too, on an unmodified ramp unit.
- Ed
On Mar 11, 2010, at 9:06 AM, Reuben K. Caron wrote:
> The same procedure worked correctly for me on a ramp unit that has the
> solar modification by Wad.
>
> On Mar 10, 2010, at 10:44 PM, Mikus Grinbe
The same procedure worked correctly for me on a ramp unit that has the
solar modification by Wad.
On Mar 10, 2010, at 10:44 PM, Mikus Grinbergs wrote:
> 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
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).
Repeated the above, but this time flashing q3a34.rom. Now the install
of os112.zd worked.
mikus
__
11 matches
Mail list logo
