Solaris 2.5 OpenWindows crashes system

On starting Open Windows, the screen goes black, followed by a small amount of disk I/O, then everything stops, and all I can do is reset the machine.

This is not a display config problem, since even setting it to 640x480 16 colours has the same result.

It started occurring after I installed Wabi and enabled my second serial port. (COM2, its an intel platform). I have reversed both of these, but it didn't solve the problem.

Has anyone encountered this sort of problem?
mgAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jlmsCommented:
No, but you should try to generate a file that displays what is happening when your X server is started, it very well could be that you find out in this "log" what is happening.

  Please explain how do you intiate your openwindows session and from there could be easier to find out how to produce a logfile of your openwindows session.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mgAuthor Commented:
Log file sounds like a wise idea. Open Windows is normally started automatically from the .login script, but I believe all it does is set an environment variable to /usr/openwin, and then calls the /usr/openwin/bin/openwin binary file.
Executing that file on its own has the same results.
0
jlmsCommented:
That's right, now, /usr/openwin/bin/openwin is a script, no a binary, this fact gives you the chance to put one or to messages here and there to find out where things are being messed up, is highly probable that the program that is failing is Xsun, check tha man page of both openwin and X (or Xsun) is should mention an option that allows you to get a log file, if there is not such option you can modify openwin launching X with a truss command, in this way you could check which files X is trying to open (a library or a configuration file could be missing).

  I promess to check myself to give you more information.

Regards.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.