KDE 3.5 Crashing
slvhwke at optusnet.com.au
Mon Jun 18 07:17:01 UTC 2007
>I apologize in advance if this advice is too rudimentary.
Rudimentry is good :) I am a BSD noob :D
>Sounds more like hardware. You did not say how you tested your memory. If
> did not use Memtest86, get and run that. Also run fsck manually.
I used Memtest and I have had already run fsck since my poor hard drive was
compaining bitterly of so many cold restarts. There were some errors that
were cleaned up - and it seems a bit more stable <as in it can go a few
hours before freezing>
> If the hardware checks out okay, you can try to isolate what is failing.
> various compoents one at a time. For example turn off the wireles
> work normally. If that still fails, set up a dd command or a benchmark
> to run under kde buut without the network. You can set up either of these
> overnight so you should get a good idea that the test worked or not. If
> a failure without the network repeat the test using twm (its built into
I pulled out my wifi card (since i wasn't even using the darn thing), the
only other thing to pull is my video card (Nividia GForce 6600) - the rest
(sound, my ethernet card etc) are all onboard.
Now I have being trying to find something comparable to windows where there
is a device manager where i can disable or enable hardware. Is there
something like that? Or is it console command only? I've been reading
through the handbook and the KDE doc but haven't come across much.
I'll try a benchmark prog and then try twm if there's a prob.
> If all this fails to identify the problem you need at least to get a
> dump. The developers handbook has information on this.
> Hope this helps,
Help heaps, Thanks :)
More information about the freebsd-questions