From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Identifying missing modules...
Date: Sun, 23 Jan 2011 14:13:00 -0800 [thread overview]
Message-ID: <AANLkTin85edYMzOnq5yWzHkSWJYx1mLuOZp59RkhdA5g@mail.gmail.com> (raw)
In-Reply-To: <20110123180815.GC4486@solfire>
On Sun, Jan 23, 2011 at 10:08 AM, <meino.cramer@gmx.de> 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: <XYZ>
>
> 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
next prev parent reply other threads:[~2011-01-23 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 18:08 [gentoo-user] Identifying missing modules meino.cramer
2011-01-23 20:03 ` [gentoo-user] " walt
2011-01-24 3:25 ` meino.cramer
2011-01-23 20:03 ` [gentoo-user] " Alan McKinnon
2011-01-23 22:13 ` Mark Knecht [this message]
2011-01-25 4:13 ` James Wall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTin85edYMzOnq5yWzHkSWJYx1mLuOZp59RkhdA5g@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox