From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Anyone can afford information about build kernel?
Date: Sun, 09 Oct 2011 08:59:43 -0500 [thread overview]
Message-ID: <4E91A8CF.9090105@gmail.com> (raw)
In-Reply-To: <CA+czFiB8jkqRJkAJmYZHSXku_a-4-QQSfFg22gPk2C8+ge9kbQ@mail.gmail.com>
Michael Mol wrote:
> On Sun, Oct 9, 2011 at 9:30 AM, Michael Mol<mikemol@gmail.com> wrote:
>> On Sun, Oct 9, 2011 at 12:53 AM, Lavender<448463782@qq.com> wrote:
>>> Yeah, your reply is exact what I mean , but I'm really confused by those
>>> modules' names, I can't find any contact between the hard device name and
>>> its module name . For example, there is a module named 3c59x.ko , I totally
>>> don't know what device it present for ,
>> This got a *lot* easier back when sysfs was added.
>>
>> cd /sys/module/<modulename>/drivers/
>>
>> And go from there
>>
>> lspci will help you see the 'text' name for the device in question.
>>
>> For example, let's say I don't know what the 'ahci' module is for.
>>
>> $ cd /sys/module/ahci/drivers
>> $ ls
>> pci:ahci
>> $ cd pci\:ahci/
>> $ ls
>> 0000:00:11.0 bind module new_id remove_id uevent unbind
>> $ sudo lspci|grep 11.0
>> 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA
>> Controller [AHCI mode]
>> $
>>
>> So now I know the ahci module manages my SATA controller.
> Came up with something possibly a little handier. This command should
> tell you what driver is associated with every device on the system.
>
> find /sys/devices -name driver -print0|xargs -0 ls -l|cut -d' '
> -f10-|sed -e 's/\.\.\///g'
>
> Output could probably still be a bit better cleaned up, but it should help.
>
Let's not fail to mention lspci -k either. That is a handy tool.
Dale
:-) :-)
next prev parent reply other threads:[~2011-10-09 14:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 4:53 [gentoo-user] Anyone can afford information about build kernel? Lavender
2011-10-09 5:55 ` Nilesh Govindarajan
2011-10-09 13:30 ` Michael Mol
2011-10-09 13:40 ` Michael Mol
2011-10-09 13:59 ` Dale [this message]
2011-10-09 14:05 ` Michael Mol
2011-10-09 14:02 ` Dale
2011-10-09 14:09 ` Michael Mol
2011-10-09 15:05 ` Dale
-- strict thread matches above, loose matches on Subject: below --
2011-10-09 9:49 Lavender
2011-10-09 16:53 ` Volker Armin Hemmann
2011-10-10 8:26 ` Spidey
2011-10-10 9:03 ` Neil Bothwick
2011-10-09 0:55 Lavender
2011-10-09 1:19 ` Nick Khamis
2011-10-09 1:28 ` Dale
2011-10-09 1:39 ` Nilesh Govindarajan
2011-10-09 6:21 ` Volker Armin Hemmann
2011-10-09 13:56 ` Dale
2011-10-09 14:07 ` meino.cramer
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=4E91A8CF.9090105@gmail.com \
--to=rdalek1967@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