Date: Wed, 7 Feb 1996 00:15:21 -0600 (CST) From: mailing list account <lists@argus.flash.net> To: jeff@stat.uconn.edu (Jeffrey M. Metcalf) Cc: bugs@FreeBSD.org Subject: Re: PS/2 Mouse Message-ID: <199602070615.AAA06158@argus.flash.net> In-Reply-To: <9602061412.AA09674@ruddles.stat.uconn.edu> from "Jeffrey M. Metcalf" at Feb 6, 96 09:12:04 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply: > Hi, > > I recently recompiled a custom kernel by adding the line: > > device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr > > > I removed all conflicts with my PS/2 mouse and the kernel boots fine and > detects my mouse. I added the dev psm0. But after I rebooted the > second time (after editing out the conflicts), my keyboard froze up > just like I was warned it could. Unfortunately pressinf the numlock > key multiple times during the bootup process didn't help (unless I am > not doing it correctly). Any other fixes short of buying a microsoft > mouse? The fix would have to be as simple as possible since I have > no experience building drivers or anything of that sort. the only solution i have found to the keyboard lockup problem is to tap a 'harmless' key a couple of times while the kernel is still probing. numlock or capslock twice [you won't see a response until rc is running, so tap it twice to keep it in the default state] will suffice. as far as freebsd psm0 support goes, this problem is old as the hills. from a security standpoint, i don't mind. someone could possibly do a three finger salute on your box, but will have a hell of a time figuring this one out. Jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" jbryant@argus.flash.net - FlashNet Communications - Ft. Worth, Texas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602070615.AAA06158>