From: Silviu Marin-Caea <silviu@delrom.ro>
To: linux-kernel@vger.kernel.org
Subject: Re: Ramdisk doesn't work well in 2.4.17
Date: Wed, 16 Jan 2002 14:02:08 +0200 [thread overview]
Message-ID: <20020116140208.0636e00d.silviu@delrom.ro> (raw)
In-Reply-To: <20020115162647.35f57d4f.silviu@delrom.ro>
In-Reply-To: <20020115162647.35f57d4f.silviu@delrom.ro>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
On Tue, 15 Jan 2002 16:26:47 +0200
Silviu Marin-Caea <silviu@delrom.ro> wrote:
Thanks to all who answered.
To Andrew Morton: unfortunately, the patch doesn't fix it for me.
http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.18pre2aa2/00_ramdisk-buffercache-2
This is what I do:
compile a kernel with the attached .config
Notes about configuration:
* Loopback device support
* Network block device support
* RAM disk support with a default size of 40960 (that's not an error)
disk size* Initial RAM disk initrd support
* No Kernel module loader
Tried kernel versions: 2.4.17, 2.4.18pre1 with the above patch,
2.4.18pre3 and pre4
Then:
rdev bzImage /dev/fd0 && rdev -r bzImage 49152 && rdev -R bzImage 0
dd if=bzImage of=/dev/fd0
Using this rootdisk:
http://prdownloads.sourceforge.net/partimage/partimage-0.6.1-i386-rootdisk-1.raw
I also tried with a modified version that uses a regular init, not
busybox.
This happens:
RAMDISK: Compressed image found at block 0
...
VFS: Mounted root (minix filesystem).
Freeing unused kernel memory: 204k freed
Kernel panic: no init found. Try passing init= option to kernel.
> The root disk is good, because I have built a 2.4.9 in a similar
> fashion, and it works with it. The problem is I need NTFS support,
> and that doesn't compile in 2.4.9.
--
Silviu Marin-Caea - Network & Systems Administrator - Delta Romania
Phone +4093-267961
[-- Attachment #2: kernelconfig.gz --]
[-- Type: application/x-gzip, Size: 3600 bytes --]
prev parent reply other threads:[~2002-01-16 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 14:26 Silviu Marin-Caea
2002-01-16 12:02 ` Silviu Marin-Caea [this message]
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=20020116140208.0636e00d.silviu@delrom.ro \
--to=silviu@delrom.ro \
--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®