Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!marge.eaglequest.com!news.tacom.army.mil!news.webspan.net!usenet From: "Jordan K. Hubbard" <jkh@FreeBSD.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Error on Boot : "Error: C:0 H:0 S:0" Date: Wed, 02 Oct 1996 18:27:52 -0700 Organization: Walnut Creek CDROM Lines: 24 Message-ID: <32531698.52BFA1D7@FreeBSD.org> References: <52oj41$3jg@thunder.mgl.ca> NNTP-Posting-Host: time.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.2-CURRENT i386) To: Matthew Stein <matt@bdd.net> Matthew Stein wrote: > > I've installed FreeBSD 2.2-960801-SNAP on a machine which previously ran > FreeBSD without error. Now that I've reinstalled, and changed the boot > drive, I'm at a loss. Me too. :-) This is apparently some rare interaction at work, and something which was introduced post- 2.1-RELEASE since it worked back then but started occurring after some changes were made to the boot blocks for 2.1.5. I've been putting a case together for the folks who made those changes and hope we can get something fixed (or at least further tested and narrowed down) for the next 2.2-SNAP. It only seems to happen with certain Packard Bell or Gateway machines, and one user furthermore reports that he fixed it in his case by going to the Gateway web site and getting a BIOS upgrade from BR0T 1.005 to BR01.010. I don't know what kind of hardware you have, but that might be one route to go, if you've got a Gateway. In the meantime, we'll try to figure out why this mystery bug appears on only certain machines. -- - Jordan Hubbard President, FreeBSD Project