Lines Matching refs:you

52    kernel you're using.  When configuring the kernel, in the section 
65    Depending on what type of IDE interface you have, you may need to
89    If you want your CDROM drive to be found automatically by the
90    driver, you should make sure your IDE interface uses either the
93    be jumpered as `master'.  (If for some reason you cannot configure
94    your system in this manner, you can probably still use the driver.
96    when you boot, however.  See Documentation/ide/ide.txt for more
99 4. Boot the system.  If the drive is recognized, you should see a
104    If you do not see this, see section 5 below.
129 CDROM under the /mnt/cdrom directory.  If you want to eject the CDROM,
130 you must first dismount it with a command like
138 manner, though, and it may be a nuisance if you change CDROMs often.
140 mount CDROMs manually if that suits you better.
146 To play an audio CD, you should first unmount and remove any data
150 On a few drives, you can read digital audio directly using a program
152 this are Sony and Toshiba drives.  You will get errors if you try to
155 For supported changers, you can use the `cdchange' program (appended to
158 two arguments:  the CDROM device, and the slot number to which you wish
166 use the driver, and some possible solutions.  Note that if you are
167 experiencing problems, you should probably also review
172 In most cases, you should probably check with `dmesg' for any errors
185      or 0x1f0, you'll need to explicitly inform the driver using a
189    - If the autoprobing is not finding your drive, you can tell the
192      where your drive is installed.  Note that if you do this and you 
199      drive, but is assuming there's one there anyway because you told
200      it so.  If you actually try to do I/O to a drive defined at a
201      nonexistent or nonresponding I/O address, you'll probably get
214      Even if support is not available for your interface, you may be
223   - If you always get timeout errors, interrupts from the drive are
237     you don't have some other hardware which might be conflicting with
238     the IRQ you're using.  Also check the BIOS setup for your system;
247   - If you own a Pioneer DR-A24X, you _will_ get nasty error messages 
251     the standard Linux ATA disk drive probe. If you own one of these drives,
252     you can bypass the ATA probing which confuses these CDROM drives, by 
259   - If the system locks up when you try to access the CDROM, the most
260     likely cause is that you have a buggy IDE adapter which doesn't
276   - If you get errors from mount, it may help to check `dmesg' to see
287     If you see a dump, then the drive and driver are probably working
291   - If you see `not a block device' errors, check that the definitions
301     these are wrong, you can remake them by running the script
305     If you have a /dev/cdrom symbolic link, check that it is pointing
308     If you hear people talking of the devices `hd1a' and `hd1b', these
313     available, but you know it is (check /proc/filesystems), you
322     which could cause this.  It was fixed in 1.3.0.  If you can't
323     upgrade, you can probably work around the problem by specifying a
324     blocksize of 2048 when mounting.  (Note that you won't be able to
327     If you see this in kernels later than 1.3.0, please report it as a
334     CDR-7730 CDROM. If you experience data corruption, using "hdx=slow"