SOLVED: Drivers: general/preferred/additional/byAudit

[giner]

Hello,

There are four levels of drivers:
- general
- preferred
- additional
- byAudit

And I'm completely confused. First three (as I get form the manual) are checked by vendor/product IDs and the difference between them is not clear. Do these levels work just as priorities? General = 1, Preferred = 2, Additional = 3. If we find in 3 - we use it, if not, search in 2. If we find in 2 - we use it, if not, search in 1. Am I right or there is something else?

And another thing is byAduit. What is it for? How does it work?

Best regards,
Stanislav

[wolfbardo]

Yes,

http://download.uib.de/opsi4.0/doc/html ... ntegration

"Processing of the Different Levels of Driver Integration

The top priority is given to drivers that are found using the property additional_drivers or using the inventory data in ./drivers/drivers/additional/byAudit. Tests will be made during driver integration to determine which drivers are already installed on which hardware devices. When a driver is not found for a device, the following method will be used to search for drivers."

So additional and byAudit are on the same level (say 3)

For devices that have drivers that were not listed in additional_drivers, opsi will search for, and integrate, an appropriate driver based off of the PCI ID (ie. USB-, HD_Audio-ID)."

regards,
bardo wolf

[giner]

Hello Wolf,

What is the source for Vendor/Model names when using "byAudit" ?

Regards,
Stanislav German-Evtushenko

[n.wenselowski]

Hello Stanislav,

What is the source for Vendor/Model names when using "byAudit" ?

we rely on the output created by lshw. You can use the hwinvent-netboot product to get this information from a system that is able to boot via network but does not have any OS installed. After that you can use the data from the hardware inventory tab.


With kind regards

Niko

[giner]

Hello Niko,

Great. Thanks a lot for your clarification.

Best regards,
Stanislav