Intel R2224WT Server System BIOS/Firmware 01.01.0018 Download

Posted at November 21, 2024 by PCI-DB Team

Intel R2224WT Server System BIOS/Firmware 01.01.0018 Description

Versions:

- System BIOS - 01.01.0018
- ME Firmware - 03.01.03.032
- BMC Firmware - 01.46.9995
- FRUSDR - 1.13a

BIOS Changes:

- EPSD 100253916: The default value of BIOS setup option [Snooped Response Wait Time for Posted Prefetch] is not correct during R9 to R16 update
- EPSD 100254004: Security Fix for Grantley SmmRuntime driver
- EPSD 100253648: Grantley memory RAS feature ECC error Leaky Bucket decay time window is set to 100 days, which is too long.
- EPSD 100253299: 4x4x4x4 on Slot5 for S2600CW2SR
- EPSD 100253233: CC_SPARE bits not cleared in accordance with E5-2600V3 spec update (CDI # 550584) errata HSE22S - may cause NVMe issues
- EPSD 100253548: Fan PWM Limit default value and operational range are wrong
- CCB 391: Implement a BIOS setup option to Limit PWM to a maximum value similar to Purley
- EPSD 100252598: [x] Add more DIMM support -- supported DIMM informaiton can't be shown correctly in SMBIOS Table Memory information
- EPSD 100032105: [E5-2600V4][E5-2600V4 CPU] Error message of memory channel A not match other Channel.
- Update ME to 03.01.03.032
- EPSD 100032453 [E5-2600V4][E5-2600V4 CPU]The String not right at IOU Non-Posted Prefetch Control in BIOS Setup.
- EPSD 100251776 [S2600WT] VR Watchdog reports it has been asserted after Global reset(Update ACM to v3.0.5) hidden "Platform type input for SPD page selection"
- BIOS workaround for EPSD 100031139 [Switch]The DPC function couldn't work on the PCIe switch AIC via Switch AIC
- EPSD 100032467 [E5-2600V4][E5-2600V4 CPU] Press Hot key F6 , F12 will not display any screens describe during POST
- EPSD 100252973: NTB performance drop with DMA-enabled. Notes: Need to disable Relaxed Ordering under IIO configuration setup menu when DMA-enabled in NTB Linux driver.
- Roll back W/A for [E5-2600V4] 2400MHz LRDIMM size missed in power cycling test
- EPSD 100251966: 32GB Hynix LRDIMM size mismatch during cycle test
- EPSD 100031669: Intel SSD AIC SSDPEDMX020T4 Link margin Fail
- EPSD 100252478 After saving in setup, PXE boot option is not maintained during reboot
- EPSD 100032100: [E5-2600V4][E5-2600V4 CPU]Hot key F12 without function during POST when boot mode change to UEFI
- Sync Grantley RC 3.2.0 code
- EPSD 100032112: SBO function not correct when insert USB device in J3A1 and J8E2
- EPSD 100252440 Inversion PCIE card location was detected between Riser slot 1 and slot 2
- EPSD 100252718: Use Angilent Card to inject Poisoned TLP and Surprise Link Down fatal error the function is abnormal.
- IpPlan v1.12 update.
- IpPlan v1.12 document update.
- NO SIGHTING: IpPlan Doc update.
- EPSD 100252195: Clone of: [X] DMI type 41 records is not correct for onboard and IO module NICs.
- EPSD 100252209 [X] Syscfg 13.1-15 sets [Snooped Response Wait Time] and [Non-Posted Prefetch] options fail with BIOS R15 + E5-2600V4.
- EPSD 100252266: [E5-2600V4][TGF]Connect Resistor TGF card to Riser slot 2 and set bifurcation to x16, SUT hang at POST screen.
- EPSD 100031863 [E5-2600V4][E5-2600V4 CPU]SMBIOS Type 7 L3-Cache associativity should display 20 way not fully.
- EPSD 100031758: [E5-2600V4][E5-2600V4 CPU] Error message not match EPS1.16 at Error manager
- Update copyright to 2016

ME Changes:

- SPS FW sends P-state change requests to OS when no power limiting policy is configured.
- Can't set power policy in S5 after Power Button Override.
- SPS generates health event in each AC cycle.
- SmaRT&CLST Status of Get SEL Entry have wrong byte order.
- Predictive Power Limiting NM Policy does not meet 99.5% below power limit criteria in case of SMBAlert assertions (Fast #PROCHOT).
- CPU cannot reach max frequency when stressed by PTU in SMI Optimized mode.
- NM PTU option ROM running on HSX systems will exit early, after first characterization, and may cause system instability

BMC Changes:

- Watchdog assert happened on Nodes with bigger number while unplug PSU on S2600KP/S2600TP
- EPSD100253232: [S2600WT] FRUSDR112 and FRUSDR113 dont detect PSUs on a 3rd party chassis
- EPSD100251931: Email and SNMP alerts are not sent during a drive fault on 1U HSBP.
- EPSD100253499: EWS show in Chinese not align with English
- EPSD100252884: Change FAN to auto-rearm, fan status cannot show correct status on EWS
- Remove the 2130W PSU FW Ver24 for update hang issue
- EPSD100252472: Defect title: vulnerabilities found on BMC release 01.41.9579
- EPSD100252826: BMC FW Use of Voltage Fault (D1h) Violates DFT Rule #1619
- EPSD100252984: modify master.cfg to automation will results fail
- EPSD100249322: duplicate response from remote host during SSH SOL/SMASH session
- EPSD100252884: Change FAN to auto-rearm, fan status cannot show correct status on EWS
- After load FCT or Default SDR in 24HDD System, HSBP update process cannot start
- EPSD100031139: The DPC function couldn't work on the PCIe switch AIC via Switch AIC (Implement OEM Misc command (NetFn:0x30, Cmd:0x67) to detect SSD switch AIC)
- EPSD100248833: SMASH cannot read recent SEL events when SEL has a high volume.
- EPSD100031101: IE11 displaying EWS->Configuration->KVM & Media /SOL & SMASH, Sever. Diagnostics->POST Codes with help ON, text exceeds the Box size
- EPSD100252439: PCIe SSD Add-in-Card present slot bitmap don't match current inserted slot number in EFI shell

FRUSDR 1.

13a

- Update frusdr.efi and ipmi.efi utility 13.1 build 11.
- Update master.cfg and mster_internal.cfg files with added the wildcard "%".
- Add S2600WTTS1R.fru file for board S2600WTTS1R 10G.

System Firmware Update Package Usage instructions

<>This package can be updated using one of the following methods:
- Windows or Linux operating system using Intel One-boot Flash Update (OFU) V13.1 Build 13
- Windows Preboot Execution Environment (WinPE)

<>To update from Windows and Linux or operating systems using the Intel One Boot
- Flash Update Utility (OFU)

<>Use OFU to update system firmware by the following steps:
- Install OFU on Windows or Linux system
- Download the latest firmware update package from http://downloadcenter.intel.com/
- Unzip package to a folder
- Run the following command in Windows command line/Linux terminal window: <OFU install folder name>:flashupdt -u <package folder name>flashupdt.cfg

<>To update from Windows Preboot Execution Environment (WinPE)

The System Firmware Update Package can be inserted to Windows PE customized image for creating a bootable Windows PE CD. User is able to update system firmware from customized WinPE CD by the following steps:
- Boot server with customized WinPE CD
- Run script "WinPE21_x64_Update.bat" or "WinPE20_x86_Update.bat" (name may be varied depends on your own customization)

About ME Firmware:

If you wish to apply this ME (Management Engine) Firmware version, you should first make sure that the version number matches your AMT (Active Management Technology) family, as each update is specifically developed for certain system configurations.

While this technology is mostly associated with enterprises, it can also be used by various IT administrators as well as regular users. However, bear in mind that even though other platforms might also be compatible, we do not recommend installing this release on OSes other than the specified ones.

In order to apply this package, it would be best if you carefully read and understand the instructions provided by your computer manufacturer, and perform the update only when you have completely familiarized yourself with the steps.

In addition to that, make sure you perform a system reboot after upgrading the firmware version in order to allow all changes to take effect properly.

About OS Independent BIOS:

Although installing a newer BIOS version might add new features, update various components, or improve the device’s usability, this process is very risky, so the upgrade is recommended to be performed only when it is really needed.

In addition to that, this task should be performed by someone who has the knowledge to successfully complete the installation; regular users may fulfill it at their own risk.

When it comes to applying a new version without taking into account the computer’s operating system, the most commonly used method to flash the BIOS is by creating a bootable USB or CD containing the update file, and running it from DOS.

Still, regardless of the method used or whether the upgrade is performed by a regular or power user, it’s recommended that the new BIOS be applied in a steady power environment such as the one ensured by a UPS unit.

The Basic Input/Output System (BIOS) is a very important software that loads the currently installed OS, and tests all of the system’s hardware components – so make sure you flash it correctly.

Bear in mind that failing to perform a successful installation could seriously damage your device, and the faulty BIOS resulted from the process might even render it unusable.

About Firmware Updates:

Applying a newer firmware version than the one already installed on your unit can bring various enhancements, include workarounds for diverse problems encountered by the device, and improve or add newly developed features.

On the other hand, downgrading the firmware version can recover the device’s functionality in the event of a software update either turning up faulty or causing the unit’s overall performance to drop. However, bear in mind that applying an older firmware isn’t recommended and might not always be possible.

When it comes to the update steps, due to the large variety of devices and numerous ways for installing a new firmware, it is recommended that you carefully read and understand the upgrade steps, and consider applying a different firmware only when you have familiarized yourself with the update method.

As the installation process is most of the times quite risky, this step should be taken by users that have the ability to successfully complete the update; regular users may initiate it at their own risk. Moreover, it’s best that this task be performed in a steady power environment such as the one ensured by a UPS unit.

Therefore, if you consider applying this release, hit the download button, take into account all the aforementioned aspects, and update the device’s firmware. Also make sure you constantly check with our website to ensure that you don’t miss a single new release.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related Intel Drivers