From owner-freebsd-hackers Mon Oct 30 16: 7:10 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 0272437B4CF; Mon, 30 Oct 2000 16:06:58 -0800 (PST) Received: by gatekeeper.veriohosting.com; Mon, 30 Oct 2000 17:06:57 -0700 (MST) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma008986; Mon, 30 Oct 00 17:06:53 -0700 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 RAA57180; Mon, 30 Oct 2000 17:06:53 -0700 (MST) Date: Mon, 30 Oct 2000 17:23:44 -0700 (MST) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Doug White Cc: Paul Saab , Mike Smith , freebsd-stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware In-Reply-To: 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 I've messed with these a lot and I'm pretty sure that the bios is trying to be 'compatible' with the geometry information it finds on the disk, Theoretically, if you set up a disk with one brand X disk controller, you'll get a different fake CHS mapping than you would with a brand Y controller. So, say you set up a machine and fdisk/label all your disks, then your controller dies, you go to the store and find that no identical one is available, you buy another one because you're uh, under pressure to get the machine working. With older controllers, things may not work right if the geometry was different than expected on the disk. So, theoretically a controller could read the geometry it finds there and then use whatever it finds as the right mapping. I think where the motherboard you mention gets hosed is when it tries to read the geometry and finds the bogus boot1 stuff there. Shrug. For me, I didn't even need 2 disks to make it fail -- single disk, and you cant even boot a floppy (or the disk) when it finds a partition table. I'll definitely switch to non-dangerous installs if/when the patch that was posted gets put in. In fact, I'll probably start using it anyway :) Fred > The Adaptec BIOS is doing something really fugly when it doesn't find > proper partition tables on the disks. > > It does it if ANY of the disks are done 'dangerously dedicated.' > > The easy solution: always put proper partitions on your disks. > The hard solution: figure out what nastiness Adaptec is doing and slap > their hand. -- 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