From owner-freebsd-i386@FreeBSD.ORG Sat Dec 17 12:50:06 2005 Return-Path: X-Original-To: freebsd-i386@hub.freebsd.org Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4041916A41F for ; Sat, 17 Dec 2005 12:50:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05A2843D49 for ; Sat, 17 Dec 2005 12:50:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBHCo5Cs048584 for ; Sat, 17 Dec 2005 12:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBHCo5qJ048583; Sat, 17 Dec 2005 12:50:05 GMT (envelope-from gnats) Date: Sat, 17 Dec 2005 12:50:05 GMT Message-Id: <200512171250.jBHCo5qJ048583@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: "Bill Schmitt (SW)" Cc: Subject: Re: i386/86820: ISO Install Disk hangs after acd0: X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Bill Schmitt \(SW\)" List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 12:50:06 -0000 The following reply was made to PR i386/86820; it has been noted by GNATS. From: "Bill Schmitt (SW)" To: bug-followup@FreeBSD.org, software@schmittnet.com Cc: Subject: Re: i386/86820: ISO Install Disk hangs after acd0: Date: Sat, 17 Dec 2005 07:43:35 -0500 It's been several months, and nobody seems to have an interest in this. It's beyond my abilities to work on or debug. I've got a machine here that I cannot update. Much of what I had built before a crash cannot be rebuilt as far as I can tell because the 4.9 modules are no longer online. I think I supplied enough information to indicate that this was a problem that was introduced into the installation process at 4.10, and then added to the boot process at 5, and continues with 6. I would think that it indicates a serious issue, so I don't understand why I cannot get a response or at least a suggested workaround.