Dell Products Inc.

Dell Inc.

Mark W Shutt

Wei G Liu

Sundar Dasar

Yogesh Prabhakar Kulkarni

Mukund Purshottam Khatri

Quy Hoang

Alberto David Perez Guevara

Richard Louis Holmberg, Jr

Tzu-Hsiu Tsai

Andy Butcher

Fernando Antonio Garcia Castillo

Raja Tamilarasan

Benjamin Andrew Martinez

Sumanth Vidyadhara

Anand Prakash Joshi

Austin Patrick Bolen

Madhusudhan Rangarajan

Sanjeev Dambal

Wayne Robert Weilnau, Jr

Terry Wayne Liles

Robert J Volentine

James E Dailey

Swamy Kadaba Chaluvaiah

Patrick Oliver Boyd

Sruthi Reddy Mothukupally

Vigneswaran Ponnusamy

Charles E Rose

Samer El Haj Mahmoud

Satyajit Dipakbhai Desai

Thomas Cantwell

Richard L Holmberg

William Carl Edwards, Iii

Daiqian Zhan

Ganesh Kuppuswamy Viswanathan

Sumeet Kukreja

Natalie Quach

Peter Cloney

Krishna P Mohan

Price Tsai

Keungsik Kim

In one or more embodiments, an information handling system (IHS) manufacturer is configured to: manufacture multiple motherboards configured to be installed in multiple IHS product lines; respectively install multiple non-volatile memory media on the multiple motherboards; store first product line firmware, associated with a first product line of the IHS manufacturer, via the multiple non-volatile memory media; provide a first portion of the multiple motherboards to a first division; and provide a second portion of the multiple motherboards to a second division; the first division is configured to: permanently store a first IHS identity type on the first portion of the multiple motherboards; and the second division is configured to: permanently store a second IHS identity type on the second portion of the multiple motherboards; and store second product line firmware via non-volatile memory media of the second portion of the multiple motherboards.

System and method of utilizing information handling system identity types with motherboards of information handling systems

A boot option system includes a pre-boot execution environment system coupled to a server device through a network. The server device creates a device placeholder boot option including a device path terminating at a storage controller in the server device. During a first boot and based on first boot instructions received from the pre-boot execution environment system, the server device moves the device placeholder boot option to a desired location within a boot sequence for the server device. During a second boot and based on second boot instructions received from the pre-boot execution environment system, the server device provides an operating system on the server device. The server device then replaces, at the desired location within the boot sequence, the device placeholder boot option with an operating system boot option that was provided on the server device in response to the provisioning of the operating system on the server device.

Placeholder boot option and boot option replacement system

An information handling system may include a processor, and a cryptoprocessor comprising at least one storage location. The information handling system may be configured to: store, in the at least one storage location, cryptographic data regarding secure boot of the information handling system; receive an indication that a lockdown is to be initiated; in response to the indication, overwrite the at least one storage location with invalid data; and initiate the lockdown by triggering a reboot of the information handling system.

System lockdown and data protection

A BIOS platform configuration system includes a BIOS coupled to hardware subsystems. During initialization operations, the BIOS communicates with each of the hardware subsystems and retrieves respective hardware subsystem information that is associated with each of the hardware subsystems and that describes at least a portion of a communication route between that hardware subsystem and at least one other hardware subsystem. The BIOS then combines the respective hardware subsystem information that is associated with each of the hardware subsystems to generate configuration information that describes complete communication routes between each of the hardware subsystems, and configures at least one of the hardware subsystems using the configuration information. In a specific example, the configuration information may provide a processing subsystem/chipset initialization table that is used initialize a processing subsystem/chipset in order to allow it to communicate with a device connected to a planar subsystem/motherboard that includes the processing system/chipset.

Automated bios platform configuration system

Systems and methods for enabling license management in pre-boot environments are described. In some embodiments, a method may include: loading, by a Basic System Input/Output (BIOS) of an Information Handling System (IHS), prior to the booting of any Operating System (OS) by the IHS, a license manager Unified Extensible Firmware Interface (UEFI) driver; and executing, by the BIOS, a command received from a component or device coupled to the IHS following a license management protocol provided by the UEFI driver, where the command is to obtain or verify license data.

License management in pre-boot environments

An information handling system includes a dual in-line memory module (DIMM) coupled to a memory controller via a memory channel. A processor during a first in time boot process of the information handling system determines a first environmental condition of the information handling system, and initializes the memory controller and the DIMM to determine a first set of initialization parameters for the memory controller and the DIMM. During a second in time boot process of the information handling system, the processor determines if a second environmental condition is different than the first environmental condition, if the second environmental condition is not different then to continue the second in time boot process without initializing the memory controller and the DIMM, and if the second environmental condition is different then to initialize the memory controller and the DIMM to determine a second set of initialization parameters for the memory controller and the DIMM.

Dual inline memory module with multiple boot processes based on first and second environmental conditions

An information handling system includes a dual in-line memory module (DIMM) coupled to a memory controller. The memory controller provides interrupts to a processor each time a read transaction from the DIMM results in a correctable read error. The processor instantiates a failure predictor that receives the interrupts, accumulates a count of the interrupts, and provides an error indication when the count exceeds an error threshold. In accumulating the count, the failure predictor increments the count each time the predictor receives a particular interrupt and decrements the count in accordance with an error leak rate. The error leak rate has a first value when a training coefficient for the DIMM is greater than a deviation threshold, and has a second value when the training coefficient for the DIMM is less than the deviation threshold.

System and method for improved handling of memory failures

A BIOS setting modification system is provided in a computing device. During a computing device runtime for the computing device, an Out-Of-Band (OOB) controller device receives a first BIOS setting modification request and, in response, generates first BIOS setting modification information and causes the transmission of a System Management Interrupt (SMI). During the computing device runtime for the computing device, an SMI handler subsystem in the computing device retrieves, in response to the SMI, the first BIOS setting modification information, either directly from the OOB controller device, or from a storage subsystem in which it was provided by the OOB controller device. The SMI handler subsystem then applies the first BIOS setting modification information to at least one subsystem in the computing device such that a first BIOS setting modification provided by the first BIOS setting modification information takes effect during the computing device runtime for the computing device.

BIOS setting modification system

Automated BIOS platform configuration system

An information handling system includes a storage device and a processor. The storage device includes a boot image for the information handling system. The processor determines an architectural location for a boot device for the information handling system, determines that the storage device is located at the architectural location of the information handling system, determines a unique identifier for the storage device, determines from a basic input/output system (BIOS) of the information handling system a BIOS identifier associated with the unique identifier, and places the BIOS identifier at the top of a BIOS boot order list.

Boot disk detection and management in an information handling system manufacturing environment

A system, method, and computer-readable medium are disclosed for a boot mapping system. More specifically, in certain embodiments, BIOS of an information handling system includes a boot mapping system which allows the information handling system to boot up regardless of a boot order change in a network mode of operation or a BIOS boot order change. Additionally, in certain embodiments, the boot mapping system further includes a service location protocol (SLP) which locates operating system images based on the type of network protocol selected for deployment.

System and method to perform an OS boot using service location protocol and launching OS using a dynamic update of network boot order without a reboot

In accordance with embodiments of the present disclosure, an information handling system may include a processor and a memory communicatively coupled to the processor, the memory having stored thereon a basic input/output system (BIOS) comprising a program of instructions executable by the processor for initializing one or more information handling resources of the information handling system during boot up or power on of the information handling system. The memory may comprise a plurality of firmware volumes comprising at least a first firmware volume having stored therein one or more components of the BIOS having a first expected update frequency and a second firmware volume having stored therein one or more components of the BIOS having a second expected update frequency less than that of the first expected update frequency.

Systems and methods for bios update optimization

In accordance with these and other embodiments of the present disclosure, a method may include receiving at a management controller of an information handling system a request for remote boot of the information handling system from a remote target communicatively coupled to a network interface of a host system comprising the network interface and a host system processor communicatively coupled to the network interface and the management controller, configuring the network interface for remote boot via the network interface, and issuing an instruction to reboot the host system, wherein receipt of the request for remote boot, configuration of the network interface for remote boot, and issuance of the instruction to reboot the host system are performed without an intervening boot of the host system.

Systems and methods for configuring bootable network target for boot in a single reboot

A method and an information handling system (IHS) perform server boot failure recovery by disabling failed devices and/or failed functions within functional devices. According to one aspect, a processor-executed fault isolation module (FIM) initiates calls to detected devices during a binding phase. The FIM identifies devices corresponding to successfully completed calls as operational devices, and identifies devices corresponding to failed calls as failed devices. Following completion of the binding phase, the FIM initiates calls, via a pre-boot application, to individual protocol functions of each operational device identified during the binding phase. If a first protocol call to a first operational device is successfully completed, the FIM identifies a protocol function(s) corresponding to the first protocol call as an operational function(s). If a second protocol call fails, the FIM identifies a corresponding protocol function(s) as a failed function(s) and isolates failed functions from operational functions for the first operational device.

Automatic mapping out of the faulty device/drivers during system boot-up

Growing community of inventors

Austin, TX, United States of America

Mark W Shutt