From owner-freebsd-hackers Mon Jul 10 05:33:17 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA07195 for hackers-outgoing; Mon, 10 Jul 1995 05:33:17 -0700 Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA07187 for ; Mon, 10 Jul 1995 05:33:16 -0700 Received: by dg-rtp.dg.com (5.4R2.01/dg-rtp-v02) id AA29408; Mon, 10 Jul 1995 08:32:38 -0400 Received: from lakes (lakes [192.96.3.39]) by ponds.UUCP (8.6.9/8.6.5) with ESMTP id IAA13848 for ; Mon, 10 Jul 1995 08:16:53 -0400 Received: (from rivers@localhost) by lakes (8.6.11/8.6.9) id IAA01062 for freebsd-hackers@freefall.cdrom.com; Mon, 10 Jul 1995 08:19:05 -0400 Date: Mon, 10 Jul 1995 08:19:05 -0400 From: Thomas David Rivers Message-Id: <199507101219.IAA01062@lakes> To: freebsd-hackers@freefall.cdrom.com Subject: Problems with 2.0.5-R and IBM PS/NOTE? Sender: hackers-owner@FreeBSD.org Precedence: bulk I just tried to upgrade a 1.1.5 IBM PS/NOTE to 2.0.5-R. Most everything went fine (thank goodness for the "holographic shell"), except that the psm driver still suffers the same problem it had in 1.1.5. That is, when I enable the psm driver, and it does its probe to determine there is a PS/2 mouse; I wind up with a locked-down keyboard. If I don't do the probe (disable it with boot -c), everything works just fine. This tends to point to the psm probe routine as being the culprit that locks down the keyboard... any ideas? - Dave Rivers -