Messages in this thread | | | Date | Wed, 27 Jan 1999 16:51:03 -0700 | From | Richard Fish <> | Subject | Re: Quite off topic, but I'm running out of options... |
| |
storner@image.dk wrote: > > In <36AF7260.D959827F@njmc.com> John LeMay <jlemay@njmc.com> writes: > > >After installing 2.2.0 (final), I receive the following messege upon > >reboot: > > >Kmod: failed to exec /sbin/modprobe -s -k binfmt-464c, errno=8 > >request_module[binfmt-464c]: fork failed, errorno=11 > > errno=8 means "exec format error". binfmt-464c is ELF format ("EL" = > 0x46 0x4C). > > Sounds like you built your kernel without ELF support, and your > modprobe is an ELF binary.
This is getting to be a very common posting/answer sequence here.
Does anybody else think it would be a good idea to have a warning message for menuconfig or xconfig that appears when ext2fs or elf binary support are modularized that says something like:
WARNING: Most systems will not boot if ELF binary/EXT2 filesystem support is not in the kernel.
These two in particular seem to be the most common user goofs that show up like kernel problems.
-- Richard Fish Enhanced Software Technologies, Inc. Software Developer 4014 E Broadway Rd Suite 405 rjf@estinc.com Phoenix, AZ 85040 (602) 470-1115 http://www.estinc.com
- 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/
| |