- Message:
No EEPROM Data -> EISA Card ID: eisa_id |
- Cause:
An EISA card identified itself, but non-volatile
memory (NVM) has no configuration data for the slot.
- Action:
Run eisa_config to update NVM.
- Message:
- Cause:
NVM recognizes that the card exists, but cannot
read its ID.
- Action:
If a card is present, there is a hardware problem.
Replace the card. If a card is not present, ignore the message.
- Message:
Board ID: eisa_id inconsistent with NVM ID: eisa_id |
- Cause:
The ID read from the card does not match the card
ID information stored in NVM.
- Action:
If board has been moved, run eisa_config in automatic mode. If this message persists after
running eisa_config and updating NVM, replace the board. If board
has been removed, ignore the message.
- Message:
Bad eeprom data for board eisa_id |
- Cause:
An attempt to read the NVM configuration information
failed. This represents a system problem.
- Action:
Call your HP representative.
- Message:
Error initializing board eisa_id |
- Cause:
An attempt to initialize the card with the stored
NVM initialization data failed.
- Action:
Check CFG file for inaccuracies. Suspect a hardware problem.
- Message:
EISA Board ID:eisa_id ignored Board not present or driver not configured into kernel |
- Cause:
The ID displayed was obtained from NVM, not the
card. Either an ISA card is present, but not its driver or the driver
is present, but not the card. (Since ISA cards do not identify themselves,
only the card's driver can verify its existence.)
- Action:
Ensure the card in installed and verify that the
driver is configured into the kernel.
- Message:
EISA Board ID: eisa_id ignoredDriver not configured into kernel |
- Cause:
The system found the EISA card, but not its driver.
- Action:
Verify that the driver is configured into the kernel.
- Message:
EISA Board ID: eisa_id ignored, error initializing board |
- Cause:
A driver accepted this card, but failed to initialize
it.
- Action:
This is probably a defective card.
- Message:
EISA: eisa_last_attach not called, bad driver in kernel |
- Cause:
If a driver does return correctly from its attach
routine, this will panic the kernel. Assuming that the drivers installed
are working, this message should never appear.
- Action:
If you are using a non-HP card and driver, remove
both the card and driver and try again. If error does not recur,
the non-HP driver is bad. If the error recurs, call your HP representative.
- Messages:
EISA WARNING: mapping in system board failed EISA WARNING: mapping in I/O map entries failed
|
- Causes:
System encountered problems either in creating virtual-to-physical mappings
of the EISA system board registers or in attempting to initialize
a system board resource.
If either of these messages appear while booting from EISA
SCSI, the system will fail to boot. If booting from other than EISA
SCSI, the EISA cards will not be recognized.
- Action:
Call your HP representative.
- Message:
slot_num Slot EISA Expander Initialized: eisa_id |
- Cause:
This informational message indicates that the bus
adapter located between the EISA bus and the host system bus initialized
properly. It also indicates how many slots the kernel is configured
to recognize.
- Action:
None.
- Message:
- Cause:
This informational message indicates which slot
is currently being initialized. When successful, each driver displays
its own initialization message. For example:
EISA SLOT 1: driver_specific_message |
- Action:
None.
- Message:
Successfully Initialized EISA Boot Device |
- Cause:
The system recognized a special case. If the system
boots from EISA SCSI before EISA SCSI configuration
information is stored in NVM, the processor-dependent code uses
default configuration data that might conflict with other EISA cards
in the system. To handle this, the system ignores all cards except
the boot EISA SCSI during the first power-up and continues a limited
boot.
If eisa_config (run in /sbin/bcheckrc) can create a valid configuration, it records
it in NVM and the system.sci file, and the system is automatically rebooted.
If a valid configuration cannot be created, eisa_config issues an error message, the system comes up with
the other cards unusable. In this case, you can run eisa_config interactively to fix the configuration and to
reboot manually.
- Action:
None.
- Message:
- Cause:
Either the slot is empty, or NVM reports the slot
is empty, or the slot has an ISA card but no EEPROM data, or the
slot was skipped because of an already cited circumstance.
- Action:
None.
- Message:
EISA card id eisa_id in slot slot_num had fatal error |
- Cause:
An EISA card asserted the IOCHK line indicating
a fatal error. An expansion card might do this if there was a parity
error on a memory card. (Not all cards assert IOCHK.)
- Action:
Replace the card.
- Messages:
EISA_WARNING: unable to allocate eeprom_geninfo EISA_WARNING: unable to allocate eeprom_slot_info for slot 0 EISA_WARNING: unable to allocate eeprom_slot_info EISA WARNING: unable to allocate: func_data EISA_WARNING: unable to allocate eeprom_cfg_header EISA WARNING: unable to allocate eeprom WARNING: unable to map eeprom registers EISA WARNING: unable to map eeprom |
- Cause:
These warnings indicate system problems when attempting
to allocate resources necessary for EISA initialization. If booting
from an EISA device, the system will not boot up. If not booting
from an EISA device, the system will boot up but EISA will not be
initialized.
- Action:
Call your HP representative.
- Message:
EISA_WARNING: NVM checksum invalid, clearing eeprom |
- Cause:
A checksum failed when performed on NVM at power-up,
causing the system to erase the contents of non-volatile memory.
As EISA comes up, it will complain that NVM data is missing for
cards that identify themselves. eisa_config running from /etc/bcheckrc will automatically generate data for and reconfigure
the EISA cards that are present. You will need to reconfigure ISA
cards, by running eisa_config interactively.
- Action:
Follow instructions in “Configuring E/ISA
Boards Using Interactive Mode ”.