From owner-freebsd-current@FreeBSD.ORG Thu Apr 6 03:14:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 1CC7D16A401 for ; Thu, 6 Apr 2006 03:14:10 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04DCE43D45 for ; Thu, 6 Apr 2006 03:14:08 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FRL2P-0007U7-VC; Thu, 06 Apr 2006 12:20:02 +0900 Message-ID: <44348790.6040006@micom.mng.net> Date: Thu, 06 Apr 2006 12:14:24 +0900 From: Ganbold User-Agent: Thunderbird 1.5 (X11/20060202) MIME-Version: 1.0 To: Peter Jeremy References: <20060404090837.GC683@turion.vk2pj.dyndns.org> <44323B37.4040605@micom.mng.net> <20060404101223.GH683@turion.vk2pj.dyndns.org> <44336331.40909@micom.mng.net> <20060405075841.GB699@turion.vk2pj.dyndns.org> <443381F9.3010504@micom.mng.net> <20060405090326.GD699@turion.vk2pj.dyndns.org> <44338D08.3070000@micom.mng.net> <20060405102528.GE699@turion.vk2pj.dyndns.org> <4433A4A0.5060300@micom.mng.net> <20060405185221.GI699@turion.vk2pj.dyndns.org> In-Reply-To: <20060405185221.GI699@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: CPU class not configured problem in CURRENT-solved, boot problem -SOLVED X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2006 03:14:10 -0000 Hi Peter, Peter Jeremy wrote: > On Wed, 2006-Apr-05 20:06:08 +0900, Ganbold wrote: > >> Sorry for the noise, it was my big fault, I was using I486_CPU instead >> of I686_CPU in the config and never thought this problem might happen >> because of incorrect CPU definition in the config. >> > > The Ixxx_CPU flags are used to conditionally compile CPU support code > so failing to include the correct CPU type is fatal. If you'd posted > the correct config file, we could have solved it much faster. > Yes, that was basically my fault, wasted your time on basic thing. I'm really sorry about that. > >> Only one problem still remains, it still can not boot without >> pressing "Enter" key at the boot prompt (- sign waits forever). >> I created /boot.config with -Dh, now it shows boot.config: -Dh and waits >> for user to press "Enter". >> > > I presume 6.x and -current behave the same. This prompt is from the > second-stage boot loader (boot2). If the problem goes away when you > add '-n' to your /boot.config then your bios isn't starting the 18.2Hz > timer. Otherwise, I have no idea. > Really great news, thanks a lot Peter, actually by adding -n option in /boot.config solves the boot problem. It boots now without user intervention both 6.1-PRERELEASE and CURRENT. However should this kind of situation must be documented somewhere, maybe in FAQ ? thanks again, Ganbold