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 EAA89138334 for ; Mon, 15 Jul 2019 04:30:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A3824E0955; Mon, 15 Jul 2019 04:30:13 +0000 (UTC) Received: from very.loosely.org (very.loosely.org [173.255.215.69]) (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 DCC3DE0936 for ; Mon, 15 Jul 2019 04:30:12 +0000 (UTC) Received: from c-67-174-233-217.hsd1.ca.comcast.net ([67.174.233.217]:40914 helo=foolinux.mooo.com) by ahiker.mooo.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92-111-1a207ebe0) (envelope-from ) id 1hmsct-0002EH-K5; Sun, 14 Jul 2019 21:30:11 -0700 Date: Sun, 14 Jul 2019 21:30:01 -0700 From: Ian Zimmerman To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: AMD microcode updates - where are they?! Message-ID: <20190715043001.n3wxrw5jieuh6ton@matica.foolinux.mooo.com> References: <8454413.yhxcbTWUVq@localhost> 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 Content-Disposition: inline In-Reply-To: <8454413.yhxcbTWUVq@localhost> User-Agent: NeoMutt/20180716 X-Loosely-ASN: 7922 X-Archives-Salt: b30c4b5f-77dd-4d12-a1ce-733bfad77699 X-Archives-Hash: affcc59be4af38a4745e9592053ec2f1 On 2019-07-13 19:06, Mick wrote: > > If linux-firmware is emerged with the savedconfig use flag, then > > only the firmware not deleted from the config file is left. > > Yes. I used to do this, but gave up after a while. I find it odd that there is apparently no central way to track which firmwares are being loaded without a debugging kernel. The relevant messages in linux/drivers/base/firmware_loader/main.c are all dev_dbg(), which as I understand does nothing on a non-debug kernel. Even the message printed when the firmware file is missing is of that type. I guess I could turn on the userspace helper, set it to some script that just logs every request and fails, and then remove the whole /lib/firmware tree, but that is a _really_ round-about way. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet and on broken lists which rewrite From, fetch the TXT record for no-use.mooo.com.