Ndis 4.0 (Windows Nt) Driver Messages; Unix Messages - IBM xSeries 230 6RY Hardware Maintenance Manual

Table 3. NDIS 2.01 (OS/2) driver messages for the Ethernet controller (continued)
PCNTND-25 PCI scan specified, PCI bus not found!
PCNTND-29 WARNING: DMA number is not necessary for PCI device.
PCNTND-33 PCNET device with specified IOBASE is already in use.

NDIS 4.0 (Windows NT) driver messages

This section contains the error messages for the NDIS 4.0 drivers. The explanation
and recommended action are included with each message.
Table 4. NDIS (Windows NT) driver messages for the Ethernet controller
™
PermaNet Server:
PermaNet Server:
PermaNet Server:

UNIX messages

This section provides descriptions of the Ethernet error messages for the SCO
UNIX LLI driver, and suggested actions to resolve each problem.
Table 5. UNIX LLI driver messages for the Ethernet controller
pnt0-2 PCI search specified, PCI device not found!
Explanation: The driver cannot locate the Ethernet controller on the PCI bus. Action:
v Run the NETCONFIG program to search for another Ethernet controller
v Verify that the Ethernet controller is enabled. If the Ethernet controller is enabled, run the
diagnostic programs.
24
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
Explanation: The driver cannot locate the PCI bus. Action: Run the diagnostic
programs.
Explanation: The Ethernet controller does not require a DMA setting. Action:
Remove the DMA setting in the PROTOCOL.INI file.
Explanation: The specified I/O address number is already in use by another
Ethernet controller or device. Action: Remove the I/O address setting in the
PROTOCOL.INI file.
No Secondary Adapter Found. Grouping Mode is disabled.
Explanation: The failover option requires an adapter that is compatible
with the device driver of the Ethernet controller on the system board.
No such adapter was found. Action: Make sure the correct adapter is
installed.
Problem Occurs on the Primary Adapter. Switching over to the
Secondary Adapter.
Explanation: The system detected a problem with the primary
Ethernet connection and has transferred all network traffic to the
secondary Ethernet controller. Action: identify the cause of the failure
on the primary Ethernet connection. Restoring the operational state of
the primary connection will cause the network traffic to automatically
transfer to the primary Ethernet controller.
Switching back to Primary Adapter.
Explanation: The primary Ethernet connection is now operating
correctly. Network traffic will automatically transfer to the primary
Ethernet controller. Action: None needed, message is for information
only.