X386 1.1
Thomas Roell
roell at informatik.tu-muenchen.de
Thu Mar 7 19:35:05 AEST 1991
>1. I get errors from Xlib about too many clients. I have 32 pty's and
> 32 streams ports, so that is not the problem. Anyone know why?
What about raising NFILE in /etc/conf/cf.d/stune ? If you have this only
set to 20 logically no more than about 13 clients can connect ...
>2. Does anyone have a good 1024x768 configuration for a Sigma Legend card.
> My monitor will go to 66 Mhz. Can 1152x900 be used in non-interlaced
> mode with this monitor configuration?
No. The problem is not the Monitor, the problem is the Video-Chip. The
ET4000 allows only dot-clocks up to 65MHz (this restriction seem simply to
be imposed by the speed of the DRAMS). For 1152x900 non-interlaced, you'll need
a much higher dot-clock.
>3. I originally installed the X386 binaries on the system with 2.2.1
> and then later added TCP/IP. Now the machine locks up quite often
> and I lose the console. I can get to the machine over the net, however.
> X drops out and doesn't reset the keyboard, so there is no control left.
> Moreover, I get wierd activity while trying to run clients. For example,
> trying to run an xterm will fail one time and then succeed the next.
> Is there a progam available to reset the keyboard? That is, one that
> could be run from a remote terminal, but will reset the console setup?
a) Do never a 'kill -9' to the xserver !!! Use a 'kill -1'. Then the server
will gracefully exit and restore the keyboard.
b) TCP/IP with many clients may use up more STREAMS buffers. Use 'netstat -m'
to detect the problematic buffers and increase the allocated buffers then
in /etc/conf/cf.d/stune.
- Thomas
--
_______________________________________________________________________________
E-Mail (domain): roell at lan.informatik.tu-muenchen.de
UUCP (if above fails): roell at tumult.{uucp | informatik.tu-muenchen.de}
famous last words: "diskspace - the final frontier..."
More information about the Comp.unix.sysv386
mailing list