From owner-freebsd-questions@FreeBSD.ORG Sat Nov 12 17:59:44 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDEC91065670 for ; Sat, 12 Nov 2011 17:59:44 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from anakin.london.02.net (anakin.london.02.net [87.194.255.134]) by mx1.freebsd.org (Postfix) with ESMTP id 7552D8FC08 for ; Sat, 12 Nov 2011 17:59:44 +0000 (UTC) Received: from muji2.config (87.194.237.233) by anakin.london.02.net (8.5.140) id 4E1D604003AD218E; Sat, 12 Nov 2011 17:59:40 +0000 Message-ID: <4EBEB40C.2060100@onetel.com> Date: Sat, 12 Nov 2011 17:59:40 +0000 From: Chris Whitehouse User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100924 Thunderbird/3.1.4 MIME-Version: 1.0 To: Chuck Bacon References: <4EBD0582.2000509@onetel.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: User Questions Subject: Re: Still stalls on xpt_config X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2011 17:59:44 -0000 On 11/11/2011 16:39, Chuck Bacon wrote: > Magnificent! Quick and easy; not using FW anyhow (& the BIOS calls it > 1394 )-: Furthermore, we've reversed the order of disks and given them > new names. Ugh. I'll get used to it. > Many Thanks, > Chuck Bacon -- crtb@cape.com > ABHOR SECRECY -- DEFEND PRIVACY Glad to hear it. I hope you won't mind that I've cc'd the list. cheers Chris > > On Fri, 11 Nov 2011, Chris Whitehouse wrote: >> On 11/11/2011 00:21, Chuck Bacon wrote: >>> Every 9.0 version I've tried has failed to boot, ending up with: >>> Still waiting after {60,..,300} seconds for xpt_config. >>> What's a body to do? I've tried disabling ACPI, going single, >>> safe mode. All on my ASUS M4A785TD-EVO mobo with some amd64 x4. >>> Any additional info I can provide? >> >> Try disabling firewire in your BIOS. If that lets you boot then >> rebuild your kernel without device sbp and re-enable firewire. >> >> Chris >