From owner-freebsd-current@FreeBSD.ORG Wed May 18 16:23:51 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 3F9E816A4CE for ; Wed, 18 May 2005 16:23:51 +0000 (GMT) Received: from infor.ck.tp.edu.tw (infor.ck.tp.edu.tw [203.64.26.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id E695343DC2 for ; Wed, 18 May 2005 16:23:50 +0000 (GMT) (envelope-from llwang@infor.ck.tp.edu.tw) Received: by infor.ck.tp.edu.tw (Postfix, from userid 1001) id 5EF0845E7B; Thu, 19 May 2005 00:23:44 +0800 (CST) Date: Thu, 19 May 2005 00:23:44 +0800 From: "Li-Lun Wang (Leland Wang)" To: freebsd-current@freebsd.org Message-ID: <20050518162344.GA48280@Athena.infor.org> References: <20050518051111.GA33262@Athena.infor.org> <428ADE11.8040109@alumni.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <428ADE11.8040109@alumni.rice.edu> User-Agent: Mutt/1.5.6i 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: Wed, 18 May 2005 16:23:51 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, May 18, 2005 at 01:17:53AM -0500, Jonathan Noack wrote: > On 05/18/05 00:11, Li-Lun Wang (Leland Wang) wrote: > >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? > > If you are building/installing just the loader, do a full build/install > world without setting CPUTYPE. From my experience it seems like it is > gcc that is being affected (when it is compiled with CPUTYPE set) and > producing incorrect code for the loader, so a build/install world is > necessary. This may not help, but it narrows the problem. I rebuilt the world without setting CPUTYPE, and the loader works. I wonder if setting CPUTYPE=p3 when building the world will also work. It is strange how gcc could be affected... - -- Li-Lun Wang -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCi2wPCQM7t5B2mhARApZZAJ4lyyN8gFpElx0ryR0ln4xlqMq69gCfX7T4 GMHfTZYdaKgBDCHsnmqchYU= =qHgx -----END PGP SIGNATURE-----