On Saturday 30 Apr 2016 10:24:43 Mick wrote: > On Saturday 30 Apr 2016 09:29:08 Neil Bothwick wrote: > > On Sat, 30 Apr 2016 09:07:29 +0100, Mick wrote: > > > I seem to have mislaid my microcode somewhere, in the latest stable > > > gentoo kernel: > > > > > > # grep -i MICROCODE .config > > > # > > > > Grepping .config is unreliable, and always has been. You should use the > > search option in make menuconfig. If th eoption you want does not show > > up > > in .config, you are probably missing one of the options it depends on. > > Thanks Neil, I use both, especially if grepping does not reveal what I am > looking for. > > > The search results show what they are and whether they are set. I get > > this > > > > Symbol: MICROCODE [=y] > > > > Type : boolean > > Prompt: CPU microcode loading support > > Location: > > (1) -> Processor type and features > > > > Defined at arch/x86/Kconfig:1159 > > Depends on: CPU_SUP_AMD [=y] || CPU_SUP_INTEL [=y] > > Selects: FW_LOADER [=y] > > Yes, I got (almost) the same and it shows that MICROCODE is a top level > module, but I can't see it when I walk through the 'Processor type and > features' contents. Fine, my eyesight is not what it used to be, but it > can't be this bad! :p > > Symbol: MICROCODE [=n] > Type : boolean > Prompt: CPU microcode loading support > Location: > (1) -> Processor type and features > Defined at arch/x86/Kconfig:1125 > Depends on: (CPU_SUP_AMD [=y] || CPU_SUP_INTEL [=y]) && BLK_DEV_INITRD > Selects: FW_LOADER [=y]
It seems to require BLK_DEV_INITRD if my logic is still up to scratch. What happens if you set this; does MICROCODE appear then? This is odd, because I see this, searching from the /usr/src/ directory: peak src # grep MICROCODE linux-4.4.6-gentoo/.config # peak src # grep MICROCODE linux-4.4.7-gentoo/.config CONFIG_MICROCODE=y CONFIG_MICROCODE_INTEL=y # CONFIG_MICROCODE_AMD is not set CONFIG_MICROCODE_OLD_INTERFACE=y peak src # grep MICROCODE linux-4.5.0-gentoo-r1/.config # peak src # grep MICROCODE linux-4.5.1-gentoo/.config CONFIG_MICROCODE=y CONFIG_MICROCODE_INTEL=y # CONFIG_MICROCODE_AMD is not set CONFIG_MICROCODE_OLD_INTERFACE=y So the rules seem to change with succeeding versions of the kernel. Not sure what to suggest here. (I've been playing with lots of versions of kernel, boinc, virtualbox and others recently, which is why I still have those kernel sources installed. I've compiled and booted all of them at various times.) -- Rgds Peter
