![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to INSTALL CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Qemu by Fabrice Bellard] / qemu / roms / SLOF|
Return to INSTALL CVS log | Up to [Qemu by Fabrice Bellard] / qemu / roms / SLOF |
1.1 root 1: Slimline Open Firmware - SLOF
2:
3: Copyright (C) 2005, 2008 IBM Corporation
4:
5:
6: BUILD
7: ===============================================================================
8:
9: To build SLOF you need:
10: - Recent GNU tools, configured for powerpc64-linux
11: - GCC: 3.3.3 and newer are known to work
12: - Binutils: use a version as new as possible
13: - Subversion
14:
15: - set the CROSS variable
16: - something like export CROSS="powerpc64-unknown-linux-gnu-"
17: when using a cross compiler
18: or
19: - export CROSS=""
20: when using a native compiler
21:
22: - four more files to build a bootable image:
23: - libipmi.oco
24: - takeover.oco
25: - i2c_bmc.oco
26: - ipmi_oem.oco
27: these files are also provided through developerworks and have to be
28: also downloaded just like the SLOF source code
29:
30: - starting with the SLOF release JX-1.6.0-0 it is necessary to
31: download a x86 emulator which is used to execute the BIOS
32: of VGA card; to download the x86 emulator following steps are
33: required:
34: - cd other-licence/x86emu/
35: - ./x86emu_download.sh # this downloads the x86 emulator sources
36: - cd -
37:
38: - make js2x
39:
40: INSTALL
41: ===============================================================================
42:
43: Detailed information about how to use SLOF on JS20 and JS21 can be found in
44: the document FlashingSLOF.pdf
45:
46: The JS20 and JS21 blades both have 2 "flashsides". They have a 8MB flash part
47: which is divided into a 4MB "temporary" side and a 4MB "permanent" side.
48:
49: The temporary side is the flashside used for the normal operation and the
50: permanent side is used as a backup if the temporary should ever fail.
51:
52: Therefore it is important that the permanent flash side is not changed so
53: that if ever required the original firmware can be restored.
54:
55: SLOF usually warns or in most cases does not easily allow to overwrite the
56: permanent side.
57:
58: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
59: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
60: ! !
61: ! WITH THE FOLLOWING STEPS YOU MIGHT DESTROY YOUR FIRMWARE !
62: ! IMAGE AND LOOSE YOUR WARRANTY ! !
63: ! YOU MAY NEED TO CALL SERVICE, IF THE FIRMWARE IMAGE IS !
64: ! DESTROYED ! !
65: ! !
66: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
67: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
68:
69: UNINSTALL
70: ===============================================================================
71:
72: If you want to boot the original firmware again, you need to boot the blade
73: from the management module. If auto-boot is enabled you have to press "s"
74: to reach the firmware prompt.
75: On the SLOF command line, type:
76:
77: 0 > other-firmware
78:
79: and it should get you back to running the original firmware. To permanently
80: get it back, after booting Linux from there, type
81:
82: $ update_flash -r
83: $ halt
84:
85: You will boot on the PERM side. To boot from the TEMP side again, you need to
86: restart the Blade System MGMT Processor.
87:
88: Following steps are needed on
89: Management Module -> Blade Tasks -> Power/Restart
90:
91: Power Off Blade
92: Restart Blade System Mgmt Processor
93: Power On Blade
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.