All of lore.kernel.org
 help / color / mirror / Atom feed
From: gshan <gshan@alcatel-lucent.com>
To: peter360 <peter360@fastmail.us>
Cc: linux-kernel@vger.kernel.org
Subject: Re: which .ko file?
Date: Mon, 03 Nov 2008 13:10:00 +0800	[thread overview]
Message-ID: <490E87A8.8020600@alcatel-lucent.com> (raw)
In-Reply-To: <20297391.post@talk.nabble.com>

peter360 wrote:
> Hi,
>
> How do I determine the .ko file used for a certain kernel module in a
> running kernel?  For example, on my dell laptop I see
> $ lsmod | grep 3945
> ipw3945               230952  1 
> ieee80211              65161  1 ipw3945
>
> $ modinfo ipw3945
> modinfo: could not open /lib/modules/2.6.18-92.1.1.el5/extra/ipw3945.ko: No
> such file or directory
>
> $ locate ipw3945.ko
> /lib/modules/2.6.18-52.el5/weak-updates/ipw3945.ko
> /lib/modules/2.6.18-52.el5/weak-updates/ipw3945/ipw3945.ko
> /lib/modules/2.6.18-8.1.4.el5/extra/ipw3945/ipw3945.ko
> /lib/modules/2.6.18-92.1.1.el5/weak-updates/ipw3945/ipw3945.ko
> /lib/modules/2.6.18-92.1.10.el5/weak-updates/ipw3945.ko
> /lib/modules/2.6.18-92.1.10.el5/weak-updates/ipw3945/ipw3945.ko
>
> $ uname -a
> Linux mylaptop 2.6.18-92.1.1.el5 #1 SMP Thu May 22 09:01:47 EDT 2008 x86_64
> x86_64 x86_64 GNU/Linux
>
> How do I find out which ipw3945.ko file was actually loaded into the kernel?
> thanks!
>   
I think it's 
/lib/modules/2.6.18-92.1.1.el5/weak-updates/ipw3945/ipw3945.ko, which
matches your kernel version, right? You could remove it to another 
directory instead
of current used /lib/modules/2.6.18-92.1.1.el5/, then try "lsmod | grep 
3495". If you
still could see it, then my guess is wrong. Otherwise, I'm correct.

  reply	other threads:[~2008-11-03  5:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03  5:03 which .ko file? peter360
2008-11-03  5:10 ` gshan [this message]
2008-11-03  6:35   ` peter360

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=490E87A8.8020600@alcatel-lucent.com \
    --to=gshan@alcatel-lucent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter360@fastmail.us \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.