Re: 2.2.18 - failed to exec /sbin/modprobe -s -k binfmt-464c

From: Keith Owens (kaos@ocs.com.au)
Date: Wed Jan 31 2001 - 19:44:41 EST

Next message: Mathieu Chouquet-Stringer: "Re: modules as drivers and the order of loading"
Previous message: List User: "Any reason why we can't auto-start LVM (vg's) in the kernel?"
In reply to: Josh Higham: "2.2.18 - failed to exec /sbin/modprobe -s -k binfmt-464c"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, 31 Jan 2001 14:17:56 -0700,
"Josh Higham" <jhigham@bigsky.net> wrote:
>failed to exec /sbin/modprobe -s -k binfmt-464c

You compiled your kernel with support for ELF objects as a module. You
execute an ELF program, the kernel tries to autoload the ELF module
using modprobe which is an ELF program. But you need ELF support to
run modprobe, curse and recurse.

Compile the kernel with builtin ELF, not a module.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Mathieu Chouquet-Stringer: "Re: modules as drivers and the order of loading"
Previous message: List User: "Any reason why we can't auto-start LVM (vg's) in the kernel?"
In reply to: Josh Higham: "2.2.18 - failed to exec /sbin/modprobe -s -k binfmt-464c"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Jan 31 2001 - 21:00:41 EST