From owner-freebsd-mobile@FreeBSD.ORG Wed Aug 3 14:50:29 2005 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3DA616A41F for ; Wed, 3 Aug 2005 14:50:29 +0000 (GMT) (envelope-from john@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3EF743D49 for ; Wed, 3 Aug 2005 14:50:28 +0000 (GMT) (envelope-from john@jnielsen.net) Received: from localhost (ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id j73EoPsh035151; Wed, 3 Aug 2005 07:50:26 -0700 (PDT) (envelope-from john@jnielsen.net) From: John Nielsen To: freebsd-mobile@freebsd.org Date: Wed, 3 Aug 2005 10:50:00 -0400 User-Agent: KMail/1.8.1 References: <20050803075431.E40037@ramstind.gtf.ol.no> In-Reply-To: <20050803075431.E40037@ramstind.gtf.ol.no> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200508031050.01339.john@jnielsen.net> X-Virus-Scanned: ClamAV 0.85.1/1002/Wed Aug 3 03:29:36 2005 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Trond =?iso-8859-1?q?Endrest=F8l?= Subject: Re: FreeBSD 5.4-RELEASE not bootable on a Dell Latitude D510 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Aug 2005 14:50:30 -0000 On Wednesday 03 August 2005 01:56, Trond Endrest=F8l wrote: > Hi all, > > I received a Dell Latitude D510 yesterday and I wanted to boot FreeBSD > 5.4-RELEASE from the computer's DVD drive. > > However, the booting process stopped abruptly with the following > messages: > > fwohci0: EUI64 36:4f:c0:00:07:ce:d8:30 > NMI ISA b0, EISA ff > RAM parity error, likely hardware failure. I saw the same thing on the same hardware. (The RAM was fine.) Since I wa= s=20 booting into FreeBSD as a diagnostic measure and not to do an installation,= =20 I didn't pursue the matter much further. I _think_ I was able to boot from= =20 a FreeBSD 5.2.1 CD. (I don't remember if I tried 5.3 or not.) That might=20 be the easiest approach, followed by an upgrarde from source with a custom= =20 (non-firewire) kernel. If all else fails, you can build a kernel without=20 firewire on another machine, make your own CD, and boot from that. I'm not sure if a PR has been filed for this or not, or if the problem=20 persists in 6.0-BETA1. JN