Abstract: An information handling system and a method of using it can allow the information handling system to be started or restarted and have an operating system loaded, even if a boot variable within a persistent memory is currently invalid. The method can detect and determine a hardware path name to a new drive that has an operating system. The new drive can have a relative path name to boot entries that include a pointer to a boot file. The boot file can be executed to run a boot loader that loads the operating system. During loading of the operating system, other boot entries within the drive can provide boot parameters. The boot variable within persistent memory, and potentially the relative path name or boot parameter(s) can be updated on the new drive. In a particular embodiment, the information handling system can include a unified extensible firmware interface (UEFI).

Abstract: A system and method is disclosed for identifying at least one bootable USB device coupled to a computer system across multiple reboots of the computer system. A four-byte signature for each bootable USB device is generated by performing a hash function on a Device Identification Number, a Vendor Identification Number, and at least a subset of a Serial Number, all of which are associated with that bootable USB device. The four-byte signature for each bootable USB device is saved in a BIOS boot order table located in a non-volatile storage unit in the computer system.

Abstract: A method for writing bytes to flash memory is disclosed herein whereby the method comprising includes counting bytes from a data source, the bytes associated with a first value and a second value and comparing a number of bytes associated with the first value with a number of bytes associated with the second value. The method may further include inverting the bytes in the case where the number of bytes associated with the first value is greater than the number of bytes associated with the second value and transferring the bytes not associated with the second value to the flash memory.

Abstract: A method may for updating system configuration data is provided. A configuration change request may be received from a remote user at a local baseboard management controller (BMC) via a network while a processor associated with the BMC is offline. The configuration change request may be stored in a request log. After the processor comes online, the configuration data may be updated based on the configuration change request stored in the request log. A copy of the updated configuration data from the chipset may be stored in a storage device coupled to the BMC such that the copy of the updated configuration data is accessible when the processor is offline. The copy of the updated system configuration may be provided to a subsequent remote user for a subsequent system configuration update.

Abstract: For updating a basic input output system (BIOS) code stored in a non-volatile memory (NVM) included in an information handling system (IHS), a plurality of conditions permitting the updating of the BIOS stored in the NVM from a memory of the IHS are verified. The contents of the memory are preserved by disabling interrupts and disabling bus masters capable of causing a change in the contents of the memory. The BIOS stored in the NVM is updated from the memory. A user interface is provided to display status of the updating of the NVM to improve user experience. Upon completion of the updating the IHS is reset by enabling a cold reboot, thereby enabling the changes made to the BIOS to take effect.

Abstract: A system for identifying peripheral devices in an information handling system uses a path-based signature for each peripheral component device. A static table is included for listing the path of each peripheral device and is accessible to the Basic Input-Output System (BIOS). The BIOS is configured to identify peripheral components associated and determine a path-base device signature for each peripheral component.

Abstract: A system and method is disclosed for identifying at least one bootable USB device coupled to a computer system across multiple reboots of the computer system. A four-byte signature for each bootable USB device is generated by performing a hash function on a Device Identification Number, a Vendor Identification Number, and at least a subset of a Serial Number, all of which are associated with that bootable USB device. The four-byte signature for each bootable USB device is saved in a BIOS boot order table located in a non-volatile storage unit in the computer system.