From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Miguel_Gonz=E1lez_Casta=F1os?= Subject: Re: compile kernel 2.6 Date: Wed, 18 Jan 2006 16:04:58 +0100 Message-ID: <43CE591A.8070202@tid.es> References: <43CA4740.5080803@yahoo.es> <43CE3668.7050402@tid.es> <6.2.3.4.0.20060118134231.02061190@127.0.0.1> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-reply-to: <6.2.3.4.0.20060118134231.02061190@127.0.0.1> Sender: linux-admin-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: linux-admin@vger.kernel.org Carl escribi=F3: > At 12:36 18/01/2006, Miguel Gonz=E1lez Casta=F1os wrote: > >> I have reviewed my configurations and I do not see why I getting=20 >> this error: >> >> - I have deactivated modules support, so EXT3 support is within the=20 >> kernel, not loaded as a module > > > I always thought you REQUIRED ext3 support in the initrd image so the= =20 > ext3 filesystem > that holds the kernel can be mounted. I have read that filesystem modules should be compiled within the kernel, not as modules, otherwise the system doesn=B4t boot. Initrd use= s the information in the /lib/modules/ directory to build the img file, s= o I am not sure whether I have to use initrd, anyway I have tried to use mkinitrd with a monolithic kernel and obviously didn=B4t work. Are you sure of that point? Best Regards, Miguel - To unsubscribe from this list: send the line "unsubscribe linux-admin" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html