Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:9948 comp.windows.x.i386unix:8726 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!europa.eng.gtefsd.com!library.ucla.edu!ihnp4.ucsd.edu!ames!olivea!news.hal.COM!decwrl!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions,comp.windows.x.i386unix Subject: Re: FreeBSD-1.1-BETA, XFree86-2.1, Logitech Bus Mouse, messed up keyboard I/O Date: 21 Apr 1994 03:41:15 GMT Organization: Montana State University, Bozeman MT Lines: 33 Message-ID: <2p4skr$22p@pdq.coe.montana.edu> References: <2ovtqc$fis@solaria.mil.wi.us> NNTP-Posting-Host: 153.90.192.29 In article <2ovtqc$fis@solaria.mil.wi.us>, Joe Greco <jgreco@solaria.sol.net> wrote: >I've spent all day messing with this, trying to get a Logitech Bus Mouse to >work. Symptoms: XF86_SVGA seems to work fine, except that most (usually >all) keyboard I/O never appears. I can move the mouse around the screen and >scroll the screen. I can pop an xterm up. But when I try to type (in the >xterm), only about 10% of my characters make it, and eventually this seems >to dwindle to nearly 0%. FAQ: 95% of the time the problem is that getty and X are fighting for the keyboard. - Use a console driver that allows multiple consoles >The >console driver is whatever GENERICAH's is (pccons I believe). My kernel >sources are 30 miles away over a 14.4K SLIP link, so recompiles are a pain - >ie I haven't played extensively with the kernel. Either disable the getty on /dev/ttyv0 and start up X via xdm in /etc/rc.local, OR start X after logging in with startx. The former is known to work, the latter has caused some folks problems. Nate -- nate@bsd.coe.montana.edu | FreeBSD core member and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-4836 | Graduating May '94 with a BS in EE home #: (406) 586-0579 | - looking for work in CS/EE field.