Posted at December 3, 2024 by PCI-DB Team
Install Driver AutomaticallyDevice Name | Intel S2600STB Server Board BIOS/Firmware 00.01.0012 |
---|---|
Category | Firmware |
Manufacturer | Intel |
File Size | 24.5 MB |
Supported OS | OS Independent |
- System BIOS: 00.01.0012
- ME Firmware: 04.00.04.294
- BMC Firmware: 1.43.33e8d6b4
- FRUSDR: 1.28
- Microcode 0x43 and 0x13f update to address Intel-SA-00088
- [S2600WF] NM configuration Couldn't dispaly the memory power policy in the EWS
- No fwpiaupd.efi version from EFI SUP package
- Use BMC_1.43.1ec4fc15, while entering the BIOS UI, the EWS SEL Log change the Date and Time to 1970.
- [VMViewer]Fail to run the script of fulltest.sh on S2600ST Base SKU.
- iKVM wasn't able to launch after configuring the router for IP map
- [S2600BP] L9 systems BMC log time set to 01/01/2015 or 01/01/2016
- Q4'17 [Xeon Scalable Family BMC] Change behavior for unconditional power off to work around ME bug
- [S2600BT] SUT shut down during first reboot after IFWI update. CRITICAL events on SPS and ME
- BMC Video signal lost(Black Screen) after a randomly time of normal use
- iKVM Video signal lost(Black Screen) after a random time
- [S2600BT] Lots unexpected events logged during execute 3 remote scripts and 1 local script.
- [S2600WF] Lots unexpected events logged during execute 3 remote scripts and 1 local script.
- [S2600BT] Deleting Alert Destination would show wrong message
- [S2600WF] Deleting Alert Destination would show wrong message
- [S2600WF] SOL Log can't download by EWS after record a lot of logs.
- [S2600WF] LNET Router BMC Reporting PS1 Status, P1 and P2 Status, and Fan Non-redundant:Insufficient Resources events on OS and DC Cycling
- [S2600BP] OpenIPMI driver fails to detect BMC on startup.
- [S2600BT] The time stamp in sellog is incorrect after offline flash BIOS , BMC , set clear CMOS jumper and remove battery.
- It generates some incorrect event logs in the AC cycle stress test
- Sometimes system will generate an abnormal event log about “Sensor failure—HSBP temp -- Asserted” and status LED show green blinking
- [S2600BP] SEL Log has the Processor P1/P2 Status Assert during the Linpack Cluster Stress Test
- [S2600BP] There is LAN Leash Lost event recorded during os reboot cycling test
- PS1/PS2 Temperature sensor Upper Threshold failed.
- [S2600WF] The warning message will pop-up twice after launch 2nd JAVA SOL form EWS
- [S2600BT] The warning message will pop-up twice after launch 2nd JAVA SOL form EWS
- [S2600WF] There are conflicting between help page and its NOTE in EWS keyboard macros page
- [S2600BT] There are conflicting between help page and its NOTE in EWS keyboard macros page
- SEL decoding doesn't align with BIOS EPS
- [S2600BT] Deleting Alert Destination would show wrong message
- #CCB 1937: [Xeon Scalable Family BMC]Disable/Enable IPMI network ports by IPMI command and EWS
- [S2600BP] SOL can't login via Java SOL viewer
- The EWS -> Alerts -> Lan channel to configure help page description is mismatched with the function.
- [S2600BT] SOL can't login via Java SOL viewer
- Status LED keep solid green when second Fan of System Fan reach Lower Critical status.
- When install Windows 2016 from 1 Client PC to 2 SUT, it used more than 80 minutes to completed the installation
- [S2600BT] The Alerts LAN channel configure function is still exist on help page description.
1. Unzip the contents of the update package and copy all files to the root directory of a removable media (USB flash drive)
2. Insert the USB flash drive to any available USB port on the system to be updated
3. Power on the server and load the uEFI shell
4. Begin the update process running the Startup.nsh
5. Reboot the system after the update process has successfully completed
1. Unzip the package onto your system
2. Log into the BMC web GUI
3. Navigate to Configuration, then Firmware Update
4. Click browse, and direct the browser to the location of Purley_1.04.f80688d0.bin
5. Click upload. Progress and status will be shown as the update progresses
1. Unzip package and load onto a flash drive
2. Boot to UEFI shell, and navigate to the folder where this package lives
3. Run fwUpdateBMC.nsh and follow the prompts
01. After the final update has completed successfully, reboot the system
02. During POST, hit the <F2> Key when prompted to access the BIOS Setup Utility
03. From the BIOS Setup Utility main menu, hit the <F9> key to load BIOS defaults
04. Hit the <F10> key to Save Changes and Exit the BIOS defaults
04. At the main menu verify the BIOS revision is correct
05. Move cursor to the SERVER MANAGEMENT menu and hit Enter
06. Move cursor to the SYSTEM INFORMATION Option and hit Enter
07. Verify the BMC Firmware revision is correct
08. Verify the SDR revision is correct
09. Verify the ME Firmware revision is correct
10. Configure desired BIOS Option settings
11. Hit the F10 Key to Save Changes and Exit
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.
Device Type: Graphics Board File Size: 354.1 MB Windows 10 64 bit
Install DriverDevice Type: Graphics Board File Size: 355.1 MB Windows 10 64 bit
Install DriverDevice Type: Graphics Board File Size: 300 MB Windows 10 64 bit
Install DriverDevice Type: Graphics Board File Size: 117 MB Windows 10 64 bit
Install DriverDevice Type: Graphics Board File Size: 300 MB Windows 10 64 bit
Install DriverDevice Type: Graphics Board File Size: 111.5 MB Windows 8
Install DriverDevice Type: Graphics Board File Size: 355.1 MB Windows 10 64 bit
Install DriverDevice Type: Graphics Board File Size: 148.1 MB Windows 8.1 64 bit
Install DriverDevice Type: Graphics Board File Size: 49.8 MB Windows 7 64 bit
Install DriverDevice Type: Graphics Board File Size: 25.3 MB Windows 7 64 bit
Install DriverFind Missing Drivers
Recent Devices
Recent Drivers
© 2024 PCI-DB.com - PCI Database Replacement. All rights reserved.