From owner-freebsd-questions Sat Jun 22 14:46:14 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA11823 for questions-outgoing; Sat, 22 Jun 1996 14:46:14 -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 OAA11818 for ; Sat, 22 Jun 1996 14:46:11 -0700 (PDT) Received: from btc.btc.adaptec.com ([162.62.63.6]) by milpitas.adaptec.com (4.1/SMI-4.1) id AA20358; Sat, 22 Jun 96 14:42:42 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 PAA13219; Sat, 22 Jun 1996 15:46:10 -0600 Message-Id: <199606222146.PAA13219@btc.btc.adaptec.com> Comments: Authenticated sender is From: "Aaron Dailey" To: Terry Lambert , Nate Williams Date: Sat, 22 Jun 1996 15:35:41 +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: aarond@btc.btc.adaptec.com, 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 > To: Terry Lambert > 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). > > 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 > > An update of where I'm at . . . I've tried disabling L1 (on CPU) cache, to no avail. I don't have L2 cache. I already do have 8 MB of memory, so I don't think I'm running into memory constraints. I have also tried pounding on the num lock key after the uncompress message in the boot disk, but also to no luck there either. One thing I want to try is pulling out my DX4/100, and just running with the original SX/25, which would also run the whole VL BUS at 25 MHZ. Any other ideas? Aaron Dailey