From owner-freebsd-current@FreeBSD.ORG Tue Mar 6 18:04:03 2012 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 42B4E106566B for ; Tue, 6 Mar 2012 18:04:03 +0000 (UTC) (envelope-from ohauer@FreeBSD.org) Received: from p578be941.dip0.t-ipconnect.de (p578be941.dip0.t-ipconnect.de [87.139.233.65]) by mx1.freebsd.org (Postfix) with ESMTP id 008AD8FC16 for ; Tue, 6 Mar 2012 18:04:03 +0000 (UTC) Received: from [192.168.0.100] (cde1100.uni.vrs [192.168.0.100]) (Authenticated sender: ohauer) by p578be941.dip0.t-ipconnect.de (Postfix) with ESMTPSA id E010220858; Tue, 6 Mar 2012 19:03:52 +0100 (CET) Message-ID: <4F565180.6090704@FreeBSD.org> Date: Tue, 06 Mar 2012 19:03:44 +0100 From: Olli Hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4F5636AA.2060703@mail.zedat.fu-berlin.de> In-Reply-To: <4F5636AA.2060703@mail.zedat.fu-berlin.de> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "O. Hartmann" Subject: Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2012 18:04:03 -0000 On 2012-03-06 17:09, O. Hartmann wrote: > Hello. > > Well, I run on a brand new "luxury" box the newest Intel CPU > Sandy-Brideg-E in its incarnation of the Core i7-X3930K on a decent ASUS > workstation motherboard. The box is running FreeBSD 9.0-STABLE/amd64 at > the moment. > I discovered some "problems" with the SATA/AHCI interface. Since the > peripherial hardware didn't change, except mainboard and CPU (and a lot > of more memory), I guess FreeBSD 9.0-STABLE does have some issues with > the new hardware. So I'd like to use FreeBSD 10.0-CURRENT/amd64, which I > use successfully on an oldish two core Core2Duo box. > > VirtualBox, for instance, on the FBSD 9.0 box with the new hardware, > stops working from time to time, the Windows-7 is getting stuck. The > implication, that FreeBSD 9 can not handle the new hardware is wrong at > that point, since even the VBox could have it's issues with the new 6 > core Sandy Bridge-E, but the issues with the SATA 6GB subsystems are > "real". Sometimes the system gets stuck. > > Well, I tried to switch by doing a "svn switch" in /usr/src, building a > kernel, restarting the kernel in single user mode and then trying to > build the world. At some point in /usr/src/share (I forgot were exactly, > it was somewhere with lots of locale stuff), the buildworld process > fails so I couldn't build a world. > > It wouldn't be bad if the "switch" isn't possible at the moment by > simply switching the sources, but I'm still inclined to give the new > hardware the propper new OS - hoping, that new driver will pay tribute > to new hardware ... > > > Thanks for your comments in advance, > Oliver > Maybe you can reach your update goal faster... >From your mails to current I know you already have a box running FBSD 10. My way to upgrade machines is to share / rsync /usr/src from a central machine to all others, same for /usr/obj if the architectur match. Do not forget to sync also make.conf/src.conf and runing mergemaster. If the machine is alive after the fast upgrade you can experiment with different src.conf / kernel settings.