From owner-freebsd-current@FreeBSD.ORG Tue Mar 6 16:09:22 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 17D271065672 for ; Tue, 6 Mar 2012 16:09:22 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id C65198FC0C for ; Tue, 6 Mar 2012 16:09:21 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1S4wwy-0002aF-Rl>; Tue, 06 Mar 2012 17:09:20 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1S4wwy-0006AY-O9>; Tue, 06 Mar 2012 17:09:20 +0100 Message-ID: <4F5636AA.2060703@mail.zedat.fu-berlin.de> Date: Tue, 06 Mar 2012 17:09:14 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120224 Thunderbird/10.0.2 MIME-Version: 1.0 To: Current FreeBSD X-Enigmail-Version: 1.3.5 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig65C11C6F65C1E16A5C721EE1" X-Originating-IP: 130.133.86.198 X-Mailman-Approved-At: Tue, 06 Mar 2012 16:35:58 +0000 Subject: 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 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 16:09:22 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig65C11C6F65C1E16A5C721EE1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 --------------enig65C11C6F65C1E16A5C721EE1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBAgAGBQJPVjawAAoJEOgBcD7A/5N817MIALpNuCjCIcX0H5W212ephAvN QeIIlxvtCDiYaNuxpGI+pYSsVehNtkD/C6BUfWUBUKRnMjOR0w9KiSK8mEp/CYxi SLt2lAy3ppDkgNsu+pYsH+hIFJO9PV4aD00cttcLLJtllmaNKW358uivh74hSULB J6t0qzrF8PUSXpS+m2Wdk4ukIcak/9Q7BUwyADsgpv+HAR5wMZF70BlQB5GEJL2e NA/z+7Q3S3sL1mmC4L2LPe/Y1IQGObpQUpj61VYwfsiP9K2jTQID4vurDAHGxllD UpXmCWTl66FYW4NTW5ofbjqtceHbx4irwGEjXIB/MwRS8qpuCMuwS0xbap26hak= =1xu1 -----END PGP SIGNATURE----- --------------enig65C11C6F65C1E16A5C721EE1--