Re: RHEL v3 to RHEL v4 SNAFUs (laus, microcode_ctl, networking)

[Arjan van de Ven <arjan infradead org>]

On Fri, 2005-03-18 at 23:43 -0600, Chris Adams wrote:
> Once upon a time, Arjan van de Ven <arjan infradead org> said:
> > and you don't actually need nor sort of want the microcode thing anyway,
> > so really nothing is lost here.
> 
> Why would you not want it 

it tries to update something the bios should have updated. In fact the
bios knows update it does, any later updates the bios doesn't know
about. So you may end up with the bios working around an issue that is
then fixed differently in the microcode you update later on, and that
could clash.


Another "fun" thing is some of the newer microcodes that could, say, add
NX support to intel cpus that didn't have it before. If you do that via
the microcode driver, the kernel doesn't know about it really, however
the cpu does. That makes things, ehm, interesting.

>
> (and if you don't want it, why is it
> included)?

good question. I wouldn't want it in.