On Saturday, April 30, 2011 11:00:51 AM StarLion wrote: > > Apologies if I missed it, but you havent yet clarified if the whole m/c > > is locked up or just the display/kbd. > > Can you access it via the network - as various people suggested? > > If so, what does ps show? > > what happens when you send a HUP signal to the X server? > > Regards > > Andy > > That's my mistake for overlooking that, sorry. > It seems to be inaccesssible over the network as well. The network's > router lists it in the DHCP client list, but neither ping or ssh can > reach it. > > -- > Next meeting: Blandford Forum, Wednesday 2011-05-04 20:00 > Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ > How to Report Bugs Effectively: http://goo.gl/4Xue Ah - thanks for that - I had a similar problem with FC13 - I concluded it was a hardware fault to do with memory mapped between the Graphics card & something else. So I just lived with it and surprise surprise after upgrading, it doesn't occur in FC14 - so it wasnt a hardware issue after all. I tried various guesswork things at the time, but what had the most effect was getting X to decrease its use of memory - I did the following straw-clutching - o Dont load a background bitmap o Ensure KDE uses NO clever things like silly graphics effects o Disconnect any usb devices you don't really need o If poss (prob not with a laptop display) run X at a lower resolution. o Use an external monitor (if that works it would seem to indicate a heat problem associated with the laptop display ?!?). o Have the m/c exorcised :) .... But after my experience it really looked like a misbehaving device driver. Sorry can't help - but of course - if you have a much older kernel in you boot list - see if it runs better with that. Regards Andy
-- Next meeting: Blandford Forum, Wednesday 2011-05-04 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
