Update to upstream 2.1-15. 20180108. Includes fix for Spectre.
This update has been submitted for testing by aarapov.
works on various systems here:
microcode updated early to revision 0x23, date = 2017-11-20 previous was 0x22 from January
I have a question:
Does this microcode update negate the need for a firmware update? And if so, why do Windows machines require firmware updates if a microcode update would suffice?
So yes, and no. This is pushing the same microcode that a firmware update would. Obviously firmware can load the microcode earlier, so that is a better solution.
As for Windows, I have no idea how they handle microcode loads, certainly they are capable of something similar, but this microcode was literally released about 30 minutes before the package hit koji. I got a heads up from Intel and passed it along. The date is 11-20, so it has probably been available for hardware vendors to do QA and push firmware updates for a while now. Certainly Fedora users would have gotten it sooner if a firmware update was available from their vendor.
works for me
This update has been pushed to testing.
Works, but as already noted by Intel, no new revision for 1st, 2nd and many 3rd gen Core i(X). Fine by me, no Intel anymore :-/
This update has been submitted for batched by bodhi.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
Comment fields support Fedora-Flavored Markdown.
Text fields in Bodhi2 support an
version of markdown.
This is a cheat sheet for your reference.
You can do headers by underlining or by prefixing with the # character:
This is an H1
This is an H2
# This is another H1
## This is another H2
You can do blockquotes using email-style prefixes with the > character:
> This is a quotation
> over many lines
> > and it can be nested(!)
Lists work like you'd expect, by prefixing with any of the *, +, or - characters:
Check out this list:
* a list..
You need a blank line between a paragraph and the start of a list for the renderer to pick up on it.
Emphasis can be added like this:
You can save your code references from being misinterpreted as emphasis by surrounding them with backtick characters (`):
Use `the_best_function()` and _not_ that crummy one.
Links look like this:
..but we also support bare links if you just provide a URL.
You can create code blocks by indenting
every line of the block by at least 4 spaces or 1 tab.
Here is a code block:
for i in range(4):
You can reference bug reports by simply writing something of the form tracker#ticketid.
This fixes PHP#1234 and Python#2345
... we will automatically generate links to the tickets in the appropriate trackers in place.
The supported bug tracker prefixes are: (these are all case-insensitive)
And you can refer to other users by prefixing their username with the @ symbol.
This will generate a link to their profile, but it won't necessarily send them a notification unless they have a special FMN rule set up to catch it.
Lastly, you can embed inline images with syntax like this:
Is the update generally functional? (karma)
You need to be logged in to add karma!
Copyright © 2007-2018 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.