search for: ucod

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > "We recommend that OEMs, cloud service providers, system > manufacturers, software vendors and end users stop deployment of > current versions." Current versions of what? Microcode? Well, that's the only thing Intel provides for CPUs, so that's all it can be. > What these means for people who

On Wed, Jan 24, 2018 at 4:41 PM, Leon Fauster <leonfauster at googlemail.com> wrote: ... > > Comparing microcode-20171117 with microcode-20180108 shows that > from the 94 ucode files only 19 where updated > > $ diff -r --brief microcode-20171117 microcode-20180108 > Files microcode-20171117/intel-ucode/06-3c-03 and microcode-20180108/intel-ucode/06-3c-03 differ > Files microcode-20171117/intel-ucode/06-3d-04 and microcode-20180108/intel-ucode/06-3d-04 differ...

...release only actually updated microcode for recent > CPUs. I have many servers that aren't crashing, but that's because > Intel hasn't actually even tried to fix the microcode for their CPUs > yet. Comparing microcode-20171117 with microcode-20180108 shows that from the 94 ucode files only 19 where updated $ diff -r --brief microcode-20171117 microcode-20180108 Files microcode-20171117/intel-ucode/06-3c-03 and microcode-20180108/intel-ucode/06-3c-03 differ Files microcode-20171117/intel-ucode/06-3d-04 and microcode-20180108/intel-ucode/06-3d-04 differ Files microcode-201...

Hi List, Any idea how to get wireless lan : 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 (rev 34) working on centos 5? Eero

Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/docs/misc/xen-command-line.markdown +++ b/docs/misc/xen-command-line.markdown @@ -785,6 +785,19 @@ Specify the per-cpu trace buffer size in > `= unstable | skewed` ### ucode +> `= <integer>` + +Specify the CPU microcode update blob module index. When positive, this +specifies the n-th module (in the GrUB entry, zero based) to be used +for updating CPU micrcode. When negative, counting starts at the end of +the modules in the GrUB entry (so with the blob commo...

On Tue, May 19, 2015 at 12:47:51PM +0100, Ian Campbell wrote: >The reconcatenate bit is easy, just: > $ cat initrd.ucode initrd.real > initrd.img >With initrd.real extracted above. > >initrd.ucode creation I'm a little unsure about but something like: > >$ mkdir initrd.ucode.tree >$ cd initrd.ucode.tree >$ cat /boot/initrd.img | cpio -id >$ find >. >./kernel >./kernel/x86 >...

...$ zcat initrd.real | cpio -t | head -n 5 > > . > > etc > > etc/ld.so.conf.d > > etc/ld.so.conf.d/fakeroot-x86_64-linux-gnu.conf > > etc/ld.so.conf.d/x86_64-linux-gnu.conf > > > >Now you can experiment with regenerating the ucode bit with whatever > >commands are recommended and reconcatenating the two. If that works then > >we know there is some incompatibility between iucode-tools's output and > >Xen's cpio reader (could be a bug in either or both I think). > > All right. Can you please p...

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 -- ------ Greetz

Package: xen-hypervisor-4.5-amd64 Version: 4.5.0-1 Severity: normal Dear Maintainer, according to the documentation the option ucode=scan should tell XEN to look for a microcode update in an uncompressed initrd. While I don?t use the Debian kernel the tools to generate the initrd are part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? creates the directory structure ?kernel/x86/microcode/GenuineIntel.bin?...

x86/ucode: fix for AMD Fam15 CPUs Remove hardcoded maximum size a microcode patch can have. This is dynamic now. The microcode patch for family15h can be larger than 2048 bytes and gets silently truncated. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> Backport from xen-unstable changeset...

On Thu, 2015-05-14 at 22:45 +0200, Stephan Seitz wrote: > On Wed, May 13, 2015 at 11:57:55AM -0400, Konrad Rzeszutek Wilk wrote: > >> > according to the documentation the option ucode=scan should tell XEN to > >> > look for a microcode update in an uncompressed initrd. > >> > > >> > While I don?t use the Debian kernel the tools to generate the initrd are > >> > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0?...

I think I remember some discussion of something in this area not too long ago on xen-devel. CC-s added. Konrad, do you know of any issues with ucode=scan in 4.4? On Wed, 2015-05-13 at 10:27 +0200, Stephan Seitz wrote: > Package: xen-hypervisor-4.5-amd64 > Version: 4.5.0-1 > Severity: normal > > Dear Maintainer, > > according to the documentation the option ucode=scan should tell XEN to > look for a microcode update...

Hi Martin, I was asked to clarify a few things: (1) Are all the user reports of loud fans on Fermi-era GPUs? (2) When the VBIOS POSTs the card, it loads initial ucode onto the Falcon processor (PMU), which will do basic fan management on its own. We call this init ucode "IFR" (Init From ROM). nvidia.ko will restore the IFR ucode when unloaded. I assume the loud fan symptom occurs after Nouveau is loaded and running, correct? I.e., this is a proble...

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 how to update the ?code of the cpu with xen? >> >> I have added the ucode=scan parameter to xen but it does...

...ntioned in there should get you up and running > - unless there's really a bug lurking somewhere. > > My guess is that the cpio archive was not created with the (required) > cpio option "-H newc". > > Regards Atom2 > > Konrad, do you know of any issues with ucode=scan in 4.4? > > > > On Wed, 2015-05-13 at 10:27 +0200, Stephan Seitz wrote: > >> Package: xen-hypervisor-4.5-amd64 > >> Version: 4.5.0-1 > >> Severity: normal > >> > >> Dear Maintainer, > >> > >> according to the documenta...

...t; + bool use_fw; Perhaps "ext_fw" or "use_ext_fw" would be more accurate. > int ret, i; > > + use_fw = nouveau_boolopt(device->cfgopt, "NvGrUseFW", false); > + > ret = nouveau_graph_create(parent, engine, bclass, > - (oclass->fecs.ucode != NULL), &priv); > + (oclass->fecs.ucode != NULL) || use_fw, > + &priv); Or perhaps a more intuitive way would be to name the variable "enable" and have something like: if (!nouveau_boolopt(device->cfgopt, "NvGrUseFW", false)) enable = ocla...

...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 reinstall microcode_ctl (there were arguably better ways to do this part, but I cant recall) add ucode=scan to your GRUB_CMDLINE_XEN_DEFAULT line grub2-mkconfig to update your grub config reboot Once that's done, every t...

> > according to the documentation the option ucode=scan should tell XEN to > > look for a microcode update in an uncompressed initrd. > > > > While I don?t use the Debian kernel the tools to generate the initrd are > > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? > > creates the directory...

On 09/18/2018 11:55 PM, 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 > We use ucode=-1 and provide it as a module for grub.

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