1 |
On Saturday 30 Apr 2016 08:50:55 Alec Ten Harmsel wrote: |
2 |
> On Sat, Apr 30, 2016 at 09:29:08AM +0100, Neil Bothwick wrote: |
3 |
> > On Sat, 30 Apr 2016 09:07:29 +0100, Mick wrote: |
4 |
> > > I seem to have mislaid my microcode somewhere, in the latest stable |
5 |
> > > gentoo kernel: |
6 |
> > > |
7 |
> > > # grep -i MICROCODE .config |
8 |
> > > # |
9 |
> > |
10 |
> > Grepping .config is unreliable, and always has been. |
11 |
> |
12 |
> I usually use something like: |
13 |
> |
14 |
> grep MICROCODE $(find . -name Kconfig) |
15 |
> |
16 |
> Alec |
17 |
|
18 |
# grep -i MICROCODE /boot/config-4.4.6-gentoo |
19 |
# |
20 |
# grep -i MICROCODE .config |
21 |
# |
22 |
# grep MICROCODE $(find . -name Kconfig) |
23 |
./arch/x86/Kconfig:config MICROCODE |
24 |
./arch/x86/Kconfig:config MICROCODE_INTEL |
25 |
./arch/x86/Kconfig: depends on MICROCODE |
26 |
./arch/x86/Kconfig: default MICROCODE |
27 |
./arch/x86/Kconfig:config MICROCODE_AMD |
28 |
./arch/x86/Kconfig: depends on MICROCODE |
29 |
./arch/x86/Kconfig:config MICROCODE_OLD_INTERFACE |
30 |
./arch/x86/Kconfig: depends on MICROCODE |
31 |
# |
32 |
|
33 |
Now you see it ... now you don't! I am getting really confused. :-/ |
34 |
|
35 |
Why on this PC the MICROCODE options become available only when I enable |
36 |
INITRD, but on other PCs such a problem does not exist? |
37 |
|
38 |
-- |
39 |
Regards, |
40 |
Mick |