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.
OS: Debian Sid with kernel 3.2.0-1-686-pae
CPU: Core2Duo 7500 @ 2.93GHz
Mother Board: Asrock G31M-S R2.0
Memory: 2 sticks of 2 Gb each. (I think they work at 800 Mhz).
Graphics card: nVidia GeForce 7300 GT.
Since about 2 or 3 weeks ago the computer freezes randomly and all of a sudden with no apparent reason (it has happened about 6 times during this period). I have checked /var/log/kern.log, /var/log/messages and /var/log/dmesg and they never show anything by the time the freezes have occurred. At first I suspected it could be caused by a defective memory stick, so I grabbed a LinuxMint CD and let memtest86+ run during 7 hours, but when I came back, it had not found any memory error. I haven't made any hardware or BIOS change recently and this is a computer I put together about 2 years ago (this didn't use to happen before; it was completely stable).
BTW, I'm not sure if this is a hardware problem or a software problem, but for the type of freeze it seems to be hardware-related (everything just freezes completely and suddenly, as I said before; if, for example, I'm listening music, the sound just keeps repeating itself, the pointer gets stuck at one point of the screen, etc). So far it has only happened on Debian Sid, but it's almost the only OS I use on this machine; though I have Windows and Ubuntu installed as well, I never used them.
How can I know what is causing these freezes? Should I let memtest86+ run longer (if so, how many hours)?
Hi kuser. Thanks for the links (and the warning). I can watch youtube videos, I'll take a look later. I booted a CD with memtest86+ and will let it run for 12 hours to see if it finds some error, then I will try to find a DVM to measure the voltages.
Be sure to use caution when making any measurements. One hand rule! Place your reference probe(power ground) via clip then be sure to use one hand to hold the other probe to measure. Do not ground yourself.
Be sure to have the pinout for the measurement points. ATX pinouts. Use caution! Always be safe.
If you've got away with running memtest for a 7 hours, I doubt its your RAM.
I'm suprised that nobody has suggested cleaning the CPU heatsink out. Overheating CPUs can cause random lockups, etc..
You can normally check the voltages from inside the BIOS. Its not as accurate as using a voltmeter, but it at least gives you a good idea of where the voltages are.
The only problem with using the BIOS voltages is that you cant check when you put the machine under load, which is where power problems are mostly likely to happen.
Why did you change the PSU?
I'd be very careful with brands like 'delux'. Its better to have a good quality power supply than some cheap 'yum-cha' junk with a 600watt sticker on the side......
I checked the heatsink and though it's a little bit dusty, I don't think it's as dusty as to cause any malfunction. I also used cpuburn (a cpu stress program) for about 5 or 8 minutes, checked the CPU temperature and they didn't rise too much during this time; from 38║ C idle to around 52║ C under load, although it probably would have rised more if I had let cpuburn run longer; (the machine didn't freeze during the stress test).
I also let memtest86+ run for 12 hours last night and it didn't find any error, so I guess we can discard the memory sticks from the list of suspects.
Now I'm starting to be suspcicious about the PSU. I replaced the one I had before because the machine just stopped working one day (it didn't even beeped, no leds, the PSU fan didn't spin, etc.); so I took this one I had bought like 2 years ago but had not used, connected it, and the PC worked again. Will have to do the voltage test these days to see what I find. BTW; in case I decide -or have- to buy a new PSU, which brands would you recommend?
Yes, I'm using the nvidia binary driver available on the Debian repositories. I'm not on my PC right now to check, but according to this, the nvidia-glx package on Debian Sid is at version 295.20-1 at the moment, so I probably have this version installed. In fact, if memory doesn't fail me, the nvidia-glx package was upgraded to this version about 2 or 3 weeks ago, around the time the problem started happening, so it might very well be the driver causing issues. Now, in that thread you say you could type "reboot" to reboot the machine; can you switch to a virtual console when it happens? In my case I can't because the system is completely frozen and unresponsive when the problem occurs, so I can't switch to a virtual console in order to reboot.
Fortunately, it hasn't happened to me for over 3 weeks now so I can't verify it. As far as I remember that time it froze while I was in X and a terminal was open, music was playing, etc., so I typed 'reboot' in sakura and it worked (rebooted). In my case it was clear that it's not the system itself that froze, just the display. I've been using nouveau drivers for some time now and it works fine.