| 1 |
Apparently, though unproven, at 20:08 on Sunday 23 January 2011, |
| 2 |
meino.cramer@×××.de did opine thusly: |
| 3 |
|
| 4 |
> Hi, |
| 5 |
> |
| 6 |
> when doing as root |
| 7 |
> |
| 8 |
> lspci -vk |
| 9 |
> |
| 10 |
> I get all pci devices and "bus inhabitants" listed. |
| 11 |
> Additionally there are often two lines added to each |
| 12 |
> device saying similiar things like: |
| 13 |
> |
| 14 |
> Kernel driver in use: >XYZ> |
| 15 |
> Kernel modules: <XYZ> |
| 16 |
> |
| 17 |
> and there other devices do not have similiar entries. |
| 18 |
> |
| 19 |
> My question is: How can I distinguish devices/entities, |
| 20 |
> which do not need any driver to work and those, which |
| 21 |
> need a driver but in the current setup the driver wasn't |
| 22 |
> compiled in/compiled as module? |
| 23 |
|
| 24 |
|
| 25 |
lspci won't show you the info you request. That's a function known only the |
| 26 |
the kernel, not to userspace. What lspci does is find stuff on the pci bus, |
| 27 |
then go looking for modules that are attached to it. |
| 28 |
|
| 29 |
Note that it looks for modules (via some kernel<->userspace interface), not |
| 30 |
any kernel code driving the device. |
| 31 |
|
| 32 |
Your question is an entirely different beast. I think your best bet is google, |
| 33 |
or to find some web site showing a kernel/hardware/module compatibility list. |
| 34 |
|
| 35 |
-- |
| 36 |
alan dot mckinnon at gmail dot com |
Archives