Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 19 of 19
Ok do you know which device your cdrom drive is? It is not /dev/hdc. if you cd /proc/ide, in there it will have all your available ide devices....
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux Engineer
    Join Date
    Jan 2003
    Location
    Lebanon, pa
    Posts
    994

    Ok do you know which device your cdrom drive is? It is not /dev/hdc. if you cd /proc/ide, in there it will have all your available ide devices.

  2. #12
    Just Joined!
    Join Date
    Apr 2003
    Posts
    7
    Code:
    [root@RH9-ltop root]# cd /proc/ide
    [root@RH9-ltop ide]# ls
    drivers  hda  hdc  ide0  ide1  piix
    hda and hdc are symlinks and ide0 and ide1 are directories and piix is an empy document
    My cd rom does spin up when I try and mount it.

  3. #13
    Linux Engineer
    Join Date
    Jan 2003
    Location
    Lebanon, pa
    Posts
    994
    Can you paste output from
    Code:
    ls -al /dev/hdc

  4. #14
    Just Joined!
    Join Date
    Apr 2003
    Posts
    7
    Code:
    [root@RH9-ltop root]# ls -al /dev/hdc
    brw-rw----    1 root     disk      22,   0 Jan 30 02:24 /dev/hdc
    [root@RH9-ltop root]#

  5. #15
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    After you try and mount /dev/hdc, check /var/log/messages if any errors have been put there from the kernel.

  6. #16
    Just Joined!
    Join Date
    Apr 2003
    Posts
    7
    Code:
    Apr  9 10:18:23 RH9-ltop kernel: udf: registering filesystem
    Apr  9 10:18:23 RH9-ltop kernel: ide-floppy driver 0.99.newide
    Apr  9 10:18:24 RH9-ltop kernel: hdc: ATAPI 24X CD-ROM drive, 128kB Cache, DMA
    Apr  9 10:18:24 RH9-ltop kernel: Uniform CD-ROM driver Revision: 3.12
    Apr  9 10:18:34 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:18:34 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:18:34 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:18:34 RH9-ltop kernel: hdc: status error: error=0x00
    Apr  9 10:18:34 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:18:34 RH9-ltop kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error }
    Apr  9 10:18:34 RH9-ltop kernel: hdc: command error: error=0x51
    Apr  9 10:18:34 RH9-ltop kernel: end_request: I/O error, dev 16:00 (hdc), sector 1323860
    Apr  9 10:18:44 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:18:44 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:18:44 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:18:44 RH9-ltop kernel: hdc: status error: error=0x00
    Apr  9 10:18:44 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:18:54 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:18:54 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:18:54 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:18:54 RH9-ltop kernel: hdc: status error: error=0x04Aborted Command 
    Apr  9 10:18:54 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:19:04 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:19:04 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:19:04 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:19:04 RH9-ltop kernel: hdc: status error: error=0x04Aborted Command 
    Apr  9 10:19:04 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:19:14 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:19:14 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:19:14 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:19:14 RH9-ltop kernel: hdc: status error: error=0x04Aborted Command 
    Apr  9 10:19:14 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:19:24 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:19:24 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:19:24 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:19:24 RH9-ltop kernel: hdc: status error: error=0x04Aborted Command 
    Apr  9 10:19:24 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:19:34 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:19:34 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:19:34 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:19:34 RH9-ltop kernel: hdc: status error: error=0x04Aborted Command 
    Apr  9 10:19:34 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:19:44 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:19:44 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:19:44 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:19:44 RH9-ltop kernel: hdc: status error: error=0x04Aborted Command 
    Apr  9 10:19:44 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:19:54 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:19:54 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:19:54 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:19:54 RH9-ltop kernel: hdc: status error: error=0x04Aborted Command 
    Apr  9 10:19:54 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:20:04 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:20:04 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:20:04 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:20:04 RH9-ltop kernel: hdc: status error: error=0x04Aborted Command 
    Apr  9 10:20:04 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:20:14 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:20:14 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:20:14 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:20:14 RH9-ltop kernel: hdc: status error: error=0x04Aborted Command 
    Apr  9 10:20:14 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:20:24 RH9-ltop kernel: hdc: DMA interrupt recovery
    Apr  9 10:20:24 RH9-ltop kernel: hdc: lost interrupt
    Apr  9 10:20:24 RH9-ltop kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    Apr  9 10:20:24 RH9-ltop kernel: hdc: status error: error=0x04Aborted Command 
    Apr  9 10:20:24 RH9-ltop kernel: hdc: drive not ready for command
    Apr  9 10:35:48 RH9-ltop syslogd 1.4.1: restart.
    at the point it shows restart, that was due to me rebooting becuase the system hung.

  7. #17
    Linux Engineer
    Join Date
    Jan 2003
    Location
    Lebanon, pa
    Posts
    994
    I looked up some of those errors and it seems to effect random cd drives on 2.4.20. Some users have installed prerelease of 2.4.21 and it fixed. You could also try using scsi emulation on the cd drive. In your grub or lilo config, you can add the option hdc=scsi to enable scsi emulation on the cd drive.

  8. #18
    Linux Engineer
    Join Date
    Jan 2003
    Location
    Lebanon, pa
    Posts
    994
    http://groups.google.com/groups?hl=e...8%26oe%3DUTF-8

    That link might be of some use to you.

  9. #19
    Just Joined!
    Join Date
    Apr 2003
    Posts
    7
    Thanks for all the help so far.
    I tried SCSI emultation and that didn't make a difference. As for updating the kernel, this will be a new experience for me. I am currently using the 2.4.20-9, just used the red hat update utility yesterday to install it. I was hoping that this would fix the cd issue but it did not.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •