Re: [XFree86] X locked up and now will not load

2003-01-21 Thread [EMAIL PROTECTED]
Thanks for trying to help me. 

Yes, I have done a complete power off. 
I always leave my machine on 24-7, and have not had problems prior to this. 
(My old SCO-Unix 486 box ran 24-7-365 from 1992 through 1999 and was very
rarely shut down and never had a problem.) 

I have not made any configuration changes in this machine for many months 
and I have rebooted a few times since the last config change (when I
installed win4lin) several months ago. 

Apparently, the monitor is dead.  It is about two years old and has not
given me any problems (19 Sylvania F91).  So, I took the monitor off of 
my wife's machine and it works fine with my Windows 98 partition and with 
the non-X terminals.  only F7 does not work. 

We have very stable and even power here (Arizona) and have had no power
outages as far back as I can remember.  The fact that everything works fine
except X on F7 seems to suggest to me that the problem is not hardware, but
something wrong with the X software.  When I try to do startx on another
shell terminal, I get a message saying X is still running and I can't kill
it.  How could that be hardware? 

Joe 


Original Message:
-
From: Peter Finderup Lund [EMAIL PROTECTED]
Date: Tue, 21 Jan 2003 05:57:34 +0100 (MET)
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [XFree86] X locked up and now will not load

On Mon, 20 Jan 2003, [EMAIL PROTECTED] wrote:

 I have tried to kill all related processes and it just respawns.
 I have rebooted several times by shutdown -r now and by CTRL+ALT+DEL
 Yes, the process IDs are different, and I have tried killing every
 applicable process by the most recent process ID numbers, always
 with the same blacked screen and respawn that locks up.

Ok - I initially thought some glitch had happened that tripped the X
server and once you got rid of it things would work fine again.

Apparently that is not the case :(

Did you try a complete power off?  (sometimes a reset isn't as complete
as a power off is)

How long had the machine been on before things went wrong?  Could you have
done something that changed some configuration files some time ago without
restarting X or rebooting?  I have seen this happen a couple of times,
where a machine seems to be perfectly configured until one tries to
restart a service or reboot it whereupon it trips on a broken
configuration file :/

Does the monitor work on other machines?  If it didn't, that would be a
confirmation that something nasty really did happen to the power and that
your UPS didn't handle it all too well :/   In that case you might have an
acute case of bad hardware on your hand and no amount of reconfiguration
and software trickery will fix it :(

-Peter




mail2web - Check your email from the web at
http://mail2web.com/ .


___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86



Re: [XFree86] X locked up and now will not load

2003-01-21 Thread Peter Finderup Lund
josef: If you try this, please don't delete them.  Move them to a separate
directory instead so you have a way of getting them back.

-Peter

On Tue, 21 Jan 2003, Yury Tarasievich wrote:

 This is only guessing, but could you try removing files in your ~
 directory which have names like .X... (dot capital X something). Also
 remove everything having such names in /tmp directory.

 Of course all this has to be done before attempting to run X.

 [EMAIL PROTECTED] wrote:

 Tried all the actions you suggested, with no success.
 Tried killing 2935 and all other X-related processes,
 but the screen instantly goes blank and the system just
 tries to restart all the same processes, causing another
 lock-up.  So, where do I go from here?

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86



Re: [XFree86] X locked up and now will not load

2003-01-20 Thread [EMAIL PROTECTED]
Tried all the actions you suggested, with no success. 
Tried killing 2935 and all other X-related processes, 
but the screen instantly goes blank and the system just 
tries to restart all the same processes, causing another 
lock-up.  So, where do I go from here? 



Original Message:
-
From: Peter Finderup Lund [EMAIL PROTECTED]
Date: Tue, 21 Jan 2003 02:06:43 +0100 (MET)
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [XFree86] X locked up and now will not load


On Mon, 20 Jan 2003, [EMAIL PROTECTED] wrote:

 and F11 displays a graphical display, but F7 where X is supposed
 to be running is black.  When I tried 'startx' on another terminal,
 I got the error messages shown below.

X is still running but hangs somehow.

 How do I get things cleared out so X will start again?

killall X or kill 2935 (or whatever the process id of X is) as root.
Or reboot (with ctrl-alt-delete so everything closes down properly).

 It seems whatever happened blew my primary monitor, also.

Yes, apparently.  That really boggles me.

 I have everything on a UPS, so I don't think it was a power
 spike.

Most UPSes are not very good.  They do paper over most of the 3rd world
power problems you have in the US but not all of them.  The better
solution is of course to get a good power grid, like we have in the
civilized world ;)

 Please respond with some guidance asap. You could call toll free
 800-552-7102.  I'm limping on an old system to send this email.

No way.  If you need it that bad you can call somebody else and pay for
customer support.  I'm happy to help you by email, though, as long as it
all stays on the xfree86 mailing list :)

 _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
 _XSERVTransMakeAllCOTSServerListeners: server already running

 Fatal server error:
 Cannot establish any listening sockets - Make sure an X server isn't
 already running

it says here that your old server is still running

 Xlib: connection to :0.0 refused by server
 Xlib: Invalid MIT-MAGIC-COOKIE-1 key
 giving up.
 xinit: unable to connect to X server
 Xinit: No such process (errno 3): Server error.

... but you can't get to it.

 root  2935  2924  0 14:45 ?00:00:01 /etc/X11/X -deferglyphs
16 -auth

Yep, here it is.

Hey, isn't there something wrong there?  Why has it only used a second of
CPU time?

-Peter



mail2web - Check your email from the web at
http://mail2web.com/ .


___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86



Re: [XFree86] X locked up and now will not load

2003-01-20 Thread Peter Finderup Lund
On Mon, 20 Jan 2003, [EMAIL PROTECTED] wrote:

 I have tried to kill all related processes and it just respawns.
 I have rebooted several times by shutdown -r now and by CTRL+ALT+DEL
 Yes, the process IDs are different, and I have tried killing every
 applicable process by the most recent process ID numbers, always
 with the same blacked screen and respawn that locks up.

Ok - I initially thought some glitch had happened that tripped the X
server and once you got rid of it things would work fine again.

Apparently that is not the case :(

Did you try a complete power off?  (sometimes a reset isn't as complete
as a power off is)

How long had the machine been on before things went wrong?  Could you have
done something that changed some configuration files some time ago without
restarting X or rebooting?  I have seen this happen a couple of times,
where a machine seems to be perfectly configured until one tries to
restart a service or reboot it whereupon it trips on a broken
configuration file :/

Does the monitor work on other machines?  If it didn't, that would be a
confirmation that something nasty really did happen to the power and that
your UPS didn't handle it all too well :/   In that case you might have an
acute case of bad hardware on your hand and no amount of reconfiguration
and software trickery will fix it :(

-Peter


___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86