Readme.ide HELP

Readme.ide HELP

Post by sande.. » Fri, 20 Jan 1995 22:34:12

"Here's the README.ide file from the 1.1.81 kernel"
Ok I see this everywhere answering EIDE problems, where is this file(site&dir)
and the new install disks for UMSDOS for the eide drives???


Readme.ide HELP

Post by Mark Lo » Mon, 23 Jan 1995 08:10:32

In article <> writes:

<"Here's the README.ide file from the 1.1.81 kernel"
<Ok I see this everywhere answering EIDE problems, where is this file(site&dir)

The 1.1.81 kernel is everywhere, and the README.ide is part of it.
It is also included below for your convenience.

README.ide -- Information regarding ide.c and ide-cd.c
Supported by:           -- disks, interfaces, probing
      -- cdroms, ATAPI, audio

(see description later on below for handling BIG IDE drives with >1024 cyls).

Major features of ide.c & ide-cd.c:

        - support for up to two IDE interfaces on one or two IRQs
        - support for any mix of up to four disk and/or cdrom drives
        - support for reading IDE ATAPI cdrom drives (NEC, MITSUMI, VERSA, SONY)
        - support for audio functions on FX400,NEC-260 cdrom drives (others?)
        - auto-detection of interfaces, drives, IRQs, and disk geometries
        - support for BIOSs which report "more than 16 heads" on disk drives
        - uses LBA (slightly faster) on disk drives which support it
        - support for lots of fancy (E)IDE drive functions with hdparm utility
        - optional (compile time) support for 32-bit VLB data transfers
        - support for IDE multiple (block) mode (same as hd.c)
        - support for interrupt unmasking during I/O (better than hd.c)
        - compile flag for auto detection/use of multiple mode setting from BIOS
        - improved handshaking and error detection/recovery
        - can co-exist with hd.c to control only the secondary interface

Under construction:

        - support for interface speed selection on jumperless interfaces
        - improved detection of non-standard IDE ATAPI cdrom drives

To access devices on the second interface, device entries must first be
created in /dev for them.  To create such entries, simply run the included
shell script:   MAKEDEV.ide1

ide.c automatically probes for the primary and secondary interfaces,
for the drives/geometries attached to those interfaces, and for the
IRQ numbers being used by the interfaces (normally IRQ14 & IRQ15).

The primary and secondary interfaces may share a single IRQ if necessary,
at a slight performance penalty, whether on separate cards or a single VLB card.

Drives are normally found by auto-probing and/or examining the CMOS/BIOS data.
For really weird situations, the apparent (fdisk) geometry can also be specified
on the kernel "command line" using LILO.  The format of such lines is:  

or      hdx=cdrom

where hdx can be any of {hda,hdb,hdc,hdd}, or simply hd, for the "next" drive
in sequence.  Only the first three parameters are required (cyls,heads,sects),
and wpcom is ignored for IDE drives.  For example:

        hdc=1050,32,64 hdd=cdrom

If an irq number is given, it will apply to both drives on the same interface,
either {hda,hdb} or {hdc,hdd}.  The results of successful auto-probing may
override the physical geometry/irq specified, though the "original" geometry
is retained as the "logical" geometry for partitioning purposes (fdisk).

If the auto-probing during boot time confuses a drive (ie. the drive works
with hd.c but not with ide.c), then an command line option may be specified
for each drive for which you'd like the drive to skip the hardware
probe/identification sequence.  For example:


Courtesy of Scott Snyder, the driver now supports ATAPI cdrom drives
such as the NEC-260 and the new MITSUMI triple/quad speed drives.
Such drives will be identified at boot time, as hda,hdb,hdc or hdd,
just like a harddisk.

If for some reason your cdrom drive is *not* found at boot time, you can force
the probe to look harder by supplying a kernel command line parameter
via LILO, such as:  hdc=cdrom

For example, a GW2000 system might have a harddrive on the primary
interface (/dev/hda) and an IDE cdrom drive on the secondary interface
(/dev/hdc).  To mount a CD in the cdrom drive, one would use something like:

        ln -sf /dev/hdc /dev/cdrom
        mkdir /cd
        mount /dev/cdrom /cd -t iso9660 -o ro

Please pass on any feedback on the cdrom stuff to the author & maintainer,
Scott Snyder (

The kernel is now be able to execute binaries directly off of the cdrom,
provided it is mounted with the default block size of 1024.

The hdparm.c program for controlling various IDE features is now packaged
separately.  Look for it on popular linux FTP sites.

How To Use *Big* IDE drives with Linux/DOS
All IDE drives larger than 504MB ("528Meg") use a "physical" geometry which
has more than 1024 cylinders.  This presents two problems to most systems:

        1. The INT13 interface to the BIOS only allows 10-bits for cylinder
        addresses, giving a limit of 1024cyls for programs which use it.

        2. The physical geometry fields of the disk partition table only
        allow 10-bits for cylinder addresses, giving a similar limit of 1024
        cyls for operating systems that do not use the "sector count" fields
        instead of the physical Cyl/Head/Sect (CHS) geometry fields.

 [ For the curious, the "504MB" number comes from the 1024 cyl BIOS limit,
   and the fact that IDE hardware has only four bits for head selection,
   which limits the number of "real" heads to 16 or less.  The BIOS also
   limits the number of sectors per track to 63 in most cases, thus giving:
        1024 * 16 * 63 = 1032192 sectors (512 bytes each)
   Divide the capacity in bytes (1032192 * 512) by (1024 * 1024) to get 504MB ]

Neither of these limitations affects Linux itself, as it (1) does not use the
BIOS for disk access, and it (2) is clever enough to use the "sector count"
fields of the partition table instead of the physical CHS geometry fields.

        a) Most folks use LILO to load linux.  LILO uses the INT13 interface
        to the BIOS to load the kernel at boot time.  Therefore, LILO can only
        load linux if the files it needs (usually just the kernel images) are
        located below the magic 1024 cylinder "boundary" (more on this later).

        b) Many folks also like to have bootable DOS partitions on their
        drive(s).  DOS also uses the INT13 interface to the BIOS, not only
        for booting, but also for operation after booting.  Therefore, DOS
        can normally only access partitions which are contained entirely below
        the magic 1024 cylinder "boundary".

There are at least seven commonly used schemes for kludging DOS to work
around this "limitation".  In the long term, the problem is being solved
by introduction of an alternative BIOS interface that does not have the
same limitations as the INT13 interface.  New versions of DOS are expected
to detect and use this interface in systems whose BIOS provides it.

But in the present day, alternative solutions are necessary.

The most popular solution in newer systems is to have the BIOS shift bits
between the cylinder and head number fields.  This is activated by entering
a translated logical geometry into the BIOS/CMOS setup for the drive.
Thus, if the drive has a geometry of 2100/16/63 (CHS), then the BIOS could
present a "logical" geometry of 525/64/63 by "shifting" two bits from the
cylinder number into the head number field for purposes of the partition table,
CMOS setup, and INT13 interfaces.  Linux kernels 1.1.39 and higher detect and
"handle" this translation automatically, making this a rather painless solution
for the 1024 cyls problem.  If for some reason Linux gets confused (unlikely),
then use the kernel command line parameters to pass the *logical* geometry,
as in:  hda=525,64,63

If the BIOS does not support this form of drive translation, then several
options remain, listed below in inverse order of popularity:

        - boot from a floppy disk instead of the hard drive (takes 10 seconds).
        - use a partition below the 1024 cyl boundary to hold the linux
        boot files (kernel images and /boot directory), and place the rest
        of linux anywhere else on the drive.  These files can reside in a DOS
        partition, or in a tailor-made linux boot partition.

If you cannot use drive translation, *and* your BIOS also restricts you to
entering no more than 1024 cylinders in the geometry field in the CMOS setup,
then just set it to 1024.  As of v3.5 of this driver, Linux automatically
determines the *real* number of cylinders for fdisk to use, allowing easy
access to the full disk capacity without having to fiddle around.

Regardless of what you do, all DOS partitions *must* be contained entirely
within the first 1024 logical cylinders.  For a 1Gig WD disk drive, here's
a good "half and half" partitioning scheme to start with:

        geometry = 2100/16/63
        /dev/hda1 from cyl    1 to  992         dos
        /dev/hda2 from cyl  993 to 1023         swap
        /dev/hda3 from cyl 1024 to 2100         linux

To ensure that LILO can boot linux, the boot files (kernel and /boot/*)
must reside within the first 1024 cylinders of the drive.  If your linux
root partition is *not* completely within the first 1024 cyls (quite common),
then you can use LILO to boot linux from files on your DOS partition
by doing the following after installing slackware (or whatever):

        0. Boot from the "boot floppy" created during the installation
        1. Mount your DOS partition as /dos (and stick it in /etc/fstab)
        2. Move your kernel (/vmlinuz) to /dos/vmlinuz with:  mv /vmlinuz /dos
        3. Edit /etc/lilo.conf to change /vmlinuz to /dos/vmlinuz
        4. Move /boot to /dos/boot with:  cp -a /boot /dos ; rm -r /boot
        5. Create a symlink for LILO to use with:  ln -s /dos/boot /boot
        6. Re-run LILO with:  lilo

        A danger with this approach is that whenever an MS-DOS "defragmentation"
        program is run (like Norton "speeddisk"), it may move the Linux boot
        files around, confusing LILO and making the (Linux) system unbootable.
        Be sure to keep a

read more »


1. >1024 cyl README.ide

Well. I'm having the same problems as a lot of people here.  I'm also
seeing reference to /linux-1.1.76/drivers/block/README.ide but no one has
yet mentioned where this can be found.  I'm using the site

Oh.  If this is answered in the FAQ, then ignore this, but if not...

I have a 740 HD that uses a driver instead of altering CMOS directly (at least,
that's the way it looks..CMOS says the drive is a 10 meg type 1 drive).
I'm also using Linux 2.1.0 w/ 4 megs ram.  I have a partition for dos that's
540 megs, and want to install Linux after that. (this is also my second HD)
Everything works fine until i use the Linux fdisk...which will report the

device     boot    begin     start     end      blocks    id    system

/dev/hdb1            1         1        1          0       6  Dos 16-bit>32M
[other error messages are supposed to be solved with the README.ide]

I don't get it?  why does it (basically) say i have a non-existant dos
drive?  I must have done something wrong...but can't figure out what.
When i use fdisk on my first HD (which is all dos), it reports everything
correctly.  Hopefully, there is an answer somewhere out there.



   \\ /          University of Toronto
    oo             Computer Science

2. Proof that the daemon is superior

3. where is README.ide?

4. a DIAMOND SPEEDSTAR A55 work with REDHAT 6.1.

5. README about large IDE drives

6. C Code Scrambler?


8. FYI-buffer overflow

9. *Help - README*

10. CDU55E help, i've read the READMEs!

11. README.edi Help!

12. Help: Indexes: filename length / "global" readme/footer