From owner-freebsd-hackers  Mon Aug 26 12:23:46 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA07619
          for hackers-outgoing; Mon, 26 Aug 1996 12:23:46 -0700 (PDT)
Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA07613;
          Mon, 26 Aug 1996 12:23:39 -0700 (PDT)
Received: by gvr.win.tue.nl (8.6.13/1.53)
    id VAA09844; Mon, 26 Aug 1996 21:23:31 +0200
From: guido@gvr.win.tue.nl (Guido van Rooij)
Message-Id: <199608261923.VAA09844@gvr.win.tue.nl>
Subject: 2.1.5 install failure: booting from fd0 in stead of sd0
To: bde@freebsd.org, FreeBSD-hackers@freebsd.org (FreeBSD-hackers)
Date: Mon, 26 Aug 1996 21:23:29 +0200 (MET DST)
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I've installed 2.1.5 on a DEC Celebris XL 5133 and it fails:
The installation itsself went OK. But when booting the new system,
it tries to boot off the floppy drive. When I manually enter
sd(0,a)kernel as the device to boot from, it does boot however.
The disk is a Quantum Fireball SCSI disk hanging on a NCR controller.
(NCR SDMS V3.0 PCI scsi bios, PCI rev 2, NCRPCI 3.05.03)
So the bootblock itsself is read from the disk.
When trying to boot, it says it is using dosdev:0 biosdev: 0 unit: 0 major: 2.
WHen I manually enter sd(0,a)kernel, it tells me it is booting from
dosdev: 80 biosdev: 0 unit: 0 major: 4.

Apparently, the boot code doesn't get the correct boot device. I'm wondering
how this can happen...The Windows-NT installation that is installed in
the first partition of the drive boots fine...

The bios is a Phoenix one.

Can Anyone give me a clue?

-Guido