From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mr2.ash.ops.us.uu.net([198.5.241.87]) (1839 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Mon, 8 Jan 2001 22:46:38 -0500 (EST) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from 1Cust225.tnt1.washington.dc.da.uu.net by mr2.ash.ops.us.uu.net with ESMTP (peer crosschecked as: 1Cust225.tnt1.washington.dc.da.uu.net [63.10.40.225]) id QQjxed17132; Tue, 9 Jan 2001 03:46:41 GMT Date: Mon, 8 Jan 2001 22:43:22 -0500 (EST) From: Janina Sajka X-Sender: janina@toccata.grg.afb.net To: speakup@braille.uwo.ca cc: "LUG, DC -- DC LUG" , ma-linux@gwyn.tux.org Subject: Re: Lilo geo_comp_addr Error with 2.4.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: The kernel is a bzImage of 651,696 bytes. Is that too large? Seems to me that this should just make it. The exact error lilo is reporting is: geo_comp_addr: Cylinder number is too big (1530 > 1023) Sure sounds like the old "keep it below 1024" There was one other problem, now that I look back at the logs. 'make modules_install' complained about depmod -f. I ran depmod -a 2.4.0 by hand, but is this perhaps not the same thing? Might this be a modules issue? On 8 Jan 2001, Kirk Reiser wrote: > Hi Again Janina: Check the size of the kernel you built. Did you > compile it as a zImage or a bzImage? Looks more like lilo is > complaning about the size of the kernel rather than the size of the > drive. > > Kirk > > -- > > Kirk Reiser The Computer Braille Facility > e-mail: kirk@braille.uwo.ca University of Western Ontario > phone: (519) 661-3061 > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >