From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PeveC-0003xp-UN for garchives@archives.gentoo.org; Mon, 17 Jan 2011 20:25:53 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 15EC1E0458 for ; Mon, 17 Jan 2011 20:25:51 +0000 (UTC) Received: from mail-ey0-f181.google.com (mail-ey0-f181.google.com [209.85.215.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 2F708E085B for ; Mon, 17 Jan 2011 20:13:54 +0000 (UTC) Received: by eyh6 with SMTP id 6so3306744eyh.40 for ; Mon, 17 Jan 2011 12:13:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=cmiw/yacHdVoYvf16FW19ZjagiFQ/OARgMJA+NoxMcY=; b=n84qEcSVEmQ2Ma5V+qo983L/LMjk2rq8VWNDsve4xKbsD7gChE4uRg1+UWI1cypf5Y a91Zw9my9Tek8xsb0f47gKLQdFb9BiB339EzBAWWkPdJIqC3z6bvAS9PfTFSXXrqor29 nwnMQiF3+DrdfyIrHcdIubakejSRK781rsyu0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=hEHo7h5oLuLaKFIukQlvojCwMu9xGzrsSj6vG4YWiZFvopHvl1y+1uVEl7QGov9LdO KIPNk07q805x7WgXjKSvgX3TiLQhJgG2YYYFl24xhLuydQqAYximSbT7g9xxvXSactgv Ixg8oXyPlpMxVDEgZckSEILKiurPEo7OZIRCQ= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.14.127.137 with SMTP id d9mr3766310eei.2.1295295234271; Mon, 17 Jan 2011 12:13:54 -0800 (PST) Received: by 10.14.37.141 with HTTP; Mon, 17 Jan 2011 12:13:54 -0800 (PST) Received: by 10.14.37.141 with HTTP; Mon, 17 Jan 2011 12:13:54 -0800 (PST) In-Reply-To: <20110117191904.GM5748@solfire> References: <20110117172148.GD5748@solfire> <4d3493c4.0297df0a.7fb2.ffffc8c0@mx.google.com> <20110117191904.GM5748@solfire> Date: Mon, 17 Jan 2011 15:13:54 -0500 Message-ID: Subject: Re: [gentoo-user] Microcode update AMD From: Jason Weisberger To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=90e6ba5bb8fb516a4e049a106cae X-Archives-Salt: 11d7c38f-8181-4c78-a3f5-adb4b20a1743 X-Archives-Hash: 45bb0c7aa87e49199f38d57ba82d8dae --90e6ba5bb8fb516a4e049a106cae Content-Type: text/plain; charset=ISO-8859-1 As he said in the previous message, there are almost never changelogs for microcode updates. I do, however, have to disagree with *never* disabling microcode updates. If I recall properly, the AMD Phenom II 720 was able to be unlocked to 4 cores via a misconfiguration that enabled it with ACC. AMD later corrected this issue with a microcode update. True, some motherboards worked around that fix a different way, but if you had a first gen board with ACC support you *had* to have the old microcode for it to work. The update killed your free core :) On Jan 17, 2011 3:06 PM, wrote: > Volker Armin Hemmann [11-01-17 20:16]: >> On Monday 17 January 2011 18:21:48 meino.cramer@gmx.de wrote: >> > Hi, >> > >> > I have two questions: >> > >> > 1) Do I have to enable microcode updates in the BIOS of my Crosshair >> > IV Formula to activate microcodes push in the CPU by the module >> > "microcode" ? (AMD Phenom X6 1090T) >> > >> >> you ALWAYS have to activate that! This way the bios updates the microcode with >> the latest version it is carrying around. Not activating that option is >> really, really stupid. For many reasons. It is also (almost) completely >> unrelated to that blob. >> >> That blob is for the OS so you can upload an even more recent version of >> microcode. In case your bios sucks. For example. >> >> > 2) Does anyone know, what these microcodes do? They are fixes for... >> > ...what? >> >> the CPU. All CPUs use microcode. For decades. Google, or go straight to >> wikipedia. >> http://en.wikipedia.org/wiki/Microcode >> > > Cool down. I know for waht microcodes are good for. > > My question means: What specific bugs/features of my CPU get fixed, > when I use the microcde included in the recent microcode update??? > > > > --90e6ba5bb8fb516a4e049a106cae Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

As he said in the previous message, there are almost never changelogs fo= r microcode updates.

I do, however, have to disagree with *never* disabling microcode updates= .=A0 If I recall properly, the AMD Phenom II 720 was able to be unlocked to= 4 cores via a misconfiguration that enabled it with ACC.=A0 AMD later corr= ected this issue with a microcode update.=A0 True, some motherboards worked= around that fix a different way, but if you had a first gen board with ACC= support you *had* to have the old microcode for it to work.=A0 The update = killed your free core :)

On Jan 17, 2011 3:06 PM, <meino.cramer@gmx.de> wrote:
> Volker Armin Hemmann <volkerarmin@googlemail.com> [11-01-17 20:16]:
>> On Monday 17 January 2011 18:21:48 meino.cramer@gmx.de wrote:
>> > Hi,
>> >= ;
>> > I have two questions:
>> >
>> >= ; 1) Do I have to enable microcode updates in the BIOS of my Crosshair
>> > IV Formula to activate microcodes push in the CPU by the = module
>> > "microcode" ? (AMD Phenom X6 1090T)>> >
>>
>> you ALWAYS have to activate that!= This way the bios updates the microcode with
>> the latest version it is carrying around. Not activating that opti= on is
>> really, really stupid. For many reasons. It is also (alm= ost) completely
>> unrelated to that blob.
>>
>&g= t; That blob is for the OS so you can upload an even more recent version of=
>> microcode. In case your bios sucks. For example.
>>
&= gt;> > 2) Does anyone know, what these microcodes do? They are fixes= for...
>> > ...what?
>>
>> the CPU. All= CPUs use microcode. For decades. Google, or go straight to
>> wikipedia.
>> http://en.wikipedia.org/wiki/Microcode
>>
> > Cool down. I know for waht microcodes are good for.
>
> = My question means: What specific bugs/features of my CPU get fixed,
> when I use the microcde included in the recent microcode update???
= >
>
>
>
--90e6ba5bb8fb516a4e049a106cae--