From owner-freebsd-i386@FreeBSD.ORG Wed Nov 7 21:50:03 2007 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4C2516A421 for ; Wed, 7 Nov 2007 21:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D2C3D13C491 for ; Wed, 7 Nov 2007 21:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id lA7Lo3AK071546 for ; Wed, 7 Nov 2007 21:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id lA7Lo376071545; Wed, 7 Nov 2007 21:50:03 GMT (envelope-from gnats) Date: Wed, 7 Nov 2007 21:50:03 GMT Message-Id: <200711072150.lA7Lo376071545@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Kees van Gemert Cc: Subject: Re: i386/113160: [install] mountroot> prompt during first boot for installation X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kees van Gemert List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2007 21:50:04 -0000 The following reply was made to PR i386/113160; it has been noted by GNATS. From: Kees van Gemert To: bug-followup@FreeBSD.org, businessgeeks@pinoy-compuworld.com Cc: Subject: Re: i386/113160: [install] mountroot> prompt during first boot for installation Date: Wed, 07 Nov 2007 21:40:26 +0100 LS, Having the same problem on an via system (via VIA VT133 + 686B with onboard Via C3 cpu) FreeBSD 6.2 -> failed FreeBSD 6.3 Beta -> failed FreeBSD 7.0 Beta2 -> failed PCBSD 1.4 -> failed FreeBSD 5.5 -> succes Tried diferent memory configurations, changed cd-rom with FreeBSD 6.2, no change. Since also 6.3 and 7.0 fail, i'm wondering if this issue is still under investigation or is it a dead issue? Thanx, Kees.