Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
i have a plextor 40-12-10a that has been working fine since i installed rh. now, all of a suden, the cdrom will not work. it is setting up as a hard drive. does anyone have a starting point where i can begin to troubleshoot this problem?
talkinggoat; assume u refer to cd working in W. but now not with rh? any probability u can check if that cdrom is proprietary with windows. also check
favorite http://tldp.org/HOWTO/HARDWARE-HOWTO/index cdrom for compatiblity/support/nonsupport. those will indicate if usable with linux.
penguin4; the cdrom was working fine since the original install six months ago. it isn't a proprietary issue. it is seeing it in the bios and in the bootup of linux, however, it thinks that it is a hard drive, all of a suden. it has JUST started doing this, but i don't yet know enough to have a starting point.
if i remove or reconfigure the hard drive in any physical way, it causes the os to look for it during boot. in short, it causes problems. there is some type of of software issue at work here. as i am a noob to linux, but a guru to windows, i don't know where to start searching for a problem. if anyone has a real starting point, please feel free to voice it here.
Last edited by talkinggoat; 07-07-2004 at 11:55 PM.
talkinggoat - the very first question would be: did you make any system changes, after which the CD started to misbehave? If so, what were they? Additionally, when you say the CD is being recognized as a hard drive, what exactly do you mean? What kinds of error messages are you getting, or what kinds of tasks are you attempting to perform when you encounter this obstacle? Additionally, could you post the results of running the "fdisk -l" command (that's a lower case L) as well as the contents of the fstab file (which is in the /etc directory) I'll admit at first glance, I thought your question may be about the boot sequence in your BIOS, but if you've got deep experience in Windows I'll assume that's not what you're talking about. -- J.W.
J.W.,hasnain, & talkinggoat; thanks J.W. & hasnian, that is what was refering to. the reference added to original post was cd dr labeled as for
W or better. which maybe interpreted as only W, ME, XP. maybe wrong and
will stand corrected thank you.
I'm still a little confused. If you can mount the CD successfully, then you can safely ignore any "readonly" messages, because by definition a CD-ROM is read only. Additionally, if you were to remove the CD drive itself, then of course the system would complain during bootup, because you are referencing a device in fstab that is not physically connected to the machine.
Let's return to the beginning: you indicated that your CD was working fine for several weeks, then suddenly started to misbehave. What system changes/modifications did you make immediately prior to that? I would expect that's the likely cause in this sudden change in operation.
In any event, the process for mounting a data CD (not an audio CD, which doesn't need to be mounted) is to place the CD into the drive, then mount it. Example
mount /dev/cdrom /mnt/cdrom
Please see the man pages for mount for more detail as well as for optional parameters you can set. Once the CD has been mounted, you should be able to go to the /mnt/cdrom directory and access the data. Note: depending on how the CD was burned, it's possible that a regular user account may not have Read permissions on those files. If so, you could temporarily switch to being root, copy the data from the CD into a directory in the regular user's /home directory, and then access it from there.
Hopefully this will be helpful. If not, then perhaps you could describe what data files you've got on that CD-ROM, and also exactly what kind of error messages are generated when the system "goes haywire" and crashes. From the sound of it most of what you describe seems generally OK, but obviously having the system crash when accessing the CD isn't normal. -- J.W.