From owner-freebsd-hackers Fri Jun 16 14:08:23 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA19384 for hackers-outgoing; Fri, 16 Jun 1995 14:08:23 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA19365 for ; Fri, 16 Jun 1995 14:08:20 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA12949; Fri, 16 Jun 95 15:01:28 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506162101.AA12949@cs.weber.edu> Subject: Re: HD Geometry dirty trick To: aflundi@sandia.gov (Alan F Lundin) Date: Fri, 16 Jun 95 15:01:27 MDT Cc: freebsd-hackers@freebsd.org In-Reply-To: <199506162002.OAA14999@sargon.mdl.sandia.gov> from "Alan F Lundin" at Jun 16, 95 02:02:50 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@freebsd.org Precedence: bulk > Does this mean that it's possible that every distinct > BIOS could produce a different geometry for a given disk > drive, so that there is no way to predict via an algorithm > for all machines what the BIOS geometry should be? Bummer! Yes. Generally, it's on a per controller ROM revision basis, and is not specific to internal machine BIOS. It gets the general name of "BIOS" because the POST routines on the card point the INT 13 interface to their own ROMs, replacing/chaining the default BIOS. And there's no way to ask... there's a way to figure it out that mostly works, but which can run into LCF problems. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.