Re: [gentoo-user] Identifying missing modules...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/23/11 16:13, Mark Knecht wrote: > On Sun, Jan 23, 2011 at 10:08 AM, wrote: >> >> Hi, >> >> when doing as root >> >>lspci -vk >> >> I get all pci devices and "bus inhabitants" listed. >> Additionally there are often two lines added to each >> device saying similiar things like: >> >>Kernel driver in use: >XYZ> >>Kernel modules: >> >> and there other devices do not have similiar entries. >> >> My question is: How can I distinguish devices/entities, >> which do not need any driver to work and those, which >> need a driver but in the current setup the driver wasn't >> compiled in/compiled as module? >> >> Thank you very much in advance for any help! >> Best regards, >> mcc > > Devices that need a driver are listed as 'Kernel driver in use:' > whether the driver is compiled in or not. > > Devices that have their driver compiled in do not have the line > 'Kernel modules:' > > Devices that have neither line are controlled by the kernel but don't > need anything from the driver section. > > I suppose there is the possibility that lspci could find a PCI device > which hasn't had a driver selected as module or builtin and then not > show anything. In this case I expect that the device wouldn't > function. > > Hope this helps, > Mark > Check out http://www.kernel-seeds.org for a walkthrough of kernel configuration or dump the results of lspci -n into http://kmuto.jp/debian/hcl/ for a list of modules James Wall - -- No trees were harmed in the sending of this message. However, a large number of electrons were terribly inconvenienced. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNPk3zAAoJEISPTA/exVD8/WgH/114CSqMLPm0us9gOnUJmJZM 8bvpZDa1x5xWCjLcI4zn0fwqo8UZpQBGjFYDtrrGnSwXpZSbN4H0mCCZOVZDoNFZ 0szNemJwF68oMm8u71D5LFBianCZfCQmsMAf5bC0nG4SJe80YnREDPJVRt9xvl91 lBRrBDvV1ZxOzOl/gBIA3si8aiKWQ6V+WeoQi7nO1zaCWMw1p8LuyoONuPModl+U sjt67czGRE6bnC8Y5Lu48v4zJU6jKM20zjdTaTPcrLOce0kzYNqBFRnDCWRO2TRu jr+Se9JNcq97IQOWSiwPcCUW1Q3a9p2+WAz045FUwrKkT/08OvRKDw4S9rdSLa0= =77yQ -END PGP SIGNATURE-
Re: [gentoo-user] Identifying missing modules...
On Sun, Jan 23, 2011 at 10:08 AM, wrote: > > Hi, > > when doing as root > > lspci -vk > > I get all pci devices and "bus inhabitants" listed. > Additionally there are often two lines added to each > device saying similiar things like: > > Kernel driver in use: >XYZ> > Kernel modules: > > and there other devices do not have similiar entries. > > My question is: How can I distinguish devices/entities, > which do not need any driver to work and those, which > need a driver but in the current setup the driver wasn't > compiled in/compiled as module? > > Thank you very much in advance for any help! > Best regards, > mcc Devices that need a driver are listed as 'Kernel driver in use:' whether the driver is compiled in or not. Devices that have their driver compiled in do not have the line 'Kernel modules:' Devices that have neither line are controlled by the kernel but don't need anything from the driver section. I suppose there is the possibility that lspci could find a PCI device which hasn't had a driver selected as module or builtin and then not show anything. In this case I expect that the device wouldn't function. Hope this helps, Mark
Re: [gentoo-user] Identifying missing modules...
Apparently, though unproven, at 20:08 on Sunday 23 January 2011, meino.cra...@gmx.de did opine thusly: > Hi, > > when doing as root > > lspci -vk > > I get all pci devices and "bus inhabitants" listed. > Additionally there are often two lines added to each > device saying similiar things like: > > Kernel driver in use: >XYZ> > Kernel modules: > > and there other devices do not have similiar entries. > > My question is: How can I distinguish devices/entities, > which do not need any driver to work and those, which > need a driver but in the current setup the driver wasn't > compiled in/compiled as module? lspci won't show you the info you request. That's a function known only the the kernel, not to userspace. What lspci does is find stuff on the pci bus, then go looking for modules that are attached to it. Note that it looks for modules (via some kernel<->userspace interface), not any kernel code driving the device. Your question is an entirely different beast. I think your best bet is google, or to find some web site showing a kernel/hardware/module compatibility list. -- alan dot mckinnon at gmail dot com
