Lines Matching full:if

15 interface.  If your drive uses one of those proprietary interfaces,
69    can see if a filesystem is known to the kernel by catting
87    If you want your CDROM drive to be found automatically by the
89    primary or secondary addresses mentioned above.  In addition, if
91    be jumpered as `master`.  (If for some reason you cannot configure
97 4. Boot the system.  If the drive is recognized, you should see a
102    If you do not see this, see section 5 below.
127 CDROM under the /mnt/cdrom directory.  If you want to eject the CDROM,
136 manner, though, and it may be a nuisance if you change CDROMs often.
138 mount CDROMs manually if that suits you better.
150 this are Sony and Toshiba drives.  You will get errors if you try to
157 to change.  If the slot number is -1, the drive is unloaded.
164 use the driver, and some possible solutions.  Note that if you are
179    - If your drive is the only device on an IDE interface, it should
180      be jumpered as master, if at all possible.
182    - If your IDE interface is not at the standard addresses of 0x170
187    - If the autoprobing is not finding your drive, you can tell the
190      where your drive is installed.  Note that if you do this and you
198      it so.  If you actually try to do I/O to a drive defined at a
203      before they'll function properly.  (If this is the case, there
212      Even if support is not available for your interface, you may be
215      (i.e., without powering off).  If this works, it can be automated
221   - If you always get timeout errors, interrupts from the drive are
225     `IRQ probe failed (<n>)` while booting.  If <n> is zero, that
227     it was expecting one (on any feasible IRQ).  If <n> is negative,
241   - Note that many MS-DOS CDROM drivers will still function even if
245   - If you own a Pioneer DR-A24X, you _will_ get nasty error messages
249     the standard Linux ATA disk drive probe. If you own one of these drives,
257   - If the system locks up when you try to access the CDROM, the most
274   - If you get errors from mount, it may help to check `dmesg` to see
275     if there are any more specific errors from the driver or from the
285     If you see a dump, then the drive and driver are probably working
289   - If you see `not a block device` errors, check that the definitions
298     Some early Slackware releases had these defined incorrectly.  If
303     If you have a /dev/cdrom symbolic link, check that it is pointing
306     If you hear people talking of the devices `hd1a` and `hd1b`, these
310   - If mount is complaining that the iso9660 filesystem is not
320     which could cause this.  It was fixed in 1.3.0.  If you can't
325     If you see this in kernels later than 1.3.0, please report it as a
332     CDR-7730 CDROM. If you experience data corruption, using "hdx=slow"
349    * Changer information is displayed if either the -v flag is specified
383 	if (argc < 1 || argc > 3) {
390        if (strcmp (argv[0], "-v") == 0) {
398 	if (argc == 2)
403 	if (fd < 0) {
411 	if (total_slots_available <= 1 ) {
417 	if (slot >= 0) {
418 		if (slot >= total_slots_available) {
427 		if (slot<0) {
434 	if (slot < 0 || verbose) {
437 		if (status<0) {
450                 if (status<0) {
470 			if (status<0) {
492 		  if (slot == x_slot) {
494                   if (status<0) {
515 			if (status<0) {
531 	if (status != 0) {