Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!serv.hinet.net!news.cc.nctu.edu.tw!spring.edu.tw!howland.erols.net!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: sd2/2 FreeBSD installation problem Date: 28 Sep 1996 17:44:16 GMT Organization: Private BSD site, Dresden Lines: 24 Message-ID: <52jo5g$8s@uriah.heep.sax.de> References: <51pdak$s1@ns1.win.net> <3244C4A3.ABD322C@freebsd.org> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E "Jordan K. Hubbard" <jkh@FreeBSD.org> wrote: > You cannot boot from the 3rd drive, only one of the first two. That's no longer The Only Truth. Modern SCSI hostadapters (and the AHA-2842 likely belongs to this group) support BIOS mapping for more than two drives, thus these drives can be used as boot devices as well. For the Adaptec's, this is usually configurable by their SCSIselect[tm] utility. _However_, their ability to select another drive than ID 0 as a boot drive _should not_ be used. This is meant to be a silly-DOS method for booting off another drive than 0, but due to DOS' (and other system's) constraints, they do it AFAIK by reassigning BIOS ID 0x80 to the new boot device. This conflicts with FreeBSD's expectation, so you end up with a mismatch between BIOS and FreeBSD devices (BIOS drive 0x80 == ``C:'' != FreeBSD sd0). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)