similar to: [PATCH] Support newer microcode

Not sure about CentOS 6, but this was covered previously (at least for 7...not sure how much they differ)...not that I can find the message now, but here's what I recall/pieced together from bash history that works on CentOS 7: If the microcode you want is in the microcode_ctl package: mkdir -p /etc/microcode_ctl/ucode_with_caveats/ touch /etc/microcode_ctl/ucode_with_caveats/force yum

On Thu, Jan 18, 2018 at 11:45:42AM -0500, Pete Geenhuizen wrote: > >>Do we update the microcode now or do we wait until the latest > >>microcode_ctl rpm is available and then tackle this issue? > >Check with your hardware vendor for BIOS/EFI firmware updates. Apply > >those. > > > Thanks for the reply, but you missed what I was asking.? I've > already

On 01/18/18 09:01, Johnny Hughes wrote: > On 01/18/2018 07:51 AM, Phelps, Matthew wrote: >> On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes <johnny at centos.org> wrote: >> >> So, if we applied the previous microcode update, and all our machines >> rebooted OK, then we don't need to fallback? >> >> Also, do we know if the updated CentOS microcode RPM

/etc/init.d/microcode_ctl start /etc/init.d/microcode_ctl: microcode device /dev/cpu/microcode doesn't exist? This is on a clean install from the 4.1 x86 ISO. This is the 2nd box that is reporting this error. Adam Breaux Sr. Network Administrator Domain Bank, Inc. 23 W 4th St. Bethlehem, PA 18015 Phone: 610.317.9606 Fax: 610.317.9570 abreaux at domainbank.com

On 01/18/2018 07:51 AM, Phelps, Matthew wrote: > On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes <johnny at centos.org> wrote: > >> On 01/18/2018 03:41 AM, Pete Biggs wrote: >>> >>>> Look at: >>>> >>>> https://t.co/6fT61xgtGH >>>> >>>> Get the latest microcode.dat file from here: >>>>

On 01/18/18 11:31, Matthew Miller wrote: > On Thu, Jan 18, 2018 at 11:01:18AM -0500, Pete Geenhuizen wrote: >> Do we update the microcode now or do we wait until the latest >> microcode_ctl rpm is available and then tackle this issue? > Check with your hardware vendor for BIOS/EFI firmware updates. Apply > those. > > > Thanks for the reply, but you missed what I was

On 01/22/18 09:08, Johnny Hughes wrote: > On 01/18/2018 09:42 AM, Valeri Galtsev wrote: >> >> >> On 01/18/18 03:41, Pete Biggs wrote: >>> >>>> Look at: >>>> >>>> https://t.co/6fT61xgtGH >>>> >>>> Get the latest microcode.dat file from here: >>>> >>>> https://t.co/zPwagbeJFY

On 01/18/2018 03:41 AM, Pete Biggs wrote: > >> Look at: >> >> https://t.co/6fT61xgtGH >> >> Get the latest microcode.dat file from here: >> >> https://t.co/zPwagbeJFY >> >> See how to update the microcode from the links at the bottom of this page: >> >> https://t.co/EOgclWdHCw >> >> An before anyone asks .. I have no

On 01/18/18 03:41, Pete Biggs wrote: > >> Look at: >> >> https://t.co/6fT61xgtGH >> >> Get the latest microcode.dat file from here: >> >> https://t.co/zPwagbeJFY >> >> See how to update the microcode from the links at the bottom of this page: >> >> https://t.co/EOgclWdHCw >> >> An before anyone asks .. I have no idea

In 7.3.1611, running kernel "3.10.0-514.2.2.el7.centos.plus.x86_64 #1 SMP Wed Dec 7 19:10:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux" with microcode_ctl-2.1-16.1.el7_3.x86_64, I'm seeing the following error when booting: systemd[1]: [/usr/lib/systemd/system/microcode.service:10] Trailing garbage, ignoring. systemd[1]: microcode.service lacks both ExecStart= and ExecStop= setting.

On 01/18/2018 09:42 AM, Valeri Galtsev wrote: > > > On 01/18/18 03:41, Pete Biggs wrote: >> >>> Look at: >>> >>> https://t.co/6fT61xgtGH >>> >>> Get the latest microcode.dat file from here: >>> >>> https://t.co/zPwagbeJFY >>> >>> See how to update the microcode from the links at the bottom of this

On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes <johnny at centos.org> wrote: > On 01/18/2018 03:41 AM, Pete Biggs wrote: > > > >> Look at: > >> > >> https://t.co/6fT61xgtGH > >> > >> Get the latest microcode.dat file from here: > >> > >> https://t.co/zPwagbeJFY > >> > >> See how to update the microcode

On 01/22/2018 10:06 AM, Valeri Galtsev wrote: > > > On 01/22/18 09:08, Johnny Hughes wrote: >> On 01/18/2018 09:42 AM, Valeri Galtsev wrote: >>> >>> >>> On 01/18/18 03:41, Pete Biggs wrote: >>>> >>>>> Look at: >>>>> >>>>> https://t.co/6fT61xgtGH >>>>> >>>>> Get the

> Look at: > > https://t.co/6fT61xgtGH > > Get the latest microcode.dat file from here: > > https://t.co/zPwagbeJFY > > See how to update the microcode from the links at the bottom of this page: > > https://t.co/EOgclWdHCw > > An before anyone asks .. I have no idea why Red Hat chose this path, > they did. It doesn't matter if I (or anyone else)

it is working thx a lot... but it has included the GenuineIntel.bin only in actually used kernel... do I need to reinstall microcode_ctl every time I update the kernel? And second question, I quess I still need the ucode = scan as xen parameter right? Am 2018-09-19 20:08, schrieb Kevin Stange: > On 9/19/18 1:55 AM, Christoph wrote: >> >> Hi >> >> can someone say me

On Thu, Jan 18, 2018 at 11:01:18AM -0500, Pete Geenhuizen wrote: > Do we update the microcode now or do we wait until the latest > microcode_ctl rpm is available and then tackle this issue? Check with your hardware vendor for BIOS/EFI firmware updates. Apply those. -- Matthew Miller <mattdm at fedoraproject.org> Fedora Project Leader

On 9/19/18 1:55 AM, Christoph wrote: > > Hi > > can someone say me how to update the ?code of the cpu with xen? > > I have added the ucode=scan parameter to xen but it does not seem to > work... > > the ?code version of my xeon is really old :/ > > model name??? : Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz > microcode??? : 0x10 > There is a

Hi, is there any guide for CPU microcode updates on CentOS6, Xen 4.10, kernel 4.9 ? Thanks Karel

Hi, On Mon, Jan 16, 2006 at 11:26:09PM +0000, Kurt Garloff wrote: > (1) A patch to xend/XenDomainInfo.py, xend/XenBootloader.py and > xm/create.py, making sure that all the needed info is passed > to the bootloader and also stored for reuse on rebooting. Some more remarks: XendBootloader.py misses a timeout and waits for the bootloader to finish forever; I just made a TODO.

I have just installed Centos 5.0 from DVD. I have also run the software updates and I think everything is up to date. The motherboard is a Gigabyte GA945GM-S2 with an Intel E2140 processor. At boot time if I select show details - there is one error shown "in red", Like this: Applying Intel CPU microcode update. FATAL: Module microcode not found. ERROR: Module microcode does not exist