Bienvenue sur le site admin-sys

Commandes OBP

Jerome ROBERT — 2008-09-17T18:49:21Z

Solaris 1.x

Booter MUNIX puis MINIROOT à partir du cd-rom

Boot PROM version 1.x	Boot PROM version 2.x
ok boot sd(0,6,2)	ok boot cdrom

Solaris 2.x

Booter en single-user à partir du CD-ROM

Boot PROM version 1.x	Boot PROM version 2.x
ok boot sd(0,6,2) -sw	ok boot cdrom - sw

Sur le CD-ROM, on a accès à diverse commande comme :

format
newfs
fsck
mount
installboot

Alias prédéfinis

Boot PROM version 1.x	Boot PROM version 2.x et 3.x
disk	disk disk0 disk1 disk2 disk3
tape	tape tape0 tape1
net	net
	cdrom cdroma

Format de la commande boot :

ok boot périphérique] - options]

les options :

v	mode verbeux, plus de détaille dans les messages
a	mode interractif
r	mode reconfigure des devices
install	pour effectuer une installation (ok boot cdrom - install )
s	single user, ou maintenance

Exemple :

Boot sur le périphérique
par défaut :

ok boot

Installation via le réseau :

ok boot net - install

Boot PROM version 1.x	Boot PROM version 2.x ou 3.x
ok boot st(0,0,0) ok boot sd(0,3,0)	ok boot tape ok boot disk3 ok boot /sbus/esp@0,800000/sd@6,0:c

NVRAM 1.x

Jerome ROBERT — 2008-09-17T11:57:01Z

Présentation des paramètres de la NVRAM
version 1.x

Paramètre	Signification	Valeur	Par défaut
auto-boot ?	Si "true", boot automatique apres la mise sous tension	False	True
diag-switch ?	Si "true", passe en mode diagnostic	False	True
fcode-debug ?	Si "true", permet le debogage des pgms tierce-partie	False	False
keyboard-click ?	Si "true", valide le clic clavier	False	False
mfg-switch ?	Si "true", boucle sur les POST	False	False
oem-banner ?	Si "true", utilise une banniere personnalisee	False	False
oem-logo ?	Si "true", utilise un logo personnalise	False	False
sunmon-compat ?	Si "true", utilise par defaut 1'ancien prompt ">"	True	True
ttya-ignore-cd	Si "true", ignore la detection de porteuse sur ttya	True	True
ttyb-ignore-cd	Si "true", ignore la detection de porteuse sur ttyb	True	True
ttya-rts-dtr-off	Si "true", ne gere pas DTR et RTS sur ttya	False	False
ttyb-rts-dtr-off	Si "true", ne gere pas DTR et RTS sur ttyb	False	False
watchdog-reboot ?	Si "true", reboot apres un watchdog reset	False	False
screen-#columns	Nombre de colonnes (caracteres par ligne) à 1'ecran	80	80
screen-#rows	Nombre de lignes de caracteres à 1'ecran	34	34
scsi-initiators-id	Adresse de la CPU sur le bus SCSI, de 0 à 7	7	7
selftest-#megs	Mo de RAM a tester a la mise sous tension	1	1
input-device	Peripherique d'entree (keyboard, ttya ou ttyb)	ttya	keyboard
output-device	Peripherique de sortie (screen, ttya ou ttyb)	ttya	screen
boot-from	Source du boot (peripherique par defaut est sd)	vmunix	vmunix
boot-from-diag	Source du boot en mode diagnostic	disk	le()vmunix
hardware-revision	Information sur la version courante du systeme	-	-
oem-banner	Banniere personnalisee	vide	vide
use-nvramrc ?	Utilise en programmation. Ne pas mettre à "true"	False	False
sbus-probe-list	Ordre des tests sur les slots SBus	0123	0123
ttya-mode	ttya (baud, #bits, parite, #stop, contrdle de flot)	9600,8,n,1,-	9600,8,n,1,
ttyb-mode	ttyb (baud, #bits, parite, #stop, contr6le de flot)	9600,8,n,1,-	9600,8,n,1,
oem-logo	Tableau d'octets representant un logo personnel	vide	vide
sd-targets	Correspondance targets/unites logiques disques	31204567	31204567
st-targets	Correspondance targets/unites logiques bandes	45670123	45670123
testarea	Un octet disponible pour des tests lecture /ecriture	0	0
security-mode	Niveau de securite (none, command, full)	None	None
security-passwd	Mot de passe systeme (jamais affiche)	vide	vide
security-#badlogins	Affiche le nombre de tentatives infructueuses (login)	vide	vide

NVRAM 2.x

Jerome ROBERT — 2008-09-17T11:56:17Z

P ALIGN=CENTER>Présentation des paramètres de la NVRAM
version 2.x

Paramètre	Signification	Valeur	Valeur par défaut
selftest-#megs	Mo de RAM a tester a la mise sous tension	1	vide
tpe-link-test ?	Si "true", permet le test du resenu TPE	true	true
oem-logo	Tableau d'octets representant logo personnel	vide	vide
oem-logo ?	Si "true", utiliser logo personnel	False	False
oem-banner	Bvlniere personnahsee	vide	vide
oem-banner ?	Si "true", utiliser banniere personnalisee	False	False
output-device	Peripherique de sortie (seen, ttya ou ttyb)	ttya	sciver,
input-device	Peripherique d'entree (keyboard, ttya ou ttyb)	ttva	ke vbolrd
sbus-probe-list	Ordre des tests sur les slots SBus	0123	0123
keyboard-click ?	Si "true", valide le clic clavier	False	False
keyboardmap	Remap les touches de fonctions
ttyb-rts-itroff	Si "true", ne gee pas DTR et RTS sur ttvb	False	False
ttyb-ignore-cd	Si "true", ignore detection de porteuse sur b	True	True
ttya-rts-itr-off	Si "true", ne gere pas DTR et RTS sur tiya	False	False
ttya-ignore-cd	Si "true", ignore detection de porteuse sur a	True	True
ttyb-mode	ttyb (baud, #bits, parite, #stop, flot)	9600,8,n,1,-	9600,8,n,1,
ttya-mode	ttya (baud, #bits, parite, #stop, flot)	9600,8,n,1,-	9600,8,n,1,
fcodedebug ?	Si "true", permet le debogage des pgms tierce-partie	False	False
ding-device	Peripherique de boot en mode diagnostic	disk	net
boot-device	Penpherique de boot en mode normal (sd par defaut)	disk	disk
auto-boot ?	Si "true", boot nutomatique apres mise sous tension	True	True
watchdog-reboot ?	Si "true", reboot apres un watchdog reset	False	False
local-mac-address	Uadresse Ethernet	False	False
use-nvramrc ?	Utilise en progamrnation. Ne pas mettre à "true"	False	False
nvramrc	Partie vide à progranuner	vide	vide
screen-#columns	Nornbre de colorunes (caracteres par ligne) à 1'ecran	80	80
screen-#rows	Nombre de lignes de caracteres à 1'ecran	34	34
surunon-compat ?	Si "true", utilise par defaut 1'ancien mode ">"	True	False
security-mode	Nivenu de securite (none, command, full)	None.	None
security-passwd	Mot de passe systeme (jamais affiche)	vide	vide
security-#badlogins	Affiche le nombre de tentatives infructueuses login)	vide	vide
scsi-initiator-id	Adresse de la CPU sur le bus SCSI, de 0 à 7	7	7
hardware-revision	Information sur la version courante du systeme	vide	vidc
last-hardware-update	Information de mise à jour du systeme	vide	vide
testarea	Un octet disponible pour des tests lecture/ecriture	0	0
mfg-switch ?	Si "true", boucle sur les POST	False	False
diag-switch ?	Si "true", prise en mode diagnostic	False	False

NVRAM v3

Jerome ROBERT — 2008-09-17T11:55:18Z

 PrÃ©sentation des paramÃ¨tres de la NVRAM version 3.x ParamÃ¨tre	Valeur	Valeur par dÃ©faut tpe-link-test?	true	true scsi-initiator-id	7	7 keyboard-click?	false	false keymap ttyb-rts-dtr-off	false	false ttyb-ignore-cd	true	true ttya-rts-dtr-off	false	false ttya-ignore-cd	true	true ttyb-mode	9600,8,n,1,-	9600,8,n,1,- ttya-mode	9600,8,n,1,-	9600,8,n,1,- pcia-probe-list	1,2,3,4	1,2,3,4 pcib-probe-list	1,2,3	1,2,3 mfg-mode	off	off diag-level	max	cf machine #power-cycles	50	cf machine system-board-serial# system-board-date fcode-debug?	false	false output-device	screen	screen input-device	keyboard	keyboard load-base	16384	16384 boot-command	boot	boot auto-boot?	true	true watchdog-reboot?	false	false diag-file diag-device	net	net boot-file boot-device	disk net	disk net local-mac-address?	false	false ansi-terminal?	true	true screen-#columns	80	80 screen-#rows	34	34 silent-mode?	false	false use-nvramrc?	false	false nvramrc security-mode	none	none security-password security-#badlogins	0	0 oem-logo oem-logo?	false	false oem-banner oem-banner?	false	false hardware-revision last-hardware-update diag-switch?	false	true

man eeprom

Jerome ROBERT — 2008-09-17T11:53:43Z

Maintenance Commands eeprom(1M)

NAME
eeprom - EEPROM display and load utility

SYNOPSIS
SPARC
/usr/platform/ platform-name /sbin/eeprom [ - ] [
-f device ] [ parameter [ =value ] ]

IA
/usr/platform/ platform-name /sbin/eeprom [ - ] [
-f device ] [ -I ] [ mmu-modlist ] [ parameter [
=value ] ]

DESCRIPTION
eeprom displays or changes the values of parameters in the
EEPROM. It processes parameters in the order given. When
processing a parameter accompanied by a value, eeprom makes
the indicated alteration to the EEPROM ; otherwise it
displays the parameter's value. When given no parameter
specifiers, eeprom displays the values of all EEPROM parame-
ters. A `-' (hyphen) flag specifies that parameters and
values are to be read from the standard input (one parameter
or parameter =value per line).

Only the super-user may alter the EEPROM contents.

eeprom verifies the EEPROM checksums and complains if they
are incorrect.

platform-name is the name of the platform implementation and
can be found using the -i option of uname(1).

SPARC
SPARC based systems implement firmware password protection
with eeprom using the security-mode, security-password and
security-#badlogins properties.

IA
EEPROM storage is simulated using a file residing in the
platform specific boot area. The /platform/platform-
name/boot/solaris/bootenv.rc file simulates EEPROM storage.

Because IA based systems typically implement password pro-
tection in the sytem BIOS, there is no support for pass-
word protection in the eeprom program. While it is possible
to set the security-mode, security-password and security-
#badlogins properties on IA based systems, these properties
have no special meaning or behavior on IA based systems.

OPTIONS
-f device
Use device as the EEPROM device.

IA Only
-I Initialize boot properties on an IA based system. Only
init(1M) run-level initialization scripts should use
this option.

OPERANDS
IA Only
acpi-user-options
A configuration variable that controls the use of
ACPI. A value of 0x0 attempts to use ACPI if it is
available on the system. A value of 0x2 disables the
use of ACPI. The default value is 0x0.

mmu-modlist
A colon-separated list of candidate modules that
implement memory management. If mmu-modlist is
defined, it overrides the default list derived from
the memory configuration on IA based systems. Instead,
the first module in the list that is found in
/platform/platform-name/kernel/mmu is used.

NVRAM CONFIGURATION PARAMETERS
Not all OpenBoot systems support all parameters. Defaults
may vary depending on the system and the PROM revision.

auto-boot ?
If true, boot automatically after power-on or reset.
Defaults to true.

ansi-terminal ?
Configuration variable used to control the behavior of
the terminal emulator. The value false makes the ter-
minal emulator stop interpreting ANSI escape
sequences, instead just echoing them to the output
device. Default value : true.

boot-command
Command executed if auto-boot ? is true. Default value
is boot.

boot-device
Device from which to boot. boot-device may contain 0
or more device specifiers separated by spaces. Each
device specifier may be either a prom device alias or
a prom device path. The boot prom will attempt to open
each successive device specifier in the list beginning
with the first device specifier. The first device
specifier which opens successfully will be used as
the device to boot from. Defaults to disk net.

boot-file
File to boot (an empty string lets the secondary
booter choose default). Defaults to empty string.

boot-from
Boot device and file (OpenBoot PROM version 1.x only).
Defaults to vmunix.

boot-from-diag
Diagnostic boot device and file (OpenBoot PROM version
1.x only). Defaults to le()unix.

comX-noprobe
Where X is the number of the serial port, prevents
device probe on serial port X.

diag-device
Diagnostic boot source device. Defaults to net.

diag-file
File from which to boot in diagnostic mode. Defaults
to empty string.

diag-level
Diagnostics level. Values include off, min,max and
menus. There may be additional platform-specific
values. When set to off, POST is not called. If POST
is called, the value is made available as an argument
to, and is interpretted by POST. The default value is
platform-dependent.

diag-switch ?
If true, run in diagnostic mode. Defaults to true.

fcode-debug ?
If true, include name parameter for plug-in device
FCodes. Defaults to false.

hardware-revision
System version information.

input-device
Input device used at power-on (usually keyboard, ttya,
or ttyb). Defaults to keyboard.

keyboard-click ?
If true enable keyboard click. Defaults to false.

keymap
Keymap for custom keyboard.

last-hardware-update
System update information.

load-base
Default load address for client programs. Default
value is 16384.

local-mac-address ?
If true, network drivers use their own MAC address,
not system's. Defaults to false.

mfg-mode
Manufacturing mode argument for POST. Possible values
include off or chamber. The value is passed as an
argument to POST. Default value : off.

mfg-switch ?
If true, repeat system self-tests until interrupted
with STOP-A. Defaults to false.

nvramrc
Contents of NVRAMRC. Defaults to empty.

oem-banner
Custom OEM banner (enabled by setting oem-banner ? to
true). Defaults to empty string.

oem-banner ?
If true, use custom OEM banner. Defaults to false.

oem-logo
Byte array custom OEM logo (enabled by setting oem-
logo ? to true). Displayed in hexadecimal.

oem-logo ?
If true, use custom OEM logo (else, use Sun logo).
Defaults to false.

output-device
Output device used at power-on (usually screen, ttya,
or ttyb). Defaults to screen.

sbus-probe-list
Which SBus slots are probed and in what order.
Defaults to 0123.

screen-#columns
Number of on-screen columns (characters/line).
Defaults to 80.

screen-#rows
Number of on-screen rows (lines). Defaults to 34.

scsi-initiator-id
SCSI bus address of host adapter, range 0-7. Defaults
to 7.

sd-targets
Map SCSI disk units (OpenBoot PROM version 1.x only).
Defaults to 31204567, which means that unit 0 maps to
target 3, unit 1 maps to target 1, and so on.

security-#badlogins
Number of incorrect security password attempts.

This property has no special meaning or behavior on IA
based systems.

security-mode
Firmware security level (options : none, command, or
full). If set to command or full, system will prompt
for PROM security password. Defaults to none.

This property has no special meaning or behavior on IA
based systems.

security-password
Firmware security password (never displayed). Can be
set only when security-mode is set to command or full.

This property has no special meaning or behavior on IA
based systems.

example# eeprom security-password=
Changing PROM password :
New password :
Retype new password :

selftest-#megs
Metabytes of RAM to test. Ignored if diag-switch ? is
true. Defaults to 1.

skip-vme-loopback ?
If true, POST does not do VMEbus loopback tests.
Defaults to false.

st-targets
Map SCSI tape units (OpenBoot PROM version 1.x only).
Defaults to 45670123, which means that unit 0 maps to
target 4, unit 1 maps to target 5, and so on.

sunmon-compat ?
If true, display Restricted Monitor prompt (>).
Defaults to false.

testarea
One-byte scratch field, available for read/write test.
Defaults to 0.

tpe-link-test ?
Enable 10baseT link test for built-in twisted pair
Ethernet. Defaults to true.

ttya-mode
TTYA (baud rate, #bits, parity, #stop, handshake).
Defaults to 9600,8,n,1,-.

Fields, in left-to-right order, are :

baud rate :
110, 300, 1200, 4800, 9600...

data bits :
5, 6, 7, 8

parity :
n(none), e(even), o(odd), m(mark), s(space)

stop bits :
1, 1.5, 2

handshake :
-(none), h(hardware:rts/cts),
s(software:xon/xoff)

ttyb-mode
TTYB (baud rate, #bits, parity, #stop, handshake).
Defaults to 9600,8,n,1,-.

Fields, in left-to-right order, are :

baud rate :
110, 300, 1200, 4800, 9600...

data bits :
5, 6, 7, 8

stop bits :
1, 1.5, 2

parity :
n(none), e(even), o(odd), m(mark), s(space)

handshake :
-(none), h(hardware:rts/cts),
s(software:xon/xoff)

ttya-ignore-cd
If true, operating system ignores carrier-detect on
TTYA. Defaults to true.

ttyb-ignore-cd
If true, operating system ignores carrier-detect on
TTYA. Defaults to true.

ttya-rts-dtr-off
If true, operating system does not assert DTR and RTS
on TTYA. Defaults to false.

ttyb-rts-dtr-off
If true, operating system does not assert DTR and RTS
on TTYB. Defaults to false.

use-nvramrc ?
If true, execute commands in NVRAMRC during system
start-up. Defaults to false.

version2 ?
If true, hybrid (1.x/2.x) PROM comes up in version
2.x. Defaults to true.

watchdog-reboot ?
If true, reboot after watchdog reset. Defaults to
false.

EXAMPLES
Example 1 : Changing the number of megabytes of RAM.

The following example demonstrates the method for changing
from one to two the number of megabytes of RAM that the sys-
tem will test.

example# eeprom selftest-#megs
selftest-#megs=1

example# eeprom selftest-#megs=2

example# eeprom selftest-#megs
selftest-#megs=2

Example 2 : Setting the auto-boot ? parameter to true.

The following example demonstrates the method for setting
the auto-boot ? parameter to true.

example# eeprom auto-boot ?=true

When the eeprom command is executed in user mode, the param-
eters with a trailing question mark (?) need to be enclosed
in double quotation marks (" ") to prevent the shell from
interpreting the question mark. Preceding the question mark
with an escape character (\) will also prevent the shell
from interpreting the question mark.

example% eeprom "auto-boot ?"=true

FILES
/dev/openprom
device file

/usr/platform/platform-name/sbin/eeprom
Platform-specific version of eeprom. Use uname -i. to
obtain platform-name.

flash OBP

Jerome ROBERT — 2008-09-17T11:53:02Z

Comment flasher l'OBP de votre Ultra 5 / 10 .... Le patch 106121-18 permet
entre autre de faire fonctionner les nouvelles fonctionnalitÃ©es de Solaris 8
02/02 et Solaris 9.

Exemple : faire des installations de machine avec Jumpstart et des
clients en DHCP. Il faut que ces derniers aient au moins une OBP supÃ©rieurs Ã
3.25 .

[ Download Patch (5,207,398 bytes) ]
http://sunsolve.sun.com/pub-cgi/patchDownload.pl?target=106121&method=h

http://sunsolve.sun.com/pub-cgi/patchDownload.pl?target=106121&method=f

RÃ©sumÃ© :

# unzip 106121*.zip
# cp flash*- ?? /flash-update

!!!!! choisir le bon fichier suivant votre version OBP !!!!
# chmod 755 /flash-update
# init 0
Mettre le jumper : JP2 to write enable at 2+3. Default is write protect at
1+2
ok boot disk /flash-update

Standalone Flash PROM Update Utility, Rev. 2.5

Ultra(tm) 1

Ultra(tm) 2

Ultra(tm) 5/10

Ultra(tm) 30

Ultra(tm) 60 / E220R

Ultra(tm) 80 / E420R

Ultra(tm) Enterprise(tm) 250

Ultra(tm) Enterprise(tm) 450

This utility allows you to interactively update the firmware
revisions in specific system Flash PROM components.

Type h for help, q to quit, Return or Enter to continue :

Every precaution should be taken to prevent the loss of system
power during the Flash PROM programming process !

Type h for help, q to quit, Return or Enter to continue :

Firmware
Release(s)
Firmware Release(s)
Currently Existing in the System Available for
Installation / Install ?

-------------------------------------------
OBP 3.1.2 1996/03/28 17:08 OBP
3.1.5 1996/08/27
16:13 no
POST 3.1.4 1996/04/09 03:23 POST 3.1.5
1996/06/28 11:54 no

Type sa if you wish to select all available firmware releases for
installation. Type h for help, quit to exit, or cont to continue : sa

Firmware
Release(s)
Firmware Release(s)
Currently Existing in the System Available for
Installation / Install ?

-------------------------------------------
OBP 3.1.2 1996/03/28 17:08 OBP
3.1.5 1996/08/27
16:13 YES
POST 3.1.4 1996/04/09 03:23 POST 3.1.5
1996/06/28 11:54 YES

Type sa if you wish to select all available firmware releases for
installation. Type h for help, quit to exit, or cont to continue : cont

The Flash programming process is about to begin.

Type h for help, q to quit, Return or Enter to continue :

Erasing the top half of the Flash PROM.
Programming OBP into the top half of the Flash PROM.
Verifying OBP in the top half of the Flash PROM.

Erasing the bottom half of the Flash PROM.
Programming OBP into the bottom half of Flash PROM.
Verifying OBP in the bottom half of the Flash PROM.

Erasing the top half of the Flash PROM.
Programming POST into the top half of Flash PROM.
Verifying POST in the top half of the Flash PROM.

Programming was successful.

Resetting ...

Mettre le jumper : JP2 to write protect at 1+2

# rm /flash-update

Voici la version Officielle de Mr SUN :

Patch-ID# 106121-18 Keywords: Desktop Standalone Flash PROM Update Synopsis: Hardware/PROM: Ultra 5/10 Standalone Flash PROM Update Date: May/15/2002 Solaris Release: 7 8 SunOS Release: 5.7 5.8 Unbundled Product: Hardware/PROM NOTE: This utility is *not* OS-dependent. The list of releases shown under the "Solaris Release" and "SunOS Release" sections may not be complete: The absence of a valid Solaris Release or SunOS Release from the lists above does not preclude the installation of this patch against the hardware. Unbundled Release: OBP_3.31.0,POST_3.1.0,OBDIAG_P2.9 Xref: Topic: Relevant Architectures: sparc NOTE: Sun4u Ultra 5/10 only BugId's fixed with this patch: 4670050 Changes incorporated in this version: 4463337 4483753, 4091949 4114343 4114784 4119822 4169774 4176300 4187987 4188219 4198675 4203447 4221374 4256699 4267135 4287319 4310258 4318271 4325933 4338343 4342398 4346332 4360786 4360814 4360883 4407855 4407869 4123985 4129194 4511402 4661718 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: flash-update-Ultra510-10, flash-update-Ultra510-14, flash-update-Ultra510-16, flash-update-Ultra510-18, flash-update-Ultra510-latest 802-3233-20.ps, copyright,

Problem Description: 4670050: Patch 106121-17 will not work for Darwin 4661718: Add support for new audio chip AD1845 for Einstein OBDiag 4511402: patch 106121-15 with 375-0009(ultra10 Darwin system BD) does not work 4463337: PCI2.2 T(rhfa) timing violation causing devices behind pci-pci bridge not probed 4483753: RARP replies which dont include ar$spa must be handled correctly 4407855: Code that validates idprom contents incorrectly expects 0x80 at offset 1 4407869: probe-scsi and probe-scsi-all need to recognize device_type=scsi* 4360814: PCI resources allocated on one segment is not available on the other 4318271: During probe register at 0x30 not found on Ultra 10 4360786: Ecache sizing may be incorrect on modules using IBM SRAM parts 4360883: DHCP IP address validation code must be more robust 4123985: erroneous divide by zero bug in OBP 4325933: Branch on register intructions are broken in assem.fth 4338343: fb8: "Memory Address not Aligned" error in fb8-insert-lines 4176300: Draw logo doesn't clip, returns negative number for line# to draw at. 4203447: setting nvram variables when config-valid? is false leaves parameters on stack 4346332: System type is not displayed in banner after flash update 4267135: The "mfg-mode" name does not retain the custom value 4342398: Fix memory timing violation when using 440 Mhz CPU modules 4310258: Add support for DHCP. 4287319: The flash utility needs to be able to support ST and Hyundai 29F080 parts. 4256699: Ultra 60s/450 mhz cpus fail jumpstart install even with OE CD modification 4221374: Provide more descriptive message when user tries to use wrong Flash update image. 4091949: Flashprom updates for Sun4u systems may cause NVRAM contents to change 4198675: The flash update utility is unable to detect locked flashprom sectors. 4169774: DTR not asserted high when Ultra-10 powered on to ok prompt. 4129194: Fix the hex parsing of the IP address. 4114784: Can't boot from Symbios single or differential scsi drives. 4114343: Incorrect patterns used to probe PCI device register. 4119822: Restored the power-cycle-limit of 3000. 4187987: Corrects "Unimplemented Fcode token" message displayed. 4188219: Integrated PGX24 ATI FCode version 1.7 (Graphics fcode only detects 2 MB SGRAM, instead of 4MB as standarD).

Patch Installation Instructions: ================================ Intro ----- This README is intended for users who wish to upgrade the firmware in their Ultra 5/10 system Flash PROM. Summary of the Patch Installation Process: ------------------------------------------ The installation shall comprise of the following steps 1) Determine the system's current Flash PROM firmware revision. 2) Compare the current Flash PROM firmware revision with the available or latest Flash PROM firmware revisions. 3) If the current Flash PROM firmware revision is lower than the latest available firmware revision in this patch, then proceed to the next step. If NOT, STOP: DO NOT CONTINUE. 4) Prepare the system for the Flash PROM update 5) Running the Flash PROM Utility 6) Verifying successful Flash PROM Update 7) Restoring the system 8) Resume operations Patch Installation instructions (in detail): ============================================ The required steps are explained in greater detail below. 1) Determine the System's Current Firmware Revisions ------------------------------------------------- While the OS is running the following command may be used to determine the current system firmware revisions; /usr/sbin/prtconf -V The firmware revisions may also be determined from the PROM monitor's "ok" prompt with the following command; .version 2) Compare the current Flash PROM firmware revision with the available or latest Flash PROM firmware revisions. Compare the output of the OBP line in the "prtconf -V" output. Find the revision number and compare with the revision on the entries below that of the "flash-update-Ultra510-latest" line; Available Firmware Revisions ---------------------------- -10 flash-update-Ultra510-10 All Models OBP: 3.27 Version 0 created 2000/08/23 15:45 POST: 3.1.0 -14 flash-update-Ultra510-14 All Models OBP: 3.29 Version 0 created 2000/12/20 18:45 POST: 3.1.0 -16 flash-update-Ultra510-16 All Models OBP: 3.31 Version 0 created 2001/07/25 20:36 POST: 3.1.0 LATEST flash-update-Ultra510-18; flash-update-Ultra510-latest All Models OBP: 3.31 Version 0 created 2001/07/25 20:36 POST: 3.1.0 3) Is the UPGRADE NECESSARY? If the current Flash PROM revision matches the version numbers given under the flash-update-Ultra510-latest line, then STOP Here. This UPGRADE IS NOT NECESSARY. If the current Flash PROM firmware revision is lower than the latest firmware revision in this patch, then proceed to the next step. 4) Preparing the System --------------------- a) As root, copy the latest "flash-update" file from the directory containing the patch to the root directory as follows: # cp flash*latest / # chmod 755 /flash-update* In order to boot the binary, it must be located within the root partition. If it is not already located within the root partition then move it to /. If the binary is already located elsewhere within the root partition then note the exact filepath so that the binary can be booted later. b) As root, exit the OS such that the system returns to the PROM's "ok" prompt: # halt ok c) Power off the system. ** CAUTION ** Do not attempt to access any part of the system hardware with the system power still on! d) Remove the system top cover. (If you unsure how to do this then consult your system "Installation Guide" or "Service Manual".) e) Set JP2 to write enable at 2+3. Default is write protect at 1+2 Locate jumper JP2. Jumper JP2 provides a write enable/disable mechanism for the Flash PROM. JP2 normally connects pins 1+2, which causes the Flash PROM to be write protected. To enable patch installation, write enable the Flash PROM by MOVING the JP2 jumper from pins 1+2 to pins 2+3. **IMPORTANT NOTE**: If this jumper is NOT set to WRITE ENABLE, the Flash update will fail. (If you have difficulty locating JP2 then consult Figure 1-3 in the "Sun Flash PROM Guide for Workstations and Workgroup Servers - Standalone Version"). f) Replace the system top cover. 5) Running the Flash Update Utility -------------------------------- a) Power on the system Wait for the PROM's banner to appear, and then b) use the Stop-A keys (or Break key, if running from a serial line) to abort the auto-boot sequence. ** NOTE ** If the flash update completes normally then the values contained within the system's Non-Volatile RAM (NVRAM) configuration variables will be retained. However, if the update process is some- how interrrupted then it is possible that any non-default values contained in NVRAM will be lost. For this reason it is recommended that you note down on paper the contents of any NVRAM configuration variable which has been customized so that they may be manually restored at a later time, if necessary. (Use the PROM's "printenv" command to list the variables and their values.) c) The system should now display the PROM monitor's "ok" prompt. Now boot the Flash update utility as given below: CAUTION: Do not boot/run revisions lower than the latest unless you are absolutely sure that that is what you want to do! ok boot disk /flash-update-Ultra510-latest NOTE: If your system's boot device is not "disk" then you will have to specify the appropriate devalias (e.g. disk2). If the binary is located in a location other than / then provide the entire filepath after the boot device. Answer the questions as prompted by the utility. +++++++++++++++++++++ example Flash update follows ++++++++++++++++++++++++ ++++++++ Note that this is an example only. Much of the information ++++++ ++++++++ which is displayed by your system will be different from ++++++ ++++++++ what is shown below. ++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Standalone Flash PROM Update Utility, Rev. 2.5 Ultra(tm) 1 Ultra(tm) 2 Ultra(tm) 5/10 Ultra(tm) 30 Ultra(tm) 60 / E220R Ultra(tm) 80 / E420R Ultra(tm) Enterprise(tm) 250 Ultra(tm) Enterprise(tm) 450 This utility allows you to interactively update the firmware revisions in specific system Flash PROM components. Type h for help, q to quit, Return or Enter to continue: Every precaution should be taken to prevent the loss of system power during the Flash PROM programming process! Type h for help, q to quit, Return or Enter to continue: Firmware Release(s) Firmware Release(s) Currently Existing in the System Available for Installation / Install? --------------------------------- ------------------------------------------- OBP 3.1.2 1996/03/28 17:08 OBP 3.1.5 1996/08/27 16:13 no POST 3.1.4 1996/04/09 03:23 POST 3.1.5 1996/06/28 11:54 no Type sa if you wish to select all available firmware releases for installation. Type h for help, quit to exit, or cont to continue: sa Firmware Release(s) Firmware Release(s) Currently Existing in the System Available for Installation / Install? ---------------------------------- ------------------------------------------- OBP 3.1.2 1996/03/28 17:08 OBP 3.1.5 1996/08/27 16:13 YES POST 3.1.4 1996/04/09 03:23 POST 3.1.5 1996/06/28 11:54 YES Type sa if you wish to select all available firmware releases for installation. Type h for help, quit to exit, or cont to continue: cont The Flash programming process is about to begin. Type h for help, q to quit, Return or Enter to continue: Erasing the top half of the Flash PROM. Programming OBP into the top half of the Flash PROM. Verifying OBP in the top half of the Flash PROM. Erasing the bottom half of the Flash PROM. Programming OBP into the bottom half of Flash PROM. Verifying OBP in the bottom half of the Flash PROM. Erasing the top half of the Flash PROM. Programming POST into the top half of Flash PROM. Verifying POST in the top half of the Flash PROM. Programming was successful. Resetting ... Restoring previous NVRAM environment settings... #power-cycles = 10 auto-boot? = false security-#badlogins = 0 OK Resetting ... +++++++++++++++++++++ example Flash update ends ++++++++++++++++++++++++++ Note that the section "Restoring previous NVRAM environment settings..." up to the "Resetting ..." line will only be displayed on serial port A. If you are running from the keyboard/console devices then you will not see those lines displayed. Once the PROM's banner reappears then use the Stop-A keys (or Break key, if running from a serial line) to abort the auto-boot sequence if the system begins to boot. 6) Verifying successful Flash PROM Update Verify from the results of the .version command that the OBP version matches the OBP version given above under the flash-update-Ultra510-latest entry in Step 2. 7) Restoring the system The system should be restored to the original set-up as follows: a) Turn the power to the system off. b) Remove the top cover and move jumper JP2 to pins 1+2. c) Replace the top cover. If any problems should be encountered during the firmware upgrade then consult the "Sun Flash PROM Guide for Workstations and Workgroup Servers - Standalone Version". 8) Resume operations a) Turn on the system power and allow the system to boot the operating system. b) Once the system has rebooted you may wish to remove the Flash Update binaries and documents since they will no longer be needed. # rm /flash-update* c) Remember to remove the files from their original location if they were not extracted directly into the root directory. Special Install Instructions: ----------------------------- ************************************************************************** ************************************************************************** **WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:** * PLEASE READ THE INSTRUCTIONS CAREFULLY AND ENTIRELY. PLEASE FOLLOW THE INSTRUCTIONS EXACTLY AS THEY ARE STATED. * FAILURE TO FOLLOW INSTRUCTIONS COULD EITHER RESULT IN A DEFECTIVE BOARD OR UNSUCCESSFUL FLASH PROM UPDATE. * THIS IS NOT A STANDARD PATCH in that it does not use the installpatch and backoutpatch scripts. * THIS PATCH CANNOT BE INSTALLED ON AN ONLINE OPERATING SYSTEM BECAUSE THE INSTALL INSTRUCTIONS REQUIRES THAT THE SYSTEM BE BROUGHT DOWN. BE SURE TO SCHEDULE DOWN TIME TO INSTALL THIS PATCH. * INSTALLATION OF THIS PATCH REQUIRES A HARDWARE JUMPER CHANGE. IF YOU ARE UNSURE ON HOW TO OPEN THE SYSTEM BOX, PLEASE ENSURE THAT A QUALIFIED PERSON, WITH THE STATIC WRIST STRAP KIT NEEDED TO SERVICE ELECTRONIC EQUIPMENT, IS AVAILABLE TO COMPLETE THIS ACTIVITY. FAILURE TO USE STATIC PROTECTION KIT OR IMPROPER HANDLING COULD RESULT IN THE DAMAGE OF THE SYSTEM BOARD. * PLEASE REVIEW NOT ONLY THIS README BUT ALSO ADDITIONAL DOCUMENTATION GIVEN. The file "802-3233-xx.ps" (where xx stands for the latest numeric revision) is a PostScript copy of the "Sun Flash PROM Guide for Workstations and Workgroup Servers - Standalone Version", which provides the following; (i) A board-level diagram that gives the approximate location of the hardware jumper (that will need to be changed). Note, however, that The Flash PROM Guide was originally written for a user who is running the Flash PROM update utility from a bootable CDROM, and thus it will not contain the proper boot commands for installation of this patch. Also note that the instructions in the document for installing packages are not valid for this patch. * TAKE EVERY PRECAUTION TO ENSURE THAT THE UPGRADE IS NOT INTERRUPTED ONCE IT IS STARTED! **WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:** ************************************************************************** ************************************************************************** README -- Last modified date: Wednesday, May 15, 2002