From: Wolfgang Denk <wd@denx.de>
To: Cindy Peters <cinpet@adaptivemicro.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Upgrading to kernel 2.4.6 with old init program
Date: Sun, 23 Sep 2001 20:00:32 +0200 [thread overview]
Message-ID: <20010923180037.DE0A61009E@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 21 Sep 2001 15:29:29 CDT." <41EDEC3C1B88D51186EB00A0C9CFADF702FA81@AMWMAIL>
In message <41EDEC3C1B88D51186EB00A0C9CFADF702FA81@AMWMAIL> you wrote:
>
> I am upgrading my Linux kernel from 2.2.13 to 2.4.6 on an MPC823. When the
> kernel startup process gets to running the sbin/init program I am getting a
> usage error for ld.so and then a kernel panic. It looks like it is
> attempting to run ld.so. I am still using an old ramdisk with old versions
> of executables that ran successfully on Linux 2.2.13. Have the file formats
> changed somehow? Do I need to get the source for the executables and rebuild
> them with the latest libraries? If so, where can I get them?
This souns as if you are still running code based on libc-1.99. You
need a modified version of /lib/ld.so.1 then. There is one on our FTP
server, AFAIR in ftp://ftp.denx.de/pub/LinuxPPC/usr/src/ld.so* (or
maybe in the "patches" directory?).
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Nothing ever becomes real until it is experienced. - John Keats
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-23 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 20:29 Upgrading to kernel 2.4.6 with old init program Cindy Peters
2001-09-23 18:00 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-24 14:33 Cindy Peters
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=20010923180037.DE0A61009E@denx.denx.de \
--to=wd@denx.de \
--cc=cinpet@adaptivemicro.com \
--cc=linuxppc-embedded@lists.linuxppc.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