From owner-freebsd-hardware@FreeBSD.ORG Fri Jun 22 01:32:53 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CE9F716A421 for ; Fri, 22 Jun 2007 01:32:53 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from auriate.fluffles.net (cust.95.160.adsl.cistron.nl [195.64.95.160]) by mx1.freebsd.org (Postfix) with ESMTP id 7EA5313C48C for ; Fri, 22 Jun 2007 01:32:53 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from 195-241-125-45.dsl.ip.tiscali.nl ([195.241.125.45] helo=[10.0.0.18]) by auriate.fluffles.net with esmtpa (Exim 4.66 (FreeBSD)) (envelope-from ) id 1I1Y0r-00014b-LV; Fri, 22 Jun 2007 03:32:37 +0200 Message-ID: <467B26BC.4070403@fluffles.net> Date: Fri, 22 Jun 2007 03:32:44 +0200 From: Fluffles User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <4676BAF0.4030703@gmail.com> <20070618180813.GA13003@eos.sc1.parodius.com> <322073cc0706181415o17ecd532i971d8bdf5ea1dafd@mail.gmail.com> <20070618221022.GA17952@eos.sc1.parodius.com> <868xadj651.fsf@dwp.des.no> In-Reply-To: <868xadj651.fsf@dwp.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, Jeremy Chadwick , Martin Turgeon , freebsd-hardware@freebsd.org Subject: Re: i386 with PAE or AMD64 on PowerEdge with 4G RAM X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2007 01:32:53 -0000 Dag-Erling Smørgrav wrote: > Jeremy Chadwick writes: > >> Like I said, I don't run 64-bit OSes because I prefer compatibility. >> Believe me, the instant you run into some quirky problem with either the >> kernel or any of its subsystems, or a third-party program (from ports or >> otherwise), the first thing you'll be told is "it works for me on i386, >> have you tried i386?" >> > > Absolute nonsense. FreeBSD is just as solid on amd64 as on i386, and > the people who do most of the kernel work in FreeBSD tend to have > up-to-date hardware (meaning Athlon64, Opteron, or Core 2). > > DES > His point was compatiblity, not stability. And he also mentioned the portstree where many ports are known to be broken for AMD64. Also, it's worth mentioning that nVidia (and probably others) have no AMD64 drivers for FreeBSD which means fallback on "nv" driver for X.org with extremely poor performance. On my 7600GT that meant the opengl performance equivalent of a sub Riva TNT card, not really impressive. And isn't it true that the cause for these missing AMD64 drivers from nVidia is some missing memory mapping issue on FreeBSD AMD64? In that sense it *is* a kernel issue. URL: http://lists.freebsd.org/pipermail/freebsd-hackers/2006-June/016995.html While it is mostly 'proprietary' software that has AMD64 issues, there are lots of ports that are known broken on AMD64 and for this reason (again: compatibility) many people who want to use AMD64 feel i386 is a safer choice. For dedicated servers AMD64 might be great, provided it runs only software known to work on AMD64. However, for more complex setups or desktops i think i386 is a much safer choice. From a user standpoint, there might only be one tier-1 platform; i386. - Veronica