From owner-freebsd-hackers Fri Sep 14 11:33:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C07D837B406; Fri, 14 Sep 2001 11:33:27 -0700 (PDT) Received: (from rnordier@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f8EIXRf42001; Fri, 14 Sep 2001 11:33:27 -0700 (PDT) (envelope-from rnordier) From: Message-Id: <200109141833.f8EIXRf42001@freefall.freebsd.org> Subject: Re: Does boot1 still have a > 1023 cyl limit? In-Reply-To: <3BA2479A.4582C4BC@urx.com> from Kent Stewart at "Sep 14, 2001 11: 8:26 am" To: kstewart@urx.com Date: Fri, 14 Sep 2001 11:33:27 -0700 (PDT) Cc: msmith@freebsd.org, roam@ringlet.net, rnordier@freebsd.org, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kent Stewart wrote: > Mike Smith wrote: > > > > > So.. if I read you right, booting correctly for > 1024 cylinders works > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in the fbsd > > > slice? Does this mean that boot1 and boot2 should work just fine if they > > > are loaded by another kind of MBR loader (say, Grub), and they find out > > > that they are placed beyond the 1023th cylinder? > > > > This should work, yes. > > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I > had to go back to the boot1 from 4.3 before I could boot. That could be serious. Can you post a brief description of your hardware, together with the BTX register dump if possible? boot1 was changed to address some problems with certain hardware, so it is important to know if other incompatibilities have been introduced. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message