A method, device and equipment for generating a startup item in a traditional startup guide mode

Abstract

The application belongs to the technical field of BIOS, and specifically provides a method, device and system for generating a starting item in a traditional starting guide mode, which comprises the following steps: when it is judged that an OPROM maintenance table is not maintained, OPRMs of all peripherals are acquired, and the OPROM size of each peripheral is saved to the OPROM maintenance table; when it is judged that all OPROM sizes are greater than or equal to a set threshold, prompt information is output according to the OPROM maintenance table; whether the device not placed in the shadow memory is a device for generating a starting item is judged according to the prompt information; if yes, whether the device is replaced is selected; when the device is not replaced, the device which does not need to generate a starting item is selected to update the OPROM maintenance table; the server is restarted; if no, the prompt information is ignored, and the booting is continued until the booting is completed. The problem that a starting item cannot be generated when the customer storage devices are too many is solved.

Description

Technical Field

[0001] This invention relates to the field of BIOS technology, and more specifically to a method, apparatus, and device for generating boot entries under a traditional boot mode. Background Technology

[0002] BIOS (Basic Input / Output System) is a set of programs embedded in a ROM chip on the computer's motherboard. It stores the computer's most important basic input / output programs, power-on self-test (POST) programs, and system boot programs. It can read and write specific system settings from the CMOS. Its main function is to provide the lowest-level, most direct hardware settings and control for the computer. Simply put, it's the first program to start after the computer is turned on, preparing for the operating system to boot. This includes initializing the CPU, memory, motherboard, and other components, and then loading the operating system into memory. This process is the entire journey from pressing the power button to finally entering the operating system.

[0003] BIOS boot modes are divided into two types: UEFI and Legacy. UEFI is a new type of BIOS, characterized by fast boot speed, high security, and support for large-capacity hard drives. Legacy refers to the traditional BIOS boot mode. A system installed in UEFI mode can only be booted in UEFI mode; similarly, a system installed in Legacy mode can only be booted in Legacy mode.

[0004] Current server BIOSes include both UEFI and Legacy boot modes, which can be switched via options. Legacy, as a traditional BIOS, has several drawbacks. For example, Shadow RAM occupies a portion of the system's main memory address space. Its address range is C0000~FFFFF, which is 768KB~1024KB of 1MB main memory. The function of Shadow RAM is to store the contents of various ROM BIOS files. In other words, the contents of Shadow RAM are copies of the ROM BIOS. The ten 16KB blocks from C8000 to EFFFF can be used as the shadow area for other adapters' ROM BIOS. It generally stores the OPROMs of various peripherals. For early servers, due to the small number of peripherals, this area occupied relatively little space, so it was sufficient. However, with the gradual increase in peripherals and the continuous upgrading of various device firmware, this area has become overflowing, leading to problems with boot entries not being generated. Summary of the Invention

[0005] Shadow RAM typically stores the OPROM of various peripherals. For early servers, due to the small number of peripherals, this area was relatively small and sufficient. However, with the increasing number of peripherals and the continuous upgrading of various device firmware, this area has become overflowing, leading to the inability to generate boot entries. This invention provides a method, apparatus, and device for generating boot entries under traditional boot mode.

[0006] In a first aspect, the present invention provides a method for generating boot entries under a traditional boot mode, comprising the following steps:

[0007] During the BIOS POST process in the traditional boot mode, when it is determined that the OPROM maintenance table has not been fully maintained, the ORPM of all peripherals is obtained and the OPROM size of each peripheral is saved to the OPROM maintenance table.

[0008] When all OPROM sizes are greater than or equal to a set threshold, output a prompt message based on the OPROM maintenance table;

[0009] Based on the prompt information, determine whether the device not placed in the shadow memory is the device that generated the boot entry;

[0010] If so, choose whether to replace the equipment;

[0011] When not replacing the device, select the device that does not need to generate a boot entry and update the OPROM maintenance table;

[0012] When the server restarts, the following steps are executed: If the OPROM maintenance table is not fully maintained, obtain the ORPPM of all peripherals and save the OPROM size of each peripheral to the OPROM maintenance table.

[0013] If not, ignore the prompt message and continue booting until booting is complete.

[0014] As a further limitation of the technical solution of the present invention, the method includes:

[0015] After the OPROM maintenance table is completed, set the value of the maintenance completion flag.

[0016] As a further limitation of the technical solution of the present invention, the method further includes:

[0017] After the OPROM maintenance table is maintained, set the field value for whether to store it in shadow memory.

[0018] As a further limitation of the technical solution of the present invention, in the BIOS POST process under the traditional boot mode, when it is determined that the OPROM maintenance table has not been fully maintained, the steps of obtaining the ORPPM of all peripherals and saving the OPROM size of each peripheral to the OPROM maintenance table include:

[0019] During the BIOS POST process in traditional boot mode, it is determined whether the maintenance completion flag of the OPROM maintenance table is 0;

[0020] If so, retrieve the ORPPM of all peripherals and save it to the OPROM maintenance table, and set the maintenance completion flag to 1; at the same time, set the field value for whether to store it in shadow memory to 1;

[0021] If not, fill the shadow memory according to the OPROM maintenance table.

[0022] As a further limitation of the technical solution of the present invention, the step of outputting a prompt message when determining that the size of all OPROMs is greater than or equal to a set threshold includes:

[0023] When the field value for whether to store in shadow memory is 1, check whether the size of all OPROMs is less than the set threshold.

[0024] If so, move the entire OPROM maintenance table into shadow memory;

[0025] If not, output a prompt message.

[0026] As a further limitation of the technical solution of the present invention, the step of selecting whether to replace the equipment includes:

[0027] If not, select the device that does not need to generate a boot entry to update the OPROM maintenance table;

[0028] The value of the field indicating whether the selected device settings should be placed in shadow memory is 0;

[0029] If so, shut down the server and replace or reduce equipment as needed;

[0030] Execution steps: Configure server restart.

[0031] As a further limitation of the technical solution of the present invention, the method also includes:

[0032] When the BIOS receives a clear command, the BIOS boot process will first clear all data in the OPROM maintenance table and set the maintenance completion flag to 0.

[0033] As a further limitation of the technical solution of the present invention, the method also includes:

[0034] When the configuration changes or needs to be reset, the BMC sends a clear command to the BIOS via the IPMI command.

[0035] Secondly, the present invention also provides a device for generating boot items in a traditional boot mode, including an OPROM maintenance table setting module, an output prompt module, an update module, and a restart setting module;

[0036] The OPROM maintenance table setting module is used to determine the OPROM maintenance table in the traditional boot mode during the BIOS POST process if the OPROM maintenance table has not been maintained. It then obtains the ORPPM of all peripherals and saves the OPROM size of each peripheral to the OPROM maintenance table.

[0037] The output prompt module is used to output prompt information according to the OPROM maintenance table when all OPROM sizes are greater than or equal to a set threshold.

[0038] The update module is used to determine, based on the prompt information, whether the device not placed in the shadow memory is the device that generates the boot entry, and when the device is not selected to be changed, to select the device that does not need to generate the boot entry to update the OPROM maintenance table.

[0039] The restart settings module is used to configure the server to restart after the OPROM maintenance table update is completed.

[0040] As a further limitation of the technical solution of the present invention, the device includes an identifier setting module and a field value setting module;

[0041] The flag setting module is used to set the value of the maintenance completion flag after the OPROM maintenance table is maintained.

[0042] The field value setting module sets whether to store field values ​​in shadow memory after the OPROM maintenance table is completed.

[0043] As a further limitation of the technical solution of the present invention, the device also includes an identifier bit determination module and a writing module;

[0044] The flag bit judgment module is used to obtain the maintenance completion flag bit during the BIOS POST process in the traditional boot mode and to determine whether the maintenance completion flag bit of the OPROM maintenance table is 0.

[0045] The OPROM maintenance table setting module is used to obtain the ORPPM of all peripherals and save it to the OPROM maintenance table. The flag setting module sets the maintenance completion flag to 1. At the same time, the field value setting module sets the field value of whether to store in shadow memory to 1.

[0046] The write module is used to fill the shadow memory according to the OPROM maintenance table when the maintenance completion flag is 1.

[0047] As a further limitation of the technical solution of the present invention, the device also includes a first judgment module, which is used to determine whether the size of all OPROMs is less than a set threshold when the field value of whether it is stored in the shadow memory is 1.

[0048] The write module is used to put the entire OPROM maintenance table into shadow memory when the output OPROM size from the first judgment module is less than a set threshold.

[0049] As a further limitation of the technical solution of the present invention, the device also includes an equipment reduction module, used to replace or reduce equipment as needed.

[0050] The update module is specifically used to select devices that do not require the generation of boot entries to update the OPROM maintenance table;

[0051] The field value setting module specifies whether the selected device setting should be placed in shadow memory; the field value is 0.

[0052] As a further limitation of the technical solution of the present invention, the device also includes a clear setting module, which, when a clear command is received, will first clear all data in the OPROM maintenance table during the BIOS boot process, and trigger the flag bit judgment module to set the maintenance completion flag bit to 0.

[0053] Thirdly, the technical solution of the present invention also provides a system for generating boot entries under the traditional boot mode, including BIOS and BMC communicating with BIOS;

[0054] When the configuration changes or needs to be reset, the BMC sends a clear command to the BIOS via the IPMI command.

[0055] When the BIOS receives a clear command, the boot process will first clear all data in the OPROM maintenance table and trigger the flag bit judgment module to set the maintenance completion flag bit to 0.

[0056] The BIOS includes an OPROM maintenance table setting module, an output prompt module, an update module, and a restart setting module;

[0057] The OPROM maintenance table setting module is used to determine the OPROM maintenance table in the traditional boot mode during the BIOS POST process if the OPROM maintenance table has not been maintained. It then obtains the ORPPM of all peripherals and saves the OPROM size of each peripheral to the OPROM maintenance table.

[0058] The output prompt module is used to output prompt information according to the OPROM maintenance table when all OPROM sizes are greater than or equal to a set threshold.

[0059] The update module is used to determine, based on the prompt information, whether the device not placed in the shadow memory is the device that generates the boot entry, and when the device is not selected to be changed, to select the device that does not need to generate the boot entry to update the OPROM maintenance table.

[0060] The restart settings module is used to configure the server to restart after the OPROM maintenance table update is completed.

[0061] As a further limitation of the technical solution of the present invention, the device includes an identifier setting module and a field value setting module;

[0062] The flag setting module is used to set the value of the maintenance completion flag after the OPROM maintenance table is maintained.

[0063] The field value setting module sets whether to store field values ​​in shadow memory after the OPROM maintenance table is completed.

[0064] As a further limitation of the technical solution of the present invention, the device also includes an identifier bit determination module and a writing module;

[0065] The flag bit judgment module is used to obtain the maintenance completion flag bit during the BIOS POST process in the traditional boot mode and to determine whether the maintenance completion flag bit of the OPROM maintenance table is 0.

[0066] The OPROM maintenance table setting module is used to obtain the ORPPM of all peripherals and save it to the OPROM maintenance table. The flag setting module sets the maintenance completion flag to 1. At the same time, the field value setting module sets the field value of whether to store in shadow memory to 1.

[0067] The write module is used to fill the shadow memory according to the OPROM maintenance table when the maintenance completion flag is 1.

[0068] As a further limitation of the technical solution of the present invention, the device also includes a first judgment module, which is used to determine whether the size of all OPROMs is less than a set threshold when the field value of whether it is stored in the shadow memory is 1.

[0069] The write module is used to put the entire OPROM maintenance table into shadow memory when the output OPROM size from the first judgment module is less than a set threshold.

[0070] As a further limitation of the technical solution of the present invention, the device also includes an equipment reduction module, used to replace or reduce equipment as needed.

[0071] The update module is specifically used to select devices that do not require the generation of boot entries to update the OPROM maintenance table;

[0072] The field value setting module specifies whether the selected device setting should be placed in shadow memory; the field value is 0.

[0073] As can be seen from the above technical solutions, the present invention has the following advantages: it solves the problem of not being able to generate startup items when customers have too many storage devices, making customers more satisfied and enabling us to be more competitive in the industry.

[0074] Furthermore, the design principle of this invention is reliable, the structure is simple, and it has a very wide range of application prospects.

[0075] Therefore, it is evident that the present invention has outstanding substantive features and significant progress compared with the prior art, and the beneficial effects of its implementation are also obvious. Attached Figure Description

[0076] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0077] Figure 1 This is a schematic flowchart of a method according to an embodiment of the present invention.

[0078] Figure 2 This is a schematic flowchart of a method according to another embodiment of the present invention.

[0079] Figure 3 This is a schematic block diagram of an apparatus according to an embodiment of the present invention. Detailed Implementation

[0080] Current server BIOSes include both UEFI and Legacy boot modes, which can be switched via options. Legacy, as a traditional BIOS, has several drawbacks. For example, Shadow RAM occupies a portion of the system's main memory address space. Its address range is C0000~FFFFF, which is 768KB~1024KB of 1MB main memory. The function of Shadow RAM is to store the contents of various ROM BIOS files. In other words, the contents of Shadow RAM are copies of the ROM BIOS. The ten 16KB blocks from C8000 to EFFFF can be used as the shadow area for other adapters' ROM BIOS. It generally stores the OPROMs of various peripherals. For early servers, due to the small number of peripherals, this area occupied relatively little space, so it was sufficient. However, with the gradual increase in peripherals and the continuous upgrading of various device firmware, this area has become overflowing, leading to problems with boot entries not being generated.

[0081] To enable those skilled in the art to better understand the technical solutions of this invention, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this invention.

[0082] like Figure 1 As shown, this embodiment of the invention provides a method for generating boot entries in a traditional boot mode, comprising the following steps:

[0083] Step 1: During the BIOS POST process in the traditional boot mode, when it is determined that the OPROM maintenance table has not been fully maintained, the ORPPM of all peripherals is obtained and the OPROM size of each peripheral is saved to the OPROM maintenance table.

[0084] Step 2: When all OPROM sizes are greater than or equal to the set threshold, output a prompt message according to the OPROM maintenance table;

[0085] Step 3: Determine whether the device not placed in shadow memory is the device that generated the boot entry based on the prompt information;

[0086] If so, proceed to step 4;

[0087] If not, proceed to step 7;

[0088] Step 4: Choose whether to replace the equipment;

[0089] Step 5: When not replacing the device, select the device that does not need to generate a boot entry and update the OPROM maintenance table;

[0090] Step 6: Configure the server to restart, then execute step 2;

[0091] Step 7: Ignore the prompts and continue booting until booting is complete.

[0092] like Figure 2 As shown, this embodiment of the invention provides a method for generating boot entries in a traditional boot mode, comprising the following steps:

[0093] S1: When the server is powered on, the BIOS switches the boot mode to the traditional boot mode. During the BIOS POST process, it checks whether the maintenance completion flag of the OPROM maintenance table is 0.

[0094] If not, proceed to step S2;

[0095] If so, proceed to step S3;

[0096] S2: Fill the shadow memory according to the OPROM maintenance table; proceed to step S14;

[0097] S3: Obtain the ORPPM of all peripherals and save it to the OPROM maintenance table, and set the maintenance completion flag to 1; at the same time, set the field value of whether to store in shadow memory to 1;

[0098] S4: Determine if the size of all OPROMs is less than the set threshold;

[0099] If so, proceed to step S5;

[0100] If not, proceed to step S6;

[0101] S5: Load the entire OPROM maintenance table into shadow memory; execute step S14;

[0102] S6: Output prompt information based on the OPROM maintenance table;

[0103] S7: Determine whether the device not placed in the shadow memory is the device that generated the boot entry based on the prompt information;

[0104] If so, execute S9;

[0105] If not, proceed to S8;

[0106] S8: Ignore the prompt message and continue booting; proceed to step S14;

[0107] S9: Select whether to replace the equipment;

[0108] If not, proceed to step S10;

[0109] If so, proceed to step S13;

[0110] S10: Select devices that do not require startup entries to update the OPROM maintenance table;

[0111] S11: Whether the selected device settings are placed in shadow memory; the field value is 0.

[0112] S12: Configure server restart; execute step S1;

[0113] S13: Set the server to shut down, and replace or reduce equipment as needed; proceed to step S12.

[0114] S14: Booting complete, end.

[0115] In some embodiments, the method further includes:

[0116] When the BIOS receives a clear command, the BIOS boot process will first clear all data in the OPROM maintenance table and set the maintenance completion flag to 0.

[0117] The specific implementation process includes: 1) The server powers on, and the BIOS switches the boot mode to the legacy boot mode. 2) During the BIOS POST process, it checks if the flag in the OPROM maintenance table is 0. If flag = 0, when polling each peripheral, it retrieves the OPROM of all peripherals and saves the OPROM size of each peripheral to the OPROM maintenance table. The field indicating whether to place the device in the Shadow area is set to 1 by default. If flag = 1, it means that the Shadow area data has already been set, and the Shadow area will be filled according to the OPROM maintenance table, continuing to step 6). Here, flag is the maintenance completion flag. 3) It checks if the size of all OPROMs is less than 160K. If "yes", no processing is done, and all are placed in the Shadow area. If "no", a prompt message is displayed according to the OPROM maintenance table, including information about each peripheral, OPROM size, total OPROM size, devices already placed in the Shadow area, and devices not placed in the Shadow area. 4) Select whether to accept. According to the prompt, you can see the devices not placed in the Shadow area. If you don't care about whether a boot entry is generated for a device, you can accept it by selecting "Yes" and ignoring the prompt to continue booting and skip to step 6). If you care, select "No". 5) Select whether to replace the device. If you want to replace or reduce the device, select "Yes". The server will shut down. Replace or reduce the device as needed and then power on. If you select "No", for devices that do not need to generate boot entries, such as data disks and network cards that do not need boot entries, you can choose not to place the device in the Shadow RAM area. After clicking OK, the OPROM maintenance table will be updated. For the selected device, the "Whether to place in Shadow area" field will be set to 0. The next time you boot, the device excluded from the OPROM maintenance table will be ignored, and the Shadow RAM area will no longer store the OPROM of that device. Restart and skip to step 2). 6) End.

[0118] like Figure 3 As shown, this embodiment of the invention also provides an apparatus for generating boot items in a conventional boot mode, including an OPROM maintenance table setting module, an output prompt module, an update module, and a restart setting module;

[0119] The OPROM maintenance table setting module is used to determine the OPROM maintenance table in the traditional boot mode during the BIOS POST process if the OPROM maintenance table has not been maintained. It then obtains the ORPPM of all peripherals and saves the OPROM size of each peripheral to the OPROM maintenance table.

[0120] The output prompt module is used to output prompt information according to the OPROM maintenance table when all OPROM sizes are greater than or equal to a set threshold.

[0121] The update module is used to determine, based on the prompt information, whether the device not placed in the shadow memory is the device that generates the boot entry, and when the device is not selected to be changed, to select the device that does not need to generate the boot entry to update the OPROM maintenance table.

[0122] The restart settings module is used to configure the server to restart after the OPROM maintenance table update is completed.

[0123] This invention also provides an apparatus for generating boot items in a conventional boot mode, including an OPROM maintenance table setting module, an output prompt module, an update module, and a restart setting module;

[0124] The OPROM maintenance table setting module is used to determine the OPROM maintenance table in the traditional boot mode during the BIOS POST process if the OPROM maintenance table has not been maintained. It then obtains the ORPPM of all peripherals and saves the OPROM size of each peripheral to the OPROM maintenance table.

[0125] The output prompt module is used to output prompt information according to the OPROM maintenance table when all OPROM sizes are greater than or equal to a set threshold.

[0126] The update module is used to determine, based on the prompt information, whether the device not placed in the shadow memory is the device that generates the boot entry, and when the device is not selected to be changed, to select the device that does not need to generate the boot entry to update the OPROM maintenance table.

[0127] The restart settings module is used to configure the server to restart after the OPROM maintenance table update is completed.

[0128] The device includes an identifier setting module and a field value setting module;

[0129] The flag setting module is used to set the value of the maintenance completion flag after the OPROM maintenance table is maintained.

[0130] The field value setting module sets whether to store field values ​​in shadow memory after the OPROM maintenance table is completed.

[0131] The device also includes an identifier determination module and a writing module;

[0132] The flag bit judgment module is used to obtain the maintenance completion flag bit during the BIOS POST process in the traditional boot mode and to determine whether the maintenance completion flag bit of the OPROM maintenance table is 0.

[0133] The OPROM maintenance table setting module is used to obtain the ORPPM of all peripherals and save it to the OPROM maintenance table. The flag setting module sets the maintenance completion flag to 1. At the same time, the field value setting module sets the field value of whether to store in shadow memory to 1.

[0134] The write module is used to fill the shadow memory according to the OPROM maintenance table when the maintenance completion flag is 1.

[0135] The device also includes a first judgment module, which is used to determine whether the size of all OPROMs is less than a set threshold when the field value of whether it is stored in the shadow memory is 1.

[0136] The write module is used to put the entire OPROM maintenance table into shadow memory when the output OPROM size from the first judgment module is less than a set threshold.

[0137] The device also includes an equipment reduction module for replacing or reducing equipment as needed;

[0138] The update module is specifically used to select devices that do not require the generation of boot entries to update the OPROM maintenance table;

[0139] The field value setting module specifies whether the selected device setting should be placed in shadow memory; the field value is 0.

[0140] As a further limitation of the technical solution of the present invention, the device also includes a clear setting module, which, when a clear command is received, will first clear all data in the OPROM maintenance table during the BIOS boot process, and trigger the flag bit judgment module to set the maintenance completion flag bit to 0.

[0141] This invention also provides a system for generating boot entries under conventional boot mode, including a BIOS and a BMC that communicates with the BIOS;

[0142] When the configuration changes or needs to be reset, the BMC sends a clear command to the BIOS via the IPMI command.

[0143] When the BIOS receives a clear command, the boot process will first clear all data in the OPROM maintenance table and trigger the flag bit judgment module to set the maintenance completion flag bit to 0.

[0144] The specific implementation process on the BIOS side includes: 1) When the server powers on, the BIOS switches the boot mode to the legacy boot mode. 2) During the BIOS POST process, it checks if the flag in the OPROM maintenance table is 0. If flag = 0, when polling each peripheral, it retrieves the OPROM of all peripherals and saves the OPROM size of each peripheral to the OPROM maintenance table. The field indicating whether to place it in the Shadow area is set to 1 by default. If flag = 1, it means that the Shadow area data has already been set, and the Shadow area will be filled according to the OPROM maintenance table, continuing to step 6). Here, flag is the maintenance completion flag. 3) It checks if the size of all OPROMs is less than 160K. If "yes", no processing is done, and all are placed in the Shadow area. If "no", a prompt message is displayed according to the OPROM maintenance table, including information about each peripheral, OPROM size, total OPROM size, devices already placed in the Shadow area, and devices not placed in the Shadow area. 4) Select whether to accept. According to the prompt, you can see the devices not placed in the Shadow area. If you don't care about whether a boot entry is generated for a device, you can accept it by selecting "Yes" and ignoring the prompt to continue booting and skip to step 6). If you care, select "No". 5) Select whether to replace the device. If you want to replace or reduce the device, select "Yes". The server will shut down. Replace or reduce the device as needed and then power on. If you select "No", for devices that do not need to generate boot entries, such as data disks and network cards that do not need boot entries, you can choose not to place the device in the Shadow RAM area. After clicking OK, the OPROM maintenance table will be updated. For the selected device, the "Whether to place in Shadow area" field will be set to 0. The next time you boot, the device excluded from the OPROM maintenance table will be ignored, and the Shadow RAM area will no longer store the OPROM of that device. Restart and skip to step 2). 6) End.

[0145] The specific execution process at the BMC end includes:

[0146] This option enables or disables clearing the Shadow area configuration. If the configuration changes or needs to be reset, select "Clear". The BMC sends a clear command to the BIOS via IPMI. During the BIOS boot process, all data in the OPROM maintenance table will be cleared first, and the flag will be set to 0. End.

[0147] Although the present invention has been described in detail with reference to the accompanying drawings and preferred embodiments, the invention is not limited thereto. Various equivalent modifications or substitutions can be made to the embodiments of the invention by those skilled in the art without departing from the spirit and essence of the invention, and such modifications or substitutions should all be within the scope of the invention. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the invention should also be covered within the protection scope of the invention. Therefore, the protection scope of the invention should be determined by the scope of the claims.

Claims

1. A method for generating boot entries under a traditional boot loader mode, characterized in that, Includes the following steps: During the BIOS POST process in the traditional boot mode, when it is determined that the OPROM maintenance table has not been fully maintained, the ORPM of all peripherals is obtained and the OPROM size of each peripheral is saved to the OPROM maintenance table. When all OPROM sizes are greater than or equal to a set threshold, output a prompt message based on the OPROM maintenance table; Based on the prompt information, determine whether the device not placed in the shadow memory is the device that generated the boot entry; If so, choose whether to replace the equipment; When not replacing the device, select the device that does not need to generate a boot entry and update the OPROM maintenance table; When the server restarts, the following steps are executed: If the OPROM maintenance table is not fully maintained, obtain the ORPPM of all peripherals and save the OPROM size of each peripheral to the OPROM maintenance table. If not, ignore the prompt message and continue booting until booting is complete; This method includes: setting the value of the maintenance completion flag after the OPROM maintenance table is maintained; The method further includes: after the OPROM maintenance table is maintained, setting the field value of whether the OPROM maintenance table is stored in shadow memory; In the traditional boot mode BIOS POST process, when it is determined that the OPROM maintenance table has not been fully maintained, the steps to obtain the ORPPM of all peripherals and save the OPROM size of each peripheral to the OPROM maintenance table include: During the BIOS POST process in traditional boot mode, it is determined whether the maintenance completion flag of the OPROM maintenance table is 0; If so, obtain the ORPPM of all peripherals and save the OPROM size of each peripheral to the OPROM maintenance table, and set the maintenance completion flag to 1; at the same time, set the field value of whether to store in shadow memory to 1; If not, fill the shadow memory according to the OPROM maintenance table; The steps to output a prompt message when determining that the size of all OPROMs is greater than or equal to a set threshold include: When the field value for whether to store in shadow memory is 1, check whether the size of all OPROMs is less than the set threshold. If so, move the entire OPROM maintenance table into shadow memory; If not, output a prompt message; The step of determining whether a device not placed in shadow memory is a device that generates a boot entry based on the prompt information includes: if the prompt information shows devices not placed in shadow memory, select "Yes" for devices for which whether a boot entry is generated is not a concern.

2. The method for generating boot entries under the traditional boot loader mode according to claim 1, characterized in that, The steps following the decision on whether to replace the equipment include: If not, select the device that does not need to generate a boot entry to update the OPROM maintenance table; If the value of the field for setting the corresponding selected device to be placed in the shadow memory is 0, the corresponding selected device will be excluded from the OPROM maintenance table during the next boot, and the shadow memory will no longer store the OPROM of that device. If so, shut down the server and replace or reduce equipment as needed; Execution steps: Configure server restart.

3. The method for generating boot items under the traditional boot loader mode according to claim 2, characterized in that, The method also includes: When the BIOS receives a clear command, the BIOS boot process will first clear all data in the OPROM maintenance table and set the maintenance completion flag to 0.

4. The method for generating boot items under the traditional boot loader mode according to claim 3, characterized in that, The method also includes: When the configuration changes or needs to be reset, the BMC sends a clear command to the BIOS via the IPMI command.

5. A device for generating boot items in a traditional boot loader mode, characterized in that, Includes an OPROM maintenance table setting module, an output prompt module, an update module, and a restart setting module; The OPROM maintenance table setting module is used to determine the OPROM maintenance table in the traditional boot mode during the BIOS POST process if the OPROM maintenance table has not been maintained. It then obtains the ORPPM of all peripherals and saves the OPROM size of each peripheral to the OPROM maintenance table. The output prompt module is used to output prompt information according to the OPROM maintenance table when all OPROM sizes are greater than or equal to a set threshold. The update module is used to determine, based on the prompt information, whether the device not placed in the shadow memory is the device that generates the boot entry, and when the device is not selected to be changed, to select the device that does not need to generate the boot entry to update the OPROM maintenance table. The restart settings module is used to configure the server to restart after the OPROM maintenance table update is completed. The device is configured to perform the following: after the OPROM maintenance table is maintained, set the value of the maintenance completion flag bit; The device is also configured to perform the following: after the OPROM maintenance table is maintained, set the value of the field value for whether the OPROM maintenance table is stored in shadow memory; In the traditional boot mode BIOS POST process, when it is determined that the OPROM maintenance table has not been fully maintained, the steps to obtain the ORPPM of all peripherals and save the OPROM size of each peripheral to the OPROM maintenance table include: During the BIOS POST process in traditional boot mode, it is determined whether the maintenance completion flag of the OPROM maintenance table is 0; If so, obtain the ORPPM of all peripherals and save the OPROM size of each peripheral to the OPROM maintenance table, and set the maintenance completion flag to 1; at the same time, set the field value of whether to store in shadow memory to 1; If not, fill the shadow memory according to the OPROM maintenance table; The steps to output a prompt message when determining that the size of all OPROMs is greater than or equal to a set threshold include: When the field value for whether to store in shadow memory is 1, check whether the size of all OPROMs is less than the set threshold. If so, move the entire OPROM maintenance table into shadow memory; If not, output a prompt message; Based on the prompts, determine whether the device not placed in shadow memory is the device that generates a boot entry. This includes devices that are not placed in shadow memory and whose boot entry generation is not important to you. Select "Yes".

6. A system for generating boot entries under a traditional boot loader mode, characterized in that, This includes the BIOS and the BMC that communicates with the BIOS; When the configuration changes or needs to be reset, the BMC sends a clear command to the BIOS via the IPMI command. When the BIOS receives the clear command, the boot process will first clear all data in the OPROM maintenance table and trigger the flag bit judgment module to set the maintenance completion flag bit to 0; The BIOS includes an OPROM maintenance table setting module, an output prompt module, an update module, and a restart setting module; The OPROM maintenance table setting module is used to determine the OPROM maintenance table in the traditional boot mode during the BIOS POST process if the OPROM maintenance table has not been maintained. It then obtains the ORPPM of all peripherals and saves the OPROM size of each peripheral to the OPROM maintenance table. The output prompt module is used to output prompt information according to the OPROM maintenance table when all OPROM sizes are greater than or equal to a set threshold. The update module is used to determine, based on the prompt information, whether the device not placed in the shadow memory is the device that generates the boot entry, and when the device is not selected to be changed, to select the device that does not need to generate the boot entry to update the OPROM maintenance table. The restart settings module is used to configure the server to restart after the OPROM maintenance table update is completed. The system is configured to perform the following: after the OPROM maintenance table is maintained, set the value of the maintenance completion flag. The system is also configured to perform the following: after the OPROM maintenance table is maintained, set the value of the field indicating whether the OPROM maintenance table is stored in shadow memory; During the BIOS POST process in traditional boot mode, if it is determined that the OPROM maintenance table is not fully maintained, the ORPPM of all peripherals is obtained and the OPROM size of each peripheral is saved to the OPROM maintenance table, including: During the BIOS POST process in traditional boot mode, it is determined whether the maintenance completion flag of the OPROM maintenance table is 0; If so, obtain the ORPPM of all peripherals and save the OPROM size of each peripheral to the OPROM maintenance table, and set the maintenance completion flag to 1; at the same time, set the field value of whether to store in shadow memory to 1; If not, fill the shadow memory according to the OPROM maintenance table; The steps to output a prompt message when determining that the size of all OPROMs is greater than or equal to a set threshold include: When the field value for whether to store in shadow memory is 1, check whether the size of all OPROMs is less than the set threshold. If so, move the entire OPROM maintenance table into shadow memory; If not, output a prompt message; Based on the prompts, determine whether the device not placed in shadow memory is the device that generates a boot entry. This includes devices that are not placed in shadow memory and whose boot entry generation is not important to you. Select "Yes".

Images