Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This may not be your problem but I ran into this once before. I had compiled in the wrong chipset for the IDE controller and it was erroring out during heavy drive usage. If you want to test this, you can use something like this:
Again, that may not be what is happening to you but it is easy to test if you have hdparm installed. It may not fail until the forth or fifth set though. Mine would do three with no errors but usually fail on the forth and would always fail on the fifth.
To find out whether you have bad memory, you should download MemTest86. The easiest way to get it up and running is by downloading and burning a copy of Knoppix. If, for some reason (slow connection, etc.) you don't want to download the Knoppix CD, you can get MemTest86 from here:
KHX:DDR - Kingston HyperX memory is designed based on the latest DDR specifications available, and is 100% tested at Kingston's flagship factories. Plus, these Kingston modules come with the standard Kingston lifetime warranty and toll-free Tech Support. Built with the best-quality components, Kingston HyperX is competitively priced and is the choice for the serious gamer. HyperX is available in single and dual channel memory kits.
It is not said that memory is bad. It might be anything used during the test. As memtest is a program, it will use the CPU. The CPU reads/writes from/to memory via the motherboard. So the following might be components that can be faulty (in my opinion):
You have to eliminate the possible causes.
Further you can check the memory timings and try to relax them a bit and stop overclocking (if applicable).
I ran memtest without changing the ram configuration, how they were installed. Then I removed one stick and ran it again and got no errrors, then I removed the second stick, replaced it with the first in the same slot and thats when I got massive errors right off the bat.
Would it be safe to remove all the simms and run memtest to check the cpu and caches?
I think that since memtest only produces errors when you have a particular stick installed, it's safe to assume that it's a RAM problem and not a CPU/Motherboard problem. Also, the computer will not boot if no RAM is installed; it will just beep at you. As far as I know, memtest was not designed to test the CPU's onboard memory.