AMD C1E issue? 2.6.38.4
Hello,
Saw these in my messages after enabling C1E on my new Jetway Mini-ITX board:
# microcode_ctl -u microcode_ctl: writing microcode (length: 430080) microcode_ctl: error writing to '/dev/cpu/microcode' errno=22 (Invalid argument) microcode_ctl: there may be messages from the driver in your system log.
microcode: AMD microcode update via /dev/cpu/microcode not supported
microcode: AMD microcode update via /dev/cpu/microcode not supported
This is on kernel.org 2.6.38.4 on AMD Athlon II X2 235e on JNC84E-LF board, Fedora 14 for most of the rest of the stuff.
Anybody can tell why the update cannot work?
The previous board (JNC81) did not show these but also did not have C1E in BIOS as far as I recall.
Please explain.
Kind regards,
Udo
Hi,
Quoted 4 lines · Udo van den Heuvel
Hello,
Saw these in my messages after enabling C1E on my new Jetway Mini-ITX board:
Quoted 8 lines
# microcode_ctl -u microcode_ctl: writing microcode (length: 430080) microcode_ctl: error writing to '/dev/cpu/microcode' errno=22 (Invalid argument) microcode_ctl: there may be messages from the driver in your system log.microcode: AMD microcode update via
/dev/cpu/microcodenot supported
microcode: AMD microcode update via/dev/cpu/microcodenot supported
no, the message is correct - the AMD ucode driver doesn't support ucode loading method through the /dev node, only through the firmware loader. I.e., you should simply put the microcode image into /lib/firmware/amd-ucode/ and compile the kernel microcode driver as a module - then it'll load automatically.
Quoted 6 lines
This is on kernel.org 2.6.38.4 on AMD Athlon II X2 235e on JNC84E-LF board, Fedora 14 for most of the rest of the stuff.
Anybody can tell why the update cannot work?
The previous board (JNC81) did not show these but also did not have C1E in BIOS as far as I recall.
This doesn't have anything to do with C1E.
HTH.
Signature · 2 lines
Regards/Gruss,
Boris.Quoted 8 lines · Borislav Petkov
Quoted 8 lines
Saw these in my messages after enabling C1E on my new Jetway Mini-ITX board:
# microcode_ctl -u microcode_ctl: writing microcode (length: 430080) microcode_ctl: error writing to '/dev/cpu/microcode' errno=22 (Invalid argument) microcode_ctl: there may be messages from the driver in your system log.
Quoted 8 lines
Quoted 2 lines
microcode: AMD microcode update via
/dev/cpu/microcodenot supported
microcode: AMD microcode update via/dev/cpu/microcodenot supportedno, the message is correct - the AMD ucode driver doesn't support ucode loading method through the /dev node, only through the firmware loader. I.e., you should simply put the microcode image into
/lib/firmware/amd-ucode/and compile the kernel microcode driver as a module - then it'll load automatically.
Wel, yes/no.
It works that way on my other boxes.
On this specific box microcode_ctl is not activated automagically during startup of the machine.
Quoted 1 line
This doesn't have anything to do with C1E.
OK, that helps. Thanks.
What else could be the cause of microcode_ctl not updating? Situation is:
microcode: CPU0: patch_level=0x10000b7
microcode: CPU1: patch_level=0x10000b7
Is that new enough so that there is just no newer code to be uploaded for AMD Athlon(tm) II X2 235e Processor ?
Udo
(you've dropped the cc list, please hit "reply-to-all" when replying to those mails.
Quoted 18 lines · Udo van den Heuvel
Quoted 8 lines · Borislav Petkov
Quoted 8 lines
Saw these in my messages after enabling C1E on my new Jetway Mini-ITX board:
# microcode_ctl -u microcode_ctl: writing microcode (length: 430080) microcode_ctl: error writing to '/dev/cpu/microcode' errno=22 (Invalid argument) microcode_ctl: there may be messages from the driver in your system log.Quoted 8 lines
Quoted 2 lines
microcode: AMD microcode update via
/dev/cpu/microcodenot supported
microcode: AMD microcode update via/dev/cpu/microcodenot supportedno, the message is correct - the AMD ucode driver doesn't support ucode loading method through the /dev node, only through the firmware loader. I.e., you should simply put the microcode image into
/lib/firmware/amd-ucode/and compile the kernel microcode driver as a module - then it'll load automatically.
Quoted 4 lines
Wel, yes/no.
It works that way on my other boxes.
On this specific boxmicrocode_ctlis not activated automagically during startup of the machine.
As I said earlier, microcode_ctl cannot load the microcode on AMD - this happens upon module load with no need for userspace support except enabling loading of the microcode.ko module (you have to check how exactly Fedora does that).
Quoted 6 lines
What else could be the cause of
microcode_ctlnot updating? Situation is:
microcode: CPU0: patch_level=0x10000b7
microcode: CPU1: patch_level=0x10000b7
Is that new enough so that there is just no newer code to be uploaded for AMD Athlon(tm) II X2 235e Processor ?
Exactly, this says that you have the latest ucode for your CPU.
HTH.
Signature · 2 lines
Regards/Gruss,
Boris.Quoted 3 lines · Udo van den Heuvel
Anybody can tell why the update cannot work?
The previous board (JNC81) did not show these but also did not have C1E in BIOS as far as I recall.
If you have C1E problems besides of the microcode thing, which isn't related, you could try to boot with acpi_skip_timer_override. That works in my case.