From owner-freebsd-questions@FreeBSD.ORG Mon May 31 09:08:51 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25D2616A4CE for ; Mon, 31 May 2004 09:08:51 -0700 (PDT) Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADF2043D48 for ; Mon, 31 May 2004 09:08:50 -0700 (PDT) (envelope-from nullentropy@lineone.net) Received: from [192.168.0.2] (orbital.gotadsl.co.uk [81.6.215.230]) by smtp.nildram.co.uk (Postfix) with ESMTP id 32846252974 for ; Mon, 31 May 2004 17:07:03 +0100 (BST) Message-ID: <40BB5823.5080008@lineone.net> Date: Mon, 31 May 2004 17:06:59 +0100 From: Robert Downes User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040526 X-Accept-Language: en, fr, en-us MIME-Version: 1.0 To: FreeBSD Questions Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 5.2.1 goes beserk on EPIA M board X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2004 16:08:51 -0000 I have no CD drive on my EPIA machine, so I plugged the 2.5" Toshiba drive into another machine to install FreeBSD 5.2.1 from a minimal install CD I burned myself. Installation ran fine on the big machine (a Pentium 4) and FreeBSD was able to boot on that machine without problem. I plugged the Toshiba drive back into my EPIA M (VIA C3 processor) machine and the boot process began as normal, until it paused at the ad0 detection stage. Then messages like the following, dozens of them, start to flood up the screen: ad0: FAILURE - WRITE_DMA status=11 error=84 LBA=4127103 I did have, yesterday, FreeBSD 5.0 running on my EPIA M successfully until I tried to buildworld using 5.2.1 sources, at which point my EPIA hard crashed and reset itself. I assumed my PSU had failed briefly, but is it possible that 5.2.1 has special problems with the EPIA board or processor? Or are these messages a sign that my EPIA board is damaged now? I'm starting to lose my mind with this new hardware. Any advice that might clear up the chaos and reduce the possible lines of investigation would be much appreciated. -- Bob London, UK echo Mail fefsensmrrjyaheeoceoq\! | tr "jefroq\!" "@obe.uk"