From owner-freebsd-stable  Wed Nov 13 05:57:42 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA17780
          for stable-outgoing; Wed, 13 Nov 1996 05:57:42 -0800 (PST)
Received: from arl-img-3.compuserve.com (arl-img-3.compuserve.com [149.174.217.133])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA17772
          for <freebsd-stable@freebsd.org>; Wed, 13 Nov 1996 05:57:40 -0800 (PST)
Received: by arl-img-3.compuserve.com (8.6.10/5.950515)
	id IAA11460; Wed, 13 Nov 1996 08:56:24 -0500
Date: 13 Nov 96 08:55:14 EST
From: Berend de Boer <100120.3121@CompuServe.COM>
To: Tor Egge <Tor.Egge@idt.ntnu.no>
Cc: FreeBSD stable <freebsd-stable@freebsd.org>
Subject: Re: Follow on Atlantis board
Message-ID: <961113135513_100120.3121_EHQ76-1@CompuServe.COM>
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> When using gdb on /usr/obj/usr/src/sys/i386/boot/biosboot/boot in
> FreeBSD 3.0-current and disassembling the boot function, you'll
> see that early in the function, the boot device is placed in %edi.

Hai Tor,

The %edi was entirely correct.

What we did:

1. added a pushed/poppped %edi on get_diskinfo in bios.S.
	Result: drive was no longer destroyed

2. replaced the bios. The bios was 1.00.03.CL0. We downloaded the latest bios
from Intel which was 1.00.06.CL0. 
	Result: problem also disappeared.

Thanks everyone who took part in this discussion for their comments. I think we
can close this case.

Groetjes,

Berend.