From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 3CE89138334 for ; Sat, 13 Jul 2019 17:42:36 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EB3B9E0866; Sat, 13 Jul 2019 17:42:29 +0000 (UTC) Received: from mail-qk1-f193.google.com (mail-qk1-f193.google.com [209.85.222.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 870EBE0857 for ; Sat, 13 Jul 2019 17:42:29 +0000 (UTC) Received: by mail-qk1-f193.google.com with SMTP id a27so8811198qkk.5 for ; Sat, 13 Jul 2019 10:42:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:in-reply-to:message-id :mime-version:content-disposition:content-transfer-encoding; bh=mDp7wP17ojOdrY8GNtWNfhjJOwmxbI6bR+pzjx4SpB0=; b=K1WRgWpqaXFihv3+fJIjuv0bUtUeo7CBkrBYbN+19CAKIUJw4Dfgqo8zEVIuxcBeLE yUPmrrtCj8DAkPzfZV3Qb16DkMTCzKcq2l4syI139VngooQsyQ5VCl4YCHEran+dnzC1 WVkoJpscw2eC//wAwnlSkmMvyeVVal5Iaph8Buc4QVKAjgQzhp6htItr4EFOgLN3laaB UANg2QDgDYFijU5TSn6c3IVDGE4JrWiSPDHcVJHD1jsejwNWXJs4fJwciDPZjPrhor3f t8lFDbMs9ZTK4PSFV++7BfJ2icXEhQT8R08N3IYash4gJ5tj2sJchdSCUB9OQ98h4JsU biFQ== X-Gm-Message-State: APjAAAUVfLlqJobq4wq09n3GMhP/n53xOK8rn/Wb7K7DpYkjAC9TttpX dby7SQn6MpEeZJCvZppyqVHbw+NcdOTfcA== X-Google-Smtp-Source: APXvYqxyi3SDqM3X7Cff/2o5g5lGYKaUM8ki8sgbI9FDjaB/QWOLe9VNRlOeMkjAoNj8VPKV9BDodQ== X-Received: by 2002:a37:311:: with SMTP id 17mr10026730qkd.466.1563039748588; Sat, 13 Jul 2019 10:42:28 -0700 (PDT) Received: from ffortso4 ([2601:188:180:4f46:1ec1:deff:fe62:b72f]) by smtp.gmail.com with ESMTPSA id m10sm5269650qka.43.2019.07.13.10.42.28 for (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Sat, 13 Jul 2019 10:42:28 -0700 (PDT) Date: Sat, 13 Jul 2019 13:42:27 -0400 From: Jack Subject: Re: [gentoo-user] AMD microcode updates - where are they?! To: gentoo-user@lists.gentoo.org In-Reply-To: <5413979.80MaF9lyBd@localhost> (from michaelkintzios@gmail.com on Sat Jul 13 13:18:35 2019) X-Mailer: Balsa 2.5.6-220-gaae4051b9 Message-Id: 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: cfc03f27-d4bf-4a59-9ef8-18c38e4a9c85 X-Archives-Hash: 07c975ab6fbdaeef3c67cc279ccc28dc On 2019.07.13 13:18, Mick wrote: > On Saturday, 13 July 2019 17:21:40 BST Jack wrote: > > On 2019.07.12 08:18, Mick wrote: [snip....] >> And, one question - if I have linux-firmware emerged with =20 >> savedconfig use flag set, what's the best/easiest way to hunt =20 >> through the actually available firmware, to check if I might have =20 >> missed something relevant. So far, I've just searched the git =20 >> repository for the package. I suppose I could have kept a copy of =20 >> the manifest from the initial emerge (without savedconfig) but I =20 >> didn't think of it at the time. >=20 > Look under your /lib/firmware/ directory for the file you want to =20 > use, or the file dmesg complains is missing. For microcode there =20 > will be no complaining, but for other hardware there usually is =20 > something along the lines: "failed to load blah-blah.bin, file not =20 > found." If linux-firmware is emerged with the savedconfig use flag, then only =20 the firmware not deleted from the config file is left. I did find a =20 few extras based on the "failed to load..." messages after my initial =20 overzealous trimming of that config file. My current concern is indeed =20 with the microcode, about which no complaint. Looking at the link =20 below shows me I am missing the files for my 17h family Ryzen CPU. It =20 will be a bit before I can reboot to see if it does load them once I =20 re-emerge linux-firmware to get them. I'll update again once I've done that. Jack=