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!feed1.news.erols.com!insync!www.nntp.primenet.com!nntp.primenet.com!ddsw1!news.mcs.net!in-news.erinet.com!bug.rahul.net!rahul.net!a2i!samba.rahul.net!rahul.net!a2i!ultra.sonic.net!news From: "Eric J. Rossin" <ejr@sonic.net> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Strange boot problem on install Date: Fri, 15 Nov 1996 08:36:28 -0800 Organization: InteliData Lines: 22 Message-ID: <328C9B93.B57@sonic.net> NNTP-Posting-Host: 208.201.235.11 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01b1Gold (Win95; I) Hi all! I helped a friend install 2.1.5R last night on a pentium system, and came across a behavior I had never seen before. We were installing from the CD, so I made a boot floppy (I later installed straight from CD, but I wanted to show him how the kernel boots, etc. I re-booted the system from floppy, got the FreeBSD boot prompt, hit return and the computer re-started! The next time I just let it time out again it re-started. So finally, at the prompt I entered "fd(0,a)kernel" (which is the default, right?), and FreeBSD started! I assume this indicates some strange hardware problem on his machine, but... well anyway, we did an install (from CD); everything went fine. Then, when I re-boot from disk, the same thing happens! I had to explicitly enter "wd(1,a)kernel" (we had installed on the second drive), and it worked. Simply hitting return, or letting it default results in a re-start of the computer. I am afraid that I didn't write down the particulars of the hardwarre, but I can call and ask him if this matters. -eric