mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ronald Bultje <rbultje@ronald.bitfreak.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.21 doesn't boot: /bin/insmod.old: file not found
Date: 22 Jun 2003 19:07:58 +0200	[thread overview]
Message-ID: <1056301678.2183.10.camel@shrek.bitfreak.net> (raw)

Hey,

I'm trying to get 2.4.21 to run (2.4.20 runs nicely), and I get the
above error ("/bin/insmod.old: file not found"), after which it stops
booting.

After that, I installed the newest modutils (2.4.25) and
module-init-tools (tried both 0.9.12 and 0.9.13-pre), created symlinks
in /bin for all *mod* tools pointing to /sbin/$file, and I still cannot
get 2.4.21 to get further than this error (obviously, /bin/insmod.old
_is there_, I'm not that stupid. ;) ). I use initrd with filesystem
modules and some more in it, so obviously it fails with a panic saying
that /sbin/init wasn't found (no single HD mounted).

Of course, I could place ext3 in-kernel, but that's not the point.
2.4.21 doesn't boot for me as is - 2.4.20 does. I can't continue 2.5.x
testing if I remove the module-init-tools and only use modutils (I'm
doing that on another system, and that one works well with 2.4.21).

Does this sound familiar to anyone? Does someone know a solution that
will allow me to keep on using initrd images in 2.4.x, while also being
able to test 2.5.x?

System: RH73 (mostly), gcc-2.96.

Thanks,

Ronald

-- 
Ronald Bultje <rbultje@ronald.bitfreak.net>


             reply	other threads:[~2003-06-22 16:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 17:07 Ronald Bultje [this message]
2003-06-23  9:26 ` Keith Owens
2003-06-23 18:40   ` Ronald Bultje
2003-06-23 23:01     ` John Shillinglaw
2003-06-24  0:37     ` Keith Owens
2003-06-24  2:24       ` John Shillinglaw
2003-06-24  6:35       ` Ronald Bultje
2003-06-24 16:13         ` Stephen Hemminger
2003-06-24 21:16         ` Horst von Brand

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=1056301678.2183.10.camel@shrek.bitfreak.net \
    --to=rbultje@ronald.bitfreak.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

all inboxes | Powered by JetHome®