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 15D0F138334 for ; Sat, 13 Jul 2019 17:18:52 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CB343E086A; Sat, 13 Jul 2019 17:18:45 +0000 (UTC) Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 5EC3EE0824 for ; Sat, 13 Jul 2019 17:18:45 +0000 (UTC) Received: by mail-wm1-x32e.google.com with SMTP id s3so11480568wms.2 for ; Sat, 13 Jul 2019 10:18:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:in-reply-to:references:mime-version; bh=iZpzV/hUWGWdPoXLcGwXHEfl2w2HMMN7op9WTWdHg98=; b=Vox2Mw4H9rDqqyWh6uHCdJIvkimsAKPs68jmACYV80zcMOhHB8Vfqya+wMWWjY1uo3 9x2V9HtjIqhHg2WVLDQQ4n7xKj5NaKfWKORBUoYznz+2wsQiF4ayLgxte3tWQ6U8AARr 4S87VYKKQYqn4qKWqcXl8QYjNhUVkamN+7Lej1/S6cXxpMlJ8rEuGzobMpIgnkwIeLJR yfqClf2Rsz8WBQAUgEgiPLEew5pH0OkjSsKL16POCUqFyutZ7QtkPHIjUts5ej1iUvu0 3IP/G4mSnA/cYaUVgQT92+zGdnDye8B2qFNfrsnV/7+D2s98tYA2SbauM2skMEDYADAi hMoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version; bh=iZpzV/hUWGWdPoXLcGwXHEfl2w2HMMN7op9WTWdHg98=; b=I79j4+1ha1mBRFnh1rIZNaD28KhmiGtjCMOFl9fPO46PFNZngBeAB9rffj6PmcE/1n PTYvh8fDd4juAGErnY3WYbImVbNdK/ccKTC+nRZNcoW1q1EledvvitOac7UAWGNGnDNV H/g7wPo16Ji/gEZssgU7bgAqhHynGb17ZlwWbu7+d03LiqHCLKYaffvV8+bL2fT/FKyx Ftstz7vdvsYINlnpIRyD+nDH4YEjSTxukBlxxo8pF+qG/l3s/PddEGU6/VbtjmbD9KPr 98NJBYqFXQX6dMZma88RqKrBSwxqH/T+sAqcQiaJXXNSTE5UkTeAIws3vNCucrzzQJy9 NHwg== X-Gm-Message-State: APjAAAW0YEao4TNrduHf1tVMEZ1w0ATnUrQB70ZXtZEb+OI7mzB2vqlO Jirt0CGmuqFfdCHxgyexgQHdsxvp+sI= X-Google-Smtp-Source: APXvYqyPsR6IFoD4Ooeh9Ey9zOpi8NR//g0Ed6hmJoztlMjgcZ0HRLL19bt5N1HYRFFUzHjUd3MDLw== X-Received: by 2002:a1c:18d:: with SMTP id 135mr15316739wmb.171.1563038323905; Sat, 13 Jul 2019 10:18:43 -0700 (PDT) Received: from localhost.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by smtp.gmail.com with ESMTPSA id z6sm7981533wrw.2.2019.07.13.10.18.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 13 Jul 2019 10:18:42 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] AMD microcode updates - where are they?! Date: Sat, 13 Jul 2019 18:18:35 +0100 Message-ID: <5413979.80MaF9lyBd@localhost> In-Reply-To: References: 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: multipart/signed; boundary="nextPart3028826.rBCGUBk5jL"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-Archives-Salt: 5cffbb32-2e20-451c-b6be-ff67f7b6fa20 X-Archives-Hash: de3412886801f6a87506888c9b5460fa --nextPart3028826.rBCGUBk5jL Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" On Saturday, 13 July 2019 17:21:40 BST Jack wrote: > On 2019.07.12 08:18, Mick wrote: > > https://www.bleepingcomputer.com/news/hardware/amd-releases-spectre-v2-mic > > rocode-updates-for-cpus-going-back-to-2011/ > I have not yet done any further searching or digging, but that link > seems to only talk specifically about Windows updates, not generic > firmware updates. Yes, but any microcode releases are/should be CPU specific. If they're released for applying via one OS, they should be available to others too. Of course, if microcode has only been released to MoBo OEM's, then we're in the mercy of OEM commercial interests. I'm sure when asked for an update they will try to sell to us all the latest models they have recently launched. :p > I have three different AMD based PCs, and so far, I don't see anything > different from Mick. However, on two Artix linux systems, I'm still > not quite sure whether the microcode is in the initramfs or not. I > hate to admit I'm also not sure on my Gentoo box, having so far made > only minor changes to the kernel from the June stage 3 tarball, and > used genkernel to compile both kernel and initramfs. I'm working on > configuring 5.2.0, but it will take me a while to get through the > complete configuration (starting from scratch.) I'm not familiar with dracut to know what it uses as a default archiving engine and if you can run it to inspect directly the contents of an already created initramfs. I know it can output on the console what it is including in initramfs at the time of creation. Anyway, if you want to look at the initramfs contents manually, I suppose you will need to decompress your initramfs in a temporary directory to see its contents. First find what archive format has been used. file /boot/EFI/... initramfs-XXX.img will output gzip, bzip2, lzma or similar archive type. Then create a temporary directory to work in and use the corresponding compression type: mkdir ~/tmp_initramfs cd ~/tmp_initramfs zcat /boot/EFI/... initramfs-XXX.img | cpio -idmv or bzcat /boot/EFI/... initramfs-XXX.img | cpio -idmv or xv -dc < /boot/EFI/... initramfs-XXX.img | cpio -idmv Something like the above ought to do the job. > One suggestion - don't just grep for microcode, also check for > "firmware" for which I use 'dmesg | egrep -i "firmware|microcode"'. Well, 'firmware' will capture other firmware files, like graphics card, WiFi, BT, etc. rather than the CPU microcode. > And, one question - if I have linux-firmware emerged with savedconfig > use flag set, what's the best/easiest way to hunt through the actually > available firmware, to check if I might have missed something > relevant. So far, I've just searched the git repository for the > package. I suppose I could have kept a copy of the manifest from the > initial emerge (without savedconfig) but I didn't think of it at the > time. > > Jack Look under your /lib/firmware/ directory for the file you want to use, or the file dmesg complains is missing. For microcode there will be no complaining, but for other hardware there usually is something along the lines: "failed to load blah-blah.bin, file not found." The appropriate microcode file for your AMD CPUs can be deduced from the table here: https://wiki.gentoo.org/wiki/AMD_microcode and it should be stored under your: /lib/firmware/amd-ucode/ after you install linux-firmware. -- Regards, Mick --nextPart3028826.rBCGUBk5jL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEt7MNaGaS6HvTUrEz6WnU8jC95dcFAl0qEmsACgkQ6WnU8jC9 5dfZzQ//cd/n0wue9W68alKlJyr+GBZb3trLyU1oal/OdS4NXf7i42nifDX6QQg4 PSrTvhE9gv19rgbhJMJWVu1kIPG7Dh2d7vll2Co3ocC+ujB7Zn/Q/lQGRnyNGidg NwcRtvKuvLAGaMi1Ir0VgF84wHhO22VwgvzxB4GDD5icX46tYS7iAjk+NyUbvzlj 8bwu0DiRaov1xaobkqEQuXnDYmURV7zurX1Pq02stdGo++IflMXhmgbCg/461adD SjlP6iSWYkipAu8QzqDAdwdJ96pSuXLV2TSHeEMlNMafA9561GkPkWvRdge0oWG9 9+h6ZeGr2LFDzcKCpzuV+CcQD833sRU7ErOsHlfyGMv5eexCqSnvnfdPdMJ+Dmp+ 7VZWWAlDzOXk1HUSwEP5pKyEE9H34A8UkegHFE8BIabY635B8D+j7tYVYnTbvzMP nfOGilqvnNBst0ds+EbXl0OGGalQHuptElF6p+4pTzVkkK9btbkQeeicyfsIbulz 4Ha3Pg9DecGpmh16XuegEX6jagUQLn3D3LkYbWt3WoQvR+Y2MZYGldYeByrjZvJD aVf0crmdDe5Sd1JFZ0D/2lhq3y5/zmfN3tIjAZZclw9sGKwmT4kkspTzp64L4xqv kGAAn4D5s/z9jVkC7WjMIOaEdW7UtagHhEUKI8xO7RdygchOv1s= =ml8/ -----END PGP SIGNATURE----- --nextPart3028826.rBCGUBk5jL--