[jwhat]

Hi Indy99,

yes it was a while back.

I remember the Dr Dave days when we where doing physical CPU oscillator swaps with Octane CPU modules to squeeze a bit of extra grunt from our machines.

I still have "custody" of Dual 600 Octane2 from those days and thought I would never need anything more.

But then O350 (Origin / Onyx) prices went to the floor and I was doing some work with company in media business so ended up with some O350's and now a Fuel.

So now have lots of experience with these machines in addition to my Octane knowlege.

Funny how just before Peter turned off Nekochan, I was still updating threads on some things that had not been resolved for over 10 years, during which I did next to no IRIX / SGI stuff.

On this one, I think we will get it closed out pretty shortly.

I did a "flash -f" test on my Fuel, but it returned message saying that all parameter where ok, so without plugging in a faster CPU module I would have to resort to an "flash -F" to force update...

ALL THOSE CAPITAL AND WARNINGS do make you a little nervous, but I took plunge on a number of high risk L1 commands to get my O350 running as unless you do this it is likely we will never get to bottom of some of this stuff.

I was thinking of doing "flash -F" to just check that it come up with prompting questions and then just ctrl c out before apply update in first instance.

EDIT #1: Here is dry run...

>> pink 1# flash -f
>> No proms need flashing
>> pink 2# flash -f -v
>> setting default path_name to /usr/cpu/firmware
>> No proms need flashing
>> pink 3# flash -f -V
>>  Prom version 6.211
>> No proms need flashing
>> pink 4# flash -F -V
>>  Prom version 6.211
>> No proms need flashing

So not able to get prompt for inputs ..

EDIT #2: ok so have to override using -o flag

>> pink 6# flash -o -f -V
>> Enter CPU frequency (MHZ): [400] 600
>> Enter Hub frequency (MHZ): [200] 200
>> Enter cache size (in MBs): [4] 4
>> Enter machine type (0)SN1 (1)SN10 (2)SN11 (3)SN12:
>> If flash is killed in the middle of execution, the machine
>>  will freeze after it is reset.  continuing...
>> Invalid input... Try again.
>> Enter machine type (0)SN1 (1)SN10 (2)SN11 (3)SN12: SN11
>> Invalid input... Try again.
>> Enter machine type (0)SN1 (1)SN10 (2)SN11 (3)SN12: 2
>> Info for prom at /hw/module/001c01/node/prom
>>  Prom version 6.211
>> pink 7#

NOTE the machine type is reported at boot:

>> pink 7# cd /var/adm
>> pink 9# grep SN SYSLOG
>> Oct  4 02:33:10 6A:pink unix: Selecting SN11
>> Oct  4 03:38:37 6A:pink unix: Selecting SN11
>> Oct  4 03:43:25 6A:pink unix: Selecting SN11
>> ...
>> Feb  5 16:40:45 6A:pink unix: Selecting SN11
>> Feb  6 11:35:36 6A:pink unix: Selecting SN11

Deep inhale ....
pink (my Fuel) rebooted up ok .
I can now wipe sweat bead off brow
I think we now know how to do this from bootable machine..
As per Hamei advise for board that has been flashed for higher CPU the only known way to recover is to put back higher frequency CPU and then boot and flash to lower setting and then replace CPU.

Also documented on my blog just in case we loose info again.

Cheers from Oz,


jwhat/John