From owner-freebsd-current Mon Aug 16 21:53:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id A4EE814C87 for ; Mon, 16 Aug 1999 21:53:54 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id AAA45281; Tue, 17 Aug 1999 00:50:28 -0400 (EDT) Message-Id: <199908170450.AAA45281@cs.rpi.edu> To: "David E. Cross" Cc: Mike Smith , Tom Bartol , current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: yet more TP 600E fun... In-Reply-To: Message from "David E. Cross" of "Mon, 16 Aug 1999 23:56:24 EDT." <199908170356.XAA44730@cs.rpi.edu> Date: Tue, 17 Aug 1999 00:50:28 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok I just tried some other mods... the first was to hard-wire disk0 to be bios device 0x8b. no-go. The second was to patch to 'continue' if it missed a probe, and to limit the probe to the first 0x10 entries... for example: 0x00-0x0f and 0x80-0x8f. How is it that the old boot code works? What is it doing differently, is 0x8b perhaps not the "real" bios boot device unit? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message