|
7.571 bytes |
Service Hints & Tips |
Document ID: PMYS-3VPN2F |
IBM PS/2 - Diagnosing Direct Driver Software system failures
Applicable to: World-Wide
Symptom:
System failures may be encountered on PS/2 systems which cannot be resolved by hardware replacement. These problems may be difficult to diagnose and/or intermittent. The diagnostics run error-free, and attempts to isolate the problem by swapping hardware are unsuccesful, yet the problem "appears" to be a hardware failure. If a problem, as described above is being experienced and the operating system is of the "direct driver" variety (bypass the BIOS* interface) such as AIX**, Novell Netware**, SCO Xenix**, SCO Unix**, other Unix based software, and some "windowing" interfaces, the most likely cause is a mis-match between the software and the hardware. Applications which use the Multuprotocol Adapter/A, magnetic tape and some SCSI devices such as CD_ROM require direct software drivers. There is no BIOS interface for these devices in any PS/2 product.
Problem Isolation:
In resolving these problems, the following facts are very useful and in some cases critical:
a) Direct Driver Software is Sensitive to the Hardware
Direct driver software is sensitive to variations in hardware design. The resulting incompatibilities are usually addressed with a revision, or a "patch" to the direct driver software. Make certain the software is current and all known "fixes" or updates are present. PCPROD and other soft ware "tools" sources, such as Novell Netware, should be referenced by the software support personnel for any revisions,fixes,etc provided by the appropriate software vendor.The greatest cause of system problems, when direct driver software is involved, is the failure to obtain the latest revisions or "fixes" from the software vendor.
b) Software Installation is important
It is very important to follow the vendor's installation procedures. The software should be installed "out of the box" and not migrated from another system, unless migration is EXPRESSLY supported by the software, particularly from a different model in the product line.
Note: Migrating adapters from slower systems to faster systems, may cause failures. This is due to device specific, system specific, or time dependent software code which controls these devices.
c) Not all Adapters are Software Compatible
The hardware adapters for some operating systems must be certified by the software vendor to be compatible with that software. This certification (approval) is specific for the system, adapter (version, E.C. level) and software version. The software vendor should be contacted to confirm that the complete system/adapter configuration is supported by their software level. This compatibility approval is very important for, but not limited to, LAN adapters. This is particularly true in RIPL (Remote Initial Program Load) applications.
d) Software may fail after Hardware Change
After initial installation, any changes in the hardware configuration (addition or changes of adapters, features, etc.) may cause system failures and require reinstallation of the operating system and/or software patches or updates. Specific hardware configuration changes (such as memory address, interrupt level, Programmable option select, etc.) may result in a system failure if the software has unique operating requirements. In Summary: Almost all of the problems experienced on systems using direct driver software fall into one of the above categories. Experience has demonstrated that if the diagnostics run error-free, the hardware is probably within specifications and is not defective.
LAN support assistance is available from SOFTWARE/LAN support in Austin. They can be reached at 1-800-992-4777.
Note:
This is available in the US only. Additional level 2 LAN support is available, if required, for customers using Novell Netware purchased from IBM ("BLUE BOX"), through the IBM Defect Support Center in Austin.
Note:
Again this is only available in the US. NON-IBM (RED BOX) Novell Netware customers should contact their normal software support. For further information on the software/hardware relationship, the PS/2 Installation Planning and Beyond manual, form # G41G-2927-00, chapter 8, "PS/2 System Software," page 8-3, "BIOS Interface," should be referenced.
* BIOS (Basic Input-Output System):
BIOS is a layer of software which provides a consistent interface between the system hardware and the user application software and operating system. BIOS guarantees compatibility and flexibility of software across the hardware model line, by compensating for minor variations in hardware which may exist from system to system.
* *AIX is a registered trademark of the IBM Corporation.
Netware is a registered trademark of Novell Inc
SCO Xenix is a registered trademark of Santa Cruz Operations.
SCO Unix is a registered trademark of Santa Cruz Operations.
Fix:
None
SAS KEYWORDS:
PSY2 PS2 PS/2 PSY2PROG
PSY2ERR ZENIX WINDOW D/T8560
D/T8570 D/T8565 D/T8580 D/T8590
D/T8595 D/T8555 NOVELLE PSY2TAPE
NOVELLE D/T8590 D/T8595 D/T8555
D/T8573 PSY2TAPE D/T8525 D/T8530
D/T8557 D/T8556 D/T8540 D/T8535
NOVEL OEM PSY2OEM ABIOS
D/T6384 PSVP VALUEPOINT VALUE POINT
D/T9595 D/T9585 D/T9577 D/T9576
DJADRIVER
|
Search Keywords |
| |
|
Hint Category |
Retain | |
|
Date Created |
23-06-95 | |
|
Last Updated |
18-01-99 | |
|
Revision Date |
18-01-2000 | |
|
Brand |
IBM PC, IBM PC Server | |
|
Product Family |
PS/2, Server 85, Server 95 | |
|
Machine Type |
8530, 8535, 8540, 8555, 8556, 8557, 8560, 8565, 8570, 8573, 8580, 8590, 8595, 9557, 9576, 9595, 9585 | |
|
Model |
various | |
|
TypeModel |
| |
|
Retain Tip (if applicable) |
H104541 | |
|
Reverse Doclinks |