Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news-peer.gsl.net!news.gsl.net!hammer.uoregon.edu!news.uoregon.edu!Symiserver2.symantec.com!news From: tedm@agora.rdrop.com Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: XFree86 keyboard belly-up Date: 4 Dec 1996 07:12:30 GMT Organization: Symantec Corp. Lines: 20 Message-ID: <58388u$3cg@Symiserver2.symantec.com> References: <5802vn$3a9@anorak.coverform.lan> Reply-To: tedm@agora.rdrop.com NNTP-Posting-Host: shiva2.central.com X-Newsreader: IBM NewsReader/2 v1.2.5 In <5802vn$3a9@anorak.coverform.lan>, brian@anorak.coverform.lan (Brian Somers) writes: >I'm sure I've seen people complaining about keyboard locking under >XFree86 3.1.2G and FreeBSD 2-2-*-SNAP - well, it just happened to >me on 2.1.5..... :( > >I figured that the machine was alive and also found that I could >still connect. I wrote a very simple program (available on the web >site in my sig) called setcon that uses the VT_ACTIVATE ioctl to >change the current VT.... and lo and behold, switching back to the >X screen restored the keyboard ! > >It's not a fix, but it's a pretty good work-around :) > > Of course, you can always go to the local junk dealer and just buy another keyboard for $5 or so. That's what I have done with this problem in the past, it seems that some PC's and some keyboards don't get along very well. I've had keyboard locking occur even on DOS machines.