From owner-freebsd-current@FreeBSD.ORG Tue Aug 24 22:14:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1656116A4DA for ; Tue, 24 Aug 2004 22:14:16 +0000 (GMT) Received: from veldy.net (fuggle.veldy.net [209.98.200.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id E114F43D48 for ; Tue, 24 Aug 2004 22:14:15 +0000 (GMT) (envelope-from veldy@veldy.net) Received: from localhost (localhost [127.0.0.1]) by veldy.net (Postfix) with ESMTP id CBA02319B; Tue, 24 Aug 2004 17:14:14 -0500 (CDT) Received: from veldy.net ([127.0.0.1]) by localhost (fuggle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02344-01; Tue, 24 Aug 2004 17:14:10 -0500 (CDT) Received: from [127.0.0.1] (cascade.veldy.net [192.168.1.1]) by veldy.net (Postfix) with ESMTP id C32A7319A; Tue, 24 Aug 2004 17:14:09 -0500 (CDT) Message-ID: <412BBDB0.90903@veldy.net> Date: Tue, 24 Aug 2004 17:14:08 -0500 From: "Thomas T. Veldhouse" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <4129EE0E.7080606@veldy.net> <20040824085552.GA25548@galgenberg.net> <412B129E.9030208@DeepCore.dk> In-Reply-To: <412B129E.9030208@DeepCore.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at veldy.net cc: freebsd-current@freebsd.org Subject: Re: FREEBSD-5.3BETA hard hang during hardware probe from CD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Aug 2004 22:14:16 -0000 Søren Schmidt wrote: > Upgrade /sys/dev/ata to whats in -current, I should have fixed it there. > > -Søren > Soren, Can you please list which file(s) and what versions I should be looking for? I grabbed a copy of current as of this morning and I believe the latest updated file was from 08-22 and the problem still exists for me. Another poster mentioned that a verbose boot works and it does indeed work for me. Tom Veldhouse