PCI-DB.com
  1. Driver
  2. Motherboard
  3. Intel S2600KP Server Board UEFI Firmware 01.01.0005/03.00.07.114/01.08.6942/1.02

Intel S2600KP Server Board UEFI Firmware 01.01.0005/03.00.07.114/01.08.6942/1.02 Download

Posted at April 25, 2024 by PCI-DB Team

Install Driver Automatically
Device NameIntel S2600KP Server Board UEFI Firmware 01.01.0005/03.00.07.114/01.08.6942/1.02
CategoryMotherboard
ManufacturerIntel
File Size19.2 MB
Supported OSOS Independent

Intel S2600KP Server Board UEFI Firmware 01.01.0005/03.00.07.114/01.08.6942/1.02 Description

Versions:

- System BIOS - R01.01.0005
- ME Firmware - 03.00.07.114
- BMC Firmware - 01.08.6942
- FRUSDR - 1.02

Issues fixed in ME Firmware 03.00.07.114:

- For Shared Power Supply configuration, power isn't kept in the range of 2% during power limiting. The power kept in range of 3C 4%.
- SMLink0 utilization is too high after disabling Node Manager with Set ME FW capabilities command.
- Sporadically MESDC hangs up during reading trace logs via IPMB/RMCPP/HECI interface.
- Few events instead of one are sent after Flash Wear-Out Protection occurs.
- OSPM and DCMI policies are not created when policies maximum number of policies defined in XML file.
- BMC OEM readings discovery is working incorrectly in Sx when BMC responded with completion code different from Successful (0x00).
- [MESDC] Compliance test NM_13: After running the test the PROCHOT is not deasserted which may fail other compliance tests with power limiting.
- Certain power delivery systems may provide power data which fluctuates outside of the tolerances of the NM PTU power data filtering algorithm causing the Get Node Manager Power Characterization Range command (0x61) to return 0xFFFE power data.
- ME goes to recovery state after graceful shutdown when power and thermal readings are enabled.
- In G3 to S5 transition ME sends 2 NM Health Events: power readings in domain 0 and inlet temp readings are missing.
- BMC set as power source even if only PSU is available when auto configuration is enabled.
- P-States cannot be set while platform is in idle state.
- Unexpected CLST event is sent during S0->S5 transition.
- PSU Monitoring service error during GetSelftestResults IPMI command.
- BackBone exceptions during various power flows (SX/Global Reset) or after SKU burning / NMon alwaysOn/ s0only.
- Unexpected ME resets during SMBAlert stress test (backbone exception).
- MESDC over IPMI causes FW crash in Recovery if MeMdesAddr is disabled in xml.
- ME failed during cold reset after continuously setting and resetting ME recovery jumper - two exceptions occurred.
- Get NM Capabilities IPMI command return CompCode 0xC0 (Node Busy) when power telemetry is enabled.
- Unable to assign GPIO > 15 to MEMHOT, PROCHOT, SMBALERT.
- HMRFPO_ENABLE does not always respond during FW update after EOP.
- Missing readings policy causes maximum throttling after S3.
- Me does not send SMB Alert mask when setting redundant PSU.
- Me switches to recovery image when auto configuration is enabled and no sensors are enabled.
- Send Raw PMBUS command PMBUS_Revison does not work on SiEn SKU.
- Get Sel Entry IPMI command returns too few bytes in Recovery.
- SPS FW switches to Recovery during BMC DC Reboot.
- BMC OEM readings discovery does not work correctly in Sx.
- Platform shuts down during AC Cycles with 0W policies set on all domains.
- Threshold Exceeded event desertion not received when BMC sets new power threshold.
- Incorrect NM-PTU SHA-256 hash.
- Inband PECI Failure health events are not sent in some cases.
- "Get Self-Test Results" IPMI command reports PSU Monitoring error for PSU configured as redundant that is missing.
- When user issues “Set Max Allowed CPU P-state/T-state” command CPU will operate on Max Turbo frequency instead P1.

Issues fixed in BMC Firmware 01.08.6942:

- EPSD100244631: Added command tracking to prevent the BIOS mailbox or IPMI commands from sending more than one successful initialization sequence to specific PCIe cards on each boot.

Issues fixed in BIOS 01.01.0005:

- EPSD100244208: SEL intermittently reports therm trip

  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

Find Missing Drivers

© 2024 PCI-DB.com - PCI Database Replacement. All rights reserved.