On Tue, 2005-01-04 at 20:09 -0500, PHANI ARAVA wrote:
> Hi,
>
> Iam having a big and strange problem
>
> I have Installed Debian Sarge on to the systems of our research lab
> I have to implement a patch onto 2.4.22 kernel (vannila) I patched it and compiled the kernel the deb way (Forgot to tell u that i have copied the config file that came with Sarge). I installed the kernel and reboot the system ..
>
> I get this following error
>
> RAMDISK: cramfs filesystem found at block 0
> RAMDISK: loading 3276 blocks [1 disk] into ram disk... done.
> Freeing initrd memory: 3276k freed
> cramfs: wrong magic
> Kernel panic: VFS: Unable to miunt root fs on 22:02
>
>
> Can somebody tell me where exactly iam going wrong
> And well iam using lilo for another wierd reason..
==================================
Warning: You are using the initrd option, that may not
work unless you have applied the initrd cramfs patch to
the kernel, or modified mkinitrd not to use cramfs by
default. The cramfs initrd patch, is included in the
Debian supplied kernel sources, but is not present in
pristine kernel sources. By default, I assume you know
what you are doing, and I apologize for being so annoying.
Should I abort[Ny]?
==================================
Have you applied this patch? I'm not sure when it was merged upstream
but it looks like you don't have support for cramfs initrd.
/* Do sanity checks on the superblock */
if (super.magic != CRAMFS_MAGIC) {
/* check at 512 byte offset */
memcpy(&super, cramfs_read(sb, 512, sizeof(super)), sizeof(super));
if (super.magic != CRAMFS_MAGIC) {
printk(KERN_ERR "cramfs: wrong magic\n");
goto out;
}
}
I believe the patch adds magic to the in-memory version of the cramfs
superblock for initrd support.
Check the Debian 2.4.22 sources for relevant patches (or you could use
something other than cramfs in mkinitrd).
--
Eric Gaumer <gaumerel@ecs.fullerton.edu>
Attachment:
signature.asc
Description: This is a digitally signed message part