It appears that your module was built with the module version feature enabled
but perhaps your running kernel is not enabled for this. Do you have the
ksyms utility available on the ARM target machine? If so try this command:

        ksyms -a | grep printk

If you see something similar to this (taken from 2.4.0 on an x86):

        c0117b00 printk_Rsmp_1b7d4074

then the module version feature is enabled. On the other hand if you see a
printk symbol without the funny suffix then the feature is not enabled. To
fix, make sure to build your modules against a linux source tree that matches
the running kernel. This source tree should contain the results of a "make
xconfig" with the same options that were selected for the running kernel, in
particular the options in the "Loadable module support" dialog.

Another possibility is that both kernel and module were built with the module
version option, but the symbol suffixes do not match. If the printk suffix
shown by ksyms doesn't match the suffix shown by the unresolved external
error, you've got a symbol version mismatch. I'd be surprised if this was the
case because the interface to printk hasn't changed in a long time.

Hope this helps,
Terry Griffin

On Monday 22 January 2001 19:22, you wrote:
> Date: Tue, 23 Jan 2001 11:24:13 +0800
> MIME-Version: 1.0
> X-Mailer: Internet Mail Service (5.5.2650.21)
> Content-Type: text/plain
>
> Hi all,
>
> Currently, I am looking into the possibility of porting ng-0.1.7 code to a
> StrongARM
> platform called Assabet. It has PCMCIA support and the porting of Linux
> onto it is
> pretty successful (www.arm.linux.org.uk). I had successfully got the
> kernel 2.4 and
> KERNEL pcmcia support working on that board. Do you have any idea of how
> to port
> this ng-0.1.7 code over there? I have a cross-compiler working now and had
> tried
> once, but failed. All I did is compile the code with the cross-compiler and
> copy
> over. When I tried to manually load p80211.o module on this assabet board,
> it gives
> me errors of a lot of unresolved links, including printk_xxxxxxx. I don't
> know where
> goes wrong, I believe, no matter how simple the kernel is, is should have
> this printk
> symbol exported right?
>
> I am totally lost, any suggestion or wild guess will be apprecidated.
>
> Regards,
> Leonard Ye
> --------------------------------------------------
> Linux WLAN Developer's List
> For more information about this list see:
> http://www.absoval.com/linux-wlan/lists.html
--------------------------------------------------
Linux WLAN Developer's List
For more information about this list see:
http://www.absoval.com/linux-wlan/lists.html

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]