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 2E8FB138330 for ; Fri, 12 Jan 2018 19:06:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 30BC2E0885; Fri, 12 Jan 2018 19:06:44 +0000 (UTC) Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 A70E2E0858 for ; Fri, 12 Jan 2018 19:06:43 +0000 (UTC) Received: by mail-pf0-x231.google.com with SMTP id m26so5064809pfj.11 for ; Fri, 12 Jan 2018 11:06:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=iddgXXjLcI+WXNDTpfIA9zStw8bRppbNdvMiPt2jFz8=; b=eAueC8yxd7NpyiBK9goNDOOisc+AybjuMms1476H7YS45x1UTQjnbovh8j/aH/Bp/D VTCZl/0IUrnbZ9uuLG344HIGiJaccuVPLh47ZABuWBkGJDGm5k+95aHwCJEpqZZMBwp9 azVxgku6dlODmUwkTu3LJgpiKgoAjcNVD44IU5TCyM0ZQ0LdEl7AhYEWTrvgWgYSwugR Cpr7vQQimtDzmFNFLI3gRTQ1HHzrAPfJshAQASlnWT9JgPEtIqwg/tAN2WcaK3tkAcCp 5aef8hchjDIJO1I6SjzoYvulsIL/HbJZ+b89g5oe5vE2zSnI3XplSzVDoW39V3u3h7wS qcRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=iddgXXjLcI+WXNDTpfIA9zStw8bRppbNdvMiPt2jFz8=; b=qJHZzP5EOBepd4+L/sYXicQ0FskrNAO+HaUA4LcxVMSroCxcA01miQndxtLMsOUrBp BcroidG2HxPFmoFL4s36rfAYlkb4N3f+pb+84Oihq1wx+dYO9BLeG5vzpKgQBFkAJsGk enS/WmVWpGtxBokGd+G6ntJg2d2mS6WN627f4MHrBqYdN3F6jALH7oPluOc3u1a62IU+ 6YNPGlO0PXB9GDmviLTE2tIkjL0ZlyqNV4ZLGZY7ozj3vsXaP2kFxhQKqltcxw5RoaMX sjpGQdj8VnWEnmvyBrSe8SqTsVKHEsF2+mKSdtEKPShnaUZCopW4bzwfzITuaVzTVBTb K4lg== X-Gm-Message-State: AKwxyteQwHcf3NFht3at6PVG6OWrZ1/B2/sRXdJZPxkvQoaPCYPfA6A/ Ib2d7oKmAIdYwSS1n8pw4YSHMUDn4lginm3e9vVHPQ== X-Google-Smtp-Source: ACJfBouQqcBLVsXf8jspv1Qe+MRRCZQD2Xvoyj9oVLgE+IN1C5Ab8n48yvHxV+i7Xa/Yn0Z0EfHWA/Jav97LaOlv37Y= X-Received: by 10.84.140.1 with SMTP id 1mr10145795pls.221.1515784002103; Fri, 12 Jan 2018 11:06:42 -0800 (PST) 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 Sender: freemanrich@gmail.com Received: by 10.100.151.169 with HTTP; Fri, 12 Jan 2018 11:06:41 -0800 (PST) In-Reply-To: <8472733.tdHJfgl724@dell_xps> References: <8472733.tdHJfgl724@dell_xps> From: Rich Freeman Date: Fri, 12 Jan 2018 14:06:41 -0500 X-Google-Sender-Auth: lHF1QbsQpDIQTtRO6ILnNoVcbp4 Message-ID: Subject: Re: [gentoo-user] Microcode updates for "old" Intel CPU's To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 6353f378-db58-4e13-9477-a77008cb46f1 X-Archives-Hash: 5640b3f2186124f641a3b46601cd1ce1 On Fri, Jan 12, 2018 at 1:42 PM, Mick wrote: > On Friday, 12 January 2018 17:47:46 GMT Rich Freeman wrote: > >> The other odd thing is that a firmware update was released for my >> motherboard (ASRock AB350 Pro4) on the 10th, and if I flash it grub >> will no longer boot the linux kernel, and it is pretty slow overall, >> but it will still boot memtestx86 just fine. I figured I'd wait a few >> days and see if there is any further info on it. > > No Asus MoBo firmware updates here ... but would they be even required/ > necessary for the CPU bugs? It shouldn't be. I'm not sure if Ryzen has anything equivalent to the Intel Management Engine. Intel has been scrambling to patching the firmware for that (which basically gives a hardware-level rootkit to anybody who exploits it). The official docs just mentioned adding support for additional processors with an AGESA update. I wouldn't be surprised if at some point the motherboard vendors slip in the microcode updates there as well. When I was having issues getting linux to update the microcode I figured I'd check the firmware for updates. When it failed to boot I just rolled it back. They actually did 2 firmware releases, with one being used as a bridge to the other. That also makes me wonder if there is a microcode update of some kind in there. -- Rich