daniewicz

Ian: I think increasing the CAS latency results in less demand on suspect ram. If Keith lowers his CAS level he will experience more problems.

If the system will run without errors with one stick of ram then you are good to go B)

Yes, this is possible. Let me know what you see in the bios regarding running the memory in a less demanding fashion. You should be able to adjust the CAS latency to a higher number for example. There may also be options for speed.

It is possible that you could corrupt files on your system. As a short term fix, you might be able to make some adjustments in your bios to slow your memory down. If you stressed your memory less by running at a slower speed, the memtest errors could vanish.

Since clearing the CMOS has not helped, I would unhappily guess that your motherboard is defective.

Kieth: When you removed the motherboard battery to clear the CMOS, did you leave the battery out long enough that the clock and calendar were reset? This is necessary. If the clock didn't reset, the CMOS was not cleared.

The only way to know which ram stick is causing the trouble is to remove a stick and repeat the test until the culprit is located. It is possible that it is your motherboard that is defective and not the ram itself. I believe the first thing I would try is to clear the CMOS. This effectively resets the bios and returns everything to factory defaults. There should be a clear CMOS jumper on your motherboard. If you are unable to locate this jumper, you can also remove the motherboard battery for 5 minutes or so. This will also clear the CMOS.

Aaggh! I didn't see that. Good eyes SilverSurfer60.

You can burn a ultimate boot CD from a download at this website: http://www.ultimatebootcd.com/ Booting your computer with this CDROM in your CD drive will allow you to run various hardware diagnostic programs including memtest. This will determine if one of your ram sticks is bad.

So the system has logged a restart with no prior error message. This makes me suspect a hardware failure. Either a overheated processor as scarecrow suggested or bad ram. Are you familiar with running the program memtest to check ram?

Have a look in /var/log/messages

The default kernel is only able to see approximately 850 MB of ram, so the behavior you are seeing is normal.

Welcome to the board! B) The first thing I would suggest is looking through the file /var/log/messages for any error messages. If you post the error message(s) here, we can help.

Your link is not working.

I have used ntop in the past. It might meet your needs.

fair enough

Or if you prefer using a gui menu tools system tools configure your computer system manage system services......

Are you running the service lisa? It has been known to slow a system down.

This is default behavior in KDE under 2008.0 :unsure:

I have disabled harddrake and seen no consequences yet..... :unsure: B) I feel confident that if you disable it, your xorg.cong over-writes will be a thing of the past.

And for clarity, Adam Williamson works for Mandriva. The rest of us here do not....We are not Mandriva employees, just computer/linux enthusiasts.

You mention "massive hardware updates." As David said, try re-seating your cards. I would also clear the CMOS on the motherboard.

synthecin: Glad you were successful

go to the adobe website http://www.adobe.com/shockwave/download/do...=ShockwaveFlash and download the tar.gz file extract libflashplayer.so and copy it to ~/.mozilla/plugins This assumes you are using firefox as your browser.