From owner-freebsd-hardware Tue Aug 8 15:02:10 1995 Return-Path: hardware-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id PAA17299 for hardware-outgoing; Tue, 8 Aug 1995 15:02:10 -0700 Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id PAA17274 ; Tue, 8 Aug 1995 15:02:04 -0700 Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.6.10/8.6.9) with SMTP id RAA16360; Tue, 8 Aug 1995 17:01:56 -0500 Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Tue, 8 Aug 95 17:01 CDT Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Tue, 8 Aug 95 17:01 CDT Message-Id: Subject: Re: PS2 mouse does not work To: schwarz@alpharel.com (Steve Schwarz) Date: Tue, 8 Aug 1995 17:01:13 -0500 (CDT) From: "Lars Fredriksen" Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org In-Reply-To: <9507291543.AA23025@optisun40.optigfx.COM> from "Steve Schwarz" at Jul 29, 95 08:43:07 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1481 Sender: hardware-owner@freebsd.org Precedence: bulk Steve Schwarz writes: > > I have plugged a PS2 mouse into the PS2 port of my Gateway 2000 > DX4/100 (called Liberty) laptop. Running FreeBSD 2.0.5, I added > > device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr > > to my kernel configuration, rebuilt my kernel, and on booting, both > the keyboard and the mouse probe successfully. But after booting, > the keyboard is unusable. I noticed that the question pertaining > to the psm driver is still in the FreeBSD FAQ but the answer is now > gone. Does this mean that (temporarily?) psm support has been > eliminated from FreeBSD 2.0.5? Is there something we PS2 mouse users > should know? > > Or, is the problem some conflict between the PS2 mouse plugged into > the PS2 port and the "builtin" (read, totally unusable) pointing > device located on the keyboard? > > When the Liberty is running DOS and windows, both the mouse and the > infernal builtin thing work together.... > > sts > > There seems to be a problem with how some hardware vendors implemented the IRQ stuff. Basically it seems that disabling the IRQ from the mouse also disables the keyboard one. I posted a patch here earlier that seemed to fix the problem on NCR machines anyway. I'll see if I can't find it somewhere if you want it. Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@fredriks.pr.mcs.net (home-home) fredriks@asiago.cs.wisc.edu