From owner-freebsd-questions  Tue Jun 18 20:40:41 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA29524
          for questions-outgoing; Tue, 18 Jun 1996 20:40:41 -0700 (PDT)
Received: from milpitas.adaptec.com (milpitas.adaptec.com [162.62.21.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA29499
          for <questions@freebsd.org>; Tue, 18 Jun 1996 20:40:35 -0700 (PDT)
Received: from btc.btc.adaptec.com ([162.62.63.6]) by milpitas.adaptec.com (4.1/SMI-4.1)
	id AA18382; Tue, 18 Jun 96 20:37:14 PDT
Received: from Unknown (cosmos.btc.adaptec.com [162.62.63.104]) by btc.btc.adaptec.com (8.6.9/8.6.9) with SMTP id VAA27654; Tue, 18 Jun 1996 21:40:49 -0600
Message-Id: <199606190340.VAA27654@btc.btc.adaptec.com>
Comments: Authenticated sender is <aarond@btc>
From: "Aaron Dailey" <aarond@btc.adaptec.com>
To: Terry Lambert <terry@lambert.org>, Nate Williams <nate@sri.MT.net>
Date: Tue, 18 Jun 1996 21:26:29 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: Re: PS/Valuepoint and keyboard hang on install
Cc: questions@freebsd.org
Priority: normal
X-Mailer: Pegasus Mail for Windows (v2.33)
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Date:          Tue, 18 Jun 1996 17:42:42 -0600
> From:          Nate Williams <nate@sri.MT.net>
> To:            Terry Lambert <terry@lambert.org>
> Cc:            aarond@btc.btc.adaptec.com, questions@freebsd.org
> Subject:       Re: PS/Valuepoint and keyboard hang on install

> > > > > I'm trying to install FreeBSD 2.1 Release on an IBM  PS/Valuepoint
> > > > > 6384, and get a keyboard lock once everything boots.
> 
> > > I don't see a psm0 driver.  Once I get to visual, under input devices
> > > I have bus mouse (mse0) and syscons (sc0?).  This is on the 2.1
> > > release boot disk.  Am I missing something?
> > 
> > Argh.  You may need to get a boot disk from Nate Williams; is this
> > a PS/2 style keyboard interface?  Do you know if the keyboard starts
> > in mode 3?
> 
> If it does, you can try the ThinkPad boot floppy out, but that doesn't
> fix 'lockups'.  When you are in the wrong mode, it's pretty obvious as
> every key you touch doesn't do what you want it to do.  (But it *does*
> do something).
> 

My experience is that every key does nothing past a certain point. 
I tried bouncing the num lock key during boot up - right after the
uncompressing kernel message the num lock light stops toggling, and 
other keys don't work.

Where can I get the thinkpad boot floppy, or would it even help?

> You could try 'bouncing on the num-lock' key during bootup to see if
> that helps.  If it does then we've still got the lurking bug, but
> generally speaking it goes away after you build a custom kernel.
> 
> 
> 
> Nate
> 


Thanks, 

Aaron Dailey
aarond@btc.adaptec.com