From: rich@Rice.edu (& Murphey)
Subject: Re: Minor XFree86 problems, long function key string bug in elvis
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Wed, 30 Dec 1992 06:36:55 GMT

>>>>> In article <1992Dec30.005909.15079@tackle.uucp>, jc@tackle.uucp (John Capo) writes:

J> I have XFree86 running and only have a few problems left to solve.

J>     1. Auto-repeat is very slow.  I can turn it on and off via command
J>        line switches or in Xconfig but I can't change the repeat or
J>        delay rate.

Well, xset can enable or disable the repeat but it doesn't have
support for changing the rate or delay.  You should be able to use
'AutoRepeat 500 5' in your Xconfig to set the delay and rate.

J>     2. Num lock does not work at all.

try adding 'ServerNumLock' to your xconfig:

       servernumlock
               forces the server to handle the numlock key inter-
               nally.   The  server sends a different set of key-
               codes for the  numpad  when  the  numlock  key  is
               active.   This enables applications to make use of
               the numpad.

J>     3. I have no bell.  I have tried various command line switches and
J>        xset options but nothing.  Same hardware works fine with DOS and
J>        ISC running ISC.

the bell requires support from the console driver.  Holger's console
driver (codrv) already supports the bell, and patches to support the
bell for 0.1 console driver (pccons) have been proposed for the next
XFree86 release.  So you can either 1) install holger's console driver
in your kernel and grab the appropriate X386 binry, or 2) just hang
tight till the next XFree86 release when the bell is supported with
pccons.

J> I have not seen these problems mentioned on the net.

J> Another thing I have noticed is that my machine is on its knees when
J> I am compiling and running X at the same time.  It may take 20 seconds
J> to expose a window. Same hardware with X386 and ISC only exibited this
J> slowdown when compiling, running X, and my cron job that rebuilds the
J> uucp paths file and uuwho database kicked in.  I added a second disk
J> with 16M of swap but no difference.

Sounds like you need more memory.  Your memory (RAM) should be sized
to according to the working set size of the processes you intend to
run.  'ps axl' will report the resident set size (RSS) of each
process.  The RSS is an instantaneous measure of the ammount of memory
used by the process.  It tells you how much of the process is paged
into RAM. 

J>     No name 386/33, 8M RAM, 128K cache.
J>     Adaptec 1542B, 2 Maxtor 120MB, Archive 60MB tape, Julian's driver.
J>     Compuadd generic ET4000 VGA card.
J>     WD8000 ethernet card.
J>     All of the kernel patches in Terry's patchkit.

J> Without X running the machine is very speedy, much better raw disk I/O
J> performance than ISC with the same hardware.  My only conclusion is
J> the ISC SysV kernel makes better use of the relatively small memory I
J> have.  Any thoughts?  Is there a kernel parameter that wuld help?

shared libraries will help whenever they are added to 386bsd.  Rich
Newsgroups: comp.unix.bsd