Re: Kmod problem?

Mikael Pettersson (mikpe@csd.uu.se)
Sat, 29 May 1999 12:46:18 +0200 (MET DST)


On May 24, Alex C wrote:

> My machine runs 2.0.36 quite happily and my older 166 runs 2.2.3 ok too,
> but my main box (see deatils below) hates any 2.2 kernel (have tried up to
> 2.2.7 under Debian 2.1, Redhat 5.2 and Redhat 6.0)
>
> while attemting to boot with a 2.2 kernel, which compiled without error,
> it gets just further than the IDE Hard disk inormation and displays this:
>
> kmod: failed to exec /sbin/modprobe -s -k binfmt-464c, errno=8
> request_module[binfmt-464c]: fork failed, errno 11
>
> and loops this message indefinatley.
> This happens even when using no modules or support for them compiled in.

errno 8 is ENOEXEC, Exec format error.
I don't know what executable file format binfmt-464c denotes, what
does "file /sbin/modprobe" say on the troubled machine?

To avoid infinite regress, it is imperative that the exec format used by
/sbin/modprobe be built _into_ the kernel, i.e. not itself be a module.

/ Mikael

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