kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: andrzej-kardas@o2.pl (Andrzej Kardas)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Fwd: help with unknown symbols when trying to load kernel module
Date: Sun, 06 Mar 2011 19:55:09 +0100	[thread overview]
Message-ID: <4D73D88D.8040006@o2.pl> (raw)
In-Reply-To: <AANLkTi=8WCGMH8xmj+_=gTZny+c7ZAqvm1cgr2moFTka@mail.gmail.com>

On 06.03.2011 18:38, julie Sullivan wrote:
> I found this query on linux-kernel. Can anyone help George?
>
> ---------- Forwarded message ----------
> From: George Nychis<gnychis@cmu.edu>
> Date: Sun, Feb 27, 2011 at 5:26 PM
> Subject: help with unknown symbols when trying to load kernel module
> To: linux-kernel at vger.kernel.org
>
>
> Hi all,
>
> Long story short, I am trying to rebuild a kernel module for my
> android phone.  Unfortunately, Motorola did not post the kernel
> configuration they used
> (https://opensource.motorola.com/sf/sfmain/do/viewProject/projects.droid
> - I am running 2.2.1).  They also did not configure the kernel to dump
> it at /proc/config.gz. I have the exact source code used to build both
> the kernel, and the wireless kernel module used.  But again, I do not
> have the exact kernel configuration.  Therefore, I do not want to
> replace the kernel on the phone (in fear of misconfiguration causing
> boot errors), I simply want to rebuild the wireless module and get it
> to work with the kernel already on the phone.
>
> I've tried getting help from the android community, however their
> kernel mailing list only gets about 3 messages a day and posts are
> moderated and lag behind something like 4 days.  So, I'm hoping for a
> little bit of help here on the linux end of things from the linux
> community.
>
> I've ballparked the configuration using an older configuration file
> posted on another forum, and was able to successfully build my own
> kernel (albeit I do not use it), and then also build the wireless
> module successfully.
How did you built kernel, means by make all, or just make module_prepare 
& make madules ?
Please check if after build kernel (make all) there is a file 
Module.symvers in /your_path_to_src_kernel/

> When I try to load the module on the phone, I get a pretty long list
> of undefined symbols:
> http://pastebin.com/re5mRj4E
There is many *disagrees about version* of symbol which looks like 
sources you uesed to build module wasn't for this particular kernel.


Could you type and paste output of:

modinfo tiwlan_drv

and

modinfo some_other_module_working_on_your_phone

--
regards
Andrzej Kardas
http://www.linux.mynotes.pl



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110306/4847e9e8/attachment.html 

      reply	other threads:[~2011-03-06 18:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTim8tnk=0_uHxx1=EKrmuhsO7iMGBb_jiJeyjCgy@mail.gmail.com>
2011-03-06 17:38 ` Fwd: help with unknown symbols when trying to load kernel module julie Sullivan
2011-03-06 18:55   ` Andrzej Kardas [this message]

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=4D73D88D.8040006@o2.pl \
    --to=andrzej-kardas@o2.pl \
    --cc=kernelnewbies@lists.kernelnewbies.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).