From: Anton Altaparmakov <aia21@cam.ac.uk>
To: "Sergey Kubushin" <ksi@cyberbills.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.0ac11
Date: Thu, 25 Jan 2001 02:04:06 +0000 [thread overview]
Message-ID: <5.0.2.1.2.20010125015343.00a8fe10@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.31ksi3.0101241721470.605-100000@nomad.cyberbill s.com>
In-Reply-To: <E14LOAm-0006z0-00@the-village.bc.nu>
As I don't use initrd at all I am a bit out of my depth here but according
to Documentation/Changes you need a new mkinitrd and the version suggested
seems to be 2.8-1. Checking my up-to-date RedHat 7.0 workstation it has
mkinitrd version 2.6-1, so this might be your problem?
Best regards,
Anton
At 01:39 25/01/2001, Sergey Kubushin wrote:
>On Wed, 24 Jan 2001, Alan Cox wrote:
>
>Modules don't load. I do usually compile heavily modular kernels, with ide
>and ext2fs being also modular. When trying to load them from initrd, I have
>the following output:
>
>=== Cut ===
>ide-mod.o: Can't handle sections of type 32131
>ide-probe-mod.o: Can't handle sections of type 256950710
>ext2.o: Can't handle sections of type 688840897
>=== Cut ===
>
>I suspect that all modules are affected, but can't check it because kernel
>is unable to mount root filesystem.
>
>All of ac9-ac11 behave the same. ac4, vanilla 2.4.0 and a whole bunch of
>pre's are fine, so it looks like something was broken between ac4 and ac9 (I
>didn't compile anything inbetween).
>
>I use gcc-2.95.2, binutils-2.10.1.0.4, modutils-2.4.2, glibc-2.2.1. The
>initrd image is romfs. I don't think something was broken in romfs, 'coz
>all the programs run just fine outta the image (static ash, static insmod).
>
>Config is available and can be sent on request. Please let me know if I can
>help to find out what causes such a bug.
[snip]
--
"Programmers never die. They do a GOSUB without RETURN." - Unknown source
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
-
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 prev parent reply other threads:[~2001-01-25 2:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.31ksi3.0101241721470.605-100000@nomad.cyberbill s.com>
2001-01-24 11:33 ` Alan Cox
2001-01-24 15:05 ` Cataldo Thomas
2001-01-24 17:03 ` NTFS safety and lack thereof - Was: " Timur Tabi
2001-01-24 17:09 ` mirabilos
2001-01-26 17:38 ` Pavel Machek
2001-01-24 17:23 ` Anton Altaparmakov
2001-01-24 16:54 ` Anton Altaparmakov
2001-01-24 20:06 ` Luc de Louw
2001-01-25 1:36 ` Alan Cox
2001-01-25 1:39 ` Sergey Kubushin
2001-01-25 5:18 ` Andre Hedrick
2001-01-25 11:02 ` Matthias Andree
2001-01-25 16:50 ` Sergey Kubushin
2001-01-25 2:04 ` Anton Altaparmakov [this message]
2001-01-25 2:13 ` Sergey Kubushin
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=5.0.2.1.2.20010125015343.00a8fe10@pop.cus.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ksi@cyberbills.com \
--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®