home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!ferkel.ucsb.edu!taco!rock!stanford.edu!ames!haven.umd.edu!darwin.sura.net!news.udel.edu!udel!sbcs.sunysb.edu!sbcs!stark
- From: stark@cs.sunysb.edu (Gene Stark)
- Subject: Re: XFree86 problems (keyboard hangs overnight)
- In-Reply-To: sastdr@torpid.unx.sas.com's message of Thu, 12 Nov 1992 15: 59:17 GMT
- Message-ID: <STARK.92Nov12154408@sbstark.cs.sunysb.edu>
- Sender: usenet@sbcs.sunysb.edu (Usenet poster)
- Nntp-Posting-Host: sbstark
- Organization: SUNY at Stony Brook Computer Science Dept.
- References: <BxM1qt.2xC@unx.sas.com>
- Date: Thu, 12 Nov 1992 20:44:08 GMT
- Lines: 27
-
- > Also, I've noticed some problems with the capslock key; sometimes
- >the capslock is engaged, and I can't disengage it without restarting
- >the server. In this regard, none of the keyboard lights (capslock, numlock,
- >etc...) seem to function.
- >
- > Finally, did anyone ever find out where the <bell> went?
- >
- > - Dave Rivers -
- > (rivers@ponds.uucp (home))
- > (sastdr@unx.sas.com (work))
-
- I was one of the people who posted asking about the bell. No one who
- "knows" anything ever responded, but a few people mailed me who also
- wanted to know anything I found out.
-
- Anyway, in looking at some of the X server code while getting my bus mouse
- to work, it appeared to me that, although the server makes the appropriate
- ioctl's to ring the console bell, the 386bsd console driver doesn't actually
- support these ioctl's at present, so the bell doesn't ring. I could be
- totally wrong about this, but nevertheless my bell doesn't ring and I don't
- see any mechanism in 386bsd that would enable the server to cause it to ring.
- Similar mechanism appears to be missing in the case of the keyboard lights.
-
- I though about hacking in an ioctl for the bell and maybe for the lights,
- but I didn't get around to it yet.
-
- - Gene Stark
-