Xref: utzoo comp.sys.apollo:8674 comp.windows.x:35028 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!agate!agate!cgd From: cgd@ocf.Berkeley.EDU (Chris G. Demetriou) Newsgroups: comp.sys.apollo,comp.windows.x Subject: (a few) problems with X11R4 on Apollos Message-ID: Date: 9 Apr 91 01:21:03 GMT Sender: usenet@agate.berkeley.edu (USENET Administrator) Organization: Open Computing Facility Lines: 60 We just compiled X11R4 on our Apollos, being sick of Apollo's R3 (so they claim) release. We've got a cluster of DN3500s and DN4500s which get constant use, and we just want *X*, no DM (though i personally like DM for *MANY* things...). In any event, we've been having three problems, all on our diskless workstations. xdm-errors reports the following: (1) error (pid 1347): Unknown session exit code 2817 from process 1614 (2) apUnitScreenInit: aws_$init failed. 06090001 Fatal server bug! no screens found XIO: fatal IO error 32 (Broken pipe) on X server "" after 0 requests (0 known processed) with 0 events remaining. The connection was probably broken by a server shutdown or KillClient. (3) apUnitScreenInit: gpr_$init failed. 8013000f Fatal server bug! no screens found error (pid 2585): Server for display :0 terminated unexpectedly the first can be resolved by "kill -HUP"ing the xdm - it generally gets restarted fine. the second generally resolves itself, after trying a few times. the third renders it impossible to restart the display, in any way we've tried, without rebooting the machine. a final problem we've had is that when the screen-saver comes on, it never goes off - that is, X doesn't go away, but just loses track of the keyboard and the mouse. Perhaps using the mfb driver would help a few of the problems (all of our diskless machines are B&W). Any comments/suggestions/workarounds would be helpful. Thanks. Chris Demetriou cgd@ocf.berkeley.edu OCF Staff