SOLVED: Drivers: general/preferred/additional/byAudit
SOLVED: Drivers: general/preferred/additional/byAudit
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
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
Zuletzt geändert von giner am 08 Dez 2014, 15:33, insgesamt 1-mal geändert.
Re: Drivers: general/preferred/additional/byAudit - confused
Yes,
http://download.uib.de/opsi4.0/doc/html ... ntegration
regards,
bardo wolf
http://download.uib.de/opsi4.0/doc/html ... ntegration
So additional and byAudit are on the same level (say 3)"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."
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
Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.
Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.
uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de
Re: Drivers: general/preferred/additional/byAudit - confused
Hello Wolf,
What is the source for Vendor/Model names when using "byAudit" ?
Regards,
Stanislav German-Evtushenko
What is the source for Vendor/Model names when using "byAudit" ?
Regards,
Stanislav German-Evtushenko
- n.wenselowski
- Ex-uib-Team
- Beiträge: 3194
- Registriert: 04 Apr 2013, 12:15
Re: Drivers: general/preferred/additional/byAudit - confused
Hello Stanislav,
With kind regards
Niko
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.giner hat geschrieben:What is the source for Vendor/Model names when using "byAudit" ?
With kind regards
Niko
Code: Alles auswählen
import OPSI
Re: Drivers: general/preferred/additional/byAudit - confused
Hello Niko,
Great. Thanks a lot for your clarification.
Best regards,
Stanislav
Great. Thanks a lot for your clarification.
Best regards,
Stanislav