AW: Early microcode not being loaded

> That file is way too big. In fact, it is exactly the size of the newest > ".dat" file from Intel. The kernel doesn't grok that text format, the > microcode updates have to be converted to binary format, first. > I suggest you use "iucode_tool -S --write-earlyfw=ucode.cpio" to generate >

AW: Early microcode not being loaded

> Hi! > I'am trying to use the feature of loading early an intel microcode. > According to the documentation (early-microcode.txt) that should be possible. > > I am currently using my own initrd, so I've created a second one, as the docs > specified and merged it with my own. > > Galactica linux

AW: Early microcode not being loaded

Hi! I'am trying to use the feature of loading early an intel microcode. According to the documentation (early-microcode.txt) that should be possible. I am currently using my own initrd, so I've created a second one, as the docs specified and merged it with my own. Galactica linux # file

AW: Early microcode not being loaded

That file is way too big. In fact, it is exactly the size of the newest .dat file from Intel. The kernel doesn't grok that text format, the microcode updates have to be converted to binary format, first. I suggest you use iucode_tool -S --write-earlyfw=ucode.cpio to generate your

AW: Early microcode not being loaded

> On Fri, Jul 18, 2014 at 08:40:42PM +, Conrad Kostecki wrote: > > Where is the problem? Why is the microcode not being loaded early? > > CONFIG_MICROCODE_INTEL_EARLY=y set in .config? Yes! Galactica tmp # grep -i microcode /boot/config-3.15.5 CONFIG_MICROCODE=y CONFIG_MICROCODE_INTEL=y #

AW: Early microcode not being loaded

On Fri, Jul 18, 2014 at 08:40:42PM +, Conrad Kostecki wrote: Where is the problem? Why is the microcode not being loaded early? CONFIG_MICROCODE_INTEL_EARLY=y set in .config? Yes! Galactica tmp # grep -i microcode /boot/config-3.15.5 CONFIG_MICROCODE=y CONFIG_MICROCODE_INTEL=y #