Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
I believe I have seen reports of those errors being present when the DMA controller is not working 100% with linux.
IIRC, the users who got these errors reported that their machines still booted and worked fine. The error in their case seemed to be a slight compatibility issue between their particular DMA controller and linux.
Sorry for the vague answer, if you Google a bit I think you'll see some reference to what I am talking about.
Just wanted to be sure you didn't throw out your hard drive just because of those errors, since the HDD might not actually be at fault.
Unfortunately, I did have a hard drive failure over the weekend and lost a lot of data (sigh). Anyway, the drive that failed was not the drive that Linux was on. (The machine was a dual boot which I have since had to rebuild.) It was a dual boot Linux/Windows XP machine with one 10GB drive as my Linux drive and two other 10GB drives fro Windows. Would I still be seeing the same errors regardless of whether the failed drive was the Linux drive or not?
All the errors you posted referred to the "hdd" device (which I THINK is generally the slave-drive on the secondary IDE channel...I may be wrong on that).
That may very well be one of the Windows drives. I believe at bootup time that linux will poke around and see what's on the ide bus. It may very well be throwing those hdd DMA errors when it's trying to interrogate the failed Windows drive.