[SOLVED] Screen freeze with current kernel (3.7.1)
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.
After updating to current on my laptop, sometime during or a few moments after the boot process, the screen would freeze. The hard drive was still active, and I could perform commands successfully, ghost-like, on the console (eg., I would blindly issue a command to touch a file, and later I would see that the file had been touched).
It wasn’t until I uninstalled the laptop-mode-tools SBo package (version 1.61) that the screen freeze no longer happened. The odd thing is that /etc/rc.d/rc.laptop-mode-tools was not executable, and my rc.local had a command to execute it only if it was (the bash “-x” test), but in /var/log/messages, I could see that laptop-mode-tools was doing something, so I have no idea what else was starting it. Nothing else under /etc contained the string “laptop-mode”.
Anyway, this post is just to let anyone else seeing this symptom know that laptop-mode-tools was the cause of problem for me. I didn’t bother trying to debug it further. I just removed it and was happy enough.