Intel SDS2 User Manual
Page 124
Intel® Server Board SDS2
Errata Listing
Revision 1.2
Order Number: A85874-002
113
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 FRB-2 timer.