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.

I have a new clean install of 64bit current slackware on a machine which previously run 12.1 to 13.1. It had suspend to ram working quite reliable before, but now i get black screen (sometimes with nonresponding mouse cursor on it) at every second or third wake-up.

I found out that it is not a complete lockup - full access to kde desktop could be restored by hitting alt+sysrq+s followed by alt+sysrq+l several times. I wonder what is causing this? How to get it to wake up normally at once?

I am also getting the same thing with Fedora and OpenSuse. This is an issue with nvidia graphics cards. I've used both the nouveau and the nvidia drivers and have problems with both on resuming. And I had no problems about a month ago. Not sure what has happened.

I know this isn't an answer for you, but it's a problem with the GPU not reinitializing correctly from what I've read.

Ok. Then it is probably related to something that got upgraded, because i had 260.19.21 version of nvidia driver working fine in the middle of current's development circle somewhere in january. Maybe i should try newer kernel from testing too, just in case.