scologin hangs in root

[darreldk]

After relinking the kernal, the scologin starts the x server but it just flashes a couple of times and hangs, i can login at a regular prompt but the software we use is gui based, can anyone help

 

[darreldk]

After left alone for several minutes,it gives me
(xinit:I/O error (errno5): unable to connect to xserver

 

[darreldk]

startx doesn't work, there is no sleeptimer in the scologin scripts, the driver for my video card is correct, i have uninstalled All the graphics utilities and reinstalled
them, and nobody answers gui questions!

 

[apeasecpc]

I noticed myself that no-one seemed to be answering your post, but I avoided it because I am not really that familiar with SCO X-Windows, which I suspect is also the reason for other members.

Have you checked out the A.P. Lawrence X-Windows FAQ pages:

http://pcunix.com/Unixart/gui.html

http://pcunix.com/SCOFAQ/scotec8.html

You say you relinked the kernel and that is when the X-Windows crashed? Why did you relink the kernel? What did you change or install?

 

[darreldk]

Yes, i checked out pcunix.com but it didn't help much, i relinked the kernal because i change the ip address.

Thanks

 

[apeasecpc]

Have you attempted changing the ip address back to its old value?

Did you change just the ip address or other related settings with it?

How did you change the ip address? Did you use the network configuration manager, or did you manually edit the configuration files?

 

[darreldk]

I changed the ip back to its original value, it had no effect, I only changed the ip address and I used the network configuration manager.

 

[apeasecpc]

Do you see any error messages in /usr/adm/messages, /usr/adm/syslog, or /usr/spool/mail/root?

 

[darreldk]

no new error messages

 

[apeasecpc]

I'm sorry, but I don't have anymore ideas. I'm not really that familiar with x-windows to be much help troubleshooting it.

My guess is that x-windows broke because there were some kernell settings changed in the past that just hadn't surfaced yet because you hadn't relinked or rebooted since the changes.

One thing you can do that should fix the problem is re-install your entire system. That's probably what I would be doing by this time considering how long it has been down.

 

[darreldk]

Thanx for all your help, re-installing i will go