Date: Wed, 3 Aug 2005 23:55:24 +0200 From: Roland Smith <rsmith@xs4all.nl> To: Wil Hatfield - HyperConX <wil@hyperconx.com> Cc: freebsd-questions@freebsd.org Subject: Re: Making the Leap to 5.4 and 64bit Message-ID: <20050803215524.GA34136@slackbox.xs4all.nl> In-Reply-To: <NGBBKBOMKLFOJCCDHPEOOEMNLJAA.wil@hyperconx.com> References: <NGBBKBOMKLFOJCCDHPEOOEMNLJAA.wil@hyperconx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 03, 2005 at 02:22:14PM -0700, Wil Hatfield - HyperConX wrote: > First, greetings to the group and nice to meet everyone's acquaintance. >=20 > We are getting ready to make a big leap to Dual 64bit Xeon machines > (SuperMicro) and FreeBSD 5.4. We would really have like to stick with 4.11 > but from what I am gathering it certainly doesn't support the 64bit > processors. >=20 > Now on to my questions: You should subscribe to the freebsd-amd64 list. > Can anyone share any of their experiences that I may also encounter? Both 5.3 and 5.4-STABLE have been running fine on my Athlon64 uniprocessor. Hardware: Athlon64 3400+ (2.4 GHz, 400 MHz FSB) MSI Neo FSR (MSI-6702) [VIA chipset] 2x512 MB PC3200U-2533 RAM Nforce3 and 4 chipsets seem to have some problems, see the mailing list archives. Same goes for the ehci driver. > How can I make the most out of SMP and the dual 64bits? Run apps that are multi-process or multi-threaded. :-) > Any undocumented or hard to find settings that I should know about? Some mobos had problems with ACPI on 5.3. For those mobos it has to be disabled. This might be solved with 5.4. If you're transplanting a make.conf from a machine with another architecture, remove any --march options from CFLAGS and COPTFLAGS. Same goes for the 'machine' and 'cpu' lines in your kernel configuration if you copy that from a machine with another architecture. FAST_IPSEC is seems to be b0rken on amd64. Look at the open problem reports for amd64. > Are there any commonly used applications that won't run on this system? All apps that I use for common desktop use are fine. Emacs, Firefox, mutt, etc. To find a list of all the ports that are b0rken on amd64 try the following: cd /usr/ports find . -name Makefile | xargs grep -H "BROKEN.*amd64"|sed 's|/Makefile.*|= |' If a port is marked BROKEN on amd64, it could just be that it wasn't tested on it, or a previous version was broken. Try removing the "BROKEN" l= ine and see where the build fails. Sometimes the fix is trivial. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC8T1MEnfvsMMhpyURAvtBAJ4hijHTgrmWZwN/PWJ2GxH+e8ApegCfeW7W p5hd+L9Rhlub3kCbAV2Aoh8= =P+mw -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050803215524.GA34136>