eeprom - EEPROM display and load utility
/usr/sbin/eeprom [-] [-f device] [parameter[=value]]
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 parameters. 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 based systems implement firmware password protection with eeprom, using the security-mode, security-password and security-#badlogins properties.
EEPROM storage is simulated using a file residing in the platform-specific boot area. The /boot/solaris/bootenv.rc file simulates EEPROM storage.
Because x86 based systems typically implement password protection in the system BIOS, there is no support for password protection in the eeprom program. While it is possible to set the security-mode, security-password and security-#badlogins properties on x86 based systems, these properties have no special meaning or behavior on x86 based systems.
-f device
acpi-user-options
For all releases of Solaris 10 and Solaris 11, a value of of 0x0 means that there will be an attempt to use ACPI if it is available on the system. A value of 0x2 disables the use of ACPI.
For the Solaris 10 1/06 release, a value of 0x8 means that there will be an attempt to use ACPI in a mode compatible with previous releases of Solaris 10 if it is available on the system. The default for Solaris 10 1/06 is 0x8.
For releases of Solaris 10 after the 1/06 release and for Solaris 11, the default is 0x0.
Most users can safely accept the default value, which enables ACPI if available. If issues related to the use of ACPI are suspected on releases of Solaris after Solaris 1/06, it is suggested to first try a value of 0x8 and then, if you do not obtain satisfactory results, 0x02.
console
Not all OpenBoot systems support all parameters. Defaults vary depending on the system and the PROM revision. See the output in the "Default Value" column of the printenv command, as entered at the ok (OpenBoot) prompt, to determine the default for your system.
auto-boot?
ansi-terminal?
boot-args
boot-command
boot-device
boot-file
boot-from
boot-from-diag
boot-ncpus
comX-noprobe
diag-device
diag-file
diag-level
diag-switch?
error-reset-recovery
On platforms supporting this variable, it replaces the watchdog-reboot?, watchdog-sync?, redmode-reboot?, redmode-sync?, sir-sync?, and xir-sync? parameters.
The options are:
none
sync
boot
fcode-debug?
hardware-revision
input-device
keyboard-click?
keyboard-layout
keymap
last-hardware-update
load-base
local-mac-address?
mfg-mode
mfg-switch?
nvramrc
network-boot-arguments
The syntax for arguments supported for network booting is:
[protocol,] [key=value,]*
All arguments are optional and can appear in any order. Commas are required unless the argument is at the end of the list. If specified, an argument takes precedence over any default values, or, if booting using DHCP, over configuration information provided by a DHCP server for those parameters.
protocol, above, specifies the address discovery protocol to be used.
Configuration parameters, listed below, are specified as key=value attribute pairs.
tftp-server
file
host-ip
router-ip
subnet-mask
client-id
hostname
http-proxy
tftp-retries
dhcp-retries
If no parameters are specified (that is, network-boot-arguments is an empty string), the PROM will use the platform-specific default address discovery protocol.
Absence of the protocol parameter when other configuration parameters are specified implies manual configuration.
Manual configuration requires that the client be provided with all the information necessary for boot. If using manual configuration, information required by the PROM to load the second-stage boot program must be provided in network-boot-arguments while information required for the second-stage boot program can be specified either as arguments to the boot program or by means of the boot program's interactive command interpreter.
Information required by the PROM when using manual configuration includes the booting client's IP address, name of the boot file, and the address of the server providing the boot file image. Depending on network configuration, it might be required that the subnet mask and address of the default router to use also be specified.
oem-banner
oem-banner?
oem-logo
oem-logo?
pci-mem64?
This variable is available on SPARC platforms only and is optional. Some versions of SunOS do not support PCI MEM64 addresses and will fail in unexpected ways if the OpenBoot PROM allocates PCI MEM64 addresses.
The default value is system-dependent. If the variable exists, the default value is appropriate to the lowest version of the SunOS that shipped with a specific platform.
output-device
redmode-reboot?
redmode-sync?
rootpath
sbus-probe-list
screen-#columns
screen-#rows
scsi-initiator-id
sd-targets
security-#badlogins
security-mode
security-password
example# eeprom security-password= Changing PROM password: New password: Retype new password:
selftest-#megs
sir-sync?
skip-vme-loopback?
st-targets
sunmon-compat?
testarea
tpe-link-test?
ttya-mode
Fields, in left-to-right order, are:
Baud rate:
Data bits:
Parity:
Stop bits:
Handshake:
ttyb-mode
Fields, in left-to-right order, are:
Baud rate:
Data bits:
Stop bits:
Parity:
Handshake:
ttya-ignore-cd
ttyb-ignore-cd
ttya-rts-dtr-off
ttyb-rts-dtr-off
use-nvramrc?
verbosity
version2?
watchdog-reboot?
watchdog-sync?
xir-sync?
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 system 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 parameters 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
Example 3 Using network-boot-arguments
To use DHCP as the boot protocol and a hostname of abcd.example.com for network booting, set these values in network-boot-arguments as:
example# eeprom network-boot-arguments="dhcp,hostname=abcd.example.com"
...then boot using the command:
ok boot net
Note that network boot arguments specified from the PROM command line cause the contents of network-boot-arguments to be ignored. For example, with network-boot-arguments set as shown above, the boot command:
ok boot net:dhcp
...causes DHCP to be used, but the hostname specified in network-boot-arguments will not be used during network boot.
Example 4 Setting System Console to Auxiliary Device
The command below assigns the device /dev/term/a as the system console device. You would make such an assignment prior to using tip(1) to establish a tip connection to a host.
On a SPARC machine:
# eeprom output-device=/dev/term/a
On an x86 machine:
# eeprom console=ttya
On a SPARC machine, the preceding command would be sufficient for assigning the console to an auxiliary device. For an x86 machine, you might, in addition, need to set the characteristics of the serial line, for which you would have to consult the BIOS documentation for that machine. Also, on some x86 machines, you might use a device other than device a, as shown above. For example, you could set console to ttyb if the second serial port is present.
/boot/solaris/bootenv.rc
/dev/openprom
/usr/platform/platform-name/sbin/eeprom
See attributes(5) for descriptions of the following attributes:
|
passwd(1), sh(1), svcs(1), tip(1), uname(1), boot(1M), kadb(1M), kernel(1M), init(1M), svcadm(1M), attributes(5), smf(5)
OpenBoot 3.x Command Reference Manual
Закладки на сайте Проследить за страницей |
Created 1996-2024 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |