From owner-freebsd-hackers Thu Aug 12 11:37:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 8854D14DB9 for ; Thu, 12 Aug 1999 11:37:20 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA71681 for ; Thu, 12 Aug 1999 14:37:30 -0400 (EDT) Message-Id: <199908121837.OAA71681@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: FreeBSD 3.2 on a ThinkPad 360c [keyboard not working] Date: Thu, 12 Aug 1999 14:37:30 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am attempting to get FreeBSD 3.2 and/or 4.0 to go on a TP 360c. The problem I am having is that the keyboard works all the way up to sysinstall. I can use the keyboard in the visual kernel config/etc. I searched and found under 2.2 they suggested setting flags 0x10 on syscons. 0x10 isn't documented to do anything uner 3/4 but I tried anyway, nothing. I also noticed that flags 0x04 and 0x02 may be some use (on atkbc). I tried 0x4, 0x2, and 0x6 to no avail. help? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message