From: Pavel Roskin <proski@gnu.org>
To: Rakesh Kumar <gopchandani@gmail.com>
Cc: ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] On ath9k debugfs, having trouble recompiling and inserting only ath9k
Date: Mon, 12 Apr 2010 17:49:26 -0400 [thread overview]
Message-ID: <1271108966.15194.4.camel@mj> (raw)
In-Reply-To: <n2icdc21431004112229n9303fcc1s788eadda177d079a@mail.gmail.com>
On Mon, 2010-04-12 at 00:29 -0500, Rakesh Kumar wrote:
> So I modified few entries in ath9k's debug.c and used them in the
> code. Recompiled the module ath9k, went painlessly. But when I try to
> do following:
>
> sudo insmod drivers/net/wireless/ath/ath9k/ath9k.ko
>
> I get the following error: insmod: error inserting
> 'drivers/net/wireless/ath/ath9k/ath9k.ko': -1 Unknown symbol in module
Please use modprobe, not insmod, as modprobe can resolve symbols and
load the requisite modules first.
If modprobe doesn't help, use the "dmesg" command to see the kernel log.
You should see messages about unresolved symbols. Maybe you misspelled
some function?
> I remember this error occurs when the module being inserted is not
> compiled with the kernel currently running. But in my case, that's not
> true.
>
> dmesg only yeilds following pertinent line:
>
> [29471.324717] ath9k: Unable to create debugfs root: -2
>
> Which indicates a failure to create the root directory under
> /sys/kernel/debug/ath9k/...
>
> Any ideas on why this is happening would be highly appreciated!
Maybe /sys/kernel/debug/ath9k is already present. You may want to
reboot to "fix" it.
But I don't think you would get any message from the ath9k module if it
fails to load due to unresolved symbols.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-04-12 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 5:29 On ath9k debugfs, having trouble recompiling and inserting only ath9k Rakesh Kumar
2010-04-12 21:49 ` Pavel Roskin [this message]
2010-04-16 1:46 ` [ath9k-devel] " Rakesh Kumar
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=1271108966.15194.4.camel@mj \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=gopchandani@gmail.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).