From owner-freebsd-bugs Fri Mar 15 16:23:43 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA14135 for bugs-outgoing; Fri, 15 Mar 1996 16:23:43 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA14130 for ; Fri, 15 Mar 1996 16:23:40 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id QAA23687; Fri, 15 Mar 1996 16:16:37 -0800 (PST) Message-Id: <199603160016.QAA23687@ref.tfs.com> Subject: Re: FreeBSD 2.1 Bug ? To: alanh@fairlite.demon.co.uk (Alan Hourihane) Date: Fri, 15 Mar 1996 16:16:36 -0800 (PST) From: "JULIAN Elischer" Cc: joerg_wunsch@uriah.heep.sax.de, bugs@freebsd.org In-Reply-To: <199603152242.WAA00206@fairlite.demon.co.uk> from "Alan Hourihane" at Mar 15, 96 10:42:36 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > I have OS/2 Boot Manager installed with the following > > > > > > wd0 > > > sd0 > > > sd1 > > > sd2 > > > sd3 > > > > > > I have installed FreeBSD successfully onto sd2, but when rebooting > > > and OS/2 Boot Manager then loads the FreeBSD Boot Manager, it always > > > insists on loading from sd(3,a)/kernel. Which it isn't and fails to mount > > > the root partition. > > > > It's rather a BIOS bug... Bruce Evans posted a generic solution for > > the bootblocks about a week ago to freebsd-current. You should be > > able to find it in the mailing list archives, the subject was > > > > booting from sd5 when wd3 is also installed > > > > In addition, you could wire down the SCSI disk at ID 2 to be > > recognized by FreeBSD as sd3 (and thus match the BIOS' idea). See the > > LINT config file for the semantics on wired SCSI devices. > > > How can this be a BIOS bug ? Linux boots fine from sd0, OS/2 boots fine > from sd1. > > I have a 2940 with its bios enabled therefore.. > > 0x80 is wd0 > 0x81 is sd0 > 0x82 is sd1 > 0x83 is sd2 > 0x84 is sd3 > you don't say what you type for the bootblocks. I assume sd2(0,a)/kernel.... Or does it come up by default and use sd3? both are wrong.. using the new bootblock code bruce submitted the correct thing to say would be: 3:sd2(0,a)/kernel but as you don't have the new code..... the problem is that it's disk 4 from the BIOS's point of view but only the 3rd SCSI disk.. so they disagree about the minor number to use.. I've made some new bootblocks for you that SHOULD do the right thing.... If you want to try the new bootblocks, you can do the following: 1/ disable the wd drive in the bios 2/ use a bootblock on an install floppy.. specify sd2... ---boot the system--- 3/ get the new bootblock code, I can make some new bootblocks for you if you wish... 4/ use disklabel -B sd2 to put on the new bootblocks. I'll put a copy of them in ftp://ref.tfs.com:/incoming/boot1 and ftp://ref.tfs.com:/incoming/boot2 reenable the wd drive before trying the new blocks..... let me know how this works.... use the 'hd' option (which should be default) julian > > Alan. >