From owner-freebsd-current@FreeBSD.ORG Thu May 19 03:36:23 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F08516A4CE for ; Thu, 19 May 2005 03:36:23 +0000 (GMT) Received: from lakermmtao09.cox.net (lakermmtao09.cox.net [68.230.240.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CC7D43DB9 for ; Thu, 19 May 2005 03:36:22 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.70.216]) by lakermmtao09.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050519033620.UBDC6804.lakermmtao09.cox.net@dolphin.local.net>; Wed, 18 May 2005 23:36:20 -0400 Received: from dolphin.local.net (localhost.local.net [IPv6:::1]) by dolphin.local.net (8.13.3/8.13.3) with ESMTP id j4J3aLKB009007; Wed, 18 May 2005 22:36:21 -0500 (CDT) (envelope-from conrads@cox.net) Date: Wed, 18 May 2005 22:36:16 -0500 From: "Conrad J. Sabatier" To: "Li-Lun Wang (Leland Wang)" Message-ID: <20050518223616.3f515599@dolphin.local.net> In-Reply-To: <20050518051111.GA33262@Athena.infor.org> References: <20050518051111.GA33262@Athena.infor.org> X-Mailer: Sylpheed-Claws 1.0.4a (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Newest loader from CVS not working X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2005 03:36:23 -0000 On Wed, 18 May 2005 13:11:11 +0800, "Li-Lun Wang (Leland Wang)" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I just upgraded my pentium-m laptop from 5.4-STABLE to the newest > 6.0-CURRENT. However, the newest loader does not seem to work for > me. BTX reboots right after it detects the internal keyboard/console > and dumps the registers. I have tried to set CPUTYPE?=p-m, CPUTYPE=p3, > and even not setting CPUTYPE at all, but none of them solves my > problem. The old loader from 5.4 works perfectly. Any ideas? Yes, my new loader (built as part of a buildworld/buildkernel Tuesday morning) complains about something or the other not being a multiple of blocksize. It then panics and only offers me the option to reboot (effectively rendering the machine unbootable). Luckily, I was able to boot from a 5.2 CD-ROM (the latest I had lying around here), went into "fixit" mode, renamed loader to loader.new and loader.old to loader, and the system came back up normally on the next boot. Anyone have any idea what's going on with this? -- Conrad J. Sabatier -- "In Unix veritas"