The CPU microcode can also be brought up to date during the process.The steps you need to cover in order to carry out the task successfully are the following: run it with administrative rights, provide the BIOS file you want to modify, choose the update to be applied and wait for the application to do its job.In most cases you can revert back to a previous version of your System BIOS if the new version is causing problems for you.

You can either use the UEFI version of sas2flsh (called sas2for 6 Gb/sec, or sas3for 12 Gb/sec), or contact the motherboard vendor and ask if it is possible to add BIOS32 service directory support to the motherboard (most likely via a motherboard BIOS update). When using sas2or sas3flash.efi, but sure to put all of the files (the firmware file, BIOS file, and sas2flash.efi/sas3flash.efi) in the root directory.

Otherwise you might see a ' Could not open file:' error. Some of the scenarios below ( ) involved erasing the controller firmware first with the '-o -e 6' command line option, then flashing it back. If the EFI BSD is erased, then when the controller has IR firmware and the motherboard is in UEFI mode, then the SAS HBA will not be able to be configured in BIOS.

The release notes for each release will describe the bug fixes for each release and will help you decide if you need to update.

To upgrade the firmware, follow the instructions provided by the PC manufacturer.

UEFI BIOS Updater is a BIOS modding toolkit that allows you to perform an update for OROM / UEFI modules of an AMI UEFI BIOS without requiring advanced knowledge on modding techniques.

Developed by a modding expert, UEFI BIOS Updater has scarce competition, being one of the few tools on the market that can perform BIOS modding with low chances of BIOS failures.

Also the UEFI BSD version will be displayed as ' N/A' with the sas2flash (or sas3flash) -c 0 -list command.

You can flash the UEFI BSD firmware to resolve this.

The motherboard's manual tells me nothing and I want to use the GUI.