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!solace!news.stealth.net!www.nntp.primenet.com!nntp.primenet.com!howland.erols.net!news1.erols.com!newsmaster@erols.com From: greggd@caddmicro.com Newsgroups: comp.unix.bsd.freebsd.misc Subject: Booting From 0:sd(1,a)/kernel - Help...please.... Date: Wed, 11 Sep 1996 14:29:14 GMT Organization: Erol's Internet Service Lines: 30 Message-ID: <3236cc78.6428131@news6.erols.com> Reply-To: greggd@caddmicro.com NNTP-Posting-Host: spg-as38s11.erols.com X-Newsreader: Forte Agent .99e/32.227 I have a P133 system from Iwill (Quick Technologies) The M-Board has an Adaptec 2940 integrated. In the SCSI Select BIOS utility, it will let me select the SCSI ID of the primary drive (BIOS 0) I have a 1GB Seagate Hawk at ID0 (Windows/Windows NT WS 4.0b) I have a 2GB Seagate Barracuda at ID1 (FreeBSD 2.2 960801-SNAP) When installing, the Barracuda was the BIOS 0 bootable drive, and sysinstall put a bootblock on this device correctly...sort of.... The only problem is, if I neglect to type "0:sd(1,a)/kernel" at the "Boot:" prompt, the system understandably panics when trying to mount / on sd(0,a). I've tried a coupla things with the bootcode in /sys/i386/boot/biosboot, but the documentation in the readmes and in the makefile are all oriented to making it easy to boot from sd0 as BIOS disk 1 (after a wd drive or two....) Nothing I've found talks about booting from sd1 as BIOS disk 0. Any suggestions? As my time to read news is rare, please email suggestions, comments, solutions, bootcode options, VISA numbers w/expiration dates (just checking to see if you were paying attention...) to greggd@caddmicro.com TIA -Gregg Discenza CADD Microsystems, Inc.