From owner-freebsd-stable Fri Oct 27 13:54:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 05F4F37B479; Fri, 27 Oct 2000 13:54:24 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9RKrpf90497; Fri, 27 Oct 2000 13:53:51 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 27 Oct 2000 13:54:41 -0700 (PDT) From: John Baldwin To: Fred Clift Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h Cc: hackers@FreeBSD.org Cc: hackers@FreeBSD.org, "freebsd-stable@FreeBSD.ORG" , Terry Lambert , Matt Dillon , Robert Nordier Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-00 Fred Clift wrote: > On Fri, 27 Oct 2000, Robert Nordier wrote: > >> >> Just doing the disklabel -w -r followed by the disklabel -B is creating >> a dangerously dedicated disk, which your BIOS apparently doesn't like. >> (See the first hex dump you did, where boot1 has ended up in the MBR.) >> >> That's why installing boot blocks is messing with the partition table, >> to answer the question you asked elsewhere. >> >> You need to dd and fdisk before the disklabel commands, which will give >> you a standard partition table (at the cost of 63 sectors of disk >> space). >> > > > So why not just put a valid partition table inside the boot1 that gets put > on sector zero? When boot1 gets dropped onto sector zero, it does hose > the partition table, but there is no reason why a valid one couln't be put > there insead of this broken one: Well, for one thing, 99% of the PC architecture assumes that the first track is reserved for the MBR so to speak, so putting boot1 in the MBR is already bogus. The reason it is bogus is to work around disk geometry pain as I mentioned in my previous e-mail to Matt. The only thing you can change is the size of the last slice, but my guess is that that won't fix the problem that the SCSI BIOS's have, but that instead the hack that we use boot1 as an MBR for (having the slice start at 0/0/1) is what is causing the BIOS to choke. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message