On 12/22/05, bardo <[EMAIL PROTECTED]> wrote: > 2005/12/22, Andrew Conkling <[EMAIL PROTECTED]>: > > You've checked the usual place for the X log, IIRC '/var/log/X*.log'? > > As I said, it is a total freeze, and since logging is done *after* > something happens, my logs are just interrupted after the usual > startup.
OK. > > Also, if you can, try to ssh into your laptop from your other machine. > > Many times I've found that my "freeze" is really just hardcore CPU > > thrashing from X, so I couldn't do anything, but everything else was > > still working. In those cases, I could 'killall -9 X' and try again. > > Didn't try ssh, but if that was the case, a soft halt pressing the > power button would work, and it doesn't. I never got that to work when mine froze, but nonetheless, setting it up to see exactly what's happening doesn't really get you any closer to a solution.... > > Also, "those cases" were when I was having trouble using the nvidia > > driver with the compositor turned on. I'm sure you would've heard > > about these problems by now, but maybe this is something new. If > > you're using the nvidia driver, try switching to nv. Stability is > > almost always better--at a slight sacrifice for speed--and I read (on > > Slashdot, IIRC) that the driver should perform much better. Or try > > turning off the compositing extension. > > I've got a radeon. It doesn't matter what driver I use (ati, radeon, > fglrx), and compositor has always been off, since it never worked. > Obviously, in my first configurations with 7.0, I just need the server > to work, nothing more, so I've got no strange options :) Well, I'm just plumb out of ideas. ...hmm. Except to say, in as much sympathy as I can muster (but with plenty of humor), "Better you than me!" :-P Good luck, Andrew -- http://aconkling.blogspot.com _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
