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 1PfIro-0007Pp-5r for garchives@archives.gentoo.org; Tue, 18 Jan 2011 21:13:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BE718E063D for ; Tue, 18 Jan 2011 21:13:27 +0000 (UTC) Received: from mail-ew0-f53.google.com (mail-ew0-f53.google.com [209.85.215.53]) by pigeon.gentoo.org (Postfix) with ESMTP id A63CAE09AA for ; Tue, 18 Jan 2011 20:56:38 +0000 (UTC) Received: by ewy6 with SMTP id 6so44500ewy.40 for ; Tue, 18 Jan 2011 12:56:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:reply-to:to:subject:date:user-agent :references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=1UqvmAf9KuUmPwf+ZvVCaPi4gaXoarkpqxGNF4n7ErY=; b=xQBbsccmpcrvR01Xja05O/T+CQArdMQYVMOZj+dkuOFTI9pa4UTkM+5KL5po1/KPp0 aYthBLI/nDNvxhrzZn5E30HVfffPS51fDgOU/+kit1slsSO4Qc3Ycn3ejvoDOzdKY/BX mZiHbJeVhqPohLTDFVY1MkB6o/q9bbAJVBOuk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=wDzPfdU3WZePtZ7H4S1+M8n7WcCrKr/AlQRc0WDnGf5D77Ep40p4mgAcrXYeFis044 qOgpkMehgN67iDSrfuRp73elVBlh/y6kt81Kg+78Qzuc9+MKHWe+/EEblqRNPvTzpBBC 7LEQZLpPqY+b5OFbj9rmFkFxPo3A3mtgT3z+I= Received: by 10.216.145.154 with SMTP id p26mr1694758wej.11.1295384183388; Tue, 18 Jan 2011 12:56:23 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id i80sm3236212wej.28.2011.01.18.12.56.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 18 Jan 2011 12:56:15 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Microcode update AMD Date: Tue, 18 Jan 2011 20:56:11 +0000 User-Agent: KMail/1.13.5 (Linux/2.6.36-gentoo-r5; KDE/4.4.5; x86_64; ; ) References: <20110117172148.GD5748@solfire> In-Reply-To: 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 Content-Type: multipart/signed; boundary="nextPart1954170.riuXOZPfH0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201101182056.22212.michaelkintzios@gmail.com> X-Archives-Salt: X-Archives-Hash: 647be9569cedc24a7a16bd3c72289ca2 --nextPart1954170.riuXOZPfH0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Tuesday 18 January 2011 20:42:05 Paul Hartman wrote: > On Tue, Jan 18, 2011 at 12:21 PM, Mark Knecht wrot= e: > > On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman > >=20 > > wrote: > >> On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht =20 wrote: > >>> OK, I got it to load by hand: > >>>=20 > >>> 1) emerge microcode-ctl > >>>=20 > >>> which also emerges microcode-data. Unfortunately microcode-data looks > >>> to be out of date. > >>=20 > >> The ebuild for newer versions (including the latest 20101123) is in > >> portage as ~amd64 and ~x86. > >=20 > > Thanks Paul. > >=20 > > Also, it does seem to work, for Intel anyway, as a module or built > > into the kernel. I chose to build it in as I'm tired of how long lsmod > > is looking these days. >=20 > If you use the /etc/init.d/microcode_ctl runscript and have > MICROCODE_UNLOAD=3D"yes" set in /etc/conf.d/microcode_ctl (which is the > default), it will unload the module automatically after it runs, so > you shouldn't see it in lsmod anyway, and saves a few kb of memory. > But, quite honestly, 8kb of memory is probably inconsequential on a > system where microcode_ctl is being used in the first place... :) Is the /etc/microcode.dat path a bug, now that firmware is typically placed= in=20 /lib/firmware? Shall I create a symlink or raise a bug report? =2D-=20 Regards, Mick --nextPart1954170.riuXOZPfH0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEABECAAYFAk01/nYACgkQVTDTR3kpaLaKvwCeIzRf999HfTdgtvMDPqry4Hz6 Ky4Anixi0h4tLJAuW8wrDUGpVzRxnDQN =VjwW -----END PGP SIGNATURE----- --nextPart1954170.riuXOZPfH0--