Re: CPU class not configured problem in CURRENT-solved, boot problem remains

[ Available lists | Index of freebsd-current | Month of Apr 2006 | Week of 5 Apr 2006 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Peter Jeremy <peterjeremy@optushome.com.au>
Date
5 Apr 2006 18:52:30
Subject
Re: CPU class not configured problem in CURRENT-solved, boot problem remains
Message-ID
20060405185221.GI699@turion.vk2pj.dyndns.org

In reply to
Replies
Referenced by

[ Hide this part ]
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


Elapsed time: 0.161 seconds