Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Do you mean freeze completely, or the mouse freezes? The mouse on Both of my Debian machines has been freezing randomly for about a week. I've been in the middle of upgrading stuff and they're both now on etch. I also noticed that the Nvidia console would crash when I tried to look a the glx settings. Just now, I removed the Busid line from the display devices configuration in xorg.conf. The nvidia console doesn't crash now. I have to admit that I didn't re-enable it to make sure that was the problem. Only time will tell whether this fixes it.
The entire thing freezes, no ctrl-alt-bckspace. I have conky running so I can see if its something with the hardware. That freezes. Barley 15% of my memory is being used and not even 5% of my cpu is being used when it crashes. I let memtest run again this time for 3 hours and it didn't find any errors.
Its probably a driver thing. Is there a way to watch what is loaded live?
Ok, I tried vacuuming out my computer, and that about lowered my computer's temperature down by 10 degrees, but it still froze. So I added "noapic nolapic pci=noapc" to my kernel in grub's menu.lst. So far so good.
You shouldn't clean your computer by using a vacuum cleaner.
Wear anti-static wrist strap, or place computer on anti-static pad, avoid ESD (electro static discharge) at all cost. One littles zap can render a computer's circuitry useless. Basically, in a nut shell, static electricity is extremely harmful and the damage usually can not be un-done, the computer may not start, may start but will not work properly.
Vacuums create excessively high levels of ESD
Compressed air from a can, or from compressor with filters, are recommended, alcohol or alcohol based cleaners are not recommended as some of these types of cleaners leave residue behind that can cause a short circuit, especially in a 64 bit world where wires/tracing on mainboards/circuit boards have doubled in numbers in certain areas making them smaller & closer together.
I think that I've read in the past that a bad CD/DVD drive can indeed lock up your system. Since it doesn't work anyway no reason not to remove it (both IDE/SATA and power cable).
Also have you trying going to a terminal screen (CTRL+ALT+F1) to see if you can log in that way? If you can, run "top" and see if any process is hogging up your resources. "ps aux" can also let you check for zombie processes. CTRL+ALT+F7 will get you back to your GUI by the way.
Lastly, if you have another machine available, try to ping your frozen box. A reply means it's not completely dead. Then try ssh'ing (or telneting) in to try the top & ps aux.
I think that I've read in the past that a bad CD/DVD drive can indeed lock up your system. Since it doesn't work anyway no reason not to remove it (both IDE/SATA and power cable).
Also have you trying going to a terminal screen (CTRL+ALT+F1) to see if you can log in that way? If you can, run "top" and see if any process is hogging up your resources. "ps aux" can also let you check for zombie processes. CTRL+ALT+F7 will get you back to your GUI by the way.
Lastly, if you have another machine available, try to ping your frozen box. A reply means it's not completely dead. Then try ssh'ing (or telneting) in to try the top & ps aux.
Well..the drive isn't compleatly dead. It works, ut if it doesn't read a perfectly clean disc..I just keep ejecting it and re putting it in and it'll read it eventually. I'll try the ping thing and the terminal.
It also could be power supply related. I'll admit I haven't read through every single post here so this may have already been stated, however a bad or failing power supply could cause problems such as this (I've had my share of this as a problem before)
Its not the power supply because windows works fine. I have a feeling its a driver issue, I just need to figure out which driver. I tried the CTRL-ALT-F1 and that didn't work at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.