CN112328328B - Method, device, equipment and storage medium for equipment driving reload - Google Patents
Method, device, equipment and storage medium for equipment driving reload Download PDFInfo
- Publication number
- CN112328328B CN112328328B CN202011332811.3A CN202011332811A CN112328328B CN 112328328 B CN112328328 B CN 112328328B CN 202011332811 A CN202011332811 A CN 202011332811A CN 112328328 B CN112328328 B CN 112328328B
- Authority
- CN
- China
- Prior art keywords
- target device
- driver
- instance
- target
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44568—Immediately runnable code
- G06F9/44578—Preparing or optimising for loading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The embodiment of the application discloses a method, a device, equipment and a storage medium for equipment driving reload, and relates to the technical fields of cloud computing, cloud service and the like. The method comprises the following steps: acquiring an instance identifier of a target device; acquiring a driving instruction file storage path of the target equipment according to the instance identifier; acquiring a hardware identifier corresponding to the target equipment according to the instance identifier; according to the storage path of the drive guide file and the hardware identifier, the drive of the target equipment is updated, so that the problem that the drive cannot be loaded when the system of the target equipment is deployed is solved, and the manpower requirement and the deployment time of the system of the target equipment are reduced.
Description
Technical Field
The application relates to the technical field of computers, in particular to the technical field of the Internet such as cloud computing, cloud service and the like, and especially relates to a method, a device, equipment and a storage medium for equipment driving reload.
Background
When the cloud host and a machine room containing a large number of servers are required to install the same Windows system in batches, a Windows system mirror image manufactured in advance can be used, and the deployment mode is easy to operate, simple and quick.
With the development of artificial intelligence and other technologies, more and more image processor (Graphic Processing Unit, GPU) servers are put into a production environment, and a large number of GPU servers also face the problem of batch deployment. The GPU server has a new hardware device image processing chip, which requires integration of the corresponding driver software in the produced system image. However, when the system images with integrated drivers are used for batch deployment, the deployed Windows server GPU device drivers often cannot be loaded correctly due to the difference between servers.
Disclosure of Invention
The embodiment of the application provides a method, a device, equipment and a storage medium for equipment driving reload.
In a first aspect, an embodiment of the present application provides a method for device driver reloading, including: acquiring an instance identifier of a target device; acquiring a driving instruction file storage path of the target equipment according to the instance identifier; acquiring a hardware identifier corresponding to the target equipment according to the instance identifier; and updating the drive of the target equipment according to the drive guide file storage path and the hardware identifier.
In a second aspect, embodiments of the present application provide an apparatus for device driven reloading, including: an instance identifier obtaining module configured to obtain an instance identifier of the target device; the instruction file acquisition module is configured to acquire a driving instruction file storage path of the target device according to the instance identifier; the hardware identification acquisition module is configured to acquire a hardware identification corresponding to the target device according to the instance identification; and the drive updating module is configured to update the drive of the target device according to the drive guide file storage path and the hardware identifier.
In a third aspect, an embodiment of the present application provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method as described in any one of the implementations of the first aspect.
In a fourth aspect, embodiments of the present application provide a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform a method as described in any implementation of the first aspect.
The method, the device, the equipment and the storage medium for equipment driving reload provided by the embodiment of the application firstly acquire the instance identifier of the target equipment; then, according to the instance identification, a driving instruction file storage path of the target equipment is obtained; then, according to the instance identifier, acquiring a hardware identifier corresponding to the target device; and finally, updating the drive of the target equipment according to the storage path of the drive guide file and the hardware identifier, thereby solving the problem that the drive cannot be loaded when the system of the target equipment is deployed.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments made with reference to the following drawings. The drawings are for better understanding of the present solution and do not constitute a limitation of the present application. Wherein:
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow diagram of one embodiment of a method of device driven reloading according to the present application;
FIG. 3 is a flow diagram of another embodiment of a method of device driven reloading according to the present application;
FIG. 4 is an application scenario diagram of one embodiment of a method of device driven reloading according to the present application;
FIG. 5 is a schematic structural view of one embodiment of an apparatus for driving a heavy load of the present application;
fig. 6 is a block diagram of an electronic device for implementing a method of device driver reloading in accordance with an embodiment of the present application.
Detailed Description
The present application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other. The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of a method of device-driven reloading or an apparatus of device-driven reloading of the present application may be applied.
As shown in fig. 1, the system architecture 100 may include a terminal device 101, a server 102. The system image file terminal device 102 may be installed on the terminal device 101 including a computer, a mobile communication terminal, a tablet computer, a multimedia playing device, and the like. By using a system image file creation tool (e.g., ghost), a system image file of a template computer can be created on the terminal device 102. The server 102 may be a Windows server, a GPU server, or other device servers used to deploy the system.
The server 102 may be hardware or software. When the server 102 is hardware, it may be implemented as a distributed server cluster formed by a plurality of servers, or as a single server. When server 102 is software, it may be implemented as multiple software or software modules (e.g., to provide distributed services), or as a single software or software module. The present invention is not particularly limited herein.
It should be noted that, the method for device driving reloading provided in the embodiments of the present application is generally executed by the terminal device 101, and accordingly, the apparatus for device driving reloading is generally disposed in the terminal device 101.
It should be understood that the number of terminal devices and servers in fig. 1 is merely illustrative. There may be any number of terminal devices and servers, as desired for implementation.
With continued reference to fig. 2, a flow of one embodiment of a method of device driven reloading according to the present application is shown. The method comprises the following steps:
step 201, an instance identifier of a target device is obtained.
In this embodiment, an execution subject of the method of device driving reload (for example, the terminal device 101 shown in fig. 1) may acquire an instance identification of the target device.
Wherein the target device refers to a device used to deploy the system. The target device may be provided with a specific functional purpose, and the system is deployed for the target device to realize the utilization of the functional purpose. For example, the GPU device has a calculation or rendering function, and by deploying a system for the GPU device, normal use of the calculation or rendering function of the GPU device can be ensured.
In general, the driver of the target device may be integrated into the operating system, and the function of the target device may be utilized by correctly loading the driver. The operating system herein includes, but is not limited to, the Windows system.
Wherein the instance identifier is an identification string of the target device provided by the operating system, and is used for uniquely identifying the target device in the operating system. The target device may be identified in the operating system by its instance identification.
Step 202, according to the instance identification, obtaining a driving guidance file storage path of the target device.
In this embodiment, the execution body may obtain the driving instruction file storage path of the target device according to the instance identifier.
The driver instruction file is used for finding out a driver file and reloading the driver when the operating system does not load the driver of the target device correctly, so that the target device can be used normally. For a Windows operating system, the storage path for the drive guide files for the various devices is, for example, windows\INF\folder. The storage paths of the driving instruction files of the target equipment and the instance identifications of the target equipment are in one-to-one correspondence. For example, the storage path of the drive instruction file of the GPU device in the Windows operating system is: windows\INF\oem6.INF.
Step 203, obtaining the hardware identifier corresponding to the target device according to the instance identifier.
In this embodiment, the execution body may obtain the hardware identifier corresponding to the target device according to the instance identifier.
The hardware identifier is an identification character string defined by a target equipment manufacturer for the target equipment, and the operating system uses the character string to match the target equipment with a corresponding driving instruction file. The corresponding driving instruction file can be matched in the operating system through the hardware identification of the target equipment.
And step 204, updating the drive of the target device according to the drive guide file storage path and the hardware identifier.
In this embodiment, the execution body may update the driver of the target device according to the driver instruction file storage path and the hardware identifier.
The two parameters of the storage path of the drive instruction file and the hardware identifier can be transmitted into an update instruction to complete the update or reload of the drive of the target device.
It is worth mentioning that the operating system is identical for the same device defined driver instruction file and hardware identification. Therefore, the embodiment can reduce the manpower requirement and the deployment time of the system for deploying the target devices in batches.
The method for equipment driving heavy load solves the problem that the driving cannot be loaded when the system of the target equipment is deployed, and reduces the manpower requirement and the deployment time of the system for deploying the target equipment in batches.
In some optional implementations of this embodiment, the step 201 includes: the instance identification of the target device is looked up by executing a look-up command of the predetermined tool.
The predetermined tool refers to a tool which is installed in the operating system in advance, can perform a search operation in the operating system and find an instance identifier of the target device, for example, a devcon. Exe tool provided by microsoft for the Windows operating system. Illustratively, using the find command "find" of the devcon tool, a list of instance identifications of all devices can be viewed, so that the instance identifications of the target devices can be found through the list.
In some optional implementations of this embodiment, the step 202 includes: the drive guidance file storage path for the target device is looked up by executing the device driver node listing command of the predetermined tool.
The predetermined tool refers to a tool which is installed in the operating system in advance, can execute operations of the listed device driver nodes in the operating system and find a drive instruction file storage path of the target device, for example, a devcon. Exe tool provided by microsoft for a Windows operating system. Illustratively, the device driver node using the devcon tool enumerates the command "driverndes+instance identification," can view the driver guide file used by the target device corresponding to the instance identification, and find the storage path of the driver guide file of the target device. For example, the storage path of the driver installation instruction file of the GPU device in the Windows operating system is windows\inf\oem6.INF.
In some optional implementations of this embodiment, the step 203 further includes: by executing the machine code query command of the predetermined tool, the hardware identification corresponding to the target device is looked up.
The predetermined tool refers to a tool which is installed in the operating system in advance, can perform a machine code query operation in the operating system and find a hardware identifier of the target device, for example, a devcon. Exe tool provided by microsoft for a Windows operating system. Illustratively, using the machine code query command "hwids+instance identification" of the devcon tool, the hardware identification corresponding to the instance identification of the target device can be found.
In some optional implementations of this embodiment, the step 204 further includes: the driver of the target device is updated by executing the update command of the predetermined tool.
The predetermined tool refers to a tool which is installed in the operating system in advance, can perform an update operation in the operating system and update a driver of the target device, for example, a devcon. Exe tool provided by microsoft for the Windows operating system. For example, using the update command "update\Windows\INF\oem6. Inf+hardware identification" of the devcon tool, the update or reloading of the drive for the GPU device may be accomplished.
In some optional implementations of this embodiment, the method is applied to a startup script, where the startup script is integrated into a Windows system image file, and the Windows system image file is integrated with a driver of the target device.
Script (Script) is an executable file written in accordance with a certain format, also called macro or batch file, using a specific descriptive language. The script may typically be invoked and executed temporarily by an application program, and the startup script may run an executable file of the software. The startup script may call the method for device driver reloading provided in the above embodiment of the present application.
The image file is a file similar to an rar or zip compressed file, a specific series of files are manufactured into a single file according to a certain format for users to download, such as an operating system image and a game image, and the image file can be identified by specific software and recorded on an optical disc. The system image file contains an operating system file, a boot file, partition table information, and the like, and is used for installing and repairing a system, and the system image file can be understood to be a clone file for installing all data of an optical disc for the whole system, such as a microsoft original edition system, or can be a backup file of an operating system partition, such as a ghost system image.
Illustratively, the process of creating the Windows system image file is: installing a corresponding version of a Windows system to be deployed on a server provided with GPU equipment, then manually installing a GPU equipment driver according to the requirement of an application party, and enabling the driver to be loaded correctly, wherein the corresponding GPU computing or rendering functions are normal; then generating a system mirror image by the environment, and taking the mirror image as a template for batch deployment of GPU servers in a machine room; finally, a method for calling the device driver reload according to the embodiment of the application by a start script is designed.
By adopting the Windows system image file provided by the embodiment to carry out batch deployment on the target equipment server, the manpower requirement and the deployment time of batch deployment can be greatly reduced.
In some optional implementations of this embodiment, the method further includes stopping execution of the startup script in response to a successful drive update of the target device.
The startup script can judge whether the drive of the target device is updated or reloaded successfully through a return value of a preset tool. Wherein the predetermined tool can return success or failure, and information related to the failure. When there is an error in parameters passed to the predetermined tool, including command parameters, instance identification, drive direction file path, etc., the predetermined tool will perform the failure and return a failure result. And when the drive update or reloading of the target equipment is successful, stopping executing the start script, and ensuring that the start script is not executed when the target equipment is started next time, thereby improving the speed when the target equipment is restarted.
With further reference to fig. 3, a flow chart of another embodiment of a method of device driven reloading is shown, the method comprising the steps of:
step 301, searching for an instance identifier of a target device by executing a search command of a predetermined tool.
Step 302, searching a drive guidance file storage path of the target device by executing a device driver node listing command of the predetermined tool.
Step 303, by executing the machine code query command of the predetermined tool, the hardware identification corresponding to the target device is found.
Step 304, the driver of the target device is updated by executing the update command of the predetermined tool.
In step 305, the predetermined tool is deleted in response to the drive update of the target device being successful.
Wherein when the drive update or reloading of the target device is successful, files which are not necessary to be used in the future, such as predetermined tools, can be deleted, thereby increasing the speed at the time of restarting.
In some alternative implementations of the present embodiment, the target device is a GPU device, such as an NVIDIA GPU device.
In some alternative implementations of the present embodiment, the Windows system image file is installed on a variety of image processor servers. The hardware of each image processor may be the same or different. The image file of the Windows system is adopted to deploy various image processor servers, so that the problem of failure in loading of GPU drive when the Windows system is deployed in batches can be solved, and the deployed GPU servers do not need manual operation repair.
For ease of understanding, fig. 4 shows an application scenario diagram of one embodiment of a method of device-driven reloading according to the present application.
As shown in fig. 4, first, a Windows system image file is made, which includes the steps of: starting Windows server, installing NVIDIA driver, and deploying the start script of driver reload. The method for device driver reloading provided by the embodiment of the application can be called by the starting script; then generating a system mirror image based on the environment, and using the mirror image as a template for batch deployment of GPU servers in a machine room; and finally, deploying the generated system images to the GPU equipment server in batches.
With further reference to fig. 5, as an implementation of the method shown in the foregoing figures, the present application provides an embodiment of a device driving reload, where an embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus is particularly applicable to various electronic devices.
As shown in fig. 5, the apparatus 500 for driving heavy load by the device of the present embodiment may include: an instance identification acquisition module 501, a guide file acquisition module 502, a hardware identification acquisition module 503, and a drive update module 504. Wherein, the instance identifier obtaining module 501 is configured to obtain an instance identifier of the target device; a guidance file obtaining module 502 configured to obtain a driving guidance file storage path of the target device according to the instance identifier; a hardware identifier obtaining module 503 configured to obtain a hardware identifier corresponding to the target device according to the instance identifier; the driver update module 504 is configured to update the driver of the target device according to the driver guide file storage path and the hardware identification.
In this embodiment, in the apparatus 500 for driving heavy load by a device: the specific processes and technical effects of the instance identifier obtaining module 501, the instruction file obtaining module 502, the hardware identifier obtaining module 503, and the driving update module 504 may refer to the relevant descriptions of steps 201 to 204 in the corresponding embodiment of fig. 2, and are not described herein.
In some optional implementations of the present embodiment, the instance identification acquisition module is further configured to: the instance identification of the target device is looked up by executing a look-up command of the predetermined tool.
In some optional implementations of this embodiment, the instruction file acquisition module is further configured to: by executing the machine code query command of the predetermined tool, the hardware identification corresponding to the target device is looked up.
In some optional implementations of the present embodiment, the hardware identification acquisition module is further configured to: by executing the machine code query command of the predetermined tool, the hardware identification corresponding to the target device is looked up.
In some optional implementations of the present embodiment, the drive update module is further configured to: the driver of the target device is updated by executing the update command of the predetermined tool.
In some optional implementations of this embodiment, the device is configured in a startup script, the startup script is integrated in a Windows system image file, and the Windows system image file is integrated with a driver of the target device.
In some optional implementations of this embodiment, the apparatus further includes: and the termination module is configured to stop executing the startup script in response to successful drive update of the target device.
In some optional implementations of this embodiment, the apparatus further includes: and a deletion module configured to delete the predetermined tool in response to a drive update of the target device being successful.
In some alternative implementations of the present embodiment, the target device is an image processor.
In some alternative implementations of the present embodiment, the Windows system image file is installed on a variety of image processor servers.
As shown in fig. 6, a block diagram of an electronic device according to a method of device driving reload according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the application described and/or claimed herein.
As shown in fig. 6, the electronic device includes: one or more processors 601, memory 602, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions executing within the electronic device, including instructions stored in or on memory to display graphical information of the GUI on an external input/output device, such as a display device coupled to the interface. In other embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple electronic devices may be connected, each providing a portion of the necessary operations (e.g., as a server array, a set of blade servers, or a multiprocessor system). One processor 601 is illustrated in fig. 6.
Memory 602 is a non-transitory computer-readable storage medium provided herein. Wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method of device driver reloading provided herein. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to perform the method of device driver reloading provided herein.
The memory 602 is used as a non-transitory computer readable storage medium, and may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the method for device driver reloading in the embodiments of the present application (e.g., the instance id acquisition module 501, the instruction file acquisition module 502, the hardware id acquisition module 503, and the driver update module 504 shown in fig. 5). The processor 601 executes various functional applications of the server and data processing, i.e., implements the method of device driver reloading in the above-described method embodiments, by running non-transitory software programs, instructions, and modules stored in the memory 602.
The memory 602 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, at least one application program required for a function; the storage data area may store data created according to the use of the electronic device of the method of device-driven reloading, and the like. In addition, the memory 602 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 602 may optionally include memory remotely located with respect to processor 601, which may be connected to the electronic device of the method of device driven reloading via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the method of device driving reload may further include: an input device 603 and an output device 604. The processor 601, memory 602, input device 603 and output device 604 may be connected by a bus or otherwise, for example in fig. 6.
The input device 603 may receive input numeric or character information and key signal inputs related to user settings and function control of the electronic device that generate the method of device driving reloading, such as input devices for a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointer stick, one or more mouse buttons, a track ball, a joystick, etc. The output means 604 may include a display device, auxiliary lighting means (e.g., LEDs), tactile feedback means (e.g., vibration motors), and the like. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device may be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASIC (application specific integrated circuit), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
These computing programs (also referred to as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
According to the technical scheme of the application, firstly, the instance identifier of the target equipment is obtained; then, according to the instance identifier, a driving instruction file storage path of the target equipment is obtained; then, according to the instance identifier, acquiring a hardware identifier corresponding to the target equipment; and finally, updating the driver of the target equipment according to the storage path of the driver guide file and the hardware identifier, thereby solving the problem that the driver cannot be loaded when a system of the target equipment is deployed.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present application may be performed in parallel, sequentially, or in a different order, provided that the desired results of the technical solutions disclosed in the present application can be achieved, and are not limited herein.
The above embodiments do not limit the scope of the application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application are intended to be included within the scope of the present application.
Claims (14)
1. A method for reloading device driver is applied to a start script, wherein the start script is integrated in a Windows system image file, and the Windows system image file is integrated with a driver of a target device, and the method comprises the following steps:
acquiring an instance identifier of a target device;
acquiring a driving instruction file storage path of the target equipment according to the instance identifier;
acquiring a hardware identifier corresponding to the target equipment according to the instance identifier;
updating the driver of the target device according to the driver instruction file storage path and the hardware identifier, including: updating the driver of the target device by executing an update command of a predetermined tool;
stopping executing the start script in response to the successful drive update of the target device;
and deleting the predetermined tool in response to successful drive update of the target device.
2. The method of claim 1, wherein the obtaining an instance identification of a target device comprises:
and searching for the instance identifier of the target device by executing a search command of a predetermined tool.
3. The method according to claim 1 or 2, wherein the obtaining the driving guidance file storage path of the target device according to the instance identification comprises:
and searching a drive guidance file storage path of the target device by executing a device driver node listing command of a preset tool.
4. The method of claim 1, wherein the obtaining a hardware identification corresponding to the target device from the instance identification comprises:
by executing a machine code query command of a predetermined tool, a hardware identification corresponding to the target device is found.
5. The method of claim 1, wherein the target device is an image processor.
6. The method of claim 5, wherein the Windows system image file is installed on a plurality of image processor servers.
7. A device for device driver reloading, wherein the device is configured in a start script, the start script is integrated in a Windows system image file, and the Windows system image file is integrated with a driver of a target device, the device comprising:
an instance identifier obtaining module configured to obtain an instance identifier of the target device;
the instruction file acquisition module is configured to acquire a driving instruction file storage path of the target device according to the instance identifier;
a hardware identifier obtaining module configured to obtain a hardware identifier corresponding to the target device according to the instance identifier;
a driver update module configured to update a driver of the target device according to the driver instruction file storage path and the hardware identifier, including: updating the driver of the target device by executing an update command of a predetermined tool;
a termination module configured to stop execution of the startup script in response to a drive update of the target device being successful;
and a deletion module configured to delete a predetermined tool in response to a drive update of the target device being successful.
8. The apparatus of claim 7, wherein the instance identification acquisition module is further configured to:
and searching for the instance identifier of the target device by executing a search command of a predetermined tool.
9. The apparatus of claim 7 or 8, wherein the instruction file acquisition module is further configured to:
by executing a machine code query command of a predetermined tool, a hardware identification corresponding to the target device is found.
10. The apparatus of claim 7, wherein the hardware identification acquisition module is further configured to:
by executing a machine code query command of a predetermined tool, a hardware identification corresponding to the target device is found.
11. The apparatus of claim 7, wherein the target device is an image processor.
12. The apparatus of claim 11, wherein the Windows system image file is installed on a plurality of image processor servers.
13. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.
14. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011332811.3A CN112328328B (en) | 2020-11-24 | 2020-11-24 | Method, device, equipment and storage medium for equipment driving reload |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011332811.3A CN112328328B (en) | 2020-11-24 | 2020-11-24 | Method, device, equipment and storage medium for equipment driving reload |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112328328A CN112328328A (en) | 2021-02-05 |
| CN112328328B true CN112328328B (en) | 2023-07-25 |
Family
ID=74309380
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011332811.3A Active CN112328328B (en) | 2020-11-24 | 2020-11-24 | Method, device, equipment and storage medium for equipment driving reload |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112328328B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112925572B (en) * | 2021-03-01 | 2023-05-23 | 联想(北京)有限公司 | Control method and device and electronic equipment |
| CN116149759B (en) * | 2023-04-20 | 2023-07-14 | 深圳市吉方工控有限公司 | UEFI (unified extensible firmware interface) drive unloading method and device, electronic equipment and readable storage medium |
| CN117047785B (en) * | 2023-10-11 | 2023-12-19 | 大扬智能科技(北京)有限公司 | Robot control method, robot control device, and robot system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007115470A1 (en) * | 2006-04-11 | 2007-10-18 | Huawei Technologies Co., Ltd. | A device configuration information management method, the server and the system thereof |
| CN107066300A (en) * | 2017-04-21 | 2017-08-18 | 杭州宏杉科技股份有限公司 | The firmware upgrade method and storage device of a kind of storage device |
| CN107526777A (en) * | 2017-07-21 | 2017-12-29 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus handled based on version number file |
| CN108268346A (en) * | 2018-02-13 | 2018-07-10 | 苏州龙信信息科技有限公司 | Data back up method, device, equipment and storage medium |
| CN108717440A (en) * | 2018-05-10 | 2018-10-30 | 沈阳东软医疗系统有限公司 | A kind of method, apparatus, equipment and the storage medium of automatic acquisition correction file |
| CN109614157A (en) * | 2018-12-27 | 2019-04-12 | 联想(北京)有限公司 | A kind of configuration method of system, device and storage medium |
| CN110472413A (en) * | 2019-07-26 | 2019-11-19 | Oppo广东移动通信有限公司 | Device management method, device, storage medium and electronic equipment based on jenkins |
-
2020
- 2020-11-24 CN CN202011332811.3A patent/CN112328328B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007115470A1 (en) * | 2006-04-11 | 2007-10-18 | Huawei Technologies Co., Ltd. | A device configuration information management method, the server and the system thereof |
| CN107066300A (en) * | 2017-04-21 | 2017-08-18 | 杭州宏杉科技股份有限公司 | The firmware upgrade method and storage device of a kind of storage device |
| CN107526777A (en) * | 2017-07-21 | 2017-12-29 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus handled based on version number file |
| CN108268346A (en) * | 2018-02-13 | 2018-07-10 | 苏州龙信信息科技有限公司 | Data back up method, device, equipment and storage medium |
| CN108717440A (en) * | 2018-05-10 | 2018-10-30 | 沈阳东软医疗系统有限公司 | A kind of method, apparatus, equipment and the storage medium of automatic acquisition correction file |
| CN109614157A (en) * | 2018-12-27 | 2019-04-12 | 联想(北京)有限公司 | A kind of configuration method of system, device and storage medium |
| CN110472413A (en) * | 2019-07-26 | 2019-11-19 | Oppo广东移动通信有限公司 | Device management method, device, storage medium and electronic equipment based on jenkins |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112328328A (en) | 2021-02-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112328328B (en) | Method, device, equipment and storage medium for equipment driving reload | |
| CN110780890B (en) | System upgrading method, device, electronic equipment and medium | |
| CN111258609B (en) | Upgrading method and device of Kubernetes cluster, electronic equipment and medium | |
| US20210208951A1 (en) | Method and apparatus for sharing gpu, electronic device and readable storage medium | |
| WO2018103550A1 (en) | Application program page processing method and apparatus | |
| CN111984476B (en) | Test method and device | |
| JP7167222B2 (en) | APPLET DATA ACQUISITION METHOD, APPARATUS, DEVICE, AND STORAGE MEDIUM | |
| US11663037B2 (en) | Service information processing method, apparatus, device and computer storage medium | |
| CN111400000B (en) | Network request processing method, device, equipment and storage medium | |
| CN111767090A (en) | Method and device for starting small program, electronic equipment and storage medium | |
| CN110704162B (en) | Method, device and equipment for sharing container mirror image by physical machine and storage medium | |
| CN111506401B (en) | Automatic driving simulation task scheduling method and device, electronic equipment and storage medium | |
| CN110995480A (en) | Block chain network deployment method, device, electronic equipment and medium | |
| CN112506854A (en) | Method, device, equipment and medium for storing page template file and generating page | |
| EP3812898A2 (en) | Container-based method for application startup | |
| JP2021131897A (en) | Scheduling method, device, equipment, storage equipment, and program | |
| CN111615171B (en) | Access method and device of wireless local area network | |
| CN110908675B (en) | Method and device for acquiring running environment and electronic equipment | |
| CN111399888B (en) | Audio processing chip processing method and device and electronic equipment | |
| CN111796851A (en) | Client base library updating method and device, electronic equipment and storage medium | |
| WO2023169193A1 (en) | Method and device for generating smart contract | |
| CN115576565A (en) | Application program deployment method and device, electronic equipment and storage medium | |
| CN113163257B (en) | Screen projection method, device, equipment and storage medium | |
| CN110286973B (en) | Key triggering event processing method, intelligent terminal and storage medium | |
| CN112379954A (en) | Data processing method, device and equipment of application program and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |