CD-Rom drive won't open any more when logged into FC6
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
CD-Rom drive won't open any more when logged into FC6
Everything was working well, then I needed to install something so I tried opening my CD-ROM drive (DVD-RW if it matters) and it won't open. It opens and works before linux loads up, but I don't even get a power light once I'm in Fedora.
Last time I remember it working was when I had a different kernel version. Would this matter? Also, in KInfoCenter it does say I have a CD-ROM, labled hdf. If I navigate to /dev/ and there is indeed an hdf. mount /dev/hdf /mnt/somdirectory just hangs. "mount /mnt/cdrom" gives me:
Code:
mount: can't find /mnt/cdrom in /etc/fstab or /etc/mtab
Check that /media/cdrom is there... the command should be
# mount /dev/hdf -t iso9668 /media/cdrom
Your error is understandable, /mnt/cdrom is not in /etc/fstab nor in /etc/mtab. It isn't expected to be since it is a directory rather than a block special file.
You probably should check /etc/fstab to see that /dev/hdf is actually present.
Also check dmesg for anything relating to hdf: dmesg | grep hdf (for eg).
I tried these commands and it hung on the last one. I made the directory /mnt/cdrom.
Code:
[tnunamak@localhost ~]$ sudo mount /dev/hdf -t iso9668 /media/cdrom
Password:
mount: mount point /media/cdrom does not exist
[tnunamak@localhost ~]$ sudo mount /dev/hdf -t iso9668 /mnt/cdrom
mount: unknown filesystem type 'iso9668'
mount: maybe you meant 'iso9660'?
[tnunamak@localhost ~]$ sudo mount /dev/hdf -t iso9660 /mnt/cdrom
Anyhow - when the mount hangs, try ps from a different terminal and see what it says about the mount process. Could be in uninterruptable sleep ... sometimes a sign of a device driver working with bad hardware. (Have you checked the drive out on another system since you started having trouble?)
You should also check the syslog for messages about it - "dmesg | grep hdf" Check fstab for the line about hdf too.
I have the same motherboard - Gigabyte GA-965P-S3. Also a Core2Duo E6600. kernel 2.6.18-4-amd64 SMP. A Sony DVD-RW.
When the drive is emply, the dmesg | tail reveals stuff like
Code:
ide: failed opcode was: unknown
hda: status error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hda: ATAPI reset complete
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
I can't tell how often these errors occur. It works fine: ejects and plays stuff properly. For some reason though it likes to switch out of DMA mode once in a while.
Right now, hdparm /dev/hda returns:
Well... there is always "ide=nodma" on the kernel line in menu.lst ... also trying noacpi and noapic. This is looking at these other errors. However, I should stress that this sort of thing can also result from dud hardware. Even a new mobo can be a dud.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.