From: "Josh Higham" <jhigham@bigsky.net>
To: <linux-kernel@vger.kernel.org>
Subject: 2.2.18 - failed to exec /sbin/modprobe -s -k binfmt-464c
Date: Wed, 31 Jan 2001 14:17:56 -0700 [thread overview]
Message-ID: <01d801c08bcb$49981720$3ceefcce@adhara.bigsky.net> (raw)
I tried compiling a 2.2.18 kernel, and when I reboot I get
failed to exec /sbin/modprobe -s -k binfmt-464c
scrolling past the screen.
A web search reveals a comment about 2.3.99pre3, which indicates that it is
a problem with the USB config (video4linux must be compiled in the kernel?).
I am not using USB, and it is not compiled, so I am either misunderstanding
the problem, or there is something else at work here. I tried compiling
with USB as a module and video as a module (but no specific options, since
it was just a rough experiment) and that gave the same error. Compiling
without modules altogether wouldn't boot at all (stops after the
'uncompressing kernel now loading' bit).
Am I misunderstanding the problem (there were a few issues reported in the
archived message that I looked at, so it may be that the answer regarding
USB is the answer to a different question), or is there a simple (heh)
config change that I can make to get this to compile?
I would appreciate it if you could CC me in, as I am not a member of this
list.
Thanks,
Josh Higham
-
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 reply other threads:[~2001-01-31 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 21:17 Josh Higham [this message]
2001-02-01 0:44 ` 2.2.18 - failed to exec /sbin/modprobe -s -k binfmt-464c Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 23:18 Mikael Pettersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01d801c08bcb$49981720$3ceefcce@adhara.bigsky.net' \
--to=jhigham@bigsky.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox