^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) ============================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) Information regarding the Enhanced IDE drive
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) ============================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) The hdparm utility can be used to control various IDE features on a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) running system. It is packaged separately. Please Look for it on popular
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) linux FTP sites.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) -------------------------------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) .. important::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) BUGGY IDE CHIPSETS CAN CORRUPT DATA!!
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) PCI versions of the CMD640 and RZ1000 interfaces are now detected
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) automatically at startup when PCI BIOS support is configured.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) Linux disables the "prefetch" ("readahead") mode of the RZ1000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) to prevent data corruption possible due to hardware design flaws.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) For the CMD640, linux disables "IRQ unmasking" (hdparm -u1) on any
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) drive for which the "prefetch" mode of the CMD640 is turned on.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) If "prefetch" is disabled (hdparm -p8), then "IRQ unmasking" can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) used again.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) For the CMD640, linux disables "32bit I/O" (hdparm -c1) on any drive
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) for which the "prefetch" mode of the CMD640 is turned off.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) If "prefetch" is enabled (hdparm -p9), then "32bit I/O" can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) used again.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) The CMD640 is also used on some Vesa Local Bus (VLB) cards, and is *NOT*
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) automatically detected by Linux. For safe, reliable operation with such
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) interfaces, one *MUST* use the "cmd640.probe_vlb" kernel option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) Use of the "serialize" option is no longer necessary.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) -------------------------------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) Common pitfalls
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) ===============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) - 40-conductor IDE cables are capable of transferring data in DMA modes up to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) udma2, but no faster.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) - If possible devices should be attached to separate channels if they are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) available. Typically the disk on the first and CD-ROM on the second.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) - If you mix devices on the same cable, please consider using similar devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) in respect of the data transfer mode they support.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) - Even better try to stick to the same vendor and device type on the same
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) cable.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) This is the multiple IDE interface driver, as evolved from hd.c
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) ===============================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) It supports up to 9 IDE interfaces per default, on one or more IRQs (usually
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) 14 & 15). There can be up to two drives per interface, as per the ATA-6 spec.::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) Primary: ide0, port 0x1f0; major=3; hda is minor=0; hdb is minor=64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) Secondary: ide1, port 0x170; major=22; hdc is minor=0; hdd is minor=64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) Tertiary: ide2, port 0x1e8; major=33; hde is minor=0; hdf is minor=64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) Quaternary: ide3, port 0x168; major=34; hdg is minor=0; hdh is minor=64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) fifth.. ide4, usually PCI, probed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) sixth.. ide5, usually PCI, probed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) To access devices on interfaces > ide0, device entries please make sure that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) device files for them are present in /dev. If not, please create such
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) entries, by using /dev/MAKEDEV.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) This driver automatically probes for most IDE interfaces (including all PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) ones), for the drives/geometries attached to those interfaces, and for the IRQ
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) lines being used by the interfaces (normally 14, 15 for ide0/ide1).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) Any number of interfaces may share a single IRQ if necessary, at a slight
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) performance penalty, whether on separate cards or a single VLB card.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) The IDE driver automatically detects and handles this. However, this may
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) or may not be harmful to your hardware.. two or more cards driving the same IRQ
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) can potentially burn each other's bus driver, though in practice this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) seldom occurs. Be careful, and if in doubt, don't do it!
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) Drives are normally found by auto-probing and/or examining the CMOS/BIOS data.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) For really weird situations, the apparent (fdisk) geometry can also be specified
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) on the kernel "command line" using LILO. The format of such lines is::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) ide_core.chs=[interface_number.device_number]:cyls,heads,sects
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) or::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) ide_core.cdrom=[interface_number.device_number]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) For example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) ide_core.chs=1.0:1050,32,64 ide_core.cdrom=1.1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) The results of successful auto-probing may override the physical geometry/irq
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) specified, though the "original" geometry may be retained as the "logical"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) geometry for partitioning purposes (fdisk).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) If the auto-probing during boot time confuses a drive (ie. the drive works
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) with hd.c but not with ide.c), then an command line option may be specified
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) for each drive for which you'd like the drive to skip the hardware
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) probe/identification sequence. For example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) ide_core.noprobe=0.1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) or::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) ide_core.chs=1.0:768,16,32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) ide_core.noprobe=1.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) Note that when only one IDE device is attached to an interface, it should be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) jumpered as "single" or "master", *not* "slave". Many folks have had
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) "trouble" with cdroms because of this requirement, so the driver now probes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) for both units, though success is more likely when the drive is jumpered
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) correctly.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) Courtesy of Scott Snyder and others, the driver supports ATAPI cdrom drives
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) such as the NEC-260 and the new MITSUMI triple/quad speed drives.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) Such drives will be identified at boot time, just like a hard disk.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) If for some reason your cdrom drive is *not* found at boot time, you can force
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) the probe to look harder by supplying a kernel command line parameter
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) via LILO, such as:::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) ide_core.cdrom=1.0 /* "master" on second interface (hdc) */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) or::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) ide_core.cdrom=1.1 /* "slave" on second interface (hdd) */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) For example, a GW2000 system might have a hard drive on the primary
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) interface (/dev/hda) and an IDE cdrom drive on the secondary interface
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) (/dev/hdc). To mount a CD in the cdrom drive, one would use something like::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) ln -sf /dev/hdc /dev/cdrom
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) mkdir /mnt/cdrom
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) mount /dev/cdrom /mnt/cdrom -t iso9660 -o ro
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) If, after doing all of the above, mount doesn't work and you see
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) errors from the driver (with dmesg) complaining about `status=0xff`,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) this means that the hardware is not responding to the driver's attempts
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) to read it. One of the following is probably the problem:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) - Your hardware is broken.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) - You are using the wrong address for the device, or you have the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) drive jumpered wrong. Review the configuration instructions above.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) - Your IDE controller requires some nonstandard initialization sequence
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) before it will work properly. If this is the case, there will often
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) be a separate MS-DOS driver just for the controller. IDE interfaces
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) on sound cards usually fall into this category. Such configurations
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) can often be made to work by first booting MS-DOS, loading the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) appropriate drivers, and then warm-booting linux (without powering
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) off). This can be automated using loadlin in the MS-DOS autoexec.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) If you always get timeout errors, interrupts from the drive are probably
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) not making it to the host. Check how you have the hardware jumpered
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) and make sure it matches what the driver expects (see the configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) instructions above). If you have a PCI system, also check the BIOS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) setup; I've had one report of a system which was shipped with IRQ 15
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) disabled by the BIOS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) The kernel is able to execute binaries directly off of the cdrom,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) provided it is mounted with the default block size of 1024 (as above).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) Please pass on any feedback on any of this stuff to the maintainer,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) whose address can be found in linux/MAINTAINERS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) The IDE driver is modularized. The high level disk/CD-ROM/tape/floppy
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) drivers can always be compiled as loadable modules, the chipset drivers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) can only be compiled into the kernel, and the core code (ide.c) can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) compiled as a loadable module provided no chipset support is needed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) When using ide.c as a module in combination with kmod, add::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) alias block-major-3 ide-probe
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) to a configuration file in /etc/modprobe.d/.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) When ide.c is used as a module, you can pass command line parameters to the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) driver using the "options=" keyword to insmod, while replacing any ',' with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) ';'.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) Summary of ide driver parameters for kernel command line
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) For legacy IDE VLB host drivers (ali14xx/dtc2278/ht6560b/qd65xx/umc8672)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) you need to explicitly enable probing by using "probe" kernel parameter,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) i.e. to enable probing for ALI M14xx chipsets (ali14xx host driver) use:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) * "ali14xx.probe" boot option when ali14xx driver is built-in the kernel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) * "probe" module parameter when ali14xx driver is compiled as module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) ("modprobe ali14xx probe")
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) Also for legacy CMD640 host driver (cmd640) you need to use "probe_vlb"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) kernel paremeter to enable probing for VLB version of the chipset (PCI ones
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) are detected automatically).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) You also need to use "probe" kernel parameter for ide-4drives driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) (support for IDE generic chipset with four drives on one port).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) To enable support for IDE doublers on Amiga use "doubler" kernel parameter
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) for gayle host driver (i.e. "gayle.doubler" if the driver is built-in).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) To force ignoring cable detection (this should be needed only if you're using
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) short 40-wires cable which cannot be automatically detected - if this is not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) a case please report it as a bug instead) use "ignore_cable" kernel parameter:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) * "ide_core.ignore_cable=[interface_number]" boot option if IDE is built-in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) (i.e. "ide_core.ignore_cable=1" to force ignoring cable for "ide1")
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) * "ignore_cable=[interface_number]" module parameter (for ide_core module)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) if IDE is compiled as module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) Other kernel parameters for ide_core are:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) * "nodma=[interface_number.device_number]" to disallow DMA for a device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) * "noflush=[interface_number.device_number]" to disable flush requests
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) * "nohpa=[interface_number.device_number]" to disable Host Protected Area
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) * "noprobe=[interface_number.device_number]" to skip probing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) * "nowerr=[interface_number.device_number]" to ignore the WRERR_STAT bit
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) * "cdrom=[interface_number.device_number]" to force device as a CD-ROM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) * "chs=[interface_number.device_number]" to force device as a disk (using CHS)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) Some Terminology
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) ================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) IDE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) Integrated Drive Electronics, meaning that each drive has a built-in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) controller, which is why an "IDE interface card" is not a "controller card".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) ATA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) AT (the old IBM 286 computer) Attachment Interface, a draft American
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) National Standard for connecting hard drives to PCs. This is the official
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) name for "IDE".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) The latest standards define some enhancements, known as the ATA-6 spec,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) which grew out of vendor-specific "Enhanced IDE" (EIDE) implementations.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251) ATAPI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) ATA Packet Interface, a new protocol for controlling the drives,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) similar to SCSI protocols, created at the same time as the ATA2 standard.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254) ATAPI is currently used for controlling CDROM, TAPE and FLOPPY (ZIP or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) LS120/240) devices, removable R/W cartridges, and for high capacity hard disk
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) drives.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258) mlord@pobox.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) Wed Apr 17 22:52:44 CEST 2002 edited by Marcin Dalecki, the current
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) maintainer.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) Wed Aug 20 22:31:29 CEST 2003 updated ide boot options to current ide.c
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) comments at 2.6.0-test4 time. Maciej Soltysiak <solt@dns.toxicfilms.tv>
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags