DebianThis forum is for the discussion of Debian 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.
1: when glxgears is interrupted by ctl-c, the content of the window (gears) stays on desktop and only window frame goes away. When it is closed by closed button on window title bar, it is ok. fgl_glxgears looks ok.
2: As suggested by http://ubuntuforums.org/showthread.php?p=1840698 "noapic irqpoll pci=routeirq" looked ok, (and at least survival time was much longer). However, at the end I got completely frozen system (which is frozen screen saver). Also, cpufreqd is compromised, only works two frequencies, and slow response.
3: When mouse is connected through USB2 hub, which uses ehci driver, symptom is different. Average survival time is longer; when things go wrong, mouse gets lousy (cursor jumping all over the place, like too much acceleration.); and other USB ports on the hub die.