public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Identifying missing modules...
Date: Sun, 23 Jan 2011 22:03:49 +0200	[thread overview]
Message-ID: <201101232203.49581.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20110123180815.GC4486@solfire>

Apparently, though unproven, at 20:08 on Sunday 23 January 2011, 
meino.cramer@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: <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?


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



  parent reply	other threads:[~2011-01-23 20:05 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 ` Alan McKinnon [this message]
2011-01-23 22:13 ` [gentoo-user] " Mark Knecht
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=201101232203.49581.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@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