Driver installation deployment method, device, system and equipment and storage medium

Abstract

The embodiment of the invention provides a driver installation and deployment method and device, equipment and a medium, and the method comprises the steps: generating a hardware out-of-core driver demand list containing a target hardware equipment identifier and corresponding manufacturer information through automatically obtaining hardware equipment information and recognizing target hardware equipment lacking a driver; based on the list, a hardware drive source code is directionally obtained, compiling, installing and deploying of a drive software package are completed, and the whole process has the functions of automatically recognizing hardware drive missing, automatically compiling and manufacturing the drive software package, automatically loading a drive and the like, so that the operating system installing and deploying efficiency is improved; according to the invention, the requirement of rapid installation and deployment of a large-scale system in a cloud scene can be met, the communication cost is greatly reduced, and the efficiency of driver adaptation in the installation and deployment process of the large-scale resource pool server operating system in the cloud scene is improved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a driver installation and deployment method, apparatus, system, device, and storage medium. Background Technology

[0002] With the development of cloud computing technology, the large-scale installation and deployment of operating systems on resource pool servers in cloud scenarios has become a necessary basic step in the construction of cloud platforms. However, during the large-scale installation and deployment of operating systems, it is common to encounter situations where the operating system lacks hardware device drivers, resulting in installation failure or the inability to use hardware devices without drivers after installation. The conventional solution is for integrators to contact hardware manufacturers to obtain driver source code, and the operating system manufacturers to compile and adapt the driver source code according to the operating system version to create driver packages. After obtaining the driver packages, the integrators install the drivers during the installation and deployment process. However, this method requires a large amount of manpower, has a large compilation workload, and is inefficient. Summary of the Invention

[0003] In view of the above problems, embodiments of the present invention are proposed to provide a drive installation and deployment method, apparatus, system, device and storage medium that overcomes or at least partially solves the above problems.

[0004] In a first aspect, embodiments of the present invention provide a driver installation and deployment method, including: Obtain hardware device information for each hardware device; Based on the hardware device information of each hardware device, determine whether there is a target hardware device lacking a driver; If there are target hardware devices that lack drivers, a hardware off-core driver requirement list is generated, which includes the missing hardware driver identifier and the corresponding manufacturer information. Based on the hardware external driver requirement list, obtain the corresponding hardware driver source code; Install and deploy the corresponding driver software package for the target hardware device based on the hardware driver source code.

[0005] Optionally, the hardware device information includes a manufacturer identification code, a subsystem manufacturer identification code, and a device identification code; determining whether there is a target hardware device lacking a driver based on the hardware device information of each hardware device includes: Determine whether the operating system on each hardware device provides a driver that matches the vendor identifier, the subsystem vendor identifier, and the device identifier; If the operating system of a target hardware device does not provide a driver that matches the vendor identifier, the subsystem vendor identifier, and the device identifier, then it is determined that there is a target hardware device lacking a driver.

[0006] Optionally, it also includes: If the operating systems on each of the hardware devices provide drivers that match the vendor identifier, the subsystem vendor identifier, and the device identifier, then it is determined that there is no target hardware device lacking a driver.

[0007] Optionally, obtaining the hardware device information of each hardware device includes: The hardware device information of each hardware device is obtained through the desktop management interface decoder.

[0008] Optionally, it also includes: Check whether the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions; The step of installing and deploying the corresponding driver software package on the target hardware device based on the hardware driver source code includes: If the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions, then the corresponding driver software package is installed and deployed on the target hardware device according to the hardware driver source code.

[0009] Optionally, it also includes: If the compatibility between the driver source code and the operating system on the target hardware device does not meet the preset conditions, a compatibility report is generated and output.

[0010] Optionally, detecting whether the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions includes: The compatibility between the driver source code and the operating system on the target hardware device is checked using the kernel application binary interface and the kernel application programming interface to determine whether the compatibility meets preset conditions.

[0011] Optionally, obtaining the corresponding hardware driver source code based on the hardware off-core driver requirement list includes: Obtain the hardware driver source code uploaded by the user based on the hardware driver identifier and the corresponding manufacturer information.

[0012] Optionally, obtaining the corresponding hardware driver source code based on the hardware off-core driver requirement list includes: Based on the hardware driver identifier and the corresponding manufacturer information, the corresponding official website address is retrieved using a preset model. Obtain the hardware driver source code from the official website address.

[0013] Optionally, it also includes: Obtain the operating system version information of each hardware device; Based on the operating system version information of each hardware device, different types of driver compilation environments are constructed.

[0014] Optionally, the step of installing and deploying the corresponding driver software package on the target hardware device according to the hardware driver source code includes: Determine the target driver compilation environment that matches the operating system of the target hardware device within the different types of driver compilation environments; The target driver compilation environment is used to install and deploy the corresponding driver software package based on the hardware driver source code.

[0015] Secondly, the present invention also discloses a drive installation and deployment device, the device comprising: The first acquisition module is used to acquire hardware device information of each hardware device. The judgment module is used to determine whether there is a target hardware device lacking a driver based on the hardware device information of each hardware device. The generation module is used to generate a hardware off-core driver requirement list if there are target hardware devices that lack drivers. The hardware off-core driver requirement list includes the missing hardware driver identifier and the corresponding manufacturer information. The second acquisition module is used to acquire the corresponding hardware driver source code based on the hardware external driver requirement list. The installation module is used to install and deploy the corresponding driver software package to the target hardware device based on the hardware driver source code.

[0016] Thirdly, the present invention also discloses a driver installation and deployment system, the system comprising: Multiple hardware devices; A driver installation and deployment platform, connected to the multiple hardware devices, is used to obtain hardware device information for each hardware device; based on the hardware device information, it determines whether there are any target hardware devices lacking drivers; if there are target hardware devices lacking drivers, it generates a hardware external driver requirement list, which includes the identifier of the missing hardware driver and the corresponding manufacturer information; based on the hardware external driver requirement list, it obtains the corresponding hardware driver source code; and based on the hardware driver source code, it installs and deploys the corresponding driver software package for the target hardware device.

[0017] Fourthly, the present invention also discloses an electronic device, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the message transmission method described above. Fifthly, the present invention also discloses a readable storage medium on which a program or instruction is stored, wherein when the program or instruction is executed by a processor, the steps of the message transmission method described above are implemented.

[0018] The embodiments of the present invention have the following advantages: This invention discloses a driver installation and deployment method, apparatus, system, device, and medium. The method automatically acquires hardware device information and identifies target hardware devices lacking drivers, generating a hardware driver requirement list containing the target hardware device identifier and corresponding manufacturer information. Based on this list, it selectively acquires the hardware driver source code and completes the installation and deployment of the driver package. The entire process, through automated identification of missing hardware drivers, automatic compilation and creation of driver packages, and automatic driver loading, eliminates the need for manual compilation and adaptation, improving driver installation and deployment efficiency, reducing communication costs, and enhancing driver adaptation efficiency during the installation and deployment of operating systems on large-scale resource pool servers in cloud scenarios. It effectively avoids operating system installation failures or hardware device malfunctions due to missing hardware drivers, ensuring the smooth progress of operating system installation and deployment and the normal operation of hardware devices in cloud platform construction. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating the steps of a driver installation and deployment method provided in an embodiment of the present invention; Figure 2 This is a flowchart illustrating a driver installation and deployment method provided in an embodiment of the present invention. Figure 3 This is a structural block diagram of a drive installation and deployment device provided in an embodiment of the present invention; Figure 4 This is a structural block diagram of a driver installation and deployment system provided in an embodiment of the present invention. Detailed Implementation

[0020] One of the core concepts of this invention is that it can automatically acquire hardware device information and identify target hardware devices lacking drivers, generate a hardware driver requirement list containing the target hardware device identifier and corresponding manufacturer information, and then obtain the hardware driver source code based on this list and complete the installation and deployment of the driver package. The entire process improves the efficiency of operating system installation and deployment by automatically identifying missing hardware drivers, automatically compiling and creating driver packages, and automatically loading drivers, greatly reducing communication costs and improving the efficiency of driver adaptation during the installation and deployment of operating systems for large-scale resource pool servers in cloud scenarios. It effectively avoids problems such as operating system installation failure or hardware device malfunction due to missing hardware device drivers, ensuring the smooth progress of operating system installation and deployment and the normal operation of hardware devices in cloud platform construction.

[0021] Reference Figure 1 The diagram illustrates a flowchart of a driver installation and deployment method provided by an embodiment of the present invention, which may include the following steps: Step 101: Obtain hardware device information for each hardware device.

[0022] In this embodiment of the invention, this step can be implemented through the server's underlying hardware information reading interface, the hardware detection tool built into the operating system, or a dedicated hardware information collection module. The collected hardware device information must cover key content that can uniquely identify the hardware's identity and characteristics, including but not limited to the hardware device's model and specifications, chipset information, hardware identifier, manufacturer's name, and hardware version number.

[0023] Step 102: Based on the hardware device information of each hardware device, determine whether there is a target hardware device that is missing a driver.

[0024] In this embodiment of the invention, the driver library corresponding to the operating system installed on the current hardware device can be retrieved. The driver library contains driver-related information for all hardware devices supported by the operating system, including supported hardware models, hardware identifiers, and other matching criteria. Then, the hardware device information is compared with the driver library, and the comparison result can be used to determine whether there is a target hardware device that is missing a driver.

[0025] Step 103: If there are target hardware devices lacking drivers, generate a hardware off-core driver requirement list. The hardware off-core driver requirement list includes the missing hardware driver identifier and the corresponding manufacturer information.

[0026] In this embodiment of the invention, if there are target hardware devices that lack drivers, a hardware off-core driver requirement list can be generated. When generating this hardware off-core driver requirement list, all identified target hardware devices can be categorized and organized to ensure that the relevant information of each target hardware device is accurately entered.

[0027] The hardware driver requirements list contains hardware driver identifiers that can directly correspond to the drivers for specific target hardware devices. The corresponding manufacturer information includes key information such as the official name of the driver development company, the authoritative channel for driver release, and technical support contact information. This ensures that the hardware driver requirements list can clearly identify the ownership and acquisition path of each missing driver. The generation of this hardware driver requirements list can follow standardized format requirements to ensure that the information is clearly arranged, easy to read, and easy to parse.

[0028] Step 104: Obtain the corresponding hardware driver source code based on the hardware external driver requirement list; In this embodiment of the invention, driver source code can be obtained in multiple ways. In one example, based on the manufacturer information in the list, the system can automatically connect to the official driver source code release platform or open interface provided by the hardware manufacturer, accurately retrieve the corresponding driver source code through the hardware driver identifier, and achieve automatic download of the driver source code. In another example, if there is a third-party driver source code sharing platform or a driver source code library built by the cloud platform, the information in the hardware external driver requirement list can be matched with the resources in these platforms or libraries to quickly filter out the suitable driver source code. For some driver source codes that cannot be obtained automatically, they can also be downloaded and uploaded by relevant personnel based on the hardware driver identifier provided in the list, ensuring that no driver source code for any target hardware device is missed.

[0029] The specific acquisition method can be set according to user needs.

[0030] Step 105: Install and deploy the corresponding driver software package on the target hardware device according to the hardware driver source code.

[0031] In this embodiment of the invention, the obtained hardware driver source code can be compiled and adapted according to the environment parameters such as the version of the operating system to be installed and the kernel type, so as to generate a driver software package that is compatible with the current operating system and the target hardware device. During the compilation process, the stability and compatibility of the driver software package must be ensured to avoid compilation errors or adaptation anomalies.

[0032] Subsequently, following the driver installation process supported by the operating system, the generated driver software package is deployed to the corresponding hardware devices on the server. Automatic installation can be achieved using the operating system's built-in driver installation tool or a dedicated driver deployment module. During installation, the installation status needs to be monitored in real time to ensure that the driver software package can be successfully loaded and establish a normal driver association with the target hardware device. After installation, the operating status of the target hardware device can be checked to verify whether it can respond normally to operation commands and whether all functions are fully implemented, ensuring that the driver installation and deployment achieve the expected results. This allows target hardware devices that previously lacked drivers to fully adapt to the current operating system, ensuring the normal operation of the server's overall hardware resources. This, in turn, ensures the smooth installation and stable use of the resource pool server operating system in a cloud scenario. The platform can automatically load the corresponding drivers during system installation, eliminating the need for manual installation by maintenance personnel and improving the level of automation.

[0033] This invention discloses a driver installation and deployment method. It automatically acquires hardware device information and identifies target hardware devices lacking drivers, generating a hardware driver requirement list containing the target hardware device identifier and corresponding manufacturer information. Based on this list, it selectively acquires the hardware driver source code and completes the installation and deployment of the driver package. The entire process, through automated identification of missing hardware drivers, automatic compilation of driver packages, and automatic driver loading, improves the efficiency of operating system installation and deployment, significantly reduces communication costs, and enhances driver adaptation efficiency during the installation and deployment of operating systems on large-scale resource pool servers in cloud scenarios. It effectively avoids problems such as operating system installation failure or hardware device malfunction due to missing hardware device drivers, ensuring the smooth progress of operating system installation and deployment and the normal operation of hardware devices in cloud platform construction.

[0034] In one embodiment of the present invention, the hardware device information includes a vendor identification code, a subsystem vendor identification code, and a device identification code. Based on the hardware device information of each hardware device, determining whether a target hardware device lacks a driver includes: determining whether the operating system on each hardware device provides a driver program that matches the vendor identification code, subsystem vendor identification code, and device identification code; if the operating system of a target hardware device does not provide a driver program that matches the vendor identification code, subsystem vendor identification code, and device identification code, then it is determined that a target hardware device lacks a driver.

[0035] In this embodiment of the invention, the collection of hardware device information is the fundamental step in driver missing judgment. Its core lies in obtaining key identification information that can uniquely identify the identity and ownership of the hardware device, specifically including the manufacturer identification code, the subsystem manufacturer identification code, and the device identification code.

[0036] In actual execution, information can be collected from each hardware device in the resource pool server through the server's underlying hardware interface, the hardware information reading tool built into the operating system, or a dedicated data acquisition module. The manufacturer identification code is a unique code assigned to the hardware manufacturer by the relevant standards organization to identify the core production entity of the hardware device; the subsystem manufacturer identification code identifies the specific supplier of the subsystem component contained in the hardware device, and is applicable to complex hardware devices integrated from multiple subsystems; the device identification code is a unique code assigned by the manufacturer to the corresponding hardware device to distinguish different models and specifications of hardware products produced by the same manufacturer.

[0037] Multi-dimensional matching verification can be used to determine if a target hardware device lacks a driver. During execution, the system first retrieves the driver libraries corresponding to the operating systems installed on multiple hardware devices on the current server. These driver libraries store driver association information for the operating systems on multiple hardware devices, including key data such as the manufacturer identification code, subsystem manufacturer identification code, device identification code, and compatible driver version for each hardware device. Then, for each hardware device, the collected three types of identification codes are comprehensively compared and matched with the data in the driver library: first, all driver records from the corresponding manufacturer in the driver library are filtered out using the manufacturer identification code; then, the matching range is further narrowed down using the subsystem manufacturer identification code. The system locates the relevant driver information for the corresponding subsystem and then performs precise matching using the device identification code to determine if a fully compatible driver exists in the driver library. If, after sequential matching of the three identification codes, no fully matching driver record is found in the driver library, the hardware device is determined to be the target hardware device lacking a driver. If all three types of identification codes can find a fully matching and compatible driver record in the driver library, the hardware device is determined to have a compatible driver and no further driver supplementation is required. The entire judgment process ensures the complete identification of target hardware devices through precise matching of multi-dimensional identifiers, providing clear guidance for subsequent driver acquisition and installation.

[0038] This invention achieves efficient driver missing detection by accurately collecting three types of core identification codes of hardware devices and accurately matching multi-dimensional identifiers. This eliminates the need for manual verification of hardware driver compatibility, significantly reducing manpower and human error. Through standardized identification code matching logic, it quickly locates the target hardware device lacking a driver, providing a clear basis for subsequent driver acquisition and significantly improving driver adaptation efficiency.

[0039] In one embodiment of the present invention, the method further includes: if the operating system on each hardware device provides a driver that matches the vendor identifier, the subsystem vendor identifier, and the device identifier, then it is determined that there is no target hardware device lacking a driver.

[0040] In this embodiment of the invention, taking a resource pool server in a cloud scenario as an example, the server is configured with hardware devices such as a CPU of brand A, a gigabit network card of brand B, a SATA solid-state drive of brand C, and a PCIe interface controller of brand D. For the CPU of brand A, its manufacturer identification code is 1234, its subsystem manufacturer identification code is 5678, and its device identification code is ABCD. After the system retrieves the operating system driver library, it finds a completely consistent combination of the three identification codes in the driver records of the corresponding manufacturers, and the matched driver version is compatible with the hardware specifications and operating system version of the CPU. For the gigabit network card of brand B, its manufacturer identification code is 9ABC, its subsystem manufacturer identification code is DEF0, and its device identification code is 1122. Through comparison with the driver library, it is found that the driver corresponding to this identification code combination is already... Integrated into the corresponding operating system, it supports the full functionality of the network card; similarly, the three types of identification codes for brand C's SATA solid-state drives and brand D's PCIe interface controllers can all find precisely matching driver records in the driver library, and the driver programs are fully compatible with the technical parameters of the hardware devices and the kernel version of the operating system, with no compatibility issues. After comparing and verifying the three types of identification codes of all hardware devices in the server, including core components, storage devices, network devices, interface controllers, etc., with the driver library data one by one, all hardware device identification code combinations can form a valid match with the driver programs in the driver library, and there are no cases of identification code mismatch, driver version incompatibility, or missing driver programs. At this time, the system will determine that each hardware device of the server has provided a driver program that matches the three types of identification codes.

[0041] This invention performs a comprehensive matching and verification of the three types of core identification codes and driver libraries for all hardware devices. When the operating system on all hardware devices has compatible drivers, it can directly determine that no driver is missing, avoiding unnecessary driver acquisition and adaptation operations. This further simplifies the installation and deployment process of the operating system for resource pool servers in cloud scenarios and reduces unnecessary work.

[0042] In one embodiment of the present invention, obtaining hardware device information of each hardware device includes: obtaining hardware device information of each hardware device through a desktop management interface decoder.

[0043] In this embodiment of the invention, the desktop management interface serves as a standardized communication interface between the operating system and hardware devices. It is compatible across hardware platforms and operating system versions, and can directly interact with the firmware, configuration registers, and hardware description files of the hardware devices to ensure the integrity and accuracy of the collected information.

[0044] During execution, the desktop management interface decoder is first activated. This decoder establishes a communication connection with each hardware device in the server by calling the underlying data reading function of the desktop management interface. It achieves unified information collection from various hardware devices without requiring additional dedicated acquisition plugins. During the collection process, the desktop management interface decoder reads the manufacturer identification code, subsystem manufacturer identification code, and device identification code of each hardware device according to preset information collection rules. The manufacturer identification code uniquely identifies the manufacturer of the hardware device, the subsystem manufacturer identification code identifies the supplier of the subsystem components within the hardware device, and the device identification code distinguishes different models of hardware products from the same manufacturer. Whether it's the server's core processing unit, storage devices, network adapters, or other major hardware, or auxiliary hardware such as interface controllers and sensors, the desktop management interface decoder can complete information collection through standardized communication protocols, ensuring that no hardware device is missed. Simultaneously, the validity of the data is verified in real time during the collection process to avoid information errors caused by transmission interference or abnormal hardware responses. Ultimately, a complete data set containing the three core identification codes of all hardware devices is formed, laying a solid foundation for subsequent driver matching and verification.

[0045] This invention achieves standardized and automated collection of hardware device information through a desktop management interface decoder, eliminating the need for manual querying or the use of multiple specialized tools, thus significantly reducing manpower and collection time.

[0046] In one embodiment of the present invention, the method further includes: detecting whether the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions; and installing and deploying the corresponding driver software package on the target hardware device according to the hardware driver source code, including: if the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions, then installing and deploying the corresponding driver software package on the target hardware device according to the hardware driver source code.

[0047] In this embodiment of the invention, the preset conditions may include at least one of the following: the hardware feature adaptation requirements between the driver source code and the target hardware device, and the compatibility standards with the operating system version and kernel type.

[0048] During testing, technical parameters of the driver source code can be extracted, including the range of supported hardware models, the compatible operating system kernel version, dependent system components, and resource usage specifications. Simultaneously, this is combined with the target hardware device's manufacturer identification code, subsystem manufacturer identification code, device identification code, and hardware specifications, as well as the current server's operating system version and kernel configuration, for multi-dimensional comparison and verification. By simulating the driver source code's loading and execution environment, the system checks whether the driver source code can correctly identify the target hardware device, whether it will conflict with the core functions of the operating system, and whether it can meet the functional requirements of the target hardware device. If all test items meet the preset compatibility requirements, the driver source code is deemed to have met the preset compatibility conditions with the operating system on the target hardware device.

[0049] If the preset requirements are met, the driver package installation and deployment process can be initiated. First, the driver package is compiled based on the driver source code and the current operating system's compilation environment, ensuring that the generated driver package has the running attributes that match the operating system and target hardware device. Then, according to the driver installation specifications supported by the operating system, the compiled driver package is deployed to the specified directory on the server. By calling the operating system's driver loading interface, the installation and registration of the driver package are completed. At the same time, the driver's running parameters are configured to ensure that the driver can be automatically loaded and run when the server starts. After the installation and deployment are completed, the system can also perform driver running status detection to verify whether the target hardware device can respond normally to driver commands and whether all functions are fully implemented, ensuring that the driver installation and deployment achieve the expected results.

[0050] This invention effectively avoids installation failures or operational anomalies caused by incompatibility between driver source code and hardware devices or operating systems by adding a compatibility detection step before driver installation and deployment, thereby improving the success rate of driver installation and deployment.

[0051] In one embodiment of the present invention, the method further includes: if the compatibility between the driver source code and the operating system on the target hardware device does not meet preset conditions, a compatibility report is generated and output.

[0052] In this embodiment of the invention, after performing compatibility testing on the driver source code corresponding to the acquired target hardware device, if the test result shows that the compatibility between the driver source code and the operating system on the target hardware device does not meet the preset conditions, the compatibility report generation and output process can be automatically started.

[0053] The generation of a compatibility report must be based on various key data collected during the compatibility testing process, and must comprehensively and in detail record the specific circumstances under which the preset conditions are not met, including but not limited to the core dimensions of incompatibility, specific incompatible items, differences in relevant technical parameters, and possible operational risks.

[0054] Taking a target hardware device in a resource pool server in a cloud scenario as an example, this target hardware device is a 10 Gigabit Ethernet card from brand E. Its manufacturer identification code, subsystem manufacturer identification code, and device identification code require the driver source code to support the latest version of the operating system kernel. However, the obtained driver source code only supports an older version of the operating system kernel, and the hardware interface protocols supported in the driver source code do not match the actual interface protocols of the 10 Gigabit Ethernet card. Furthermore, the system components that the driver source code depends on are not installed in the current server's operating system. After compatibility testing, it is determined that the compatibility between the driver source code and the target hardware device does not meet the preset conditions. At this point, the system can generate a corresponding compatibility report. The report clearly indicates that the tested object is the 10 Gigabit Ethernet card from brand E and its corresponding driver source code, and details the three core dimensions of incompatibility: operating system kernel version compatibility, hardware interface protocol matching degree, and system component compatibility. For each incompatibility dimension, the system details the differences between the key technical parameters of the driver source code and the preset conditions. This includes the range of operating system kernel versions supported by the driver source code, the actual hardware interface protocol types adapted, the names of dependent system components, and the required parameters for the target hardware device and the current server operating system. The system also analyzes the potential consequences of each incompatibility, such as driver loading failure, network card inability to connect to the network, and conflicts with other system components. After the compatibility report is generated, the system can output the report according to preset methods. These methods may include displaying the report as a pop-up in the server's management interface, sending it to a designated administrator terminal or email address, or storing it in a designated log directory on the server for later review. This ensures that relevant personnel can obtain detailed information on compatibility issues in a timely manner, providing a clear basis for taking targeted measures.

[0055] This invention generates and outputs a compatibility report containing detailed incompatibility information when the compatibility between the driver source code and the operating system on the target hardware device does not meet preset conditions. This allows staff to quickly locate the core incompatibility issues and their causes, avoiding resource waste or system anomalies caused by blindly installing and deploying drivers. It provides precise guidance for subsequent driver source code optimization, adaptation adjustments, or obtaining suitable driver source code again, further improving the targeting and efficiency of driver adaptation work, reducing the trial-and-error costs of large-scale installation and deployment of operating systems on resource pool servers in cloud scenarios, and ensuring the smooth progress of cloud platform construction.

[0056] In one embodiment of the present invention, detecting whether the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions includes: detecting whether the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions through the kernel application binary interface and the kernel application programming interface.

[0057] In this embodiment of the invention, when testing whether the compatibility between the driver source code and the operating system on the target hardware device meets the preset conditions, standardized testing can be carried out through binary interface and kernel application programming interface. The compatibility between the driver source code and the hardware device and operating system kernel is ensured through the collaborative verification of the two types of interfaces.

[0058] The kernel application binary interface, as a binary-level communication standard between the driver and the operating system kernel, defines the specifications for the interaction between the driver and the kernel at the binary level, including data structure layout, function calling conventions, register usage rules, etc., to ensure that the driver can be correctly loaded and run in a specific kernel version. The kernel application programming interface provides the driver source code with a standardized function interface for accessing kernel functions, covering the calling specifications of core functions such as hardware resource management, interrupt handling, and memory allocation, and is the foundation for the driver source code to implement hardware control functions.

[0059] During the testing process, the binary file of the driver source code can be parsed through the kernel application binary interface to extract key information such as data structure definitions, function call formats, and symbol table information. This information is then compared with the kernel application binary interface specification of the operating system kernel of the target hardware device to verify whether the binary format of the driver source code conforms to the kernel loading requirements and whether there are any issues such as data structure mismatches or function call conflicts. Simultaneously, the kernel application programming interface is used to check whether the kernel functions called in the driver source code are consistent with the function interfaces supported by the current kernel version, including function names, parameter lists, and return value types. This verifies whether the driver source code depends on deprecated or unimplemented kernel functions and whether there are any issues such as mismatched function call permissions.

[0060] This invention utilizes kernel application binary interfaces and kernel application programming interfaces to perform driver source code compatibility testing, achieving standardized and precise verification of the compatibility between driver source code and operating system kernel and target hardware devices, effectively avoiding driver loading failures or abnormal operation caused by interface incompatibility.

[0061] In one embodiment of the present invention, obtaining the corresponding hardware driver source code according to the hardware external driver requirement list includes: obtaining the hardware driver source code uploaded by the user based on the hardware driver identifier and the corresponding manufacturer information.

[0062] In this embodiment of the invention, the corresponding hardware driver source code is obtained according to the hardware external driver requirement list. The core is to build a precise and compliant source code acquisition process based on the clearly defined hardware driver identifiers and manufacturer information in the list.

[0063] In practice, a hardware driver requirement list can be used as a basis to identify the unique hardware driver identifier for each target hardware device with a missing driver. This identifier is usually composed of key information such as device model, hardware version, driver function type, etc., which can accurately locate the compatible driver. At the same time, the corresponding manufacturer information, including the manufacturer's official name, technical certification mark, driver release specification, etc., can be clearly presented to the user, providing clear guidance for the user to upload source code.

[0064] After obtaining this information, users can verify, based on their own existing or officially sourced driver resources, whether the source code to be uploaded fully matches the hardware driver identifier in the requirements list and complies with the corresponding manufacturer's technical specifications and release requirements. This helps avoid uploading mismatched or non-compliant source code. Subsequently, the system provides a secure and standardized upload portal. Users can submit the corresponding hardware driver source code through this portal. During the upload process, the system will verify the source code in real time, focusing on whether the hardware driver identifier associated with the source code matches the requirements list and whether the source code contains manufacturer certification information or compliant signatures. This ensures that the uploaded source code can accurately adapt to the target hardware device and eliminates security risks such as malicious code tampering with the source code. Finally, the system obtains the compliant hardware driver source code uploaded by the user, laying the foundation for the subsequent compilation, installation, and deployment of the driver software package.

[0065] In one example, the hardware driver requirements list shows that target machine 1 lacks an E40 network card driver, with the manufacturer listed as Intel. Target machine 1 is a core terminal device in an enterprise's office network, and its E40 network card needs to function properly to ensure stable communication between the terminal and the enterprise's intranet server and external networks. The missing driver prevents the network card from being enabled, affecting office data transmission and access to business systems. After obtaining the requirements list, the technicians responsible for equipment maintenance determined that the required driver must be compatible with the E40 network card and be a compliant driver source code provided by Intel. The technicians first accessed the driver download section on Intel's official website, entering "E40 network card". The corresponding hardware model and related parameters were used to confirm the accuracy of the search path by combining the manufacturer information in the requirements list. Then, the E40 network card driver source code package adapted to the operating system version of target machine 1 was found and downloaded through official channels. After the download was completed, the technicians first checked whether the file name identifier of the source code package was consistent with the E40 network card driver identifier in the requirements list. At the same time, they confirmed that the source code package contained Intel's official digital signature file to ensure that the source code had not been tampered with by third parties and complied with Intel's technical specifications and security standards. Then, the technicians submitted and uploaded the E40 network card driver source code package through the driver source code upload portal provided in the system management interface of target machine 1.

[0066] This invention guides users to upload the corresponding hardware driver source code by providing precise device identification and manufacturer information based on the hardware external driver requirement list, avoiding the blind acquisition of driver source code and greatly improving the accuracy and efficiency of source code acquisition.

[0067] In one embodiment of the present invention, obtaining the corresponding hardware driver source code according to the hardware external driver requirement list includes: querying the corresponding official website address based on the hardware driver identifier and the corresponding manufacturer information according to a preset model; and obtaining the hardware driver source code from the official website address.

[0068] In this embodiment of the invention, the preset model is an intelligent query model trained based on the association data of massive hardware driver identifiers, manufacturer information and corresponding official website addresses. It has built-in matching rules for hardware driver identifiers and manufacturer information, verification logic for manufacturer official website addresses and parsing algorithms for source code download paths, which can quickly and accurately establish the association between hardware driver identifiers and manufacturer official websites.

[0069] In actual execution, each hardware driver identifier and its corresponding manufacturer information can be extracted from the list of external hardware driver requirements. This information is used as input parameters for a preset model. The model can verify the correlation between the device identifier and the manufacturer information through matching rules, ensuring the consistency and validity of the input information. Subsequently, based on the verified information, the built-in association database is retrieved to match the corresponding manufacturer's official website address. At the same time, the authenticity and validity of the address are confirmed through the official website address verification logic to avoid pointing to unofficial or invalid links.

[0070] Taking a resource pool server in a cloud scenario as an example, the hardware driver requirement list shows that a graphics processor of brand I is missing a driver. The hardware driver identifier for the missing driver is A, and the corresponding manufacturer is brand I. After inputting these two sets of device identifiers and manufacturer information into a preset model, the official technical support website address for the missing driver of brand I can be quickly matched. After verification, it is confirmed that the addresses are all legitimate and valid official websites. Then, based on the driver source code download path within the official website parsed by the preset model, the corresponding official website address is automatically accessed, and the driver source code download area that accurately matches the target hardware device identifier is located. The driver source code adapted to the current server operating system version is selected, and the driver source code is automatically obtained through the download interface provided by the official website.

[0071] This invention uses a preset model to accurately associate hardware devices lacking drivers with the manufacturer's official website address, eliminating the need for manual searching of the official website and driver download path, thus significantly reducing manpower and search time.

[0072] In one embodiment of the present invention, the method further includes: obtaining the operating system version information of each hardware device; and constructing different types of driver compilation environments based on the operating system version information of each hardware device.

[0073] In this embodiment of the invention, obtaining operating system version information can be achieved through the operating system's native version query interface, system kernel file parsing, or standardized system information collection tools. Taking a resource pool server cluster in a cloud scenario as an example, some servers in this cluster run open-source system version X with a specific kernel version, while some servers run commercial system version Y with a different kernel version. Two different system architectures exist simultaneously. After collecting the operating system version information of all servers, based on the collected differentiated version information, the construction of different types of driver compilation environments is initiated. For servers running open-source system version X with a specific kernel version, a compilation environment adapted to that system is built, including kernel header files corresponding to that kernel version, a dedicated compilation toolchain, dependency library files, and system configuration scripts. This ensures that the version of the compilation toolchain is compatible with the kernel version, and that the dependency libraries meet the system requirements. The system addresses the compilation dependencies of drivers. For servers running commercial system version Y with a different kernel version, it builds a compilation environment that matches the system characteristics, configuring specific compilation rules, linking parameters, and system interface files to adapt to the underlying architecture and compilation specifications of the commercial system. Simultaneously, for the two different system architectures, it builds corresponding compilation environments, configuring compilation options and binary file generation rules adapted to the architecture to ensure that the compiled driver is fully compatible with the system architecture of the hardware device. During the build process, the system automatically retrieves and deploys the compilation components required for the corresponding operating system version, automatically configures environment variables, compilation parameters, and linking paths, forming a standardized compilation environment template that corresponds one-to-one with the specific operating system version information. This ensures that the driver source code for different hardware devices can be compiled in the matching compilation environment, generating driver packages adapted to the target operating system.

[0074] This invention achieves deep adaptation between the driver compilation environment and the target operating system by accurately collecting operating system version information and constructing a differentiated driver compilation environment accordingly, effectively avoiding driver compilation failures or abnormal operation caused by incompatibility of the compilation environment.

[0075] In one embodiment of the present invention, installing and deploying the corresponding driver software package to the target hardware device according to the hardware driver source code includes: determining a target driver compilation environment that matches the operating system of the target hardware device in different types of driver compilation environments; and installing and deploying the corresponding driver software package according to the hardware driver source code through the target driver compilation environment.

[0076] In this embodiment of the invention, when installing and deploying the corresponding driver software package to the target hardware device based on the hardware driver source code, the target driver compilation environment can be matched first, and then the driver compilation and installation deployment can be completed through this environment. This ensures that the driver software package is fully compatible with the target hardware device and the corresponding operating system. In the step of determining the target driver compilation environment, the operating system version information corresponding to the target hardware device is first extracted, including key parameters such as the main version of the operating system, kernel version, system architecture and distribution version. Then, these parameters are compared one by one with the configuration information of different types of driver compilation environments that have been built. The built driver compilation environments are all associated with the corresponding operating system version characteristics. Each environment contains specific kernel header files, compilation toolchains, dependency libraries and compilation rules, which can be adapted to the corresponding version of the operating system.

[0077] During the comparison process, it can be verified whether the operating system version, kernel version, and system architecture are fully matched. At the same time, it can be confirmed whether the dependency libraries of the compilation environment are compatible with the compilation requirements of the driver source code. Finally, the environment that is fully compatible with the operating system of the target hardware device is selected as the target driver compilation environment.

[0078] Taking a resource pool server in a cloud scenario as an example, the target hardware device is a high-speed cache card of brand K, with an operating system version Z and a specific kernel version, and a 64-bit system architecture. By comparing the existing driver compilation environments, it was found that the compilation environment numbered ENV-003 is exactly associated with the operating system version Z, the corresponding kernel version, and the 64-bit system architecture. Moreover, the compilation toolchain and dependent libraries of this environment fully meet the compilation requirements of the cache card driver source code. Therefore, ENV-003 was determined as the target driver compilation environment. After determining the target driver compilation environment, the obtained hardware driver source code can be imported into this environment to start the compilation process of the driver package. The process involves using the built-in compilation toolchain within the environment to compile the source code according to preset compilation rules, generating a driver package compatible with the target operating system and hardware device. Then, following the operating system's driver installation specifications, the compiled driver package is deployed to a designated directory on the server. The system then calls the operating system's driver loading interface to complete the installation and registration of the driver package, configuring the driver's runtime parameters to ensure that the driver is automatically loaded when the server starts. After installation and deployment, the system checks the driver loading status of the target hardware device, verifying whether the device can respond normally to driver commands and whether all functions are fully implemented, ensuring that the driver installation and deployment achieve the expected results.

[0079] This invention ensures that the driver source code is compiled and installed in a compatible environment by accurately matching the target driver compilation environment, which greatly improves the compatibility of the driver software package with the operating system and target hardware devices, and effectively avoids installation failure or abnormal operation caused by incompatible compilation environments.

[0080] like Figure 2 This diagram illustrates a flowchart of a driver installation and deployment method provided by an embodiment of the present invention. First, after the server program is deployed, the server program establishes SSH connections with the operating system nodes of all hardware devices. Next, an operating system driver compilation environment is built. The server obtains different operating system version information through a network interface and user login information. After summarizing the information of different OSV vendors and versions, a corresponding driver compilation environment is built. Then, each hardware device in the resource pool is detected. The hardware device information of each hardware device in the resource pool is automatically detected through the network interface. The obtained hardware information of each node is transmitted to the server and filled into the hardware information list. This mainly includes the hardware and board vendor identification code Vendor ID, Subsystem Vendor ID, and Device ID obtained through the desktop management interface decoder dmidecode tool. This information is then used to determine whether there are available drivers on the target hardware device's operating system. This can be done by analyzing the kernel driver's Device ID. The system performs several steps: first, it matches relevant fields in the table; then, it checks for missing hardware devices. If any are found, it generates a list of required external drivers, including the missing drivers and their manufacturers, and prompts the system administrators to obtain the corresponding driver source code. Next, it receives the driver source code uploaded by the administrators and performs compatibility testing using KABI and KAPI interfaces to scan and match between the operating system kernel and driver code. Finally, it creates a driver package by compiling compatible driver source code into an installable package. During system installation, it automatically connects the created driver package to the device requiring the driver via network using PXEserver or with an external plugin, automatically loads the driver, and completes the system installation by adding the specified driver to the kernel's grub command line, ensuring the hardware devices function correctly.

[0081] If the target hardware device's operating system does not lack drivers, then the node for that target hardware device in the node hardware information list will be set to the normal state.

[0082] If the server program has traversed the last node of the node hardware information list (HNI), it means that there are no hardware devices missing drivers. At this time, it can enter the driver installation or driver update stage, and then choose the right time to install drivers for the hardware devices missing drivers according to the hardware information list and the hardware core driver requirement list.

[0083] This invention discloses a driver installation and deployment method. It automatically acquires hardware device information and identifies target hardware devices lacking drivers, generating a hardware driver requirement list containing the target hardware device identifier and corresponding manufacturer information. Based on this list, it selectively acquires the hardware driver source code and completes the installation and deployment of the driver package. The entire process, through automated identification of missing hardware drivers, automatic compilation of driver packages, and automatic driver loading, improves the efficiency of operating system installation and deployment, significantly reduces communication costs, and enhances driver adaptation efficiency during the installation and deployment of operating systems on large-scale resource pool servers in cloud scenarios. It effectively avoids problems such as operating system installation failure or hardware device malfunction due to missing hardware device drivers, ensuring the smooth progress of operating system installation and deployment and the normal operation of hardware devices in cloud platform construction.

[0084] like Figure 3 The diagram illustrates a structural block diagram of a drive installation and deployment device provided in an embodiment of the present invention. The device may include: The first acquisition module 201 is used to acquire hardware device information of each hardware device; The judgment module 202 is used to determine whether there is a target hardware device lacking a driver based on the hardware device information of each hardware device. The generation module 203 is used to generate a hardware off-core driver requirement list if there are target hardware devices that lack drivers. The hardware off-core driver requirement list includes the missing hardware driver identifier and the corresponding manufacturer information. The second acquisition module 204 is used to acquire the corresponding hardware driver source code based on the hardware external driver requirement list; Installation module 205 is used to install and deploy the corresponding driver software package to the target hardware device based on the hardware driver source code.

[0085] In one embodiment of the present invention, the hardware device information includes a manufacturer identification code, a subsystem manufacturer identification code, and a device identification code; the judgment module 202 includes: The judgment submodule is used to determine whether the operating system on each hardware device provides a driver that matches the vendor identifier, subsystem vendor identifier, and device identifier; The first determination submodule is used to determine if there is a target hardware device lacking a driver if the operating system of the target hardware device does not provide a driver that matches the vendor identifier, subsystem vendor identifier, and device identifier.

[0086] In one embodiment of the present invention, it further includes: The second determining submodule is used to determine that there is no target hardware device lacking a driver if the operating system on each hardware device provides a driver that matches the vendor identifier, subsystem vendor identifier, and device identifier.

[0087] In one embodiment of the present invention, the first acquisition module includes: The first acquisition submodule is used to obtain hardware device information of each hardware device through the desktop management interface decoder.

[0088] In one embodiment of the present invention, it further includes: The detection module is used to detect whether the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions. The installation module includes: The first installation submodule is used to install and deploy the corresponding driver software package on the target hardware device based on the hardware driver source code if the compatibility between the driver source code and the operating system on the target hardware device meets the preset conditions.

[0089] In one embodiment of the present invention, it further includes: The generation submodule is used to generate a compatibility report and output the compatibility report if the driver source code does not meet the preset compatibility conditions with the operating system on the target hardware device.

[0090] In one embodiment of the present invention, the detection module includes: The detection submodule is used to detect whether the compatibility between the driver source code and the target hardware device meets preset conditions through the kernel application binary interface and the kernel application programming interface.

[0091] In one embodiment of the present invention, the second acquisition module includes: The second acquisition submodule is used to acquire the hardware driver source code uploaded by the user based on the hardware driver identifier and the corresponding manufacturer information.

[0092] In one embodiment of the present invention, the second acquisition module includes: The query submodule is used to find the corresponding official website address based on the hardware driver identifier and the corresponding manufacturer information, using a preset model. The third submodule is used to obtain the hardware driver source code from the official website.

[0093] In one embodiment of the present invention, it further includes: The third acquisition module is used to acquire the operating system version information of each hardware device; The build module is used to build different types of driver compilation environments based on the operating system version information of each hardware device.

[0094] In one embodiment of the present invention, the installation module includes: The third determination submodule is used to determine the target driver compilation environment that matches the operating system of the target hardware device in different types of driver compilation environments; The second installation submodule is used to install and deploy the corresponding driver software package based on the hardware driver source code through the target driver compilation environment.

[0095] This invention discloses a driver installation and deployment device. It automatically acquires hardware device information and identifies target hardware devices lacking drivers, generating a hardware driver requirement list containing the target hardware device identifier and corresponding manufacturer information. Based on this list, it selectively acquires the hardware driver source code and completes the installation and deployment of the driver software package. The entire process, through automated identification of missing hardware drivers, automatic compilation and creation of driver software packages, and automatic driver loading, improves the efficiency of operating system installation and deployment, significantly reduces communication costs, and enhances the efficiency of driver adaptation during the installation and deployment of operating systems for large-scale resource pool servers in cloud scenarios. It effectively avoids problems such as operating system installation failure or hardware device malfunction due to missing hardware device drivers, ensuring the smooth progress of operating system installation and deployment and the normal operation of hardware devices in cloud platform construction.

[0096] like Figure 4 The diagram illustrates a structural block diagram of a driver installation and deployment system provided by an embodiment of the present invention. The system may include: Multiple hardware devices 301.

[0097] In this embodiment of the invention, the plurality of hardware devices may include hardware devices 3011, 3012...301 n ; The driver installation and deployment platform 302 connects to multiple hardware devices to obtain hardware device information for each device. Based on this information, it determines whether any target hardware devices lack drivers. If such devices exist, it generates a hardware external driver requirement list, which includes the identifiers of the missing drivers and their corresponding vendor information. Based on this list, it obtains the corresponding hardware driver source code and installs and deploys the corresponding driver software package on the target hardware devices using the source code.

[0098] In this invention, the driver installation and deployment platform 302 can be connected to multiple hardware devices 301 through a switch 303. It can obtain the hardware device information of the multiple hardware devices 301 through the switch 303, and then determine whether there is a target hardware device lacking a driver based on the hardware device information of the multiple hardware devices.

[0099] This invention discloses a driver installation and deployment system. It automatically acquires hardware device information and identifies target hardware devices lacking drivers, generating a list of required external hardware drivers containing the target hardware device identifier and corresponding manufacturer information. Based on this list, it selectively acquires the hardware driver source code and completes the installation and deployment of the driver software package. The entire process, through automated identification of missing hardware drivers, automatic compilation and creation of driver software packages, and automatic driver loading, improves the efficiency of operating system installation and deployment, significantly reduces communication costs, and enhances the efficiency of driver adaptation during the installation and deployment of operating systems for large-scale resource pool servers in cloud scenarios. It effectively avoids problems such as operating system installation failure or hardware device malfunction due to missing hardware device drivers, ensuring the smooth progress of operating system installation and deployment and the normal operation of hardware devices in cloud platform construction.

[0100] This invention also provides an electronic device, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement the various processes of the above-described driver installation and deployment method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0101] It should be noted that the electronic devices in the embodiments of the present invention include the mobile electronic devices and non-mobile electronic devices described above.

[0102] This invention also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described driver installation and deployment method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0103] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0104] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0105] The present invention has provided a detailed description of a driver installation and deployment method, apparatus, system, device, and medium. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A driver installation and deployment method, characterized in that, include: Obtain hardware device information for each hardware device; Based on the hardware device information of each hardware device, determine whether there is a target hardware device lacking a driver; If there are target hardware devices that lack drivers, a hardware off-core driver requirement list is generated, which includes the missing hardware driver identifier and the corresponding manufacturer information. Based on the hardware external driver requirement list, obtain the corresponding hardware driver source code; Install and deploy the corresponding driver software package for the target hardware device based on the hardware driver source code.

2. The driver installation and deployment method according to claim 1, characterized in that, The hardware device information includes a manufacturer identification code, a subsystem manufacturer identification code, and a device identification code; the step of determining whether there is a target hardware device lacking a driver based on the hardware device information of each hardware device includes: Determine whether the operating system on each hardware device provides a driver that matches the vendor identifier, the subsystem vendor identifier, and the device identifier; If the operating system of a target hardware device does not provide a driver that matches the vendor identifier, the subsystem vendor identifier, and the device identifier, then it is determined that there is a target hardware device lacking a driver.

3. The driver installation and deployment method according to claim 2, characterized in that, Also includes: If the operating systems on each of the hardware devices provide drivers that match the vendor identifier, the subsystem vendor identifier, and the device identifier, then it is determined that there is no target hardware device lacking a driver.

4. The driver installation and deployment method according to claim 1, characterized in that, The acquisition of hardware device information for each hardware device includes: The hardware device information of each hardware device is obtained through the desktop management interface decoder.

5. The driver installation and deployment method according to claim 1, characterized in that, Also includes: Check whether the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions; The step of installing and deploying the corresponding driver software package on the target hardware device based on the hardware driver source code includes: If the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions, then the corresponding driver software package is installed and deployed on the target hardware device according to the hardware driver source code.

6. The driver installation and deployment method according to claim 5, characterized in that, Also includes: If the compatibility between the driver source code and the operating system on the target hardware device does not meet the preset conditions, a compatibility report is generated and output.

7. The driver installation and deployment method according to claim 5, characterized in that, The step of detecting whether the compatibility between the driver source code and the operating system on the target hardware device meets preset conditions includes: The compatibility between the driver source code and the operating system on the target hardware device is checked using the kernel application binary interface and the kernel application programming interface to determine whether the compatibility meets preset conditions.

8. The driver installation and deployment method according to claim 1, characterized in that, The step of obtaining the corresponding hardware driver source code based on the hardware off-core driver requirement list includes: Obtain the hardware driver source code uploaded by the user based on the hardware driver identifier and the corresponding manufacturer information.

9. The driver installation and deployment method according to claim 1, characterized in that, The step of obtaining the corresponding hardware driver source code based on the hardware off-core driver requirement list includes: Based on the hardware driver identifier and the corresponding manufacturer information, the corresponding official website address is retrieved using a preset model. Obtain the hardware driver source code from the official website address.

10. The driver installation and deployment method according to claim 1, characterized in that, Also includes: Obtain the operating system version information of each hardware device; Based on the operating system version information of each hardware device, different types of driver compilation environments are constructed.

11. The driver installation and deployment method according to claim 10, characterized in that, The step of installing and deploying the corresponding driver software package on the target hardware device according to the hardware driver source code includes: Determine the target driver compilation environment that matches the operating system of the target hardware device within the different types of driver compilation environments; The target driver compilation environment is used to install and deploy the corresponding driver software package based on the hardware driver source code.

12. A drive installation and deployment device, characterized in that, The device includes: The first acquisition module is used to acquire hardware device information of each hardware device. The judgment module is used to determine whether there is a target hardware device lacking a driver based on the hardware device information of each hardware device. The generation module is used to generate a hardware off-core driver requirement list if there are target hardware devices that lack drivers. The hardware off-core driver requirement list includes the missing hardware driver identifier and the corresponding manufacturer information. The second acquisition module is used to acquire the corresponding hardware driver source code based on the hardware external driver requirement list. The installation module is used to install and deploy the corresponding driver software package to the target hardware device based on the hardware driver source code.

13. A drive installation and deployment system, characterized in that, The system includes: Multiple hardware devices; A driver installation and deployment platform, connected to the multiple hardware devices, is used to obtain hardware device information for each hardware device; based on the hardware device information, it determines whether there are any target hardware devices lacking drivers; if there are target hardware devices lacking drivers, it generates a hardware external driver requirement list, which includes the identifier of the missing hardware driver and the corresponding manufacturer information; based on the hardware external driver requirement list, it obtains the corresponding hardware driver source code; and based on the hardware driver source code, it installs and deploys the corresponding driver software package for the target hardware device.

14. An electronic device, characterized in that, include: A processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the steps of the driver installation and deployment method as described in claims 1-11.

15. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, which, when executed by a processor, implements the steps of the driver installation and deployment method as described in any one of claims 1-11.

Images