From owner-freebsd-hackers Fri Oct 27 13:28:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 7E83537B479; Fri, 27 Oct 2000 13:28:53 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Fri, 27 Oct 2000 14:28:46 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma003668; Fri, 27 Oct 00 14:28:36 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id OAA84731; Fri, 27 Oct 2000 14:28:36 -0600 (MDT) Date: Fri, 27 Oct 2000 14:45:10 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Robert Nordier Cc: Matt Dillon , Terry Lambert , "freebsd-stable@FreeBSD.ORG" , hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware In-Reply-To: <200010271110.NAA26088@siri.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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: Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 255 Why not edit the partition table after boot1 gets installed? Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message