![](https://seccdn.libravatar.org/avatar/aaff612bb0750768db78818737bfbdb6.jpg?s=120&d=mm&r=g)
On Sun, 18 Feb 2018 11:23:13 +0100 Marcus Meissner <meissner@suse.de> wrote:
I just submitted a revert update for ucode-intel, so zypper -f is not needed.
My original hope that Intel would be quick to release new firmware, but that has not manifested.
I've had 20180108-16.1 ucode-intel on kaby lake under 42.3 since 11-Jan and nothing has seemed out of place. Dell today (18-Feb) released a new BIOS for my T3620 for "Update to the latest CPU microcode to address CVE-2017-5715 and associated Intel Reboot issue." I haven't installed this yet (the package self-installs itself through the existing BIOS boot menu so the OS is not relevant to the install). Sorry if this is a dumb question but: am I safe to assume that your rollback from 20180108-16.1 ucode-intel to 20170707-10.1 tomorrow will have no effect on this new Dell burn under 42.3? http://www.dell.com/support/Home/us/en/04/Drivers/DriversDetails?driverId=J7... Thanks. Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org