Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.1, 14.2
This kind of problem can be caused by hardware problems, such as over heating. I would suggest you get a live distro, and run it for a while. If there are no problems, then you probably have a software problem. If it does freeze, then you know its hardware related.
Run memtest, it available for most distros. Look for some way to display the temperature
of your CPU(s). Some systems can do it in BIOS, and there are tools you can install in software to monitor the heat.
When was the last time you had the covers off to clean the fans and heat sink?
I was able to get memtest86 working from Hiren's Boot CD. Ran it for 12 hours with no errors. I guess in the AM, I'm going to crack the case and reseat the memory. CPU as well, if it's not soldered on.
Most of the hard freezes I've had were X locking up. Although not really frozen as you could ssh into the machine and kill X to recover. Assuming that you're running an ssh server and have another machine on the same network.
You could monitor your system if the crash is predictable. RAM usage, temperatures and such. There might already be helpful log entries in the /var/log/ files. If there is you might have a terminal open running "tail -f /var/log/syslog" and another running "tail -f /var/log/dmesg", which might provide on screen insight when the system does it again. Unless it is a hardware issue.
Distribution: Cinnamon Mint 17.3 and 18 at present.
My box is a Dell Inspiron 11 3147.
...which is a laptop so hardware wise it's likely to be an overheating issue as camorri has indicated above. This is caused by dust and fluff blocking the fins of the heat exchanger, you may be able to clear this using an air can spray but if you've already decided to open the case and dig down to the CPU, remove the heatsink/heatpipe/exchanger fin assembly and give it a good clean. Clean any old silicon heat paste from the heatsink and CPU and renew it before reassembly. Clean the fan and check it spins freely as well.
A point to watch... When you remove the screws from the case, they may not all be the same length so beware! Fitting a long screw where a short one should be could cause shorts on the motherboard or damage the case when replaced and tightened.
If you copy and paste dmesg.1.gz and unpack in /home/killingthemonkey and read it with a text editor. The last few lines also. You may get lucky and find what is killing your gear also.
I went through this on my dead asus micro atx box after a brownout and had to use a live cd to access my logs on what happened. The brownout killed my cpu. I turned that box into a parts box instead of fixing it. Because after replacing the cpu. The problem moved on to the mobo.
Yhe unit was not worth fixing for me as I get free computer replacement desktops from the city.