help with unknown symbols when trying to load kernel module

From: George Nychis
Date: Sun Feb 27 2011 - 12:27:06 EST

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
- 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

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.

When I try to load the module on the phone, I get a pretty long list
of undefined symbols:

I decided to start by focusing on one of these errors,
'register_netdev' and used 'nm' on my kernel module and found that it
is undefined:
00073b60 T regReadLastDbgState
U register_netdev
000345ec T regulatoryDomain_SetDefaults

Here is the entire nm output:

I'm a little confused as to what this means. Does this mean that the
stock kernel on the phone does not have this symbol? It seems odd
since I believe the wireless module requires it. Or does it mean
something else?

Thanks for any help. I'm also not registered on the mailing list, so
if you could CC me on any responses I would sincerely appreciate it.

- George
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at