On Sun, Oct 9, 2011 at 12:53 AM, Lavender <[email protected]> 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. > I mean I can't figure out that which > module correspond to which device though I know the hard devices consisted > of my PC. So I need information about contact between them so that I could > know what modules need to be chosen in kernel , also the options of kernel > are quiet a lot , there're many features that I never heard , I want to > find them out . > May be you think these problems are too easy , but I have never contacted > them before . Pretty sure we've all been there before. It helps to have some foreknowledge about hardware standards and the like, but it's not strictly necessary. As long as you're interested in *how* to find information, and use that knowledge once you find it, I don't doubt people will be interested in helping. -- :wq
