I crashed X again but fail to see how i can ping my computer from a different
host if my comuter is frozen...
I have attached the log file...
When X crashes i get a terminal screen with what looks like part of my
/var/log/XFree86.0.log file printed on it... it says at the end:
"PanoramiX eror : Incompatible screens. No common Visuals.
Fatal server error:
could not create connection block info."
I have to reset my computer because it will not do anything... the cursor is
flashing at the bottom of the screen but it does not respond to anything (i
do not have lights for numlock or capslock so i dont know if they are
flashing [damn wireless logitech keyoard!!!:)])
Thanks for your inquery... i am still trying to find out what i can do...
Thanks
Geoff
On July 14, 2003 03:18 am, Andy Goth wrote:
> On Sunday, July 13, 2003 3:14 pm, Geoff Petzold wrote:
> > I have stumbled onto something thsat is interesting... if i move the file
> > into my /etc/X11/ directory and rename it as XF86Config-4 then everything
> > works fine (ie both screens work the way i thought they would. Thats
> > wierd how that when i typed X -xf86config /root/<blah> it wouldnt work...
> > but if i move it into /etc/X11/ it works... does anyone know why that
> > is??
>
> Shrug. That's weird.
>
> > It works except that it is two SEPERATE desktops... i can move the mouse
> > from one to annother but not any windows. If i put the Option "Xinerama"
> > into the Xf86Config file my xserver crashes and i have to reset my
> > computer.... so right now i can get the two monitors up and running but
> > with two seperate desktops... and i want to know how i can set them up so
> > it is one desktop accross two monitors...
>
> Xinerama problem?
>
> Why do you have to reset your computer? Do you get a black or garbled
> display? Do Num Lock and Caps Lock fail to respond?
>
> Try crashing X again and then ping your computer from a different host. If
> you get a response, then your computer isn't really halted. Then try
> telnetting in. See if you can bring down X through the remote shell (first
> use kill, and then if that doesn't work, kill -9). Also you might want to
> try strace or gdb to see what XFree86 is up to. top can tell you if X is
> caught in an infinite loop or similar (~100% CPU time).
--
Geoff Petzold
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
_______________________________________________
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
