From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 13 Feb 2001 14:04:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 13 Feb 2001 14:03:57 -0500 Received: from server1.cosmoslink.net ([208.179.167.101]:6761 "EHLO server1.cosmoslink.net") by vger.kernel.org with ESMTP id ; Tue, 13 Feb 2001 14:03:47 -0500 Message-ID: <005e01c095f0$6c1b6c00$bba6b3d0@Toshiba> From: "Jaswinder Singh" To: "Mike Galbraith" , Cc: "Jaswinder Singh" In-Reply-To: Subject: Re: Problem with Ramdisk in linux-2.4.1 Date: Tue, 13 Feb 2001 11:08:57 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Dear Mike and others , 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" To: "Jaswinder Singh" 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 >