UEFI Safe Mode
Publication Date: 2012-Oct-31
The IP.com Prior Art Database
Disclosed is UEFI Safe Mode which allows users to boot up a crashed system by only loading necessary drivers and protocols at firmware level. Therefore, the crashed system is more likely to enter a specific stage for users to debug or update it. UEFI Safe Mode may be triggered by the following events: a number of failed boot, timeout, configuration assigned from system management controller, a jumper, or a button.
Page 01 of 1
UEFI Safe Mode
In current system design, if the users fail to boot up a system due to hardware fault or any other unknown reason, it would be hard for the users to acknowledge what goes wrong or how to fix it. To achieve reliability, this disclosure provides a possibility for the users to at least boot up the system to a certain level, so that they can update system firmware, update drivers, or make some investigation once they need.
This new mechanism presented here, which allows users to boot up a crashed system, is named UEFI Safe Mode. It may accompany with or without a system management controller. When the system enters UEFI Safe Mode, only those necessary drivers, protocols, and functionality fulfilling the minimum requirement to boot up a system are loaded. This makes the system much more likely to enter a specific stage than which loads all of them. Thus the users can debug, check system event log, and update the system, etc.
UEFI Safe Mode may be triggered by a certain times of failed boot, by a timer (such as watchdog timer), by a setting in the system management controller (such as BMC), by a special jumper on board, or by a special button on the system.
UEFI Safe Mode only loads those indispensable drivers and protocols, and disable all of the unnecessary chipset or CPU functionality (such as performance or power-saving). Those drivers and protocols to load, and the functionality to disable in this mode may be pre-defined. The system may allow only...