Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!mips!sdd.hp.com!caen!umeecs!dip.eecs.umich.edu!dmuntz From: dmuntz@dip.eecs.umich.edu (Daniel A Muntz) Newsgroups: comp.unix.bsd Subject: Re: X386 and keyboard locking! Message-ID: <1992Aug7.181344.497@zip.eecs.umich.edu> Date: 7 Aug 92 18:13:44 GMT Article-I.D.: zip.1992Aug7.181344.497 References: <1992Aug7.171205.10281@gumby.dsd.trw.com> Sender: news@zip.eecs.umich.edu (Mr. News) Organization: University of Michigan EECS Dept., Ann Arbor Lines: 25 In article <1992Aug7.171205.10281@gumby.dsd.trw.com> hubbell@gumby.dsd.trw.com (Steve Hubbell) writes: >Problem 1: >Once the X server is started, my keyboard is 100% dead. Nothing works >including ctrl+alt+backspace. This is the most severe of my problems. I've been corresponding with several people via email who have been having similar problems, so I've decided to post this... I have the same problem. However, after I kill the first server, all subsequent servers work correctly. > >Problem 2: >Using the Microsoft driver, the system isnt catching mouse button events UNTIL >the mouse is moved! To click on anything, I must first click the mouse and >then move it slightly before the system recognizes the mouse is down. >I can also let up on the mouse buttons and the system doesnt notice >until the mouse is moved! This may be the result of buffering in the serial port. 16550(A,AN,AFN) UARTs buffer 14 chars before generating an interrupt (as com.c currently reads). If you're using a mouse along with a 16550, the buffering needs to be disabled. 16450 and 8250 UARTs work fine. -Dan