similar to: [PATCH] docs: document "ucode=" hypervisor command line option

On Tue, 2015-05-19 at 13:31 +0200, Stephan Seitz wrote: > On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: > >Here's an idea. First extract the real initrd from the back half of the > >initrd: > > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > > kernel > > kernel/x86 > >

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

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

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

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

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

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 24411:ca5f588bd203 to Xen 4.1 -- ---to satisfy European Law for business letters:

AFAICT our current version does not correspond to any version in the Linux history. This commit resynchronised to the state in Linux commit 598bae70c2a8e35c8d39b610cca2b32afcf047af. Differences from upstream: find_cpio_data is __init, printk instead of pr_*. This appears to fix Debian bug #785187. "Appears" because my test box happens to be AMD and the issue is that the (valid) cpio

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

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

Thanks Atom2, thanks for the refs, I've added the Debian bug and the submitter back to the CC. On Wed, 2015-05-13 at 22:11 +0200, Atom2 wrote: > Am 13.05.15 um 15:41 schrieb Ian Campbell: > > I think I remember some discussion of something in this area not too > > long ago on xen-devel. CC-s added. > I assume you refer to this discussion which happend to be on the >

On Wed, 2015-05-13 at 11:57 -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 <

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 <

On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: >Here's an idea. First extract the real initrd from the back half of the >initrd: > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > kernel > kernel/x86 > kernel/x86/microcode > kernel/x86/microcode/GenuineIntel.bin > 16 blocks

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

v6 changes: - Check compiler before using [0] or []. v5 changes: - Fix prototypes in v4v.h for do_v4v_op - Add padding to make sure all the structures are 64 bits aligned - Replace [0] with [] v4 changes: - Stop using ssize_t, use long instead - Return -MSGSIZE for message bigger than 2GB - Fixup size handling - Rename

On Fri, Apr 25, 2014 at 5:19 PM, Alexandre Courbot <acourbot at nvidia.com> wrote: > nvc0_graph_ctor() would only let the graphics engine be enabled if its > oclass has a proper microcode linked to it. This prevents GR from being > enabled at all on chips that rely exclusively on external firmware, even > though such a use-case is valid. > > Relax the conditions enabling

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

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