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.
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jan 23 2002 - 21:00:15 EST