Driver for ATA/IDE disk interface and ATAPI CD-ROM interface
Fsys.eide [general_options] [fsys fsys_options...] [eide eide_options...]
If specified, the general_options must precede any fsys or eide options:
The fsys_options control the driver's interface to Fsys. If specified, they must follow the fsys keyword:
The value of num is the sum of all the buffers required for units that use sectors larger than 512 bytes. To obtain the buffer required for a unit, you must use the following formula:
buf = (2*(sector_size / 512))
The value that should be used for num will be the sum of the results for all units.
Some ISA motherboards have problems when on-board DMA and bus-mastering DMA occur concurrently. To avoid those problems, Fsys drivers which use DMA perform I/O concurrently only if the -d option is specified to either or both drivers. In general, you shouldn't use -d on an ISA machine if the floppy is going to be used at the same time as the SCSI hard disk. This option may be used safely on MCA and EISA machines.
By default, the driver assigns names as follows:
type | String equivalent | Default name |
---|---|---|
0 | direct-access (e.g. hard disk) | hd |
1 | sequential-access (e.g. tape) | tp |
4 | WORM | wo |
5 | CD-ROM | cd |
7 | optical | mo |
You can specify the type using either the number or its string equivalent.
To have the driver ignore a type of device, specify an empty setting. For example, to ignore hard disks, specify -n 0.
The eide_options control the driver's interface to the EIDE controller. If you've installed multiple controllers, you can repeat these options for each controller. Remember, however, to specify the eide keyword before each controller's set of options.
Fsys.eide is the driver for IDE (Integrated Drive Electronics) EIDE (Enhanced IDE) ATA (AT Attachment) hard disks and ATAPI (ATA Packet Interface) CD-ROM interfaces.
If | Then use |
---|---|
you have an ATAPI device (e.g. CD-ROM) | Fsys.eide |
you have a removable hard drive | Fsys.eide |
you have only a hard drive but no shortage of memory | Fsys.eide |
you are low on memory, and have only a hard drive with LBA enabled | Fsys.ata |
you are low on memory, and have only a hard drive without LBA enabled | Fsys.ide |
you are booting off the drive and your BIOS doesn't support LBA | Fsys.ide or Fsys.ata -L |
you are booting off the drive and the BIOS is set for LBA | Fsys.ata |
you are booting off the drive and the BIOS is set for CHS, and the drive supports LBA | Fsys.ide or Fsys.ata -L |
Note: If you are installing multiple OSs on the drive, make sure all OSs use a compatible mode. For example, if your drive is >=528Mb and DOS will also be installed on the drive, the driver should be configured to use LBA. |
Fsys.eide autodetects interfaces at address 0x1f0, interrupt 14 and address 0x170 interrupt 15 by default. If you have an interface at a different address/interrupt specify them to the driver.
Fsys.eide will use LBA (Logical Block Addressing) modes if the drive supports them.
If the -l option is specified, LBA is not used and the device is programmed to Cylinder-Head-Sector (CHS) mode. If the -e option is specified, enhanced PIO modes are used.
Support an IDE controller, list all connected devices:
Fsys.eide &
Support an IDE controller at hex address 170, interrupt 15 and don't display list of connected devices. Register direct access devices (e.g. hard disks) as /dev/eide#:
Fsys.eide -q fsys -n0=eide eide -a170 -i15 &
Fsys.eide closes its standard input, standard output and standard error immediately after completing its initializations. Error messages may be produced during the initialization phase and will be written to standard error.
Fsys.eide will cause Fsys to adopt various block special devices under /dev. These devices will normally be named hdn, where n is the physical unit number of the device. The base portion of this filename (hd) may be overridden by the -n option.
Fsys.eide will terminate only if an error occurs during startup, or if it has successfully forked itself upon startup because it had not been initially started in the background.
Don't use slay to shut down a filesystem driver! If you do, new drivers may not be able to load properly and Fsys itself may experience internal errors.
If you need to shut down a filesystem driver, follow the steps in the "Driver shutdown" section in the documentation for Fsys.