public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lavender <448463782@qq.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] 回复: [gentoo-user] Anyone can afford information about build kernel?
Date: Sun, 9 Oct 2011 21:44:28 +0800	[thread overview]
Message-ID: <tencent_60731DDF34E7BCBD38EF1331@qq.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]

Thank you all ! Thanks for helping , now I know which things I should do .
   
  
  ------------------ 原始邮件 ------------------
  发件人: "Michael Mol"<mikemol@gmail.com>;
 发送时间: 2011年10月9日(星期天) 晚上9:40
 收件人: "gentoo-user"<gentoo-user@lists.gentoo.org>; 
 
 主题: Re: [gentoo-user] Anyone can afford information about build kernel?

  
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.

-- 
:wq

[-- Attachment #2: Type: text/html, Size: 2505 bytes --]

             reply	other threads:[~2011-10-09 13:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 13:44 Lavender [this message]
2011-10-10 16:32 ` 回复: [gentoo-user] Anyone can afford information about build kernel? James
2011-10-11 11:03 ` [gentoo-user] " Jonas de Buhr
2011-10-11 11:51   ` this is spam (was: Re: [gentoo-user] 回复: [gentoo-user] Anyone can afford information about build kernel?) Jonas de Buhr
2011-10-11 12:54     ` Mick
2011-10-11 15:08       ` Jonas de Buhr
2011-10-11 18:58         ` Alan McKinnon
2011-10-11 23:16         ` [gentoo-user] " Matthew Finkel
2011-10-12  0:00           ` Alan McKinnon
2011-10-12 12:34             ` Neil Bothwick
2011-10-13  6:59               ` Alan McKinnon
2011-10-12 12:08           ` [gentoo-user] Re: this is spam Jonas de Buhr
2011-10-11 12:54   ` [gentoo-user] Re: [gentoo-user] 回复: [gentoo-user] Anyone can afford information about build kernel? Michael Mol
2011-10-11 15:38     ` Jonas de Buhr
2011-10-11 15:49       ` [gentoo-user] " Michael Mol

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=tencent_60731DDF34E7BCBD38EF1331@qq.com \
    --to=448463782@qq.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