Newsgroups: comp.sys.transputer
From: lunna@essex.ac.uk (Lunness A P)
Subject: Re: X Helios
Organization: Computing Service, University of Essex, England
Date: 21 Jan 94 14:05:42 GMT
Message-ID: <15762@sersun1.essex.ac.uk>

In article 94Jan20152915@pincoya.inf.utfsm.cl, maurro@pincoya.inf.utfsm.cl (Mauricio Gomez Calderon) writes:
> 
> Hi... i have recently installed PC X Windows package for Helios V1.3, but when
> i try to run the Xserver (xhelios -d), it reports all the normal messages
> EXCEPT the final "X Server Ready", and then the system hangs. The screen
> never changes to graphics mode. 
Path: sol40!lunna
Distribution: world
Newsgroups: comp.sys.transputer
Followup-To: 
References: <MAURRO.94Jan20152915@pincoya.inf.utfsm.cl>
From: lunna@essex.ac.uk (Lunness A P)
Reply-To: lunna@essex.ac.uk
Organization: Computing Service, University of Essex, England
Subject: Re: X Helios
Summary: 
Keywords: 

In article 94Jan20152915@pincoya.inf.utfsm.cl, maurro@pincoya.inf.utfsm.cl (Mauricio Gomez Calderon) writes:
> 
> Hi... i have recently installed PC X Windows package for Helios V1.3, but when
> i try to run the Xserver (xhelios -d), it reports all the normal messages
> EXCEPT the final "X Server Ready", and then the system hangs. The screen
> never changes to graphics mode. 

Hmmm.

First things first, have you got the correct screen driver set up and the correct
parameters in .newxrc? Secondly, have you got the keyboard and mouse drivers in the
correct place? I assume that you are booting first from an I/O server and then
starting X-Helios from a shell? If so then you would do better to use run -d xhelios -d
because the server needs some way of getting unique keyboard input from a window
device (via the `keyboard.no` device driver which should be renamed as keyboard.d and
stuck in /helios/lib). Finally, do you have ethernet/run tcpip etc or not. If not then
also use the option to disable sockets/internet connection when running, I forget
what this is off hand, something like -notcp, do xhelios -help for more info.
  To test the screen driver there is (used to be) a harness program supplied with
X-Helios to allow interactive editing of parameters in newxrc. Use this to check the
screen driver is OK. Finally, you must run Xhelios on the trannie holding the hardware
device (G300 etc) and indicate this processor in .newxrc with RootProcessor.
The original xhelios server supplied was bugged and didn't work. When I got x-helios
there was a supplement disc with a new version on it...

Hope this helps,
Andy Lunness (lunna@sx.ac.uk)


