Does upgrading the L1 on Fuel require the same technique as Tezro?
#11
RE: Does upgrading the L1 on Fuel require the same technique as Tezro?
So, no problems jumping straight to 1.48.1!  I installed patchSG0007149.  From that point I followed the test flash procedure; flashing, rebooting the L1 to make sure it comes up, setting the default; and eventually power cycling the machine as a final verification.

Quote:fuel 3# l1cmd flash status v
Flash image B currently booted

Image   Address       Status        Revision    Built
-----  ----------  -------------   ----------   -----
  A    0xffe10000  valid           1.20.6       03/12/2003 11:01:29
  B    0xffe80000  default         1.20.6       03/12/2003 11:01:29

fuel 4# l1cmd flash default b

fuel 5# l1cmd flash status v
Flash image B currently booted

Image   Address       Status        Revision    Built
-----  ----------  -------------   ----------   -----
  A    0xffe10000  valid           1.20.6       03/12/2003 11:01:29
  B    0xffe80000  user default    1.20.6       03/12/2003 11:01:29

fuel 22# /usr/sbin/flashsc -v ./l1.bin
/usr/sbin/flashsc: (System Controller Flash Utility) - Version 1.4.1
Multi-image binary contains 7 flash images.
Image 0: L1 version 1.48.1, Built 01/22/2007 11:33:34  [Base 1MB image]
Image 1: L1 version 1.48.1, Built 01/22/2007 11:34:20  [Fuel/PE/O300 1MB image]
Image 2: L1 version 1.48.1, Built 01/22/2007 11:34:34  [MIPS 2MB image]
Image 3: L1 version 1.48.1, Built 01/22/2007 11:34:57  [Legacy 2MB image]
Image 4: L1 version 1.48.1, Built 01/22/2007 11:36:34  [Legacy Linux L1 image]
Image 5: L1 version 1.48.1, Built 01/22/2007 11:35:27  [2MB image]
Image 6: L1 version 1.48.1, Built 01/23/2007 10:17:58  [Linux L1 image]


fuel 31# /usr/sbin/flashsc ./l1.bin local
/usr/sbin/flashsc: (System Controller Flash Utility) - Version 1.4.1
=========== Updating (local) ===========
Checking current flash image status.
Updating L1 flash image A to version 1.48.1 [Fuel/PE/O300 1MB image]
Erasing existing flash data:        100% complete
Writing new flash image:            100% complete
Validating new flash image.

fuel 32# l1cmd flash status v
Flash image B currently booted

Image   Address       Status        Revision    Built
-----  ----------  -------------   ----------   -----
  A    0xffe10000  valid           1.48.1       01/22/2007 11:34:20
  B    0xffe80000  user default    1.20.6       03/12/2003 11:01:29

fuel 34# l1cmd reboot_l1 a

fuel 35# l1cmd version
L1 1.48.1 (Image A), Built 01/22/2007 11:34:20    [Fuel/PE/O300 1MB image]

fuel 39# l1cmd flash default reset

fuel 40# l1cmd flash status
Flash image A currently booted

Image      Status        Revision    Built
-----   -------------   ----------   -----
  A     default         1.48.1       01/22/2007 11:34:20
  B     valid           1.20.6       03/12/2003 11:01:29

After this I ran a bunch of other L1 commands, e.g. env/serial/etc. just to make sure all the data was there, looked sane and such.  Upon rebooting the L1 the fans did spin way down, and came back to a (slightly) quieter level than they were before.. which is what I was hoping I'd get from an upgrade :)

Note this is all done in one go inside IRIX.  No reboots are necessary as the L1 can be restarted without the system being restarted; if it had not came back after the reboot_l1, I should have been able to just power cycle the machine and have it boot the previous image.
(This post was last modified: 11-11-2021, 12:49 AM by vvuk.)
vvuk
O2

Trade Count: (0)
Posts: 43
Threads: 4
Joined: Aug 2021
Location: California
Find Reply
11-11-2021, 12:47 AM
#12
RE: Does upgrading the L1 on Fuel require the same technique as Tezro?
Hi vvuk & Weblacky

firstly vvuk, thanks for testing straight jump, that should save others from having to do multiple step updates.

On NVRAM I am aware that there is:
- DALLAS for Serial No, L1 RTC & L1 Config &
- STI for PROM environment and system RTC,
- but it is unconfirmed that the "Bedrock PROM" is also stored in STI chip.

See this discussion thread: https://forums.irixnet.org/thread-2164-page-7.html

Weblackly has, I think, correctly identified the purpose of the little 512 byte EEPROM for holding the machine serial number.

This make sense as it ensures that you can maintain the machine ID across system board swaps which is important for licensed software, and is pretty much the same as with the Octane, but that usesthe "ID-in-a-Can" chip which looks like a battery.

The reason I am not sure if it the STI chip is that on Tezro and O350 this is on the IO9 board and not the system board and changing the CPU system board on O350 can result in PROM version change (I think, as I have seen this happen but did not really think about underlying cause at the time, so need to re-verify) ... which would not occur if it was on the IO9 board...

On my numalink'ed O350 it reports the PROM version for each chassis as part of boot sequence, so one way to determine if the IO9 has PROM would be to pull out an IO9 board from one of the chassis and see if it still reports a PROM version (currently I have 6 chassis == 6 PROM notifications).

However pulling out machines and boards is lots of work so I have been avoiding doing that in hope that some one else may have better approach.

The reason for looking into this was to see if there is way to change the PROM data (to allow for change in CPU speed), without having to boot into IRIX (as per thread discussion).

Once Weblacky gets his Fuel (which is 700 MHz ??) going then he can do PROM dump on that and it can be put into mix of looking at the data variation across the PROMs based on speed changes.

Cheers from Oz,

jwhat/John
(This post was last modified: 11-11-2021, 03:15 AM by jwhat.)
jwhat
Octane/O350/Fuel User

Trade Count: (0)
Posts: 513
Threads: 29
Joined: Jul 2018
Location: Australia
Find Reply
11-11-2021, 02:55 AM
#13
RE: Does upgrading the L1 on Fuel require the same technique as Tezro?
This is maybe relevant -- on my O350:

```
# l1cmd node
NODE Present Enabled
---- ------- --------
0 Present Enabled

# sudo l1cmd prom sel
Node PROM Image
---- ----------
0 A
```

On my fuel:
```
fuel 4# l1cmd node
INFO: command not supported on this brick type
fuel 5# l1cmd prom sel
INFO: command not supported on this brick type
```

So I'd guess that on the fuel it's part of the PROM nvram data (on the snaphat nvram). Is it possible to dump that in some way?
vvuk
O2

Trade Count: (0)
Posts: 43
Threads: 4
Joined: Aug 2021
Location: California
Find Reply
11-11-2021, 05:13 AM
#14
RE: Does upgrading the L1 on Fuel require the same technique as Tezro?
Hi vvuk,

no that is the L1 stuff.

I am talking about the "Bedrock PROM", on your Fuel or O350 do: flash -v or flash -D

You will see that this is different thing.

Cheers from Oz,

jwhat/John.
(This post was last modified: 11-12-2021, 09:30 AM by jwhat.)
jwhat
Octane/O350/Fuel User

Trade Count: (0)
Posts: 513
Threads: 29
Joined: Jul 2018
Location: Australia
Find Reply
11-11-2021, 07:04 AM


Forum Jump:


Users browsing this thread: 1 Guest(s)