Date: Tue, 06 Mar 2012 17:09:14 +0100 From: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de> To: Current FreeBSD <freebsd-current@freebsd.org> Subject: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64? Message-ID: <4F5636AA.2060703@mail.zedat.fu-berlin.de>
next in thread | raw e-mail | index | archive | help
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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F5636AA.2060703>