hey guys, please don't get me wrong on this one, i mean no offense. can anyone explain to me what this is? are these lavender threads some kind of trolling i don't get?
it (apparently on purpose, since hints in that direction are ignored) combines loads of annoying qualities: - nondescriptive titles - doing everything to rip apart threads: no In-Reply-To and even subject changes - no line-breaks - difficult to read incorrect punctuation (plenk) - problem details are kept nebulous and info requests are ignored - none of the proposed solutions are ever tried or commented it's nice how much many people on this this list are willing to help in spite of all this. but am i really the only one who finds the behavior described above at least confusing? anyway, i'm quite convinced it is fake. /jonas Am Sun, 9 Oct 2011 21:44:28 +0800 schrieb "Lavender" <448463...@qq.com>: > Thank you all ! Thanks for helping , now I know which things I should > do . > > ------------------ 原始邮件 ------------------ > 发件人: "Michael Mol"<mike...@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 <mike...@gmail.com> wrote: > > On Sun, Oct 9, 2011 at 12:53 AM, Lavender <448463...@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. >
