From owner-freebsd-questions@FreeBSD.ORG Sat Aug 8 14:52:40 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A985106566C for ; Sat, 8 Aug 2009 14:52:40 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr3.xs4all.nl (smtp-vbr3.xs4all.nl [194.109.24.23]) by mx1.freebsd.org (Postfix) with ESMTP id BBB088FC1F for ; Sat, 8 Aug 2009 14:52:39 +0000 (UTC) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr3.xs4all.nl (8.13.8/8.13.8) with ESMTP id n78Eqcjw079006 for ; Sat, 8 Aug 2009 16:52:38 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id DE0A1BA8D; Sat, 8 Aug 2009 16:52:37 +0200 (CEST) Date: Sat, 8 Aug 2009 16:52:37 +0200 From: Roland Smith To: freebsd-questions@freebsd.org Message-ID: <20090808145237.GA76086@slackbox.xs4all.nl> References: <4A7C074C.9060303@unsane.co.uk> <4d4e09680908070708x635dcd80ha96a61e9c71b0b6b@mail.gmail.com> <4d4e09680908070708i286b98a7j6f03725a848ae83c@mail.gmail.com> <20090807153027.GA39621@slackbox.xs4all.nl> <4d4e09680908070847jfed3447v4863b7637585f54@mail.gmail.com> <20090807212050.GB48236@slackbox.xs4all.nl> <4d4e09680908080453i316e1f3buc00f3d0d8477794b@mail.gmail.com> <20090808133825.GA74006@slackbox.xs4all.nl> <20090808101216.42d3813c@scorpio.seibercom.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline In-Reply-To: <20090808101216.42d3813c@scorpio.seibercom.net> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Boot failure X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Aug 2009 14:52:40 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 08, 2009 at 10:12:16AM -0400, Jerry wrote: > On Sat, 8 Aug 2009 15:38:25 +0200 > Roland Smith wrote: >=20 > > On Sat, Aug 08, 2009 at 07:53:40AM -0400, Identry wrote: > > > >> Looks like your hardware is dying/dead. > > > > > > > > Sadly, I agree. > > > > > > I'd get to the point of swapping hardware one at a time until it > > > > fixes, or until you exhaust your options. =A0Have any kind of > > > > support contract with the OEM? > > >=20 > > > I do have a support contract and I'm going to dump this right in > > > their lap. Two machines we bought from them -- pretty expensive > > > ones -- and both have had hardware failures. And they are only a > > > couple of years old. I'm not too happy with them at the moment. > >=20 > > For computers, that is already old these days. At $WORK the Dell > > computers (both desktops and servers AFAIK) that we use are ditched at > > the first problem after the warranty runs out which is after three > > years, I believe. > >=20 > > Roland >=20 > Given the concept of: "Planned (?) Obsolescence", that is probably a > wise decision. The problem is that FBSD does not always either partially > or fully support new hardware. Updating in such a scenario should > therefore be undertaken with extreme care.=20 True. Therefore I don't like getting systems from builders like Dell who focus on MS windows. I prefer specifying which parts go into my machines, because I can check for compatibility beforehand. > For example, nVidia cards > with 64 bit drivers are not supported in FBSD. Personally, I love nVidia > cards; however, this problem has caused me to put off updating my > systems temporarily. However, if this problem is not rectified soon, I > might have to consider a different OS. Considering that nVidia is > already shipping drivers for Win7, both 32 & 64 bit, the fact that they > are not supported in FBSD is rather pathetic. To be fair, nvidia requested (and were waiting for) some changes made to the FreeBSD amd64 kernel. I think these changes are now in 8-CURRENT, but I'm not sure. However, NVidia choose to create their own unified 3D support infrastructure instead of supporting the X developers with documentation and specifications. That means that nobody but NVidia can maintain their drivers. So instead of wielding the collaborative power of open source, they choose to go their own way. IMHO that is not very smart. (and yes, they doubtlessly have their reasons; NDAs with suppliers, "IP" borrowed =66rom others, whatever) I suspect they'll tire one day of doing all this work themselves. But until that day, I'll buy ATI or intel graphics hardware that _is_ supported by open-source drivers. So I'll not be left with unsupported hardware if the hardware supplier chooses to focus his attentions elswhere. Nor will I face bugs that we cannot fix because of binary-only drivers. Since I find it unacceptable to be a hostage to the whims of a hardware supplier, I will not support manufacturers who stick to closed-source drivers, and I would implore others to do the same. Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkp9kTUACgkQEnfvsMMhpyUhZwCfZA4FeYzaHm/t+/+0vorgTa2W ww4An1xgca40/ZBqXAj/ZfTNN0fbZqRG =DeIy -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV--