From owner-freebsd-current@FreeBSD.ORG Mon Mar 3 16:04:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C94C4106566B; Mon, 3 Mar 2008 16:04:07 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [91.103.162.4]) by mx1.freebsd.org (Postfix) with ESMTP id 953B88FC28; Mon, 3 Mar 2008 16:04:07 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 98B6219E023; Mon, 3 Mar 2008 17:04:05 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTP id 51BC819E019; Mon, 3 Mar 2008 17:04:03 +0100 (CET) Message-ID: <47CC2183.3040404@quip.cz> Date: Mon, 03 Mar 2008 17:04:19 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: Miroslav Lachman <000.fbsd@quip.cz> References: <200803031552.22603.root@solink.ru> <47CBCD67.3030303@yandex.ru> <47CBE852.6000704@quip.cz> In-Reply-To: <47CBE852.6000704@quip.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: freebsd 7.0+MCP55 SATA Controler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 03 Mar 2008 16:04:07 -0000 Miroslav Lachman wrote: > Ivan Voras wrote: > >> Andrey V. Elsukov wrote: >> >> >>> This is fourth problem report related to NVIDIA SATA which i saw. >>> I have MCP55 SATA on my ASUS motherboard and it works fine on >>> 8.0-CURRENT. >> >> >> >> As a datapoint, it works fine for me also, during 7-CURRENT, and now for >> 8-CURRENT, on i386. Is somebody using amd64? > > > > I am using i386 on 6 machines and amd64 on 1 machine, all FreeBSD 7.0 > (RC2 or RELEASE) with MCP55 in Sun Fire X2100 M2 without mentioned issues. > > Miroslav Lachman Today I found that my old backup machine with nForce2 is unbootable with FreeBSD 7.0-RELEASE i386 (even from CD!) Booting hangs on line with "ad2" (HDD detection) FreeBSD 6.2 (previuously installed on HDD ad2 and upgraded by freebsd-update) worked fine. Now I am in dead point, because I can't rollback - booting with kernel.old (6.2 kernel) ends with error message. (I have not the exact message, but it is about mounting root fs rw. Root fs is mounted read only and if I tried to mount another fs I got "ufs doesn't support the new mount syscall", so I think I have 7.0 world booted with 6.2 kernel and that's the problem. Can anybody tell me, how can I rollback binary upgrade if system is in this state? (can't boot with 7.0, can't mount with 6.2 kernel) (freebsd-update was not finished, because machine is unbootable after first reboot in upgrade process) Miroslav Lachman