PC Server 325 / 330 - Ethernet Controller Messages

52.066 bytes

Service Hints & Tips

Document ID: GSMH-3EWFJ2

PC Server 325 / 330 - Ethernet Controller Messages

Applicable to: World-Wide

Ethernet Controller Messages:
Ethernet Controller Messages

The integrated Ethernet controller might display messages from the following drivers:
Novell NetWare Server ODI
Novell NetWare Server DOS ODI
Novell NetWare Server OS/2 ODI
NDIS Adapter for level 2.01
NDIS Adapter for level 3.0
Packet Driver
SCO UNIX LLI, UnixWare DLPI, and SunSoft Solaris

Novell NetWare Server ODI Driver Messages:
This section contains the error messages for the Novell NetWare server ODI driver. The explanation and recommended action are included with each message.

Error Message

Explanation

Action

PCNTNW-NW-026 The MSM is unable to parse a required custom keyword.

The user entered an incorrect parameter keyword.

Enter the keyword correctly. Then, reload the driver.

PCNTNW-NW-054 The board did not respond to the initialization command.

The board did not respond when the driver tried to initialize it.

Perform the following steps:
1. Verify that the Ethernet jumper on the system board is set to the default, enabled position.
2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTNW-NW-58 The board did not respond to the initialization command.

The IRQ setting might be incorrect with the hardware setting, or the EEPROM might be corrupted.

Perform the following steps:
1. Verify that the IRQ settings in the NET.CFG file match the configuration settings in the Configuration/Setup utility programs.
See "PCI Bus Control" for information on setting the interrupt requests.
2. Verify that the EEPROM on the system board is programmed correctly. Verify that the EEPROM on the system board is programmed correctly.

PCNTNW-NW-66 The cable might be disconnected from the board.

The cable might be disconnected from the server's Ethernet port.

Verify that a cable is connected to the AUI port or the 10BASE-T port.

PCNTNW-NW-071 The matching virtual adapter could not be found.

You tried to load another instance of the driver with a different I/O address. This new board could not be found.

If you installed an IBM Ethernet adapter, make sure the adapter is seated properly. Also, check the I/O settings of the board with the settings supplied to the drive.

PCNTNW-NW-072 A resource tag is unavailable.

The driver tried to allocate some resources that were not available.

Add or free some memory in the server. Then, restart the server.

PCNTNW-NW-073 Unable to allocate memory.

The driver failed to allocate the memory needed for normal operation.

Add more memory, or free some memory resources in the server. Then, restart the server.

PCNTNW-NW-074 The hardware interrupt cannot be set.

An attempt was made to initialize a given hardware interrupt. The attempt was not successful.

Perform the following steps:
1. Verify that the Ethernet jumper on the system board is set to the default, enabled position.
2. Make sure that the interrupt request numbers are set correctly, and that no other devices are using the interrupt. See "PCI Bus Control" on for more information.

PCNTNW-NW-075 The MLID cannot be registered with the LSL.

An error occurred while the driver was trying to register with Link Support Layer.

Check the version of Netware Operating System. Make sure that this driver is correct for the version of Netware that you are using. Restart the server.

PCNTNW-NW-076 The polling procedure cannot be added.

An error occurred while the driver was adding a polling procedure to the Netware Operating System polling routines.

Check the version of Netware Operating System. Make sure that this driver is correct for the version of Netware that you are using. Restart the server.

PCNTNW-NW-077 The event notification cannot be registered.

The driver failed to register its event notification routines with the Netware Operating System.

Check the version of Netware Operating System. Make sure that this driver is correct for the version of Netware that you are using. Restart the server.

PCNTNW-NW-078 The firmware file cannot be read.

The driver to read a firmware file. The read process failed.

Make sure that the support files that accompany the driver are present. Restart the server.

PCNTNW-NW-079 The MLID did not initialize MSMTx Free Count.

The MSMTx Free Count is not initialized properly.

Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-084 Unable to allocate memory below the 16 megabyte boundary.

A request was made to allocate memory below 16 megabytes. The request did not complete successfully.

Free some memory below 16 megabytes, or add more memory below the 16 megabyte boundary.

PCNTNW-NW-086 The driver parameter block is too small.

The driver parameter block is too small.

Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-087 The media parameter block is too small.

The driver media parameter block is too small.

Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-091 The hardware configuration conflicts.

You tried to load a new frame type for the existing adapter. The hardware assumptions made in doing so are incorrect.

Make sure that the hardware configuration matches the software settings. See "PCI Bus Control" for information on viewing and changing interrupt requests.

PCNTNW-NW-092 Cannot schedule AES without an HSM routine.

The Netware Operating System needs a Hardware Support Module routine before it schedules an AES event.

Restart the server. If the error is still present, replace the system board.

PCNTNW-NW-093 Cannot schedule interrupt time call back without an HSM routine.

The driver needs a Hardware Support Module routine before it can schedule an interrupt time call back.

Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-094 Cannot set hardware interrupt without an HSM routine.

The driver needs a hardware interrupt call back routine routine before it sets the interrupt.

Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-095 Cannot add polling without an HSM routine.

The driver needs an HSM polling routine before it can start the polling process.

Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-126 The group bit in the node address override was cleared.

The IEEE address has a group bit indicating that an address belongs to a group of stations. This bit is used only as a destination address; it cannot be used as a source address. You tried to enter a source address with this bit set. The driver cleared the group bit of the source address.

None.

PCNTNW-NW-127 The local bit in the node address override was set.

The local bit in the IEEE address format indicates that the addresses are being managed locally. If you use the node address override capabilities of this driver to enter a new address, the local bit should be set. You entered an address without the local bit set. The driver has set the local bit.

None.

PCNTNW-NW-164 The device was not found.

The driver cannot find an Ethernet controller in the server.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTNW-NW-164 Device not found at IOADDRESS.

The Ethernet controller cannot be found at the IO address specified in the NET.CFG file.

Verify that the IO Address in the NET.CFG file matches with the board. Otherwise, remove the PORT keyword from the NET.CFG file.

PCNTNW-NW-167 PCI scan specified, device not found.

The driver cannot locate the Ethernet controller on the PCI bus.

Perform the following steps:
1. Verify that the Ethernet jumper on the system board is set to the default, enable position.
2. Edit the NET.CFG file to change the BUSTYPE keyword to PCI1.
3. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTNW-NW-180 The DMA parameter is not necessary for PCI device.

The Ethernet controller does not require a DMA setting.

Delete the DMA parameter from the NET.CFG file.

Novell NetWare DOS ODI Driver Messages:
This section contains the error messages for the Novell NetWare DOS ODI device driver. The explanation and recommended action are included with each message.

Error Message

Explanation

Action

PCNTW-DOS-1 The LSL is not loaded.

The Link Support support module (LSL.COM) is not loaded.

Load LSL.COM; then, load the device driver.

PCNTW-DOS-2 The LSL has no more room for a board using Frame< string>.

The maximum number of adapters, whether virtual or physical, has been registered with the Link Support Layer. In the PC Server 325, the DOS ODI LSL can support up to five PCI Ethernet adapters, plus the Ethernet controller in the system board.

Reduce the number of active adapters in the systems by removing an adapter, or by decreasing the number of frame types activated by Multiple Link Interface Driver (MLID).

PCNTW-DOS-3 Could not find PCNTNW MLID to unload.

A request was made to unload PCNTNW MLID, but the MLID is not loaded.

None.

PCNTW-DOS-4 A TSR is loaded above the PCNTNW MLID.

You tried to unload the PCNTNW MLID from memory, but the PCNTNW MLID detected another Terminate and Stay Resident (TSR) program loaded above the MLID. For the PCNTNW MLID to unload safely, you must first unload any TSR programs that were loaded after you loaded the MLID.

Either unload the other TSR program before loading the PCNTNW MLID, or unload the TSR program before attempting this operation.

PCNTW-DOS-5 PCNTNW MLID could not be unloaded; the operation was aborted.

The PCNTNW MLID attempted to remove the resident PCNTNW MLID from memory, and failed. A hardware error has probably occurred.

Run the Ethernet diagnostic.

PCNTW-DOS-6 The adapter did not initialize. PCNTNW did not unload.

The hardware did not initialize correctly. The PCNTNW driver did not load.

Check the hardware. Make sure that the board's hardware setting matches its settings in the NET.CFG file.

PCNTW-DOS-7 You need another PCNTNW MLID Section Heading in the NET.CFG file in order to load the MLID again.

You tried to load the PCNTNW MLID a second time. Normally, you would do this so that you could use two or more Ethernet controllers in the server. When two or more of the same type of Ethernet controllers are installed in the server, an associated PCNTNW MLID section heading must be specified in the NET.CFG file.

Create a NET.CFG file and add the commands for both PCNTNW MLID boards to the file. Then, restart the server.

PCNTNW-DOS-8 A NET.CFG is required to load the MLID again.

You tried to load the PCNTNW MLID a second time. Normally, you would do this so that you could use two or more Ethernet controllers in the server. When two or more of the same type of Ethernet controllers are installed in the server, an associated PCNTNW MLID section heading must be specified in the NET.CFG file.

Create a NET.CFG file and add the commands for both PCNTNW MLID boards to the file. Then, restart the server.

PCNTNW-DOS-9 The NET.CFG entry has been ignored.

The PCNTNW ignored the NET.CFG entry.

Verify that the entries in the NET.CFG file are correct.

The PCNTNW MLID has been successfully removed.

A request was made to unload a PCNTNW MLID. The PCNTNW MLID has been removed from memory.

None.

PCNTNW-DOS-11 The MLID does not support frame< string:>. The PROTOCOL keyword has been ignored.

The NET.CFG files specified the PROTOCOL option for a PCNTNW MLID. The specified frame type is not supported by the PCNTNW MLID.

Check the PROTOCOL line in the NET.CFG file for possible omissions of required dashes and underscores or any misspellings.

PCNTNW-DOS-12 The protocol keyword must have a frame type. Entry ignored.

The PROTOCOL option was specified in the NET.CFG file for a PCNTNW MLID. The entry failed to specify the
associated frame type for the protocol ID addition. An entry in the NET.CFG file for the PROTOCOL option should use the following format:
LINK DRIVER PCNTNW
PROTOCOL IPX 8137 ETHERNET_II

Specify a frame with the PROTOCOL option.

PCNTNW-DOS-13 The MLID could not register Protocol ID< string> for protocol stack< string> for frame type.

The PCNTNW MLID could not register the specified Protocol ID.

Verify the protocol information in the NET.CFG file.

PCNTNW-DOS-14 This version of LSL is not supported.

The PCNTNW MLID cannot run successfully using this version of the LSL.

Update the LSL.COM to a newer version.

PCNTNW-DOS-15 The frame type is already activated for frame< string>. The NET.CFG entry has been ignored.

Two FRAME keywords under the same main section heading specified the same frame type. A specified frame type can be specified only once per driver.

Remove the duplicate FRAME keyword entry.

PCNTNW-DOS-16 The node address was incorrectly specified in NET.CFG.

You used the NODE ADDRESS option in the NET.CFG file to override the node address on the network board. The
number specified was not a valid Ethernet address. An Ethernet address is six bytes in length. This error occurs if Bit 0 of the first address byte is a 1. This bit must always be 0. For example, if the first byte has the following address, an invalid Ethernet address is generated.

FIRST BYTE
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 1

This byte will produce node addresses in the 0100 0000 0000 to 01FF FFFF FFFF range (in hexadecimal), all of which will be invalid.

Specify a valid node address in the NET.CFG file.

PCNTNW-DOS-17 An invalid keyword was specified in NET.CFG on line xx.

The keyword specified in the NET.CFG file is incorrect.

Check the keyword in question. Make sure that the keyword is correctly spelled.

PCNTNW-DOS-18 The frame type specified in the NET.CFG file is not supported.

The NET.CFG file specified the PROTOCOL option for a PCNTNW MLID. The specified frame type is not supported by the PCNTNW MLID.

Check the PROTOCOL line in the NET.CFG file for possible omissions of required dashes and underscores, or any
misspellings. Check the PCNTNW MLID documentation for supported frame types.

PCNTNW-DOS-19 An invalid Ethernet node address is specified in NET.CFG. The MLID modified the incorrect address bits.

The NET.CFG file has an invalid node address. The PCNTNW MLID modified and corrected the address.

Verify the node address entries in the NET.CFG file.

PCNTNW-DOS-50 The board cannot be found.

The Ethernet controller is either not configured correctly or is disabled.

Perform the following steps:
1. Verify that the Ethernet jumper on the system board is set to the default, enabled position.
2. Check the settings for the Ethernet controller (for example, the I/O and interrupt request settings) against the settings in the
NET.CFG. See "PCI Bus Control" for information on setting the interrupt requests.
3. If the problem persists, go to "'General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTNW-DOS-54 The board did not respond to the initialization command.

The Ethernet controller initialization failed.

Perform the following steps:
1. Verify that the Ethernet jumper on the system board is set to the default, enabled position. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTNW-DOS-58 The board did not respond to the initialization command.

The IRQ setting might be incorrect with the hardware setting, or the EEPROM might be corrupted.

Verify that the IRQ settings in the NET.CFG file match the configuration settings in the Configuration/Setup utility programs. See "PCI Bus Control" for information on setting the interrupt requests. Verify that the EEPROM on the system board is programmed correctly.

PCNTNW-DOS-61 PCI device IRQ number mismatch.

The IRQ number specified in the NET.CFG file does not match with the IRQ number assigned in the Configuration/Setup utility programs.

Remove the IRQ number in the NET.CFG file.

PCNTNW-DOS-64 The device was not found.

The driver cannot find any PCnet device in the server.

Verify that the Ethernet enable jumper is set to the default (enable) position. Go to "Ethernet Diagnostics" to run the diagnostic utility.

PCNTNW-DOS-65 Device not found at IOADDRESS.

The device was not found at the IO address specified in the NET.CFG file. The driver cannot find an Ethernet controller in the server.

Verify that the IO address in the NET.CFG file matches with the with the board. Otherwise, remove the PORT keyword from the NET.CFG file.

PCNTNW-DOS-67 PCI scan specified, device not found.

The driver cannot locate the Ethernet controller on the PCI bus.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Use the BUSTYPE keyword to specify a value of PCI 1.
3. If the problem persists, go to "Ethernet Diagnostics" to run the Ethernet diagnostics.

PCNTNW-DOS-75 Unsupported bus ID specified.

The bus ID number specified in the NET.CFG file is not supported by Novell.

Correct the bus ID number in the NET.CFG file.

PCNTNW-DOS-76 Wrong bus ID specified.

The bus ID number specified in the NET.CFG file is different from the bus type found in the server.

Correct the bus ID number in the NET.CFG.

PCNTNW-DOS-80 The DMA parameter is not necessary for PCI device.

The board does not require a DMA setting.

Edit the NET.CFG file to delete the DMA parameter.

Novell NetWare OS/2 ODI Driver Messages:
This section contains the error messages for the NetWare OS/2 ODI driver. The explanation and recommended action is included with each message.

Error Message

Explanation

Action

PCNTNW-OS2-1 The LSL is not loaded.

The Link Support Layer module (LSL.SYS) is not loaded.

Load LSL.SYS before loading the driver.

PCNTNW-OS2-21 Could not add the MLID Protocol ID.

The PCNTNW MLID could not register the specified Protocol ID.

Edit the NET.CFG file and correct the protocol information.

PCNTNW-OS2-22 Could not allocate memory. The virtual board did not load.

The driver could not allocate memory for the virtual adapter.

Check the system configuration.

PCNTNW-OS2-54 The board did not respond to the initialization command.

The board initialization failed.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "'General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTNW-OS2-56 This interrupt is already used and cannot be shared.

The interrupt is already used by another device and cannot be shared.

Assign a different IRQ in the Configuration/Setup utility programs. See "PCI Bus Control" for information on setting the interrupt requests.

PCNTNW-OS2-58 The board did not respond to the initialization command.

The IRQ setting might be incorrect with the hardware setting, or the EEPROM might be corrupted.

Verify that the IRQ settings in the NET.CFG file match the configuration settings in the Configuration/Setup utility programs. See "PCI Bus Control" for information on setting the interrupt requests. Verify that the EEPROM on the system board is programmed correctly.

PCNTNW-OS2-61 PCI device IRQ number mismatch.

The IRQ number specified in the NET.CFG file does not match with the IRQ number assigned in the Configuration/Setup utility programs. The IRQ numbers might be assigned automatically, or you might have manually assigned the IRQ number.

Remove the IRQ number in the NET.CFG file. Or, see "'PCI Bus Control" for information on setting the interrupt requests.

PCNTNW-OS2-64 The device was not found.

The driver cannot find the Ethernet controller in the server.

Verify that the Ethernet enable jumper is set to the default (enable) position. Go to "General Checkout/Diagnostics
QAPlus/PRO" to run the diagnostic utility.

PCNTNW-OS2-65 Device not found at IOADDRESS.

The Ethernet controller cannot be found at the IO address specified in the NET.CFG file.

Verify that the IO address in NET.CFG matches with the board. Otherwise, remove the PORT keyword from the NET.CFG file.

PCNTNW-OS2-67 PCI scan specified, device not found.

The driver cannot locate the Ethernet controller on the PCI bus.

Perform the following steps:
1. Verify that the Ethernet jumper on the system board is set to the default, enable position.
2. Edit the NET.CFG file to change the BUSTYPE keyword to PCI1.
3. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTNW-OS2-73 Unable to allocate memory.

The driver could not allocate memory for the virtual board.

Check the system configuration.

PCNTNW-OS2-80 The DMA parameter is not necessary to PCI device.

The Ethernet controller does not require a DMA setting. This parameter is not a valid driver parameter.

Edit the NET.CFG file to delete the DMA parameter.

NDIS 2.01 Driver Messages:
This section contains the error messages for the NDIS 2.01 drivers. The explanation and recommended action are included with each message.

Error Message

Explanation

Action

PCNTND-DOS-1 Unable to open the Protocol Manager.

The NDIS stack is not configured properly.

Check and correct the configuration.

PCNTND-DOS-6 Out of memory while allocating buffers.

The driver could not allocate the requested buffers.

Check the system configuration. Edit the PROTOCOL.INI file to reduce the number of Txbuffers and Rxbuffers specified for the driver.

PCNTND-DOS-7 Protocol Manager device error.

The NDIS stack is not configured properly.

Check and correct the configuration.

PCNTND-DOS-8 Bad status for Protocol Manager.

The NDIS stack is not configured correctly.

Check and correct the configuration.

PCNTND-DOS-9 Cannot find PROTOCOL.INI entry.

The NDIS stack is not configured properly in the PROTOCOL.INI file.

Check and correct the configuration.

PCNTND-DOS-10 The Protocol Manager ioctl failed.

The NDIS stack is not configured properly in the PROTOCOL.INI file.

Check and correct the configuration.

PCNTND-DOS-11 Protocol Manager registration failed.

The NDIS stack is not configured properly.

Check and correct the configuration.

PCNTND-DOS-15 Device not found.

The driver cannot find an Ethernet controller in the server.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
3. Replace the system board.

PCNTND-DOS-16 PCI scan specified, device not found.

The driver cannot locate the Ethernet controller on the PCI bus.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
3. Replace the system board.

PCNTND-DOS-21 Board failed checksum test. Please run configuration utility.

The driver cannot find an Ethernet controller.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTND-DOS-23 WARNING: PCNET IRQ found=

The IRQ setting in PROTOCOL.INI does not match the hardware IRQ setting.

Remove the IRQ setting from PROTOCOL.INI (or match the IRQ setting in PROTOCOL.INI with the configuration settings in the Configuration/Setup utility programs. See "PCI Bus Control" for information on setting the interrupt requests.)

PCNTNW-DOS-24 WARNING: PCNET IRQ doesn't match protocol.ini.

The IRQ setting in PROTOCOL.INI does not match the hardware IRQ setting.

Remove the IRQ setting from PROTOCOL.INI or match the IRQ setting in PROTOCOL.INI with the hardware jumper setting.

PCNTNW-DOS-25 PCI scan specified, PCI bus not found!

The driver cannot locate the Ethernet controller on the PCI bus.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTNW-DOS-29 WARNING:
DMA number is not necessary for PCI device.

The Ethernet controller does not require a DMA setting.

Remove the DMA setting in PROTOCOL.INI.

PCNTNW-DOS-32 IRQ number is already in use by another PCNET device.

The specified IRQ number is already in use by another Ethernet controller or device.

Modify the IRQ setting in the PROTOCOL.INI file, or modify the IRQ settings in the Configuration/Setup utility programs.
See "PCI Bus Control" for information on setting the interrupt requests in the Configuration/Setup utility programs.

PCNTNW-DOS-33 PCNET device with specified IOBASE is already in use.

The specified IO address number is already in use by another Ethernet controller or device.

Modify the IO address setting on the hardware, or modify the IO address setting in the PROTOCOL.INI file.

NDIS 3.0 Driver Messages:
Windows NT error messages are logged into a log file. You can view the file with the Event Viewer. Error messages appear with the "PCNTN3" prefix followed by by a "Missing Configuration Parameter" message and several hex numbers. The hex numbers must be converted to decimal values so that they correspond to the error numbers used in this manual.

Error Message

Explanation

Action

PCNTN3-9 IO base address is already in use by another PCNET device.

The specified IO address number is already in use by another device.

Modify the IO address setting on the hardware or modify the IO Address setting in the setup dialog box.

PCNTN3-13 IRQ and/or DMA number is already in use by another device.

The specified IRQ is specified by another device.

Modify the IRQ setting in the setup dialog box.

PCNTN3-18 PCI scan specified, device not found.

The driver cannot locate the Ethernet controller on the PCI bus.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default Enable position.
2. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTN3-19 LanceOpenAdapter failed.

The configuration is set up incorrectly.

Rerun the setup program.

PCNTN3-20 Device at specified IO base address not found.

The Ethernet controller cannot be found at the specified IO address.

Verify that the IO address matches with the board. Otherwise, remove the IO Address specification from the setup.

PCNTN3-21 Device not found.

The driver cannot find any PCnet device.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default Enable position.
2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

Packet Driver Messages:
This section contains the error messages for the packet driver. The explanation and recommended action are included with each message.

PCNTPK-DOS-1 The command syntax is PCNTPK [ -n]
[-d] [-w]
< INT=packet_int_no> [IRQ=int_no] [IOADDR=io_addr] [DMA=dma_no] [BUSTYPE=bus]
[DMAROTATE] [TP] [LED0=xx] [BUSTYPE=bus] [LED0=xx]
[LED2=xx]
[LED3=xx]

The driver command was not entered correctly.

If you entered the command from the command line, enter the command with the correct syntax. If the command is in the AUTOEXEC.NET file, edit the file to correct the syntax. The only parameters that should be included are PCNTPK and BUSTYPE=PCI1.

PCNTPK-DOS-2 Unable to reset the PCnet device.

The software could not reset the Ethernet controller.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTPK-DOS-3 Unable to initialize the PCnet device.

The software could not initialize the Ethernet controller.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Check the interrupt settings in the Configuration/Setup utility programs. For more information, go to "'PCI Bus Control".
3. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTPK-DOS-5 There is already a packet driver at xxxx.

The driver is already loaded at this memory location. It cannot be loaded a second time at the same location.

Do not reload the driver. If you want to load the driver at a different memory location, specify another software interrupt
address on the INT parameter.

PCNTPK-DOS-6< IRQ=int_no> should be between 0 and 15 inclusive.

The specified IRQ is out of range for the Ethernet controller.

Use valid IRQ values.

PCNTPK-DOS-7 Packet driver failed to initialize the board.

The board initialization failed.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTPK-DOS-8< INT= packet_int_no> should be in the range 0x60 to 0x80.

The specified software interrupt number is out of the allowable range.

Specify a valid value for the INT parameter.

PCNTPK-DOS-12 PCI device IRQ number mismatch.

The specified IRQ number does not match with the IRQ number assigned by the PCI BIOS.

Remove the IRQ setting.

PCNTPK-15 The device was not found.

The driver cannot find an Ethernet controller.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

PCNTPK-DOS-18 PCI scan specified, device not found.

The driver cannot locate the Ethernet controller on the PCI bus.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

Packet driver is at segment xxxx.

The memory address where the packet driver is loaded is xxxx.

None.

Packet interrupt number xxxx.

The interrupt number used by the packet driver is xxxx.

None.

My Ethernet address is xxxxxxxxxxxx.

The Ethernet address of this station is xxxxxxxxxxxx.

None.

My ARCnet address is xxxx.

The ARCnet address of this station is xxxx.

None.

UNIX Messages:
This section contains the error messages for the following UNIX drivers.
- SCO UNIX LLI
- UnixWare DPLI
- SunSoft Solaris

pnt0-2 PCI search specified, PCI device not found!

The driver cannot locate the Ethernet controller on the PCI bus.

Perform the following steps:
1. Run netconfig to search for another Ethernet controller.
2. Verify that the Ethernet enable jumper is set to the default (enable) position.
3. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

pnt0-6 Cannot allocate memory for the adapter during an interrupt. Please check the Streams parameters.

The system is out of Streams memory blocks.

Perform the following steps:
1. Use the CRASH utility to increase the number of Streams memory blocks for the failing size.
2. Modify the IRQ settings in the Configuration/Setup utility programs, or run netconfig to match the hardware settings.

pnt0-6 Cannot allocate memory for the adapter during an interrupt! Please check the Streams parameters.

On a SunSoft Solaris system, this message indicates that the system is out of Streams memory blocks.

Use the CRASH utility to increase the number of Streams memory blocks for the failing size.

pnt0-7 Cannot allocate memory for the adapter during reset! Please check the Streams parameters.

The system is out of Streams memory blocks.

Use the CRASH utility to increase the number of Streams memory blocks for the failing size.

pnt0-11 device not found!

The driver cannot find an Ethernet controller.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "'General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

pnt0-12 device failed checksum test!

The driver cannot find an Ethernet controller.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

pnt0-13 add_intr_handler failed! Interrupts already enabled.

The IRQ specified or found conflicts with other devices in the system.

Perform the following steps:
1. Modify the hardware settings.
2. Run netconfig to match the hardware settings.

pnt0-14 Cannot locate hardware.

The SunSoft Solaris driver cannot find any Ethernet controller.

Perform the following steps:
1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

pnt0-15 No more devices to open.

The SunSoft Solaris driver cannot find any more Ethernet controllers.

Perform the following steps:
1. Verify that additional IBM PCI Ethernet adapters are present or replace the Ethernet adapter that fails to respond.
2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

pnt0-17 Device fault... Reset initiated!

The SunSoft Solaris driver has been reset due to device fault.

Perform the following steps:
1. Verify that additional IBM PCI Ethernet adapters are present or replace the PCnet card that fails to respond.
2. Go to "'General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.

pnt0-19 IRQ found for PCnet hardware does not match space.c!

This is a warning message referring to the IRQ found in the system.

Ignore this message if you are sure that this is what you want to do. Otherwise, run netconfig to match the hardware settings.

pnt0-19 IRQ found for PCnet hardware does not match pnt.conf!

This is a warning message referring to the IRQ that the SunSoft Solaris driver found in the system.

Ignore this message if you are sure that this is what you want to do. Otherwise, run netconfig to match the hardware settings.

pnt0-20 add_intr_handler failed! Unknown interrupt type.

The IRQ specified or found conflicts with other devices in the system.

Perform the following steps:
1. Modify the hardware settings.
2. Run netconfig to search for another Ethernet controller.

pnt0-21 add_intr_handler failed! Out of range interrupt number.

The IRQ specified or found conflicts with other devices in the system.

Perform the following steps:
1. Modify the hardware settings.
2. Run netconfig to search for another Ethernet controller.

pnt0-22 add_intr_handler failed! Out of range IPL.

The IRQ specified or found conflicts with other devices in the system.

Perform the following steps:
1. Modify the hardware settings.
2. Run netconfig to search for another Ethernet controller.

pnt0-23 add_intr_handler failed! Vector already occupied.

The IRQ specified or found conflicts with other devices in the system.

Perform the following steps:
1. Modify the hardware settings.
2. Run netconfig to search for another Ethernet controller.

pnt0-24 add_intr_handler failed! Vector already shared at different IPL.

The IRQ specified or found conflicts with other devices in the system.

Perform the following steps:
1. Modify the hardware settings.
2. Run netconfig to search for another Ethernet controller.

pnt0-26 The DMA number is not necessary for PCI device.

The IBM PCI Ethernet adapter does not require a DMA setting.

Edit the SPACE.C file to delete the DMA parameter.

pnt0-29 The IRQ number is already in use by another

The IBM PCI Ethernet adapter

The specified IO address is already in use by

pnt0-31 IO address is not necessary for the PCI device.

The I/O address specified is not required.

Remove the assigned IO address specified for the Ethernet controller.

Search Keywords

Hint Category

Networking, Hardware Maintenance Information

Date Created

06-03-97

Last Updated

19-11-98

Revision Date

10-11-99

Brand

IBM PC Server

Product Family

PC Server 325, PC Server 330

Machine Type

8639, 8640

Model

EJ0; ES0; ESV; RD0; RF0; RS0; XD0; XDV; XF0; XFV; XJ0; XS0; XSV; YS0; EM0; ES2; ESS; XM2; XS0; YS0; YSS

TypeModel

Retain Tip (if applicable)

Reverse Doclinks
and Admin Purposes

Error Message	Explanation	Action
PCNTNW-NW-026 The MSM is unable to parse a required custom keyword.	The user entered an incorrect parameter keyword.	Enter the keyword correctly. Then, reload the driver.
PCNTNW-NW-054 The board did not respond to the initialization command.	The board did not respond when the driver tried to initialize it.	Perform the following steps: 1. Verify that the Ethernet jumper on the system board is set to the default, enabled position. 2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
PCNTNW-NW-58 The board did not respond to the initialization command.	The IRQ setting might be incorrect with the hardware setting, or the EEPROM might be corrupted.	Perform the following steps: 1. Verify that the IRQ settings in the NET.CFG file match the configuration settings in the Configuration/Setup utility programs. See "PCI Bus Control" for information on setting the interrupt requests. 2. Verify that the EEPROM on the system board is programmed correctly. Verify that the EEPROM on the system board is programmed correctly.
PCNTNW-NW-66 The cable might be disconnected from the board.	The cable might be disconnected from the server's Ethernet port.	Verify that a cable is connected to the AUI port or the 10BASE-T port.
PCNTNW-NW-071 The matching virtual adapter could not be found.	You tried to load another instance of the driver with a different I/O address. This new board could not be found.	If you installed an IBM Ethernet adapter, make sure the adapter is seated properly. Also, check the I/O settings of the board with the settings supplied to the drive.
PCNTNW-NW-072 A resource tag is unavailable.	The driver tried to allocate some resources that were not available.	Add or free some memory in the server. Then, restart the server.
PCNTNW-NW-073 Unable to allocate memory.	The driver failed to allocate the memory needed for normal operation.	Add more memory, or free some memory resources in the server. Then, restart the server.
PCNTNW-NW-074 The hardware interrupt cannot be set.	An attempt was made to initialize a given hardware interrupt. The attempt was not successful.	Perform the following steps: 1. Verify that the Ethernet jumper on the system board is set to the default, enabled position. 2. Make sure that the interrupt request numbers are set correctly, and that no other devices are using the interrupt. See "PCI Bus Control" on for more information.
PCNTNW-NW-075 The MLID cannot be registered with the LSL.	An error occurred while the driver was trying to register with Link Support Layer.	Check the version of Netware Operating System. Make sure that this driver is correct for the version of Netware that you are using. Restart the server.
PCNTNW-NW-076 The polling procedure cannot be added.	An error occurred while the driver was adding a polling procedure to the Netware Operating System polling routines.	Check the version of Netware Operating System. Make sure that this driver is correct for the version of Netware that you are using. Restart the server.
PCNTNW-NW-077 The event notification cannot be registered.	The driver failed to register its event notification routines with the Netware Operating System.	Check the version of Netware Operating System. Make sure that this driver is correct for the version of Netware that you are using. Restart the server.
PCNTNW-NW-078 The firmware file cannot be read.	The driver to read a firmware file. The read process failed.	Make sure that the support files that accompany the driver are present. Restart the server.
PCNTNW-NW-079 The MLID did not initialize MSMTx Free Count.	The MSMTx Free Count is not initialized properly.	Restart the server. If the error recurs, replace the system board.
PCNTNW-NW-084 Unable to allocate memory below the 16 megabyte boundary.	A request was made to allocate memory below 16 megabytes. The request did not complete successfully.	Free some memory below 16 megabytes, or add more memory below the 16 megabyte boundary.
PCNTNW-NW-086 The driver parameter block is too small.	The driver parameter block is too small.	Restart the server. If the error recurs, replace the system board.
PCNTNW-NW-087 The media parameter block is too small.	The driver media parameter block is too small.	Restart the server. If the error recurs, replace the system board.
PCNTNW-NW-091 The hardware configuration conflicts.	You tried to load a new frame type for the existing adapter. The hardware assumptions made in doing so are incorrect.	Make sure that the hardware configuration matches the software settings. See "PCI Bus Control" for information on viewing and changing interrupt requests.
PCNTNW-NW-092 Cannot schedule AES without an HSM routine.	The Netware Operating System needs a Hardware Support Module routine before it schedules an AES event.	Restart the server. If the error is still present, replace the system board.
PCNTNW-NW-093 Cannot schedule interrupt time call back without an HSM routine.	The driver needs a Hardware Support Module routine before it can schedule an interrupt time call back.	Restart the server. If the error recurs, replace the system board.
PCNTNW-NW-094 Cannot set hardware interrupt without an HSM routine.	The driver needs a hardware interrupt call back routine routine before it sets the interrupt.	Restart the server. If the error recurs, replace the system board.
PCNTNW-NW-095 Cannot add polling without an HSM routine.	The driver needs an HSM polling routine before it can start the polling process.	Restart the server. If the error recurs, replace the system board.
PCNTNW-NW-126 The group bit in the node address override was cleared.	The IEEE address has a group bit indicating that an address belongs to a group of stations. This bit is used only as a destination address; it cannot be used as a source address. You tried to enter a source address with this bit set. The driver cleared the group bit of the source address.	None.
PCNTNW-NW-127 The local bit in the node address override was set.	The local bit in the IEEE address format indicates that the addresses are being managed locally. If you use the node address override capabilities of this driver to enter a new address, the local bit should be set. You entered an address without the local bit set. The driver has set the local bit.	None.
PCNTNW-NW-164 The device was not found.	The driver cannot find an Ethernet controller in the server.	Perform the following steps: 1. Verify that the Ethernet enable jumper is set to the default (enable) position. 2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
PCNTNW-NW-164 Device not found at IOADDRESS.	The Ethernet controller cannot be found at the IO address specified in the NET.CFG file.	Verify that the IO Address in the NET.CFG file matches with the board. Otherwise, remove the PORT keyword from the NET.CFG file.
PCNTNW-NW-167 PCI scan specified, device not found.	The driver cannot locate the Ethernet controller on the PCI bus.	Perform the following steps: 1. Verify that the Ethernet jumper on the system board is set to the default, enable position. 2. Edit the NET.CFG file to change the BUSTYPE keyword to PCI1. 3. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
PCNTNW-NW-180 The DMA parameter is not necessary for PCI device.	The Ethernet controller does not require a DMA setting.	Delete the DMA parameter from the NET.CFG file.

PCNTPK-DOS-1 The command syntax is PCNTPK [ -n] [-d] [-w] < INT=packet_int_no> [IRQ=int_no] [IOADDR=io_addr] [DMA=dma_no] [BUSTYPE=bus] [DMAROTATE] [TP] [LED0=xx] [BUSTYPE=bus] [LED0=xx] [LED2=xx] [LED3=xx]	The driver command was not entered correctly.	If you entered the command from the command line, enter the command with the correct syntax. If the command is in the AUTOEXEC.NET file, edit the file to correct the syntax. The only parameters that should be included are PCNTPK and BUSTYPE=PCI1.
PCNTPK-DOS-2 Unable to reset the PCnet device.	The software could not reset the Ethernet controller.	Perform the following steps: 1. Verify that the Ethernet enable jumper is set to the default (enable) position. 2. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
PCNTPK-DOS-3 Unable to initialize the PCnet device.	The software could not initialize the Ethernet controller.	Perform the following steps: 1. Verify that the Ethernet enable jumper is set to the default (enable) position. 2. Check the interrupt settings in the Configuration/Setup utility programs. For more information, go to "'PCI Bus Control". 3. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
PCNTPK-DOS-5 There is already a packet driver at xxxx.	The driver is already loaded at this memory location. It cannot be loaded a second time at the same location.	Do not reload the driver. If you want to load the driver at a different memory location, specify another software interrupt address on the INT parameter.
PCNTPK-DOS-6< IRQ=int_no> should be between 0 and 15 inclusive.	The specified IRQ is out of range for the Ethernet controller.	Use valid IRQ values.
PCNTPK-DOS-7 Packet driver failed to initialize the board.	The board initialization failed.	Perform the following steps: 1. Verify that the Ethernet enable jumper is set to the default (enable) position. 2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
PCNTPK-DOS-8< INT= packet_int_no> should be in the range 0x60 to 0x80.	The specified software interrupt number is out of the allowable range.	Specify a valid value for the INT parameter.
PCNTPK-DOS-12 PCI device IRQ number mismatch.	The specified IRQ number does not match with the IRQ number assigned by the PCI BIOS.	Remove the IRQ setting.
PCNTPK-15 The device was not found.	The driver cannot find an Ethernet controller.	Perform the following steps: 1. Verify that the Ethernet enable jumper is set to the default (enable) position. 2. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
PCNTPK-DOS-18 PCI scan specified, device not found.	The driver cannot locate the Ethernet controller on the PCI bus.	Perform the following steps: 1. Verify that the Ethernet enable jumper is set to the default (enable) position. 2. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
Packet driver is at segment xxxx.	The memory address where the packet driver is loaded is xxxx.	None.
Packet interrupt number xxxx.	The interrupt number used by the packet driver is xxxx.	None.
My Ethernet address is xxxxxxxxxxxx.	The Ethernet address of this station is xxxxxxxxxxxx.	None.
My ARCnet address is xxxx.	The ARCnet address of this station is xxxx.	None.

pnt0-2 PCI search specified, PCI device not found!	The driver cannot locate the Ethernet controller on the PCI bus.	Perform the following steps: 1. Run netconfig to search for another Ethernet controller. 2. Verify that the Ethernet enable jumper is set to the default (enable) position. 3. If the problem persists, go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
pnt0-6 Cannot allocate memory for the adapter during an interrupt. Please check the Streams parameters.	The system is out of Streams memory blocks.	Perform the following steps: 1. Use the CRASH utility to increase the number of Streams memory blocks for the failing size. 2. Modify the IRQ settings in the Configuration/Setup utility programs, or run netconfig to match the hardware settings.
pnt0-6 Cannot allocate memory for the adapter during an interrupt! Please check the Streams parameters.	On a SunSoft Solaris system, this message indicates that the system is out of Streams memory blocks.	Use the CRASH utility to increase the number of Streams memory blocks for the failing size.
pnt0-7 Cannot allocate memory for the adapter during reset! Please check the Streams parameters.	The system is out of Streams memory blocks.	Use the CRASH utility to increase the number of Streams memory blocks for the failing size.
pnt0-11 device not found!	The driver cannot find an Ethernet controller.	Perform the following steps: 1. Verify that the Ethernet enable jumper is set to the default (enable) position. 2. Go to "'General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
pnt0-12 device failed checksum test!	The driver cannot find an Ethernet controller.	Perform the following steps: 1. Verify that the Ethernet enable jumper is set to the default (enable) position. 2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
pnt0-13 add_intr_handler failed! Interrupts already enabled.	The IRQ specified or found conflicts with other devices in the system.	Perform the following steps: 1. Modify the hardware settings. 2. Run netconfig to match the hardware settings.
pnt0-14 Cannot locate hardware.	The SunSoft Solaris driver cannot find any Ethernet controller.	Perform the following steps: 1. Verify that the Ethernet enable jumper is set to the default (enable) position. 2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
pnt0-15 No more devices to open.	The SunSoft Solaris driver cannot find any more Ethernet controllers.	Perform the following steps: 1. Verify that additional IBM PCI Ethernet adapters are present or replace the Ethernet adapter that fails to respond. 2. Go to "General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
pnt0-17 Device fault... Reset initiated!	The SunSoft Solaris driver has been reset due to device fault.	Perform the following steps: 1. Verify that additional IBM PCI Ethernet adapters are present or replace the PCnet card that fails to respond. 2. Go to "'General Checkout/Diagnostics QAPlus/PRO" to run the diagnostic utility.
pnt0-19 IRQ found for PCnet hardware does not match space.c!	This is a warning message referring to the IRQ found in the system.	Ignore this message if you are sure that this is what you want to do. Otherwise, run netconfig to match the hardware settings.
pnt0-19 IRQ found for PCnet hardware does not match pnt.conf!	This is a warning message referring to the IRQ that the SunSoft Solaris driver found in the system.	Ignore this message if you are sure that this is what you want to do. Otherwise, run netconfig to match the hardware settings.
pnt0-20 add_intr_handler failed! Unknown interrupt type.	The IRQ specified or found conflicts with other devices in the system.	Perform the following steps: 1. Modify the hardware settings. 2. Run netconfig to search for another Ethernet controller.
pnt0-21 add_intr_handler failed! Out of range interrupt number.	The IRQ specified or found conflicts with other devices in the system.	Perform the following steps: 1. Modify the hardware settings. 2. Run netconfig to search for another Ethernet controller.
pnt0-22 add_intr_handler failed! Out of range IPL.	The IRQ specified or found conflicts with other devices in the system.	Perform the following steps: 1. Modify the hardware settings. 2. Run netconfig to search for another Ethernet controller.
pnt0-23 add_intr_handler failed! Vector already occupied.	The IRQ specified or found conflicts with other devices in the system.	Perform the following steps: 1. Modify the hardware settings. 2. Run netconfig to search for another Ethernet controller.
pnt0-24 add_intr_handler failed! Vector already shared at different IPL.	The IRQ specified or found conflicts with other devices in the system.	Perform the following steps: 1. Modify the hardware settings. 2. Run netconfig to search for another Ethernet controller.
pnt0-26 The DMA number is not necessary for PCI device.	The IBM PCI Ethernet adapter does not require a DMA setting.	Edit the SPACE.C file to delete the DMA parameter.
pnt0-29 The IRQ number is already in use by another	The IBM PCI Ethernet adapter	The specified IO address is already in use by
pnt0-31 IO address is not necessary for the PCI device.	The I/O address specified is not required.	Remove the assigned IO address specified for the Ethernet controller.

	Search Keywords
	Hint Category	Networking, Hardware Maintenance Information
	Date Created	06-03-97
	Last Updated	19-11-98
	Revision Date	10-11-99
	Brand	IBM PC Server
	Product Family	PC Server 325, PC Server 330
	Machine Type	8639, 8640
	Model	EJ0; ES0; ESV; RD0; RF0; RS0; XD0; XDV; XF0; XFV; XJ0; XS0; XSV; YS0; EM0; ES2; ESS; XM2; XS0; YS0; YSS
	TypeModel
	Retain Tip (if applicable)
	Reverse Doclinks and Admin Purposes