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.
you wouldnt have seen anything on the screen, but it would have created a file called error.txt in whatever directory you were in when you typed the command - probably your home directory if you had just opened up a terminal.
It could be that your drive has failed. You could try:
Power up, go to CMOS setup. Can you open the drive? If not then you have a hardware failure. Is the drive detected? If not then either the drive is totally kaput or you have a cable or controller problem.
If the drive is detected but won't open it could be simply a switch failure. You could open up the front and play around with it.
how do you know for sure, have you got it working on another motherboard, or under another OS/Distro, or are you just assuming because its new or because it worked before? If you have access to another computer you can fiddle around with, you might want to see if the drive will work on there.
i also changed the ide cable
did you also try connecting it to the other IDE controller? do other devices work on those controllers?
I think linspire is the cause of this
linspire is supposed to have excellent hardware support because they include proprietary drivers. I really can't see linspire being the cause of this, it looks a lot like a hardware problem, though anything's possible.
Last edited by Ynot Irucrem; 08-22-2005 at 07:49 PM.
I'm not happy with the idea that the DVD drive is hda. Did you first install the drive, then install linux or did you install the drive when Linux was already up and running? it could be that thewre is an inconsistency somewhere in your configuration files.
Using Windows as an analogy, the DVD is your drive C:.
In CMOS setup, what order are the drives listed in? What is the boot order?