From owner-freebsd-hackers Thu Oct 16 03:49:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA21184 for hackers-outgoing; Thu, 16 Oct 1997 03:49:04 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from ns2.yahoo.com (ns2.yahoo.com [205.216.162.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA21176 for ; Thu, 16 Oct 1997 03:48:59 -0700 (PDT) (envelope-from filo@yahoo.com) Received: (from filo@localhost) by ns2.yahoo.com (8.8.5/8.6.12) id DAA27096; Thu, 16 Oct 1997 03:48:28 -0700 (PDT) Date: Thu, 16 Oct 1997 03:48:28 -0700 (PDT) Message-Id: <199710161048.DAA27096@ns2.yahoo.com> From: David Filo To: freebsd-hackers@freebsd.org Subject: biosboot/start.S needs fix for Intel AL440LX motherboard Reply-To: filo@yahoo-inc.com Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The latest BIOS from Intel for their AL440LX board does not pass the drive number in %dl as biosboot/start.S assumes (instead %dl is set to 0). The end result is that you cannot boot from a harddrive if you're not using slices (a "Read error" occurs after the BIOS hands over control). Booting from floppy works fine and using slices with bteasy works as well. Forcing %dl to $0x80 (which is what bteasy appears to do) solves the problem for me. I assume the real solution is a bit more complex than this. I suppose this could be due to some weird BIOS setting, but I think I pretty much tried everything. This board will be popular, so would be nice to get this fixed.