Re: "Invalid module format"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Mar 5, 2010 at 7:37 PM, Mauro Carvalho Chehab
<mchehab@xxxxxxxxxx> wrote:
> I suspect that it may be related to this:
>
> # Select 32 or 64 bit
> config 64BIT
>        bool "64-bit kernel" if ARCH = "x86"
>        default ARCH = "x86_64"
>        ---help---
>          Say yes to build a 64-bit kernel - formerly known as x86_64
>          Say no to build a 32-bit kernel - formerly known as i386
>
> With 2.6.33, it is now possible to compile a 32 bits kernel on a 64 bits
> machine without needing to pass make ARCH=i386 or to use cross-compilation.
>
> Maybe you're running a 32bits kernel, and you've compiled the out-of-tree
> modules with 64bits or vice-versa.
>
> My suggestion is that you should try to force the compilation wit the proper
> ARCH with something like:
>        make distclean
>        make ARCH=`uname -i`
>        make ARCH=`uname -i` install

I had forgot to reply to this but while I do have a 64bit capable cpu,
I compile & use only 32bit.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux