make error when "Enable Loadable Module Support"

I'm using the Cyclone Development Board

With my custom *.ptf and *.sof I can get the Compact Flash up and working (ext3 format).

When I try and enable loadable module support I get the following.

CC net/sunrpc/stats.o

LD net/ipv4/built-in.o

LD net/sunrpc/sunrpc.o

LD net/sunrpc/built-in.o

LD net/built-in.o

LD vmlinux.o

MODPOST vmlinux.o

WARNING: modpost: Found 2 section mismatch(es).

To see full details build your kernel with:

'make CONFIG_DEBUG_SECTION_MISMATCH=y'

GEN .version

CHK include/linux/compile.h

UPD include/linux/compile.h

CC init/version.o

LD init/built-in.o

LD vmlinux

__pata_platform_remove: discarded in section `.devexit.text' from drivers/built-in.o

make[2]: *** [vmlinux] Error 1

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/home/janet/nios2-linux/linux-2.6'

make: *** [linux] Error 1

[janet@localhost uClinux-dist]$

When I do the "make CONFIG_DEBUG_SECTION_MISMATCH=y" I get:

CC fs/mbcache.o

LD fs/built-in.o

LD vmlinux.o

MODPOST vmlinux.o

WARNING: vmlinux.o(.text+0xe0): Section mismatch in reference from the variable data_flush to the function .init.text:start_kernel()

The function data_flush() references

the function __init start_kernel().

This is often because data_flush lacks a __init

annotation or the annotation of start_kernel is wrong.

WARNING: vmlinux.o(.text+0xe4): Section mismatch in reference from the variable data_flush to the function .init.text:start_kernel()

The function data_flush() references

the function __init start_kernel().

This is often because data_flush lacks a __init

annotation or the annotation of start_kernel is wrong.

GEN .version

CHK include/linux/compile.h

UPD include/linux/compile.h

CC init/version.o

LD init/built-in.o

LD vmlinux

__pata_platform_remove: discarded in section `.devexit.text' from drivers/built-in.o

make[2]: *** [vmlinux] Error 1

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/home/janet/nios2-linux/linux-2.6'

make: *** [linux] Error 1

But I have NO CLUE what this is telling me.

Any advice would be appreciated.

I'm using this board before I get our custom board and having loadable module support is pretty darn important when you are developing a device driver.