Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: (mouse makes) Keyboard lockup
- To: tlug@example.com
- Subject: Re: (mouse makes) Keyboard lockup
- From: Christopher SEKIYA <wileyc@example.com>
- Date: Wed, 28 Mar 2001 19:56:51 +0900
- Content-Disposition: inline
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <Pine.LNX.4.30.0103281230270.21536-100000@example.com>; from minich5@example.com on Wed, Mar 28, 2001 at 12:58:42PM +0200
- References: <200102080626.PAA01370@example.com> <Pine.LNX.4.30.0103281230270.21536-100000@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <mtO5C.A.LLB.XXcw6@example.com>
- Resent-Sender: tlug-request@example.com
- User-Agent: Mutt/1.2.5i-jp0
On Wed, Mar 28, 2001 at 12:58:42PM +0200, Martin Minich wrote: > one more thing to add: it was not only gpm, that caused the problem; > also running X led to the keyboard lockup; but running X without a mouse > (ie cheating in XF86Config about the device, not to be able to use > the mouse at all) didn't led to it; Did you set the mouse device in XF86Config to /dev/gpmdata? If you're running gpm, _always_ do this (and set the protocol to mousesystems). Otherwise you will have device contention problems that produce the problem that you describe. gpm is evil, though, and if you're using the machine primarily as an X server it's not a good idea to run it at all. -- Chris
- Follow-Ups:
- Re: (mouse makes) Keyboard lockup
- From: Martin Minich <minich5@example.com>
- References:
- (mouse makes) Keyboard lockup
- From: Martin Minich <minich5@example.com>
Home | Main Index | Thread Index
- Prev by Date: kinput2: mea culpa
- Next by Date: (mouse makes) Keyboard lockup
- Prev by thread: (mouse makes) Keyboard lockup
- Next by thread: Re: (mouse makes) Keyboard lockup
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links