From owner-freebsd-stable@FreeBSD.ORG Thu Jun 30 22:47:08 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DFBF16A41C for ; Thu, 30 Jun 2005 22:47:08 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from skippyii.compar.com (skippyii.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id E985943D1D for ; Thu, 30 Jun 2005 22:47:07 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM000039c69a66.cpe.net.cable.rogers.com [70.28.254.189]) by skippyii.compar.com (8.13.1/8.13.1) with ESMTP id j5UMwSnn088258; Thu, 30 Jun 2005 18:58:29 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <001201c57dc5$b3e5fa70$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: "Peter Jeremy" References: <005e01c57dc1$9ec97490$1200a8c0@gsicomp.on.ca> <20050630223253.GM91934@gsmx07.alcatel.com.au> Date: Thu, 30 Jun 2005 18:47:31 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Cc: freebsd-stable@freebsd.org Subject: Re: Problems with 5.x [ boot-loader related, NOT hardware related ] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 22:47:08 -0000 > On 2005-Jun-30 18:18:16 -0400, Matt Emmerton wrote: > >> More information required (as almost always): > >> - type and model of maxhine? > > > >It's home-made. It doesn't have a type or model. FWIW, it's ran FreeBSD > >fine since 3.2. > > Presumably you bought the motherboard. What brand is it? DFI 686IPK. A piece of crap, really, but it worked fine for -stable all the way through 3.x and 4.x. > >> - describe in detail your buildworld problems (and any other problems), > >> specifically any error messages you might get. > > > >Basically, it konks out immediately while trying to rebuild 'make' because > >of missing system headers. Probably a caveat with trying to build 5.x on a > >4.x machine but I didn't see anything in special instructions (UPDATING) or > >on the web about this. > > Can you please cut-and-paste the exact commandline you use to buildworld, > the contents of /etc/make.conf and the tail of the make output (back to > the last few command echos). I don't have the info. I'd need to reinstall 4.10 on it, cvsup to -stable and try again. Frankly, I'm not concerned why attempting to buildworld 5.x sources on a 4.x machine screws up -- I'm more interested why 5.x won't even install. The "build from source" was just a last-ditch attempt at 3am this morning. Is there anyone who actually _worked_ on the BTX and boot loader changes in 5.x willing to comment on my particular problems getting any flavour of 5.x to install on this machine? > >> Have you ruled out hardware problems? By running memtest86 for example? > >> (Yes, I know that 4.10 installs ok. That proves almost nothing.) > > > >The system has run fine for 3+ years - the hardware is fine. > > Hardware can fail from old age. Anything with moving parts (fans and > disk drives) as well as electrolytic capacitors have a finite lifetime. That doesn't explain why 4.10 was working fine on it yesterday and a few hours later 5.x doesn't If the hardware was broken, I'd be intelligent enough to realize that and wouldn't waste anyone's time here. I've been tracking -stable for 7 years and have seen my share of broken hardware to know what those problems look like, so let's just focus on the problem at hand, okay? -- Matt