by > Hello All,
> I am looking for persons who have successfully installed ATA-2 (EIDE)
> Hard Drives of capacity > 2.1 GB.
> My brand spanking new 3.2 GB Quantum hard drive (C/H/S = 6323?,16,63)
> is too big for my BIOS to handle (4092,16,63 = 2.1GB upper limit). To
> get the machine to recognize its existence I lied and put in
> 4096/16/63 as the specs. I then booted linux using (from memory, the
> 1st number might be off here):
> linux hdc=noprobe hdc=6323,16,63
> at the Lilo prompt. (Allowing probing makes the BIOS managed portion
> of the boot process take a very long time).
> During boot up time I get the following error messages (this may not
> be be a perfect reproduction but it's very close)
> ==============
> kernel: hdc: recal_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: recal_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: read_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: read_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: recal_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: recal_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: read_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: read_intr: status=0x04 { DriveStatus Error }
> kernel: ide1: reset: success
> kernel: hdc: set_geometry_intr: status=0x51
> kernel: hdc: set_geometry_intr: status=0x04
> kernel: hdc: recal_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: recal_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: read_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: read_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: recal_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: recal_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: read_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: read_intr: status=0x04 { DriveStatus Error }
> kernel: ide1: reset: success
> kernel: hdc: set_geometry_intr: status=0x51
> kernel: hdc: set_geometry_intr: status=0x04
> kernel: end_request: I/O error dev 16:00 sector
> ===============
> Perhaps I need to let it probe first, and I will certainly try, but I
> don't really think that is the problem. I can't try again until this
> evening.
> Also: "dev 16:00" ???
> Doesn't this mean major_device 16, minor_device 00 ?
> hdc is major 22, minor 00.
> My /dev entries look like the following:
> brw-rw---- 1 root disk 3, 0 Dec 31 1969 hda
> brw-rw---- 1 root disk 22, 0 Dec 31 1969 hdc
> crw-rw-rw- 1 root sys 16, 0 Dec 31 1969 gs4500
> brw-rw---- 1 root cdrom 16, 0 Dec 31 1969 gscd
> Another result of noprobe ?
> Other possibly relevant info:
> ASUS P/I P55TP4N motherboard with BIOS ???
> Intel P120 CPU
> From boot messages:
I am using a Large Quantum Bigfoot drive (configured as IDE1
Master) without any problem. (I am running an AMD 6x686 166 with AMI
BIOS and Kernal 2.0.29) I didn't input its data into my BIOS because I'm
not booting it or usinging it through BIOS acess. On boot you will get
a few messages complaining until it is partitioned and file systemed.
After boot Fdisk /dev/hdc (Master IDE1 is C) create a new partition type
83 Linux native then use mke2fs to create the fiole system then you can
mount it. You may want to put it in your mtab to make it automount
after boot. If it is not being recognized by FDISK check cables,
jumpers (ie. master etc.) If all else fails verify the drive under dos
on a different machine with a new BIOS to handle cylinders past 1023.
My Drives last cylinder is 65535.
Hopes this helps a little
----------------------------------------------------------------------