Very Computer

I just upgraded to 5.0, and I have run into a small snag.

The local console/Keyboard appears to be disabled.

Here is the scenario.

1.  I reboot the computer
    Normal hardward BIOS booting stuff takes place (I can hit DEL and get to
BIOS configuration)
 2.  The message about (I don't have the exact text here) System will boot
in 10, 9, 8,7,etc... press Enter to Boot now, or press any key to enter
command mode.

3.  Waiting or, pressing Enter causes the the little spinner to start
spinning, and then immeadiatly stop.

4.  Nothing else is displayed on the screen, untill the login prompt is
displayed.  and I cannot key anything in at this prompt (the keyboard
appears to be locked.)

What am I missing here?

On Sun, 27 May 2001 07:53:44 -0500, "Patrick Sonnek"

I have seen something similar (on 4.x) when I had attached a serial
console to the box. Is that the case?
--
__________________________________________________
"Nothing is as subjective as reality"

http://www.xs4all.nl/~reinoud
__________________________________________________

Quote:> I just upgraded to 5.0, and I have run into a small snag.

There isn't a FreeBSD 5.0.  It is FreeBSD 5.0-CURRENT.  This
is the bleeding edge of development; and the moment FreeBSD
5.0-CURRENT is extremely unstable.

Quote:

> What am I missing here?

Subscribe to the freebsd-current mailing list.

--
steve

I had that problem on older FreeBSD because I had an OLD keyboard
that was not picked up during boot and the system defaulted to the
serial port as control.

As soon as the boot sequence starts hit a key to if you get to a
prompt where you can get to single user mode.  This is right after
the first spinner starts.   I don't recall if that does it or not.

--

Quote:> I just upgraded to 5.0, and I have run into a small snag.

> The local console/Keyboard appears to be disabled.

> Here is the scenario.
        ... etc ...
> 4.  Nothing else is displayed on the screen, untill the login prompt is
> displayed.  and I cannot key anything in at this prompt (the keyboard
> appears to be locked.)

Is your /boot/device.hints file valid?  I got bitten by this one when
I upgraded to 5.0-CURRENT, mistakenly thinking an empty file was okay.

Chris.
--
//USENET01 JOB (CBH,ISA),'TALKING BOLLOCKS',REGION=4000K,CLASS=F,
//             MSGCLASS=A,PASSWORD=WIBBLE,USER=CBH,COND=(04,LT)