1 IDE-CD driver documentation
2 Originally by scott snyder <snyder@fnald0.fnal.gov> (19 May 1996)
3 Carrying on the torch is: Erik Andersen <andersee@debian.org>
4 New maintainers (19 Oct 1998): Jens Axboe <axboe@image.dk>
9 The ide-cd driver should work with all ATAPI ver 1.2 to ATAPI 2.6 compliant
10 CDROM drives which attach to an IDE interface. Note that some CDROM vendors
11 (including Mitsumi, Sony, Creative, Aztech, and Goldstar) have made
12 both ATAPI-compliant drives and drives which use a proprietary
13 interface. If your drive uses one of those proprietary interfaces,
14 this driver will not work with it (but one of the other CDROM drivers
15 probably will). This driver will not work with `ATAPI' drives which
16 attach to the parallel port. In addition, there is at least one drive
17 (CyCDROM CR520ie) which attaches to the IDE port but is not ATAPI;
18 this driver will not work with drives like that either (but see the
21 This driver provides the following features:
23 - Reading from data tracks, and mounting ISO 9660 filesystems.
25 - Playing audio tracks. Most of the CDROM player programs floating
26 around should work; I usually use Workman.
28 - Multisession support.
30 - On drives which support it, reading digital audio data directly
31 from audio tracks. The program cdda2wav can be used for this.
32 Note, however, that only some drives actually support this.
34 - There is now support for CDROM changers which comply with the
35 ATAPI 2.6 draft standard (such as the NEC CDR-251). This additional
36 functionality includes a function call to query which slot is the
37 currently selected slot, a function call to query which slots contain
38 CDs, etc. A sample program which demonstrates this functionality is
39 appended to the end of this file. The Sanyo 3-disc changer
40 (which does not conform to the standard) is also now supported.
41 Please note the driver refers to the first CD as slot # 0.
47 0. The ide-cd relies on the ide disk driver. See
48 <<<<<<< HEAD:Documentation/cdrom/ide-cd
49 Documentation/ide.txt for up-to-date information on the ide
51 Documentation/ide/ide.txt for up-to-date information on the ide
52 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:Documentation/cdrom/ide-cd
55 1. Make sure that the ide and ide-cd drivers are compiled into the
56 kernel you're using. When configuring the kernel, in the section
57 entitled "Floppy, IDE, and other block devices", say either `Y'
58 (which will compile the support directly into the kernel) or `M'
59 (to compile support as a module which can be loaded and unloaded)
62 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
63 Include IDE/ATAPI CDROM support
67 Use old disk-only driver on primary interface
69 Depending on what type of IDE interface you have, you may need to
70 specify additional configuration options. See
71 <<<<<<< HEAD:Documentation/cdrom/ide-cd
72 Documentation/ide.txt.
74 Documentation/ide/ide.txt.
75 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:Documentation/cdrom/ide-cd
77 2. You should also ensure that the iso9660 filesystem is either
78 compiled into the kernel or available as a loadable module. You
79 can see if a filesystem is known to the kernel by catting
82 3. The CDROM drive should be connected to the host on an IDE
83 interface. Each interface on a system is defined by an I/O port
84 address and an IRQ number, the standard assignments being
85 0x1f0 and 14 for the primary interface and 0x170 and 15 for the
86 secondary interface. Each interface can control up to two devices,
87 where each device can be a hard drive, a CDROM drive, a floppy drive,
88 or a tape drive. The two devices on an interface are called `master'
89 and `slave'; this is usually selectable via a jumper on the drive.
91 Linux names these devices as follows. The master and slave devices
92 on the primary IDE interface are called `hda' and `hdb',
93 respectively. The drives on the secondary interface are called
94 `hdc' and `hdd'. (Interfaces at other locations get other letters
95 <<<<<<< HEAD:Documentation/cdrom/ide-cd
96 in the third position; see Documentation/ide.txt.)
98 in the third position; see Documentation/ide/ide.txt.)
99 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:Documentation/cdrom/ide-cd
101 If you want your CDROM drive to be found automatically by the
102 driver, you should make sure your IDE interface uses either the
103 primary or secondary addresses mentioned above. In addition, if
104 the CDROM drive is the only device on the IDE interface, it should
105 be jumpered as `master'. (If for some reason you cannot configure
106 your system in this manner, you can probably still use the driver.
107 You may have to pass extra configuration information to the kernel
108 <<<<<<< HEAD:Documentation/cdrom/ide-cd
109 when you boot, however. See Documentation/ide.txt for more
111 when you boot, however. See Documentation/ide/ide.txt for more
112 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:Documentation/cdrom/ide-cd
115 4. Boot the system. If the drive is recognized, you should see a
116 message which looks like
118 hdb: NEC CD-ROM DRIVE:260, ATAPI CDROM drive
120 If you do not see this, see section 5 below.
122 5. You may want to create a symbolic link /dev/cdrom pointing to the
123 actual device. You can do this with the command
125 ln -s /dev/hdX /dev/cdrom
127 where X should be replaced by the letter indicating where your
130 6. You should be able to see any error messages from the driver with
137 An ISO 9660 CDROM can be mounted by putting the disc in the drive and
140 mount -t iso9660 /dev/cdrom /mnt/cdrom
142 where it is assumed that /dev/cdrom is a link pointing to the actual
143 device (as described in step 5 of the last section) and /mnt/cdrom is
144 an empty directory. You should now be able to see the contents of the
145 CDROM under the /mnt/cdrom directory. If you want to eject the CDROM,
146 you must first dismount it with a command like
150 Note that audio CDs cannot be mounted.
152 Some distributions set up /etc/fstab to always try to mount a CDROM
153 filesystem on bootup. It is not required to mount the CDROM in this
154 manner, though, and it may be a nuisance if you change CDROMs often.
155 You should feel free to remove the cdrom line from /etc/fstab and
156 mount CDROMs manually if that suits you better.
158 Multisession and photocd discs should work with no special handling.
159 The hpcdtoppm package (ftp.gwdg.de:/pub/linux/hpcdtoppm/) may be
160 useful for reading photocds.
162 To play an audio CD, you should first unmount and remove any data
163 CDROM. Any of the CDROM player programs should then work (workman,
164 workbone, cdplayer, etc.). Lacking anything else, you could use the
165 cdtester program in Documentation/cdrom/sbpcd.
167 On a few drives, you can read digital audio directly using a program
168 such as cdda2wav. The only types of drive which I've heard support
169 this are Sony and Toshiba drives. You will get errors if you try to
170 use this function on a drive which does not support it.
172 For supported changers, you can use the `cdchange' program (appended to
173 the end of this file) to switch between changer slots. Note that the
174 drive should be unmounted before attempting this. The program takes
175 two arguments: the CDROM device, and the slot number to which you wish
176 to change. If the slot number is -1, the drive is unloaded.
179 4. Compilation options
180 ----------------------
182 There are a few additional options which can be set when compiling the
183 driver. Most people should not need to mess with any of these; they
184 are listed here simply for completeness. A compilation option can be
185 enabled by adding a line of the form `#define <option> 1' to the top
186 of ide-cd.c. All these options are disabled by default.
188 VERBOSE_IDE_CD_ERRORS
189 If this is set, ATAPI error codes will be translated into textual
190 descriptions. In addition, a dump is made of the command which
191 provoked the error. This is off by default to save the memory used
192 by the (somewhat long) table of error descriptions.
195 If this is set, the code needed to deal with certain drives which do
196 not properly implement the ATAPI spec will be disabled. If you know
197 your drive implements ATAPI properly, you can turn this on to get a
198 slightly smaller kernel.
201 If this is set, the driver will never attempt to lock the door of
205 This sets the size of the buffer to be used for a CDROMREADAUDIO
206 ioctl. The default is 8.
209 This currently enables an additional ioctl which enables a user-mode
210 program to execute an arbitrary packet command. See the source for
211 details. This should be left off unless you know what you're doing.
217 This section discusses some common problems encountered when trying to
218 use the driver, and some possible solutions. Note that if you are
219 experiencing problems, you should probably also review
220 <<<<<<< HEAD:Documentation/cdrom/ide-cd
221 Documentation/ide.txt for current information about the underlying
223 Documentation/ide/ide.txt for current information about the underlying
224 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:Documentation/cdrom/ide-cd
225 IDE support code. Some of these items apply only to earlier versions
226 of the driver, but are mentioned here for completeness.
228 In most cases, you should probably check with `dmesg' for any errors
231 a. Drive is not detected during booting.
233 - Review the configuration instructions above and in
234 <<<<<<< HEAD:Documentation/cdrom/ide-cd
235 Documentation/ide.txt, and check how your hardware is
237 Documentation/ide/ide.txt, and check how your hardware is
238 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:Documentation/cdrom/ide-cd
241 - If your drive is the only device on an IDE interface, it should
242 be jumpered as master, if at all possible.
244 - If your IDE interface is not at the standard addresses of 0x170
245 or 0x1f0, you'll need to explicitly inform the driver using a
246 <<<<<<< HEAD:Documentation/cdrom/ide-cd
247 lilo option. See Documentation/ide.txt. (This feature was
249 lilo option. See Documentation/ide/ide.txt. (This feature was
250 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:Documentation/cdrom/ide-cd
251 added around kernel version 1.3.30.)
253 - If the autoprobing is not finding your drive, you can tell the
254 driver to assume that one exists by using a lilo option of the
255 form `hdX=cdrom', where X is the drive letter corresponding to
256 where your drive is installed. Note that if you do this and you
257 see a boot message like
261 this does _not_ mean that the driver has successfully detected
262 the drive; rather, it means that the driver has not detected a
263 drive, but is assuming there's one there anyway because you told
264 it so. If you actually try to do I/O to a drive defined at a
265 nonexistent or nonresponding I/O address, you'll probably get
266 errors with a status value of 0xff.
268 - Some IDE adapters require a nonstandard initialization sequence
269 before they'll function properly. (If this is the case, there
270 will often be a separate MS-DOS driver just for the controller.)
271 IDE interfaces on sound cards often fall into this category.
273 Support for some interfaces needing extra initialization is
274 provided in later 1.3.x kernels. You may need to turn on
275 additional kernel configuration options to get them to work;
276 <<<<<<< HEAD:Documentation/cdrom/ide-cd
277 see Documentation/ide.txt.
279 see Documentation/ide/ide.txt.
280 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:Documentation/cdrom/ide-cd
282 Even if support is not available for your interface, you may be
283 able to get it to work with the following procedure. First boot
284 MS-DOS and load the appropriate drivers. Then warm-boot linux
285 (i.e., without powering off). If this works, it can be automated
286 by running loadlin from the MS-DOS autoexec.
289 b. Timeout/IRQ errors.
291 - If you always get timeout errors, interrupts from the drive are
292 probably not making it to the host.
294 - IRQ problems may also be indicated by the message
295 `IRQ probe failed (<n>)' while booting. If <n> is zero, that
296 means that the system did not see an interrupt from the drive when
297 it was expecting one (on any feasible IRQ). If <n> is negative,
298 that means the system saw interrupts on multiple IRQ lines, when
299 it was expecting to receive just one from the CDROM drive.
301 - Double-check your hardware configuration to make sure that the IRQ
302 number of your IDE interface matches what the driver expects.
303 (The usual assignments are 14 for the primary (0x1f0) interface
304 and 15 for the secondary (0x170) interface.) Also be sure that
305 you don't have some other hardware which might be conflicting with
306 the IRQ you're using. Also check the BIOS setup for your system;
307 some have the ability to disable individual IRQ levels, and I've
308 had one report of a system which was shipped with IRQ 15 disabled
311 - Note that many MS-DOS CDROM drivers will still function even if
312 there are hardware problems with the interrupt setup; they
313 apparently don't use interrupts.
315 - If you own a Pioneer DR-A24X, you _will_ get nasty error messages
316 on boot such as "irq timeout: status=0x50 { DriveReady SeekComplete }"
317 The Pioneer DR-A24X CDROM drives are fairly popular these days.
318 Unfortunately, these drives seem to become very confused when we perform
319 the standard Linux ATA disk drive probe. If you own one of these drives,
320 you can bypass the ATA probing which confuses these CDROM drives, by
321 adding `append="hdX=noprobe hdX=cdrom"' to your lilo.conf file and running
322 lilo (again where X is the drive letter corresponding to where your drive
327 - If the system locks up when you try to access the CDROM, the most
328 likely cause is that you have a buggy IDE adapter which doesn't
329 properly handle simultaneous transactions on multiple interfaces.
330 The most notorious of these is the CMD640B chip. This problem can
331 be worked around by specifying the `serialize' option when
332 booting. Recent kernels should be able to detect the need for
333 this automatically in most cases, but the detection is not
334 <<<<<<< HEAD:Documentation/cdrom/ide-cd
335 foolproof. See Documentation/ide.txt for more information
337 foolproof. See Documentation/ide/ide.txt for more information
338 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:Documentation/cdrom/ide-cd
339 about the `serialize' option and the CMD640B.
341 - Note that many MS-DOS CDROM drivers will work with such buggy
342 hardware, apparently because they never attempt to overlap CDROM
343 operations with other disk activity.
346 d. Can't mount a CDROM.
348 - If you get errors from mount, it may help to check `dmesg' to see
349 if there are any more specific errors from the driver or from the
352 - Make sure there's a CDROM loaded in the drive, and that's it's an
353 ISO 9660 disc. You can't mount an audio CD.
355 - With the CDROM in the drive and unmounted, try something like
357 cat /dev/cdrom | od | more
359 If you see a dump, then the drive and driver are probably working
360 OK, and the problem is at the filesystem level (i.e., the CDROM is
361 not ISO 9660 or has errors in the filesystem structure).
363 - If you see `not a block device' errors, check that the definitions
364 of the device special files are correct. They should be as
367 brw-rw---- 1 root disk 3, 0 Nov 11 18:48 /dev/hda
368 brw-rw---- 1 root disk 3, 64 Nov 11 18:48 /dev/hdb
369 brw-rw---- 1 root disk 22, 0 Nov 11 18:48 /dev/hdc
370 brw-rw---- 1 root disk 22, 64 Nov 11 18:48 /dev/hdd
372 Some early Slackware releases had these defined incorrectly. If
373 these are wrong, you can remake them by running the script
374 scripts/MAKEDEV.ide. (You may have to make it executable
377 If you have a /dev/cdrom symbolic link, check that it is pointing
378 to the correct device file.
380 If you hear people talking of the devices `hd1a' and `hd1b', these
381 were old names for what are now called hdc and hdd. Those names
382 should be considered obsolete.
384 - If mount is complaining that the iso9660 filesystem is not
385 available, but you know it is (check /proc/filesystems), you
386 probably need a newer version of mount. Early versions would not
387 always give meaningful error messages.
390 e. Directory listings are unpredictably truncated, and `dmesg' shows
391 `buffer botch' error messages from the driver.
393 - There was a bug in the version of the driver in 1.2.x kernels
394 which could cause this. It was fixed in 1.3.0. If you can't
395 upgrade, you can probably work around the problem by specifying a
396 blocksize of 2048 when mounting. (Note that you won't be able to
397 directly execute binaries off the CDROM in that case.)
399 If you see this in kernels later than 1.3.0, please report it as a
405 - Random data corruption was occasionally observed with the Hitachi
406 CDR-7730 CDROM. If you experience data corruption, using "hdx=slow"
407 as a command line parameter may work around the problem, at the
408 expense of low system performance.
415 * cdchange.c [-v] <device> [<slot>]
417 * This loads a CDROM from a specified slot in a changer, and displays
418 * information about the changer status. The drive should be unmounted before
419 * using this program.
421 * Changer information is displayed if either the -v flag is specified
422 * or no slot was specified.
424 * Based on code originally from Gerhard Zuber <zuber@berlin.snafu.de>.
425 * Changer status information, and rewrite for the new Uniform CDROM driver
426 * interface by Erik Andersen <andersee@debian.org>.
435 #include <sys/ioctl.h>
436 #include <linux/cdrom.h>
440 main (int argc, char **argv)
444 int fd; /* file descriptor for CD-ROM device */
445 int status; /* return status for system calls */
448 int total_slots_available;
455 if (argc < 1 || argc > 3) {
456 fprintf (stderr, "usage: %s [-v] <device> [<slot>]\n",
458 fprintf (stderr, " Slots are numbered 1 -- n.\n");
462 if (strcmp (argv[0], "-v") == 0) {
471 slot = atoi (argv[1]) - 1;
474 fd = open(device, O_RDONLY | O_NONBLOCK);
476 fprintf (stderr, "%s: open failed for `%s': %s\n",
477 program, device, strerror (errno));
481 /* Check CD player status */
482 total_slots_available = ioctl (fd, CDROM_CHANGER_NSLOTS);
483 if (total_slots_available <= 1 ) {
484 fprintf (stderr, "%s: Device `%s' is not an ATAPI "
485 "compliant CD changer.\n", program, device);
490 if (slot >= total_slots_available) {
491 fprintf (stderr, "Bad slot number. "
492 "Should be 1 -- %d.\n",
493 total_slots_available);
498 slot=ioctl (fd, CDROM_SELECT_DISC, slot);
501 perror ("CDROM_SELECT_DISC ");
506 if (slot < 0 || verbose) {
508 status=ioctl (fd, CDROM_SELECT_DISC, CDSL_CURRENT);
511 perror (" CDROM_SELECT_DISC");
516 printf ("Current slot: %d\n", slot+1);
517 printf ("Total slots available: %d\n",
518 total_slots_available);
520 printf ("Drive status: ");
521 status = ioctl (fd, CDROM_DRIVE_STATUS, CDSL_CURRENT);
523 perror(" CDROM_DRIVE_STATUS");
524 } else switch(status) {
529 printf ("Tray Open.\n");
531 case CDS_DRIVE_NOT_READY:
532 printf ("Drive Not Ready.\n");
535 printf ("This Should not happen!\n");
539 for (x_slot=0; x_slot<total_slots_available; x_slot++) {
540 printf ("Slot %2d: ", x_slot+1);
541 status = ioctl (fd, CDROM_DRIVE_STATUS, x_slot);
543 perror(" CDROM_DRIVE_STATUS");
544 } else switch(status) {
546 printf ("Disc present.");
549 printf ("Empty slot.");
552 printf ("CD-ROM tray open.\n");
554 case CDS_DRIVE_NOT_READY:
555 printf ("CD-ROM drive not ready.\n");
558 printf ("No Information available.");
561 printf ("This Should not happen!\n");
564 if (slot == x_slot) {
565 status = ioctl (fd, CDROM_DISC_STATUS);
567 perror(" CDROM_DISC_STATUS");
571 printf ("\tAudio disc.\t");
575 printf ("\tData disc type %d.\t", status-CDS_DATA_1+1);
579 printf ("\tXA data disc type %d.\t", status-CDS_XA_2_1+1);
582 printf ("\tUnknown disc type 0x%x!\t", status);
586 status = ioctl (fd, CDROM_MEDIA_CHANGED, x_slot);
588 perror(" CDROM_MEDIA_CHANGED");
592 printf ("Changed.\n");
604 fprintf (stderr, "%s: close failed for `%s': %s\n",
605 program, device, strerror (errno));