Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!sdd.hp.com!spool.mu.edu!sol.ctr.columbia.edu!xlink.net!news.belwue.de!news.uni-stuttgart.de!delos!luva!migieger From: migieger@luva.stgt.sub.org (Michael Giegerich) Subject: Re: FreeBSD 1.0 boot problem... References: <2b8mtd$5uo@nigel.msen.com> <2b9fmf$880@pdq.coe.montana.edu> Organization: private 386bsd site Date: Sun, 7 Nov 1993 19:25:41 GMT Message-ID: <CG4zB7.19E@luva.stgt.sub.org> Lines: 40 In article <2b9fmf$880@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes: >In article <2b8mtd$5uo@nigel.msen.com>, >Mark Taylor <mtaylor@cybernet.com> wrote: >>Hello- >> >>"I've just installed..." FreeBSD 1.0, > >... > >>cyl 0 0 hd 0 sect 0 dev 4 unit 0 off 0 >>File not found - didn't load 386bsd, will try 386bsd.alt >>File not found - didn't load 386bsd.alt, will try 386bsd.old >>File not found - didn't load 386bsd.old, will try boot > >Are you sure you followed all the instructions. It looks like you never >installed the kernel onto the hardrive. > >1) Boot the kc floppy >2) Insert file-system floppy and follow instructions >3) Boot the kc floppy and leave it in when it tells you to install the > file-system floppy >4) copy the kernel onto the hard-drive >... >5) Rest of instructions. I once did boot with julians bootblocks from wd0. When prompting for a kernel to boot I typed hd(1,a)/386bsd (ie. I wanted to boot from my scsi drive). I had forgotten to enable BIOS support for the scsi drive - and was rewarded with the same message Mark mentioned above... (it wasn't a problem of the kernel wich did indeed exist - but a problem of the drive wich wasn't recognized). Bye, Michael. -- ------------------------------+------------------------------ Michael Giegerich | migieger@luva.stgt.sub.org ------------------------------+------------------------------