Date: Thu, 6 Apr 2006 04:52:22 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Ganbold <ganbold@micom.mng.net> Cc: freebsd-current@freebsd.org Subject: Re: CPU class not configured problem in CURRENT-solved, boot problem remains Message-ID: <20060405185221.GI699@turion.vk2pj.dyndns.org> In-Reply-To: <4433A4A0.5060300@micom.mng.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >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. -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060405185221.GI699>