1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 01/23/11 16:13, Mark Knecht wrote: |
5 |
> On Sun, Jan 23, 2011 at 10:08 AM, <meino.cramer@×××.de> wrote: |
6 |
>> |
7 |
>> Hi, |
8 |
>> |
9 |
>> when doing as root |
10 |
>> |
11 |
>> lspci -vk |
12 |
>> |
13 |
>> I get all pci devices and "bus inhabitants" listed. |
14 |
>> Additionally there are often two lines added to each |
15 |
>> device saying similiar things like: |
16 |
>> |
17 |
>> Kernel driver in use: >XYZ> |
18 |
>> Kernel modules: <XYZ> |
19 |
>> |
20 |
>> and there other devices do not have similiar entries. |
21 |
>> |
22 |
>> My question is: How can I distinguish devices/entities, |
23 |
>> which do not need any driver to work and those, which |
24 |
>> need a driver but in the current setup the driver wasn't |
25 |
>> compiled in/compiled as module? |
26 |
>> |
27 |
>> Thank you very much in advance for any help! |
28 |
>> Best regards, |
29 |
>> mcc |
30 |
> |
31 |
> Devices that need a driver are listed as 'Kernel driver in use:' |
32 |
> whether the driver is compiled in or not. |
33 |
> |
34 |
> Devices that have their driver compiled in do not have the line |
35 |
> 'Kernel modules:' |
36 |
> |
37 |
> Devices that have neither line are controlled by the kernel but don't |
38 |
> need anything from the driver section. |
39 |
> |
40 |
> I suppose there is the possibility that lspci could find a PCI device |
41 |
> which hasn't had a driver selected as module or builtin and then not |
42 |
> show anything. In this case I expect that the device wouldn't |
43 |
> function. |
44 |
> |
45 |
> Hope this helps, |
46 |
> Mark |
47 |
> |
48 |
Check out http://www.kernel-seeds.org for a walkthrough of kernel |
49 |
configuration or dump the results of lspci -n into |
50 |
http://kmuto.jp/debian/hcl/ for a list of modules |
51 |
|
52 |
James Wall |
53 |
- -- |
54 |
No trees were harmed in the sending of this message. However, a large |
55 |
number of electrons were terribly inconvenienced. |
56 |
-----BEGIN PGP SIGNATURE----- |
57 |
Version: GnuPG v2.0.16 (GNU/Linux) |
58 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
59 |
|
60 |
iQEcBAEBAgAGBQJNPk3zAAoJEISPTA/exVD8/WgH/114CSqMLPm0us9gOnUJmJZM |
61 |
8bvpZDa1x5xWCjLcI4zn0fwqo8UZpQBGjFYDtrrGnSwXpZSbN4H0mCCZOVZDoNFZ |
62 |
0szNemJwF68oMm8u71D5LFBianCZfCQmsMAf5bC0nG4SJe80YnREDPJVRt9xvl91 |
63 |
lBRrBDvV1ZxOzOl/gBIA3si8aiKWQ6V+WeoQi7nO1zaCWMw1p8LuyoONuPModl+U |
64 |
sjt67czGRE6bnC8Y5Lu48v4zJU6jKM20zjdTaTPcrLOce0kzYNqBFRnDCWRO2TRu |
65 |
jr+Se9JNcq97IQOWSiwPcCUW1Q3a9p2+WAz045FUwrKkT/08OvRKDw4S9rdSLa0= |
66 |
=77yQ |
67 |
-----END PGP SIGNATURE----- |