Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
Our main reception machine at work is running Debian unstable (and has been for a couple of years). Recently it has started jammin up eveyr now and then (a couple of times a week, sometimes more). When it does we have no choice but to turn the power off without shutting down. The times and circumstances of the jams don't seem to follow a pattern. I have checked the logs and the only thing that jumps out at me is this message that constantly repeats:
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
DMA write timed out
I have asked the advice of a friend who said it is probably harmless but if I wanted I could get rid of the message I should remove the parport and parport_pc modules. However when I try to do that I am told that they are in use so cannot be removed. I have also removed them from the /etc/modules file to try to stop them being loaded on startup but they are still there.
A couple of forum posts I've looked at mentioned recompiling kernels. I have failed at every attempt to do that so far and was wondering if anyone had any other ideas.