From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8A6441381F3 for ; Sat, 22 Dec 2012 10:41:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5040121C026; Sat, 22 Dec 2012 10:41:20 +0000 (UTC) Received: from d-out-001.smtp25.com (d-out-001.smtp25.com [67.228.158.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7AE0C21C00A for ; Sat, 22 Dec 2012 10:40:08 +0000 (UTC) Received: from ccs.covici.com (pool-71-171-111-72.clppva.fios.verizon.net [71.171.111.72]) by d-out-001.smtp25.com (8.14.2/8.14.2) with ESMTP id qBMAe6rf001409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 22 Dec 2012 05:40:06 -0500 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.5/8.14.5) with ESMTP id qBMAe5tE002120 for ; Sat, 22 Dec 2012 05:40:05 -0500 To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] problem with lilo and one of my kernels X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.4.2 Date: Sat, 22 Dec 2012 05:40:05 -0500 Message-ID: <2119.1356172805@ccs.covici.com> From: covici@ccs.covici.com X-SpamH-OriginatingIP: 71.171.111.72 X-SpamH-Filter: d-out-001.smtp25.com-qBMAe6rf001409 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Archives-Salt: fee3b648-95ad-4798-875f-8c297dba5928 X-Archives-Hash: b47ff7e4a00c81734ace38ec2c124e2f Hi. Today on one of my test kernels where I am using git bisect to find a bug, I got the following when running lilo: Boot image: /boot/vmlinuz-3.6.0-rc4-00011-g2273929-dirty Fatal: Setup length exceeds 63 maximum; kernel setup will overwrite boot loader I looked and there is a bug on gentoo, but it says the problem is fixed, but I have sys-boot/lilo-23.2-r2 andthe problem persists. Is my setup really too large and if so, how do I make it smaller, or is there an alternative to boot my kernels which does not have this problem? Thanks in advance for any ideas you might have. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com