From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ph6Bc-0007Vl-Ea for garchives@archives.gentoo.org; Sun, 23 Jan 2011 20:05:21 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7C8F6E07B1; Sun, 23 Jan 2011 20:03:17 +0000 (UTC) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 27855E07B1 for ; Sun, 23 Jan 2011 20:03:16 +0000 (UTC) Received: by wyf22 with SMTP id 22so4706675wyf.40 for ; Sun, 23 Jan 2011 12:03:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:subject:date:user-agent:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; bh=ZLjEW5AYDRhBta9EX351xgPKak2zf1pP+Z7oFtw7sYc=; b=Mz7tuoeGL0DdicBr7boYLiAEg72513B4uALbnLpWjtI+/q3xv7c0VDpNRGjb2C2vkL Fq+IBzM1aprj4YIj7/hxDMN3ngUdVXUFPGo+yKKtqQJjmUt6bHnznpbRWBx5J9p7eVel BSVzfrauMtrS6jbyx1oD/vPcMCjtc+HKH04r8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=to+Cz2HAaATZav2SqDJ/XoRImiZAwKotdKziRIfXtI0dJgtY4hcdcbgnmWjvCW/wcV aXxl77MecPD7O2yitSSGefEGReE05IJJ1Gcb/KTpM2e95LbuO75BjVkWejG5YaTlwwUb xrufnoVIG74GD0+9se03B9ai3c7G9H1I5fpG0= Received: by 10.216.59.143 with SMTP id s15mr1592607wec.49.1295812996342; Sun, 23 Jan 2011 12:03:16 -0800 (PST) Received: from nazgul.localnet (196-215-42-107.dynamic.isadsl.co.za [196.215.42.107]) by mx.google.com with ESMTPS id o19sm6177879wee.26.2011.01.23.12.03.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 23 Jan 2011 12:03:15 -0800 (PST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Identifying missing modules... Date: Sun, 23 Jan 2011 22:03:49 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.37-ck; KDE/4.5.5; x86_64; ; ) References: <20110123180815.GC4486@solfire> In-Reply-To: <20110123180815.GC4486@solfire> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201101232203.49581.alan.mckinnon@gmail.com> X-Archives-Salt: X-Archives-Hash: 281182acd99b5adf35b318c094d062f8 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: > > 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