Date: Wed, 18 Nov 2015 10:31:24 -0600 From: Doug McIntyre <merlyn@geeks.org> To: freebsd-questions@freebsd.org Subject: Re: Is processor microcode advised? Message-ID: <20151118163124.GC19167@geeks.org> In-Reply-To: <2412157.pVeQKYeata@amd.asgard.uk> References: <564B3E4D.7070808@gmail.com> <CA%2BtpaK3EMAU5iN4NC6jXQtugJbxyN%2Bm2OtN5-4cyXqnpy4fLcQ@mail.gmail.com> <564C3674.8040803@netfence.it> <2412157.pVeQKYeata@amd.asgard.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 18, 2015 at 03:13:53PM +0000, Dave wrote: > On Wednesday 18 November 2015 09:27:32 Andrea Venturoli wrote: > > Supposing BIOS has not been updated (due to no availability, lazyness, > > impossibility over a remote link, fear of bricking the box, etc...) > > FWIW, I've replaced many, many motherboards over the years and as part of our standard procedure we update the BIOS firmware to the latest company approved version with the corporate boot logo baked in and I've never, ever ended up with a bricked board. ... I have. Mostly with Dell systems. Later on, there are known errata that pop up, like if you have this board, with this RAID controller, and this version of the BCM, make sure to upgrade this component to this version first, that component next, etc. etc. And of course, usually this errata always shows up *after* I've done the deed and killed the board. Dell also doesn't have a field recovery option either. I don't use Dell much any more.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151118163124.GC19167>