SlackwareThis Forum is for the discussion of Slackware 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.
Slack gave me the creeps just now. All of a sudden the display went distorted until it become all blue. I thought it would recover and give a shell afterwards but no. My CPU screamed. Just like a fire alarm. I restarted my system and did e2fsck as instructed. It seemed all right at first but when i did exactly what im doing(Juk+kppp+desktop customization on KDE) it happened again. Whatever gone wrong when i havent even installed anything not even swaret. Its a 2 week old slack10 installation and this is what happened. I dont think ill be booting slakware for a while. I love my PC more than Slackware.
I have a dual boot system and is in the process of switching to Linux completely. I dont think it is related to hardware problem because it never happened to me in Windows even now. I also checked my cpu temp at boot and its in normal level. I bet some hardware compatibility issues is between my machine and slack or KDE or the Linux kernel?I need to try another distro.
Distribution: Debian, edition depends on what i run it, wheezy on main box.
Whatever you are told about -it is hardware problem.
You have biostar board with award bios.
You have overheated cpu and you graphics freezes because of that.
Get some cooling and check your bios cpu related voltage- temp-clock settings.
1: case is alarm as protection:
The siren-like sound is Biostar's CPU Savior technology at work. It is a warning indicating that the CPU cooler was not installed properly (e.g., the cooler was installed backwards or there is no solid contact between the heatsink and the processor).
Reinstall both the processor and the CPU cooler. Don't forget to apply an appropriate amount of thermal grease between the processor and the heatsink.
2: or it is award bios telling that cpu is too hot (overheated)
i think you have second option.
You have "burn baby, burn!!!" option too of course.
AS ive said, i always check my cpu temp. Coming from a tropical non air conditioned room, my cpu regular temp is at 50deg. Whenever i play graphics intensive games it rises to 53-54. When the crash happened my cpu temp is only at 52deg. And im only connecting to the internet while playing mp3. That wouldnt be a cause of overheating. It may be due to other parameters (voltages, current) but whatever it is, it only happened in slack. AS im still using my system flawlessly in windows xp.
My hardware monitor software in winxp also indicates perfect operation. Sad but it seems i would be using m$ for a while.