IBM eServer 135 xSeries User Reference Manual page 109

Table 17. TurboLinux driver messages for the Ethernet controller
Error code (hex)
0x13 Explanation: Did not find any Ethernet controllers that matched the required subven/subdev.
Action: Using the Configuration/Setup Utility program, make sure that Ethernet is enabled. See
"Using the Configuration/Setup Utility program" on page 12.
0x16 Explanation: Single adapter found but multiple instances tried to load.
Action: Using the Configuration/Setup Utility program, make sure that Ethernet is enabled, and
that the slot containing the IBM Netfinity 10/100 Ethernet Adapter or the IBM 10/100 EtherJet PCI
adapter is enabled. See "Using the Configuration/Setup Utility program" on page 12.
0x17 Explanation: Slot parameter not specified in the registry.
Action: Remove the adapter device driver and reinstall it. If the problem persists, call for service.
All other 4- Action: Call for service.
character
hexadecimal
codes
Table 18. NetWare driver messages for the Ethernet controller
Message
Couldn't allocate resources
AFT group for primary adapter in slot
nnn already exists.
Error locating DCT addresses in
internal table. Make sure that you
have loaded LAN drivers after
loading AFT.NLM.
Insufficient number of arguments
specified.
Duplicate slot numbers detected.
'Xxx' is not supported for AFT team.
Description
Description
Explanation: An unknown error has occurred when trying to allocate needed
resources for the AFT Module.
Action:
• Check the server configuration. If the problem persists, contact your
network supplier.
• Verify that the Ethernet controller is enabled. If the Ethernet controller is
enabled, run the diagnostic programs.
Explanation: An attempt was made to rebind an adapter already in an AFT
group.
Action: Check the AFT slot numbers for existing AFT teams. If the problem
persists, contact your network supplier.
Explanation: The bind command was entered before loading the device
driver. The device driver must be loaded after AFT.NLM but before any bind
command can be issued.
Action: Load the device driver for the supported adapter and try loading the
AFT module again. If the problem persists, contact your network supplier.
Explanation: The appropriate or expected number of parameters was not
entered in a command.
Action: Check the parameters required for the given command. If the problem
persists, contact your network supplier.
Explanation: An attempt has been made to bind the same slot number more
than once.
Action: Check the slot numbers entered during the bind. Adapter slot
numbers must be valid and unique. If the problem persists, contact your
network supplier.
Explanation: A bind command has been issued for adapters that are not
supported by AFT.NLM.
Action: Make sure that you attempt to bind only adapters that are supported
by AFT.NLM.
Chapter 6. Solving Problems
97