Boot Order Modification for Firmware Driver Dependency Handling

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods lack automatic mechanisms for updating host operating system drivers to resolve firmware dependencies during BIOS or firmware updates from a bootable image file, potentially leading to system failures if firmware-dependent drivers are boot-critical.

Innovation Solution

A method that determines if operating system driver updates are boot-critical, modifies the boot order to fetch and apply driver update packages from an update partition, and applies firmware updates while ensuring the system can boot correctly, either by prioritizing driver updates when critical or applying them sequentially.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If firmware updates are applied from a bootable image file, then firmware update capability is improved, but system reliability deteriorates if boot-critical drivers are not updated

Engineering Contradiction:

Improvefirmware update capabilityVSAvoidsystem boot reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary detection of boot-critical drivers before applying firmware updates. It identifies which drivers are required for system booting and updates them first from the bootable image file, ensuring that the operating system can successfully boot after firmware updates are applied.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The update process is segmented into distinct phases: first updating boot-critical drivers, then updating non-boot-critical drivers, and finally applying firmware updates. This segmentation ensures that critical system components are updated in the correct sequence to maintain system reliability.

Inventive Principle:

Principle #1Segmentation

2Reliability

If automatic driver update mechanisms are implemented, then system reliability is improved, but device complexity increases

Engineering Contradiction:

Improvedriver compatibilityVSAvoidupdate mechanism complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service functionality where the operating system automatically detects driver update requirements, fetches appropriate drivers from the bootable image file, and applies updates without user intervention. The system autonomously manages the entire driver update process based on firmware update requirements.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system incorporates feedback mechanisms where the operating system communicates driver version information and update requirements back to the firmware update process. This feedback loop enables automatic determination of which drivers need updating and ensures compatibility between firmware and driver versions.

Inventive Principle:

Principle #23Feedback

3Reliability

If boot order is modified to prioritize driver updates, then driver update reliability is improved, but update time increases

Engineering Contradiction:

Improvedriver update success rateVSAvoidsystem boot time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system uses periodic boot actions where the boot order is temporarily modified only when driver updates are required. After successful driver updates, the system reverts to the normal boot order, minimizing the impact on regular system operations while ensuring updates occur when necessary.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS10810017B2Systems and methods for handling firmware driver dependencies in host operating systems while applying updates from bootable image file

Publication Date: 2020.10.20 DELL PROD LP

AI summary

A bootable update image file may be configured to, if operating system driver updates associated with a firmware update are boot-critical: modify a boot order of the information handling system to cause the information handling system to boot to an operating system of the information handling system such that the operating system fetches driver update packages from an update partition of the information handling system, applies the driver update packages, and modifies the boot order to cause the information handling system to boot to the bootable image file in a subsequent boot and in the subsequent boot, apply the firmware update; and, if driver updates are non-boot-critical: apply the firmware update and modify the boot order to cause the information handling system to boot to the operating system such that the operating system fetches the driver update packages from an update partition and applies the driver update packages.