Sino Sds2 L Manual
Posted By admin On 15.08.19Connecticut Department of Transportation Bridge Load Rating Manual Revised on March 29, 2018 5 Version 2018.1.0 load rating. Load Rating Report – A PDF file which documents the load rating results, methodology, calculations, program input, and back-up documentation. 3 sds6-sds6 ---3v readout panel and keyboard 3v ---2v keyboard2v panel. « Previous Post Next Post ». Tamil hairy armpit aunties photos Tatli e let me sherbet Td w8920g v2 firmware Teac dv w28e firmware Technics rs eh600 manual Technics sa dv280 user manual Technics sa eh50 manual pdf.
Errata Listing | Intel® Server Board SDS2 |
Server Board SDS2 does not service this interrupt when the BIOS Logo screen | |
is enabled. | |
Implication: | When booting the Intel Server Board SDS2 with an Intel RAID Controller or ICP |
Vortex* RAID controller installed, the system will halt during POST when the | |
Intel Server Board SDS2 BIOS Logo screen is enabled. | |
Workaround: | A workaround for this issue is to press the ESC key when the Intel BIOS logo |
screen appears. Alternately, the Intel BIOS logo screen may be disabled. To | |
disable the Intel BIOS logo screen, access the Intel Server Board SDS2 BIOS | |
Setup (by pressing F2 when the Intel BIOS logo screen appears). In BIOS | |
Setup, change the Advanced à | |
“Enabled”. | |
Status: | Fixed: For the ICP Vortex RAID Controllers, please contact ICP technical |
support. Please refer to Technical Advisory 507 for firmware release schedules | |
and additional details. |
6.Intel® Server Board SDS2
Problem: | The Intel Server Board SDS2 system resource |
issues: | |
1. The BYO Platform Confidence Test Manual on the SDS2 system resource | |
10/2001. The instructions in the Rev. 2.0 manual for creating a bootable | |
Platform Confidence Test floppy diskette are not correct and do not contain | |
enough detail for the user to successfully create a bootable floppy diskette. | |
2. Editing a file with the DOS “Edit” command after booting to the SDS2 | |
system resource | |
Implication: | A bootable Platform Confidence Test floppy diskette cannot be successfully |
created by following the instructions in the SDS2 BYO Platform Confiedence | |
Test Manual Rev. 2.0 on the SDS2 system resource | |
edit a file with the DOS “Edit” command after booting to the SDS2 system | |
resource | |
Workaround: | Users should not use the DOS “Edit” command to edit files after booting to the |
SDS2 System Resource | |
insturctions for the BYO Platform Confidence Test Manual Rev. 2.2 to create a | |
bootable Platform Confidence Test floppy diskette: | |
Installing the Server Board Platform Confidence Test Package on the Intel | |
Server Board SDS2: | |
1. Insert the resource CD into a Windows* based system and let the auto run | |
feature launch the graphical user interface (if auto run does not launch the | |
GUI, launch it manually by double clicking on your CDROM drive). | |
110 | Revision 1.2 |
Order Number: |
Intel® Server Board SDS2 | Errata Listing | ||
2. | On the Utilities page, drop down the menu and choose the Platform | ||
Confidence Test option. | |||
3. | Click on the Create Diskette icon that appears and when prompted, choose | ||
to save the file to a temporary folder on your hard drive. | |||
4. | Locate the file you just saved and run the SDS2PCT.exe program obtained | ||
from the CD. This will extract the files for the Platform Confidence Test onto | |||
the floppy along with a file called MKBOOT.BAT. | |||
5. | Reboot the server to the resource CD and insert the floppy with the Platform | ||
Confidence Test files into the floppy drive. | |||
6. | Exit to DOS by choosing Quit from the menu and then selecting Quit Now. | ||
At the DOS prompt, change to the floppy disk and execute the | |||
MKBOOT.BAT file. This will make your floppy disk bootable and copy over | |||
the appropriate DOS components for creating a RAMDRIVE for the Platform | |||
Confidence Test to extract to. | |||
7. | Reboot your system using the floppy diskette. | ||
8. | You will be asked to agree to a licensing agreement prior to the actual file | ||
expansion occurring. The agreement is the file LEGAL.TXT. | |||
9. | A RAMDRIVE will be created into which the diagnostic tests are copied. | ||
10. | When the copy process is complete, you will be presented with a menu of | ||
five options. These menu options are discussed in greater detail in the | |||
Platform Confidence Test manual Rev. 2.2. | |||
Status: | Fixed. The SDS2 system resource | ||
has corrected these issues. |
7.NIC driver set 5.12 v.2.3.15 for UnixWare* 7.1.1 drops DPC LAN connection
Problem: | When the NIC driver set 5.1.2 v.2.3.15 for UnixWare* 7.1.1 is utilized on the |
Intel® Server Board SDS2, the DPC LAN connection to the SDS2 server is | |
dropped when a power control action is initiated. | |
Implication: | NIC driver set 5.1.2 v.2.3.15 for UnixWare* 7.1.1 should not be used with the |
Intel® Server Board SDS2 if DPC LAN is being used. | |
Workaround: | Intel recommends using the driver version embedded in the UnixWare* 7.1.1 |
operating system | |
Status: | Fixed. Intel recommends using the driver version embedded in the UnixWare* |
7.1.1operating system
8.NIC driver set 5.12 v.5.41.27 for Microsoft* Windows* 2000 prevents a DPC LAN connection when the operating system is loaded
Revision 1.2 | 111 |
Order Number: |
Errata Listing | Intel® Server Board SDS2 |
Problem: | Microsoft* Windows* 2000 NIC driver set 5.1.2 v.5.41.27 prevents the Intel® |
Server Board SDS2 from making a DPC LAN connection when the operating | |
system is loaded. | |
Implication: | NIC driver set 5.1.2 v.5.41.27 for Microsoft* Windows* 2000 should not be used |
with the Intel® Server Board SDS2 if DPC LAN is being used. | |
Workaround: | Intel recommends using NIC driver set 5.0.1 v.5.40.11 or driver set 5.1.3 |
v.5.41.32 in order to avoid this failure. | |
Status: | Fixed. Intel recommends using NIC driver set 5.0.1 v.5.40.11 or driver set 5.1.3 |
v.5.41.32 as the fix for this issue. |
9.Extended RAM Step disable option in BIOS Setup has no effect
Problem: | Setting the Intel® Server Board SDS2 BIOS Setup Advanced à Memory |
Configuration à Extended RAM Step option to “Disabled” has no effect. | |
Implication: | The Intel Server Board SDS2 will still perform the Extended RAM count even |
when this option has been set to “Disabled” in BIOS Setup. | |
Workaround: | None. |
Status: | Fixed. This issue is fixed in SDS2 BIOS Production Release 2.1 (Build 44) and |
later versions. |
10.High resolution video modes do not work correctly
Problem: | Several of the high resolution video modes listed as supported in Table 6 of the | ||
Intel® Server Board SDS2 Technical Product Specification (TPS) Rev. 1.0 are | |||
currently not supported. | |||
Implication: | Selecting unsupported high resolution and high color video modes will cause | ||
the monitor screen to turn gray, or to operate incorrectly. The following table | |||
indicates the SDS2 video modes that are currently not supported: | |||
Mode | Support Comments | ||
640x480 | Supported for all video modes indicated in the SDS2 TPS. | ||
800x600 | Supported for all video modes indicated in the SDS2 TPS. | ||
1024x768 | Supported for all color modes at refresh rates of 72Hz and lower. | ||
Supported for 8 and 16 bpp color modes only at 75Hz refresh rate. | |||
Not supported for refresh rates of 85Hz and higher. | |||
1280x1024 | Supported for 8, 16, and 24 bpp color modes only at refresh rates of | ||
47Hz and lower. | |||
Supported for 8 bpp color mode only at 60Hz refresh rate. | |||
Not supported for refresh rates of 70Hz and higher. | |||
112 | Revision 1.2 | ||
Order Number: |
Intel® Server Board SDS2 | Errata Listing | ||
1600x1200 | Not supported. |
Workaround: | Utilize a video mode that is currently supported by the SDS2 Server Board. |
Status: | Fixed. SDS2 BIOS Production Release 2.4 (Build 47) and later versions have |
added support for additional high resolution video modes. The following video | |
modes are supported by SDS2 BIOS Production Release 2.4 (Build 47) and | |
later versions: | |
640x480: Supported at refresh rates of 120Hz and lower | |
800x600: Supported at refresh rates of 100Hz and lower | |
1024x768: Supported at refresh rates of 80Hz and lower | |
1152x864: Supported at refresh rates of 75Hz and lower | |
1280x1024: Supported at refresh rates of 60Hz and lower | |
1600x1200: Not supported | |
Selecting an unsupported video mode no longer causes the monitor to turn gray | |
or to operate incorrectly. |
11.Lower performance with CAS Latency 2 memory
Problem: | Performance of the Intel® Server Board SDS2 memory subsystem is lower |
than expected when CAS Latency 2 memory is used. The copy bandwidth | |
observed with CAS Latency 2 memory installed is less than the copy bandwidth | |
with CAS Latency 3 memory installed. | |
Implication: | The memory subsystem copy performance of the SDS2 Server Board is lower |
with CAS Latency 2 memory installed than with CAS Latency 3 memory | |
installed. | |
Workaround: | Use of CAS Latency 3 memory is recommended for optimum memory |
subsystem copy performance. | |
Status: | Fixed. This issue is fixed in SDS2 BIOS Production Release 2.4 (Build 47) and |
later versions. When using SDS2 BIOS Production Release 2.4 (Build 47), the | |
copy bandwidth observed with CAS Latency 2 memory installed is greater than | |
the copy bandwidth with CAS Latency 3 memory installed. |
12.SDS2 reboots during POST with 4GB or more of total system memory installed
Problem: | When 4GB or more of total system memory is installed in the SDS2 server |
board, and the Extended RAM step option in BIOS Setup is set to “Every | |
Location”, the SDS2 server board will reboot during the memory scan portion of | |
POST. This is due to a timeout of the |
Revision 1.2 | 113 |
Order Number: |
Errata Listing | Intel® Server Board SDS2 |
Implication: | The SDS2 server board will not complete POST if more than 4GB or more of |
total system memory is installed and the Extended RAM step option in BIOS | |
Setup is set to “Every Location”. | |
Workaround: | Choose a different option besides “Every Location” for the Advanced à Memory |
Configuration à Extended RAM Step BIOS Setup option. The default setting for | |
this option is “Disabled”. | |
Status: | Fixed. This issue is fixed in SDS2 BIOS Production Release 2.4 (Build 47) and |
later versions. |
13.Novell NetWare* v. 6.0 does not install on SDS2
Problem: | Novell NetWare* v. 6.0 will not install on the SDS2 server board. The install |
proceeds normally until the NetWare v. 6.0 splash screen appears for the first | |
time. The install will then start iterating the portion of the install from “initializing | |
system resources” to the splash screen indefinitely. | |
Implication: | Novell NetWare* v. 6.0 cannot be installed to the SDS2 server board. |
Workaround: | None. |
Status: | Fixed. This issue has been root caused as a Novell NetWare* v. 6.0 operating |
system issue. Novell has released NetWare v. 6.0 support pack (SP) 1, which | |
fixes this issue. Intel has verified the Novell NetWare* v. 6.0 can be | |
successfully installed to the SDS2 server board when SP1 is applied. The | |
procedure for applying SP1 is as follows: |
1.Create a 200MB bootable DOS partition on the installation hard drive.
2.Format the partition and create a directory called “nwupdate”.
Sino Sds2 L Manual
3.Copy server.exe from the SP1 directory “startup” into the “nwupdate” directory.
4.Launch the Novell NetWare* v. 6.0 install, and select to use the existing boot partition.
14.Adaptec* 2100S RAID controller causes system lockup and video blanking
Problem: | When an Adaptec* 2100S RAID controller is installed in the SDS2 server board, |
the video will blank and the system will lock up during POST when the onboard | |
SCSI controller option ROM is set to “Enabled” in the SDS2 BIOS setup (defalt | |
option). | |
Implication: | The Adaptec* 2100S RAID controller cannot be used with the SDS2 server |
board when the onboard SCSI controller option ROM is set to “Enabled” in the | |
SDS2 BIOS setup. |
114 | Revision 1.2 |
Order Number: |
Intel® Server Board SDS2 | Errata Listing | |
Workaround: | This issue does not occur when the SDS2 onboard SCSI controller option ROM | |
is set to “Disabled”. To disable the SDS2 onboard SCSI controller option ROM, | ||
access the Intel® Server Board SDS2 BIOS Setup by pressing F2 during | ||
POST. In BIOS Setup, change the Advanced à PCI Configurationà | ||
Embedded SCSI à Option ROM Scan option to “Disabled”. | ||
Status: | Fixed. This issue is fixed in SDS2 BIOS Production Release 2.5 (Build 48) and | |
later versions. |
15.SDS2 Build Your Own (BYO) Platform Confidence Test (PCT) v. 1.00 fails on the first run
Problem: | The first time the SDS2 BYO PCT v. 1.00 is run on an SDS2 system following a |
cold boot, the following error message will be encountered: | |
***ERROR BMC.CHECKCHASSISSTATUS V4.11.1.0107 | |
Chassis Status miscompared with known values. | |
EXP: 210101h, RCVD: 210001h, MASK: FFFFFFFFh | |
Standard Error Code = 0BE1501F | |
BMC.CHECKCHASSISSTATUS FAILED | |
This issue is not seen if the SDS2 BYO PCT v. 1.00 is | |
without restarting the system, or after restarting the system with a | |
warm boot. | |
Implication: | The SDS2 PCT v. 1.00 will fail with the BMC Check Chassis Status test when |
the test is run following a cold boot. | |
Workaround: | None. |
Status: | Fixed. This issue is due to the SDS2 BYO PCT v. 1.00 incorrectly identifying an |
error condition. This issue has been fixed in SDS2 BYO PCT v. 1.01. SDS2 | |
BYO PCT v. 1.01 will be added to the SDS2 system resource | |
future engineering change order (ECO). |
16.SDS2 0B71: System Temperature out of the range POST message
Problem: | When the SDS2 server board is installed in the SC5100 chassis, if the SC5100 |
front panel cable is disconnected from the SDS2 server board and then | |
reconnected while 5V standby voltage is applied to the system (AC power cord | |
connected to the system), the following message will be seen during POST the | |
next time the system is powered on: | |
System Monitoring Check | |
0B71: System Temperature out of the range | |
(Press <F1> to override boot suppression, or <F2> to enter Setup) | |
Revision 1.2 | 115 |
Order Number: |
Errata Listing | Intel® Server Board SDS2 |
In addition to this message, the SC5100 front panel system status LED will light | |
solid amber, indicating a system temperature fault. | |
This condition will continue to appear during POST each time the SDS2 system | |
is rebooted, until AC power is removed from the system by disconnecting the | |
AC power cord. | |
Implication: | The described condition will appear if the SC5100 front panel cable is |
disconnected from the SDS2 server board and then reconnected while 5V | |
standby voltage is applied to the system. | |
Workaround: | Disconnecting the AC power cord from the system will clear this condition. |
Status: | NoFix. Disconnecting and reconnecting the SC5100 front panel cable from the |
SDS2 server board while 5V standby voltage is applied to the system is not a | |
supported action. This action causes the SC5100 front panel temperature | |
sensor to report an invalid temperature reading. Customers must disconnect | |
the AC power cord from the SDS2/SC5100 system before disconnecting or | |
reconnecting the SC5100 front panel cable to the server board. |
17.SDS2 0B75: System Voltage out of the range POST message
Problem: | The following message may be encountered during POST when SDS2 |
FRU/SDR files v. 5.0.B and previous versions are programmed on the SDS2 | |
server board: |
System Monitoring Check
0B75: System Voltage out of the range
(Press <F1> to override boot suppression, or <F2> to enter Setup)
This issu
Implication: | The described condition may appear if SDS2 FRU/SDR files v. 5.0.B or |
previous versions are programmed on the SDS2 server board. | |
Workaround: | Disconnecting the AC power cord from the system will clear this condition. |
Status: | Fixed. SDS2 FRU/SDR files v. 5.0.B and previous versions contain slightly |
incorrect SDR values for the Vbat voltage (battery backup voltage). The Vbat | |
voltage sensor values have been corrected in SDS2 FRU/SDR files v. 5.0.D | |
and later versions. |
18.Miscellaneous numeric keys entered during POST enable PXE boot
Problem: | Entering various numeric key sequences during POST will cause the SDS2 |
system BIOS to enter the PXE boot sequence. The BIOS should only enter the | |
PXE boot sequence when the F12 key is pressed during POST. | |
116 | Revision 1.2 |
Order Number: |
Intel® Server Board SDS2 | Errata Listing | |
Implication: | The SDS2 system BIOS will enter the PXE boot sequence if various numeric | |
keys are pressed during POST. | ||
Workaround: | Do not enter numeric keys during the POST process. | |
Status: | Fixed. This issue is fixed in SDS2 BIOS Production Release 2.5 (Build 48) and | |
later versions. |
19.SDS2 board level operating temperature and power supply voltage tolerance modification
Problem: | In Table 73 of the Intel® Server Board SDS2 Technical Product Specification |
(TPS) Rev. 1.0, the board level operating temperature is specified as 0°C to | |
55°C. In Table 75 of the SDS2 TPS Rev. 1.0, the power supply tolerance is | |
specified as ±5% for the 3.3V rail. Intel has induced a failure condition during | |
board level temperature and voltage margin testing at 55°C and±5% voltage on | |
the 3.3V rail in SDS2 Server Boards configured with PCI adapters in the | |
64bit/66MHz PCI slots under extreme workloads during final validation testing. | |
As a result, the SDS2 Server Board board level operating temperature | |
specification has been modified to 0°C to 45°C, and the power supply tolerance | |
specification for the 3.3V rail has been modified to ±3%. The SDS2 Server | |
Board passes board level temperature and voltage margin testing performed | |
according to these modified specifications. | |
Implication: | The SDS2 Server Board’s operating environment should be maintained within |
the modified board level operating temperature specification of 0°C to 45°C and | |
the modified power supply tolerance specification of ±3% for the 3.3V rail. The | |
power supply tolerance specification for the 5V, 12V, and 5V standby rails is still | |
±5%. The system level operating temperature specification of the Intel® Server | |
Board SDS2 integrated into the Intel® SC5100 Server Chassis is still 0°C to | |
35°C. The Intel SC5100 Server Chassis’ cooling system is capable of | |
maintaining a SDS2 board level temperature below 45°C at a 35°C system | |
ambient temperature. | |
Workaround: | None. |
Status: | Fix. Intel has identified a fix for this issue, which will be incorporated in the |
SDS2 FAB 5 server board. |
20.Recommendation for SDS2 rubber bumper installation
Problem: | A rubber bumper is included with the Intel® Server Board SDS2. Intel |
recommends installing this bumper on the chassis before integrating the board | |
into the chassis, in order to improve the board’s tolerance to vibration that may | |
occur during shipment of the integrated system product. | |
Revision 1.2 | 117 |
Order Number: |
Errata Listing | Intel® Server Board SDS2 |
Implication: | If you are installing the Intel Server Board SDS2 into the Intel SC5100 Server |
Chassis, Intel recommends installing the rubber bumper included with the | |
server board. If you are installing the Intel Server Board SDS2 into a chassis | |
other than the Intel SC5100 Server Chassis, compare the rubber bumper height | |
to the chassi standoff height. If the bumper is the same height as the standoffs | |
in the chasis, install the rubber bumper included with the SDS2 Server Board. If | |
the suport is not the same height, procure a bumper that matches the height of | |
the standoffs used in your chassis. The rubber bumper should be installed on | |
the chassis as follows: | |
For the Intel SC5100 chassis: | |
1.Remove the backing from one of the rubber bumpers included with your | |
chassis. | |
2.Press the rubber bumper firmly into place approximately ½ inch (2 cm) to the | |
right of the chassis baseboard hole marked “9.” See location A below. | |
For other chassis: | |
1.Remove the backing from one of the rubber bumpers included with your | |
chassis. | |
2.Locate the chassis standoff labeled “1” in your chassis. | |
3.Place the rubber bumper at a location 6.25 inches (16 cm) toward the front of | |
the chassis and 7.75 inches (19 cm) toward the center of the chassis from | |
standoff 1. See location B below. | |
4.Press the rubber firmly into place. |
118 | Revision 1.2 |
Order Number: |
Intel® Server Board SDS2 | Errata Listing |
Figure 1. Placing the Rubber Bumper in the Chassis | |
Workaround: | Utilizing the rubber bumper with the SDS2 Server Board is a workaround for |
issues that may occur due to vibration during shipment of the integrated system | |
product. | |
Status: | NoFix. |
21.Keyboard and Mouse do not function under Microsoft* Windows* 2000 when legacy USB is enabled in BIOS setup
Problem: | When the Legacy USB Support option is set to “Enabled” in BIOS setup, a PS/2 |
keyboard and mouse do not function under Microsoft* Windows* 2000. This | |
has not been seen to occur with other operating systems. | |
Implication: | Enabling the Legacy USB Support option in BIOS setup will make a PS/2 |
keyboard and mouse | |
Workaround: | Leave the Legacy USB Support option in BIOS setup set to “Disabled”, which is |
a default option, if Microsoft* Windows* 2000 is being used. | |
Status: | Fix. Intel has identified a fix for this issue, which will be incorporated in the |
SDS2 FAB 5 server board. | |
Revision 1.2 | 119 |
Order Number: |
Errata Listing | Intel® Server Board SDS2 |
22.Data miscompares when using Seagate* ATA III model ST310215A hard drives
Problem: | Intel has induced data miscompares in SDS2 sytems configured with a |
Seagate* ATA III model ST310215A hard drive under extreme workloads during | |
validation testing. Intel has verfied that other hard drive models are not affected | |
by this issue. | |
Implication: | The Seagate* ATA III model ST310215A hard drive installed on the Intel® Server |
Board SDS2 is currently not a supported configuration and should not be | |
implemented in a production environment. | |
Workaround: | None. |
Status: | Fix. Intel has identified a fix for this issue, which will be incorporated in the |
SDS2 FAB 5 server board. |
23.Boot to service partition via modem fails
Problem: | When utilizing the direct platform control (DPC) feature of Intel Server Control |
(ISC) v. 3.5.2 software to boot a SDS2 server board to the service partition via | |
modem, the server board will hang during | |
Implication: | The DPC feature of ISC v. 3.5.2 software cannot be used to remotely boot the |
SDS2 server board to the service partion via modem. | |
Workaround: | None. |
Status: | Fixed. SDS2 BIOS Production Release 2.6, Build 49 and later versions include |
a fix for this issue. |
24.Secondary IDE References Added To Documentation for FAB 5
Problem: | New FAB5 |
Implication: | Users now have second IDE channel for use in system configurations |
Workaround: | None |
Status: | Fixed with the release of FAB5 SDS2 severboard in October 2002. |
25.Potential Mylex AcceleRAID 352 Adaptor Card Mechanical Interference at PCI Slot 6.
120 | Revision 1.2 |
Order Number: |
Intel® Server Board SDS2 | Errata Listing | |
Problem: | Mechanical interference between the Myelex installed memory module (DIMM) | |
and the onboard SCSI connector occurs if a Wide or Singled Ended SCSI cable | ||
is installed on embedded SCSI A or B connector. LVD SCSI cable connectors | ||
do not interfer. | ||
Implication: | Mechanical interference may damage the Mylex memory module connector and | |
DIMM when the Mylex AcceleRADI 352 Adaptor Card ins fully seated in PCI slot | ||
6 connector. | ||
Workaround: | Insure correct SCSI cable connector is used if a cables are installed on the | |
onboard SCSI connectors at SCSI A or B. | ||
Status: | Will not fix. |
26.Bootable CD will not boot if inserted during OPTION ROM scan
Problem: | During POST while the OPTION ROM scan for the on board (OB) devices and |
add in PCI adapters is in process, if an bootable | |
boot to the floppy was made and then the OS on the hard drive booted. No | |
attempt was made to boot to the bootable CDROM. | |
Implication: | Bootable |
reset. | |
Workaround: | Reset system after |
Status: | Will not fix. |
27.Swapping bootable for
Problem: | Powered on the system with a bootable Win2k AS CD in the CDROM drive. As |
soon as the BIOS began to POST | |
Bootable CD was ejected and a | |
system completed POST and attempted to boot, the floppy drive showed an | |
access attempt. The system then hanged with a blinking cursor on a black | |
background. The boot order was set with 1)Floppy 2) CDROM 3) Hard Drive. |
Workaround: | Reset the system. BIOS does not rescan status of boot devices upon |
completion of POST. | |
Status: | Will not fix. |
Revision 1.2 | 121 |
Order Number: |
Errata Listing | Intel® Server Board SDS2 |
28.OB P100 NICs do not show at POST but attempt PXE boot and appear in Boot Menu
Problem: | On board NIC are not displayed during post but do appear in Boot Device menu. |
These controllers will also attempt to do a PXE boot if no other bootable devices | |
are found. | |
Implication: | Not all boot devices displayed during POST when diagnostic display is enabled. |
Workaround: | None. This is by design. The system BIOS builds the |
controller Option ROM with an option that always makes the OPROM “quiet”. It | |
therefore does not display any text messages and does not allowing the CTRL- | |
S option. | |
Status: | Will not fix. |
29.Dodson: Adaptec 39160 in slots 5 & 6 causes Expansion ROM error
Problem: | Add in Adaptec 39160 Ultra 160 controller installed in slots 5 & 6 causes an |
Expansion ROM error after last system POST. No other adapters are present. | |
Implication: | Error message: Expansion ROM not initialized - PCI Mass Storage controller in |
slot 06. Bus: 02, Device: 09, Function: 01 | |
Workaround: | Adaptec's single image Option ROM requires one 'master' controlling channel |
that is set using the | |
ROM, determines whether it is the 'master' channel, and if not it unloads | |
completely. If it is the 'master', it proceeds to scan all devices and list all | |
possible drives. Only one channel does this scanning, but ALL channels load | |
the Option ROM initially if the Option ROM is enabled on the slot. | |
The error is coming from the second channel on the Adaptec 39160, even | |
though the first channel has already completed the 'master' scan. The reason it | |
is only happening in Slots 5 and 6 and when the NIC Option ROMs are all | |
loaded is because that is when the available Option ROM space is at a | |
minimum. The NIC Option ROM's are small, but apparently they make enough | |
difference. The onboard 7899 Option ROM loads after Slots | |
Slots 5 & 6. | |
The solution here is to enable channel B of the ASC39160 as the 'master' | |
channel. When this is done, channel A loads the Option ROM, sees that it is not | |
the 'master', and unloads. Then channel B loads the Option ROM, does the full | |
scan of all devices, and remains in memory. At this point no other channels are | |
found, so no other devices error. The key here is that the LAST available | |
Adaptec channel should be listed as the Master - unfortunately, this is opposite | |
from their default - they default to the first available channel. | |
122 | Revision 1.2 |
Order Number: |
Intel® Server Board SDS2 | Errata Listing | |
Status: | Will Not Fix. |
30.Can Not Change BIOS SETUP IDE Options Using <Enter> Key
Problem: | In SETUP, when attempting to change any option under the Primary/Secondary |
IDE controller | |
function. The TPS does not mention having to use the SPACE bar to change | |
the options. | |
Implication: | Possible confusion on how to select the options in the BIOS Setup IDE sub |
menu. | |
Workaround: | None. |
Status: | Will not fix. |
31.Minimum Wait Time Between Power Off and Power On via Front Panel Power Button Is One Second.
Problem: | Minimum wait time between power off and power on using the front panel power |
button on the SC5100 chassis is not documented. | |
Implication: | System will not respond to the power button until one second has elapsed. |
Workaround: | Wait longer than one second when cycling the AC power via the front panel |
power button. | |
Status: | Will not fix. |
32.Unable to boot Netware 6.0 (NW6) From CD ROM With Adaptec Adaptor 2100S in Slot 6.
Problem: | Unable to install or boot to NW6 from CD Rom with Adaptec SCSI Adaptor |
2100S installed in Slot 6. NW6 requires SP1 updated drivers to be installed. | |
Implication: | System hangs and fails to load drivers completely. Unable to boot to SSU floppy |
if NW6 CD is installed in | |
Workaround: | Recommended installation methodology is to install from the Netware 6 SP1 |
Overlay CD. This CD installs Netware 6 with all the SP1 fixes already | |
incorporated. | |
The SP1 Overlay CD is available from | |
http://support.novell.com/filefinder/13659/index.html | |
Revision 1.2 | 123 |
Order Number: |
Errata Listing | Intel® Server Board SDS2 |
Alternatively, the updated drivers may installed using the following procedure to install NW6. .
a)Boot to DOS and fdisk/format the C: partition.
b)Boot to C: drive and load loddvc.com and cdex from there:
'loddvc aoatapi.sys /D:cdr0m001 cdex.exe /D:cdr0m001 /L:z'
(aotapi.sys is whatever driver is appropriate for the cd
c)Copy server.exe from SP1 to the nwupdate directory.
d)Run 'Install.bat' from the Z: drive
Status: Fixed.
33.3COM*
Problem: | Intel has induced blue screens under Microsoft* Windows* 2000 in SDS2 |
sytems configured with a 3COM* | |
v3.48.0.0, and greater than 4GB of system memory installed, under extreme | |
workloads during network validation testing. This issue is not seen when up to | |
4GB of system memory is installed in the SDS2 system. | |
Implication: | Blue screens may be encountered under Microsoft* Windows* 2000 when |
using a 3COM* | |
system memory installed. | |
Workaround: | This issue results because the 3COM |
support dual address cycles (DAC), therefore, the NIC is not able to access | |
physical addresses above 4GB. Due to negative performance impact, Intel | |
does not recommend using a NIC adapter that does not support DAC or | |
PCI on a system with greater than 4GB of system memory installed. Intel | |
recommends installing a maximum of 4GB of system memory in the SDS2 | |
system when utilizing the 3COM* | |
This issue does not occur when 3COM driver el98xn5.sys v4.0.0.15, which is | |
available on the Microsoft* Windows.NET* CDROM, is used, instead of 3COM | |
driver el98xn5.sys v3.48.0.0. This is another possible workaround for this | |
issue. | |
Status: | Fixed. |
124 | Revision 1.2 |
Order Number: |
Intel® Server Board SDS2 | Errata Listing |
34.
Problem: | |
controlled, | |
not supported between the | |
the legacy | |
bridge. | |
This information is not officially documented in ServerWorks datasheets or | |
confidential chipset documents. | |
Implication: | PCI adapter card transactions between |
will fail. | |
Workaround: | |
CIOB. | |
Status: | NoFix. |
35.SDS2 PCI slot current levels supported by the 5V rail
Problem: | The SDS2 server board is capable of supporting a maximum total of 21 amps |
on the 5V rail to the six PCI slots on the server board. | |
Implication: | The SDS2 server board can support a maximum total of 21 amps on the 5V rail |
to the six PCI slots on the server board. Integrators must consider this when | |
selecting PCI card configurations for use in the SDS2 server board. | |
Workaround: | Select PCI cards that utilize a combination of 3.3V and 5V voltage in order to |
minimize the current utilized by the PCI cards on the 5V rail. | |
Status: | No Fix. |
36.OB P100 NICs do not show at POST but attempt PXE boot and appear in Boot Menu
Problem: | On board NIC are not displayed during post but do appear in Boot Device menu. |
These controllers will also attempt to do a PXE boot if no other bootable devices | |
are found. | |
Implication: | Not all boot devices displayed during POST when diagnostic display is enabled. |
Workaround: | None. This is by design. The system BIOS builds the |
controller Option ROM with an option that always makes the OPROM “quiet”. It | |
Revision 1.2 | 125 |
Order Number: |
Errata Listing | Intel® Server Board SDS2 |
therefore does not display any text messages and does not allowing the CTRL- | |
S option. | |
Status: | Will not fix. |
126 | Revision 1.2 |
Order Number: |
Intel® Server Board SDS2 | Glossary |
Glossary
This appendix contains important terms used in the preceding chapters. For ease of use, numeric entries are listed first (e.g., “82460GX”) with alpha entries following (e.g., “AGP 4x”). Acronyms are then entered in their respective place, with
Term | Definition |
ACPI | Advanced Configuration and Power Interface |
ASIC | Application specific integrated circuit |
BIOS | Basic input/output system |
BIST | |
BMC | Baseboard Management Controller |
Bridge | Circuitry connecting one computer bus to another, allowing an agent on one to access the other. |
Byte | |
BYO | Build your own |
CIOB | PCI |
CMOS | In terms of this specification, this describes the |
bytes of memory, which normally resides on the baseboard. | |
CSB5 | Legacy I/O controller hub |
EEPROM | Electrically erasable programmable |
EMP | Emergency management port |
EPS | External Product Specification |
FRB | Fault resilient booting |
FRU | Field replaceable unit |
GB | 1024 MB. |
GPIO | General Purpose I/O |
GTL | Gunning Transceiver Logic |
HSC | |
Hz | Hertz (1 cycle/second) |
I2C | |
IA | Intel® architecture |
ICMB | Intelligent Chassis Management Bus |
IERR | Internal error |
IPMB | Intelligent Platform Management Bus |
IPMI | Intelligent Platform Management Interface |
ITP | |
KB | 1024 bytes. |
LAN | Local area network |
LPC | Low pin count |
LUN | Logical unit number |
MAC | Media Access Control |
MB | 1024 KB |
Ms | milliseconds |
Revision 1.2 I
Order Number:
Glossary | Intel® Server Board SDS2 |
Term | Definition |
Mux | multiplexor |
NMI | |
OEM | Original equipment manufacturer |
Ohm | Unit of electrical resistance |
32 bit PCI Segment | |
Full Length 64/66 MHz PCI Segment | |
Full Length 64/66 MHz PCI Segment | |
PBGA | Pin Ball Grid Array |
PCT | Platform Confidence Test |
PLD | programmable logic device |
PMI | Platform management interrupt |
POST | Power On Self Test |
RAM | Random Access Memory |
ROM | Read Only Memory |
RTC | |
SDRAM | Synchronous Dynamic RAM |
SEEPROM | Serial electrically erasable programmable |
SEL | System event log |
SM | Server Management |
SMI | Server management interrupt. SMI is the highest priority |
SMM | Server management mode. |
SMS | Server management software |
SNMP | Simple Network Management Protocol. |
TBD | To Be Defined |
UART | Universal asynchronous receiver and transmitter |
USB | Universal Serial Bus |
II | Revision 1.2 |
Order Number: |
Intel® Server Board SDS2 | Reference Documents |
Reference Documents
Refer to the following documents for additional information:
Refer to the following documents for additional information:
∙
∙Tualatin Processor Electrical, Mechanical, and Thermal Specification Rev 0.9,
∙Tualatin Dual Processor Platform Design Guide Rev 1.0, OR2660
∙ServerWorks Champion North Bridge 2.0 HE Version 1.8
∙ServerWorks Champion North Bridge 2.0 HE SuperLite Version 1.2
∙ServerWorks Champion IO Bridge Version 1.6
∙ServerWorks Champion South Bridge Version 1.5
∙PCI Local Bus Specification Revision 2.2
∙USB Specification, Revision 1.0
∙Adaptec
∙ATI RAGE XL Graphics Controller Specifications, Technical Reference Manual, Rev 2.01
∙VRM 8.5
∙Intelâ 82550 Fast Ethernet PCI Controller Datasheet
∙Intelligent Platform Management Interface (IPMI) Specification
∙SDS2 Baseboard Management Controller External Product Specification Rev 0.81, Ref. NO. 10282
Revision 1.2 | III |
Order Number: |