How To Install Unknown Device Drivers In Device Manager / How To Find Drivers For Known Devices Usb

How to Find Drivers for Unknown Driver in the Device / devices windows 10 doesn't recognise fix / Manage Troubleshoot and fix Device Driver Problems / Identify Drivers for an Unknown Device using device identifier and ADA64.

1)If you go to start
2)control panel
3)Device manager

You will be able to see the devices which the computer cannot
identify any drivers for,I have shown 2 ways the first way being the
easiest but the 2nd more reliable method use the first software as i do to locate the unknown device in device manager,It will have all
the hardware details there then use ADA64 too make sure that the drivers you are going to download is for the correct hardware.

There will be a more indeapth video on AIDA64 as its a great bit of software and very help full..

Please if this video helped you click the like and subscribe button as it will go a long way to helping support this channel.

Thank you all have a nice week any comments or questions just leave them down below i aim to get back within the 1hr depending on the day of the week

Finding device drivers in linux below.
=============================
Finding the Kernel Driver

lsusb

Using usbutils
============
The usbutils package on Debian, at least) includes a script called usb-devices. If you run it, it outputs information about the devices on the system, including which driver is used:

$ usb-devices

Using debugfs
============
If you have debugfs mounted, the kernel maintains a file in the same format as usb-devices prints out at /sys/kernel/debug/usb/devices; you can view with less, etc. Note that debugfs interfaces are not stable, so different kernel versions may print in a different format, or be missing the file entirely.

Once again, this only shows the current driver, not the default.


Using only basic utilities to read /sys directly
====================================
You can get the information out of /sys, thought its more painful than lspci. These /sys interfaces should be reasonably stable, so if you're writing a shell script, this is probably how you want to do it.

Initially, lsusb seems to count devices from 1, /sys from 0. So 10-2 is a good guess for where to find the APC UPS lsusb gives as bus 10, device 3. Unfortunately, over time that mapping breaks down—sysfs re-uses numbers even when device numbers aren't. The devnum file's contents will match the device number given by lsusb, so you can do something like this:

$ grep -l '^3$' /sys/bus/usb/devices/10-*/devnum # the ^ and $ to prevent also matching 13, 31, etc.
/sys/bus/usb/devices/10-2/devnum
so its 10.2

cd /sys/bus/usb/devices/10-2
$ ls

We can be sure this is the right device by cating a few of the files
$ cat idVendor idProduct manufacturer product :

$ cat 10-2\:1.0/modalias usb:v051Dp0002d0106dc00dsc00dp00ic03isc00ip00in00
$ readlink driver../../../../../../bus/usb/drivers/usbfs

So, the current driver is usbfs. You can find the default driver by asking modinfo about the modalias:
$ /sbin/modinfo `cat 10-2\:1.0/modalias`

So, the APC UPS defaults to the hid driver, which is indeed correct. And its currently using usbfs, which is correct since nut's usbhid-ups is monitoring it.