I am facing this problem in linux-2.4.1 :-
RAMDISK driver initialized: 16 RAM disks of 8192K size
1024 blocksize
RAMDISK: Compressed image found at block 0
incomplete distance tree
invalid compressed format (err=1)Freeing initrd
memory: 4096k freed
Is any body seen this problem earlier , any hint .
But this ramdisk works fine with linux-2.2.12 .
Thanks ,
Best Regards,
Jaswinder.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
Is there there any change in latest kernel 2.4.1 and old kernels like 2.2.12
with respect to Ramdisk or not .
I mean is there any change in rd.c and or lib/inflate.c .
Thanks for your help.
Best Regards,
Jaswinder.
--
These are my opinions not 3Di.
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/
I am using compressed ramdisk , i can not turn off cramfs .
my error messages are very strange and irreregular .
i am getting 3 different kind of error messages :-
invalid compressed format (err=1)
OR
invalid compressed format (err=2)
OR
crc error
I am using gzip 1.2.4 (18 Aug 93)
But when i use same ramdisk with old kernel like 2.2.12 , it works fine .
Please help me.
Thanks ,
Best Regards,
Jaswinder.
--
These are my opinions not 3Di.
----- Original Message -----
From: "Mike Galbraith" <mi...@wen-online.de>
To: "Jaswinder Singh" <jaswind...@3disystems.com>
Sent: Tuesday, February 13, 2001 12:22 AM
Subject: Re: Problem with Ramdisk in linux-2.4.1
> On Mon, 12 Feb 2001, Jaswinder Singh wrote:
>
> > Dear linux-kernel mailing list,
> >
> > I am facing this problem in linux-2.4.1 :-
> >
> > RAMDISK driver initialized: 16 RAM disks of 8192K size
> > 1024 blocksize
> > RAMDISK: Compressed image found at block 0
> > incomplete distance tree
> > invalid compressed format (err=1)Freeing initrd
> > memory: 4096k freed
> >
> > Is any body seen this problem earlier , any hint .
>
> Hi,
>
> I think I might have seen this problem before. If this isn't
> a cramfs initrd, turn off cramfs and I think it'll work right.
> I once had cramfs on by accident, and I found that my initrd
> wouldn't load.
>
> -Mike
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Sometimes i also get :-
incomplete literal tree
OR
incomplete distance tree
along with
invalid compressed format (err=1)
OR
invalid compressed format (err=2)
OR
crc error
And it is very strange because for the same ramdisk , linux2.4.1 shows me
all the error messages .
I am using Ramdisk of 8 MB on compression it becomes around 1.4 MB.
> Dear Mike and others ,
>
> I am using compressed ramdisk , i can not turn off cramfs .
(ok.. really is compressed)
> my error messages are very strange and irreregular .
>
> i am getting 3 different kind of error messages :-
>
> invalid compressed format (err=1)
> OR
> invalid compressed format (err=2)
> OR
> crc error
>
> I am using gzip 1.2.4 (18 Aug 93)
>
> But when i use same ramdisk with old kernel like 2.2.12 , it works fine .
Can you point me to a cramfs generation procedure? (never used
cramfs.. know where the docs are, but could use a small time warp)
----- Original Message -----
From: "Mike Galbraith" <mi...@wen-online.de>
To: "Jaswinder Singh" <jaswind...@3disystems.com>
Cc: <linux-...@vger.kernel.org>
Sent: Tuesday, February 13, 2001 11:56 AM
Subject: Re: Problem with Ramdisk in linux-2.4.1
> On Tue, 13 Feb 2001, Jaswinder Singh wrote:
>
> > Dear Mike and others ,
> >
> > I am using compressed ramdisk , i can not turn off cramfs .
>
> (ok.. really is compressed)
>
> > my error messages are very strange and irreregular .
> >
> > i am getting 3 different kind of error messages :-
> >
> > invalid compressed format (err=1)
> > OR
> > invalid compressed format (err=2)
> > OR
> > crc error
> >
> > I am using gzip 1.2.4 (18 Aug 93)
> >
> > But when i use same ramdisk with old kernel like 2.2.12 , it works fine
.
>
> Can you point me to a cramfs generation procedure? (never used
> cramfs.. know where the docs are, but could use a small time warp)
>
make ramdisk as you normally do and then compress it by gzip .
You can see documentation on Ramdisk in Documentation/ramdisk.txt if you
have some time ;)
Best Regards,
Jaswinder.
--
These are my opinions not 3Di.
> >
> > Can you point me to a cramfs generation procedure? (never used
> > cramfs.. know where the docs are, but could use a small time warp)
> >
>
> make ramdisk as you normally do and then compress it by gzip .
Ok, it's not a cramfs. If you disable cramfs, it will likely
work. There seems to be a (init order?) problem when cramfs is
enabled. For instance, if I enable cramfs here, my minix gzipped
initrd can not mount root.. kernel tries to use reiserfs instead
for some unknown reason. I disable cramfs and all is well.
Since the error message you posted seems to be from cramfs...