From owner-freebsd-current Wed Jul 1 09:38:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09359 for freebsd-current-outgoing; Wed, 1 Jul 1998 09:38:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09288 for ; Wed, 1 Jul 1998 09:38:00 -0700 (PDT) (envelope-from chrisc@vmunix.com) Received: from localhost (chrisc@localhost) by vnode.vmunix.com (8.8.8/8.8.8) with SMTP id MAA13478; Wed, 1 Jul 1998 12:41:34 -0400 (EDT) (envelope-from chrisc@vmunix.com) Date: Wed, 1 Jul 1998 12:41:34 -0400 (EDT) From: Chris Coleman X-Sender: chrisc@vnode To: Mike Smith cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: Not booting after install. In-Reply-To: <199807010652.XAA00749@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > This means that BIOS disk 0x80 is not sd0, ie. your BIOS probes your > > > SCSI controllers in a different order to FreeBSD. This is because > > > someone thought it would be better to do their own PCI enumeration > > > rather than use the BIOS. 8( > > > > > Any way of fixing this? > > The "best" way is to disable BIOS support on all the cards except for > the one that's providing your boot device, and making sure that this is > the controller probed first by FreeBSD. Wonderful, this fixed everything. I had two controllers in there trying to install boot bios. I enabled only the first one that FreeBSD probed and re-installed. Worked wonderful. Thanks. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message