What do you think about this MB X13SAV-PS | Motherboards | Products | Supermicro with an INTEL CORE 7 150UL with 64GB RAM, ok no ECC .... 10Gbe SFP+ via the m.2 key-m and a Broadcom HBA9600-24i ....
LGA 1700 Alder Lake "Servers"
- Thread starter tjk
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Necroing an old thread but is anyone running this board with Ubuntu and getting this error when logging in? First time I have seen this.
Pending processor microcode upgrade!
Diagnostics:
The currently running processor microcode revision is 0x012c which is not the expected microcode revision 0x012f.
I am guessing here but the reboot will probably make it go away but as I mentioned this is the first time seeing it. Not sure if this is due to an older bios as I've not updated it since it was purchased. I believe it is running what the board was released with. I could update but don't recall if that is USB only or if it can be done via the IPMI portal as I do not have a license.
System has been working great otherwise. Just not sure what this message could be about.
CPU:
13th Gen Intel(R) Core(TM) i9-13900K
Motherboard:
Product Name: X13SAE-F
Version: 1.02
BIOS Information:
Vendor: American Megatrends International, LLC.
Version: 2.0
Release Date: 10/17/2022
Pending processor microcode upgrade!
Diagnostics:
The currently running processor microcode revision is 0x012c which is not the expected microcode revision 0x012f.
I am guessing here but the reboot will probably make it go away but as I mentioned this is the first time seeing it. Not sure if this is due to an older bios as I've not updated it since it was purchased. I believe it is running what the board was released with. I could update but don't recall if that is USB only or if it can be done via the IPMI portal as I do not have a license.
System has been working great otherwise. Just not sure what this message could be about.
CPU:
13th Gen Intel(R) Core(TM) i9-13900K
Motherboard:
Product Name: X13SAE-F
Version: 1.02
BIOS Information:
Vendor: American Megatrends International, LLC.
Version: 2.0
Release Date: 10/17/2022
You should reboot since this microcode update addresses the next fix for the voltage problems of Raptor Lake.
The current version is 4.3. However, 4.3 only contains microcode 0x12e, not the current 0x12f. Therefore, there is no need to update the BIOS as far as you include microcode updates in linux (the message tells that you do that) AND run the processor according to specification (which I guess with this board).
This is from stone age
The current version is 4.3. However, 4.3 only contains microcode 0x12e, not the current 0x12f. Therefore, there is no need to update the BIOS as far as you include microcode updates in linux (the message tells that you do that) AND run the processor according to specification (which I guess with this board).
Is this true? No published BIOSes include 0x12f yet, and while you can get 0x12f from your distro, applying earlier Vmin shift microcode updates post-boot as a part of early OS load was *not* sufficient to mitigate the issue, the microcode had to be applied by the BIOS.
Do you have a source for that? This is the first time I hear this... (but I can imagine that the BIOS is able to update the processor in a state not reachable within early OS load)
Regarding 0x12f and its changes: Is update to microcode 0x12F necessary when not experiencing issues ?
Yes, one of the Intel folks who pushes the uCode updates that Linux distros pull from commented at uCode for Voltage issue · Issue #78 · intel/Intel-Linux-Processor-Microcode-Data-Files
Right, so the update is important for anyone here (ie running a 24/7 machine, presumably with a "lightly threaded workload" which a normal linux server generally will be).
Thank you for the link! I was not aware of this.
I wonder if this is also the case for 0x12f. The comment in your link indicates that the 0x129 update was NOT posted to this repository due to this issue but only to the BIOS channel. For 0x12f, the opposite happened: As you wrote (I was not aware of this because I only looked at X13SAE/X13SAE-F) it is not yet available in any BIOS but in the OS channels.
Interesting! Unfortunately, they do not publish changelogs (except for the version that contained 0x129 where they at least mentioned this version). For X13SAE (my machine at home), they even to not have 0x12e. Here, 4.2 is the latest BIOS, not 4.3 as for the X13SAE-F. Maybe I should ask them too
AFAIU, 0x12f also fixed some security issues, so its still useful to apply via the OS path (and they did eventually publish 0x129 via the OS path, just not initially). I assume the same is true, but someone could go ask.
Thanks. Will do.
Yeah, it is. It is just my home NAS server, Plex, and that is really about it. I should probably find something more energy efficient at some point. This may sound stupid but I thought I needed the IPMI or BMC license to update the Bios which is why I never have done it. Is there an update for the CPU or security?You should reboot since this microcode update addresses the next fix for the voltage problems of Raptor Lake.
This is from stone age
The current version is 4.3. However, 4.3 only contains microcode 0x12e, not the current 0x12f. Therefore, there is no need to update the BIOS as far as you include microcode updates in linux (the message tells that you do that) AND run the processor according to specification (which I guess with this board).
For X13SAE, BIOS 5.0 is released and micro code 0x12f is mentioned in the description. For X13SAE-F, however, the newest release is still 4.3 (0x12e according to my machine at work). Therefore, we now have at least one BIOS with 0x12f
Sounds like maybe it will be out in the next release for those of us using the X13SAE-F boards.
Dumb question as I'm still running the original BIOS that came with the motherboard (2.0 I think). But can that be updated using the default IPMI interface non license or do we upgrade via USB? Not sure if I should upgrade to the latest if there are any security fixes although it is home use.
Dumb question as I'm still running the original BIOS that came with the motherboard (2.0 I think). But can that be updated using the default IPMI interface non license or do we upgrade via USB? Not sure if I should upgrade to the latest if there are any security fixes although it is home use.
You must boot into UEFI shell. This is possible using BMC with no licence as well using keyboard and monitor. You need an USB stick for the update file (or put it into the EFI directory of your linux installation).
Since you have an raptor lake cpu according to your prior post, you really should update not only for security reasons (this can also be addressed by micro code loaded by OS) but especially for a long life of your processor. See posting #907.
Thanks for the detailed information. And yes, I believe the i9-13900K is a raptor lake. I'll jump back to post #907 and read it. Thank you again.
Good afternoon all.
Dumb question. Is the X13SAE-F board a valid option to consolidate servers?
I may not have asked the question properly but I have the X13SAE-F that is doing nothing other than serving up my storage using ZFS and running plex for our family. I have two docker containers running that are doing nothing other than managing a reolink security camera and its storage. The machine is basically idle. Seems overkill.
I was thinking of moving my older PC that is running an Intel 4700K (2013 ish?) to a VM on the X13SAE-F as it is more or less doing nothing also. The only thing I use it for is light weight video editing from my dive trips. Figured I could save some energy by retiring the desktop.
The X13SAE-F has a cheap Nvidia Quadro that Plex uses for transcoding and I believe there is a second PCI slot if I wanted to pass through video. I think the last time I tried this on a test VM it didn't work. Curious if anyone else is doing something similar.
Juice may not be worth the squeeze.
Dumb question. Is the X13SAE-F board a valid option to consolidate servers?
I may not have asked the question properly but I have the X13SAE-F that is doing nothing other than serving up my storage using ZFS and running plex for our family. I have two docker containers running that are doing nothing other than managing a reolink security camera and its storage. The machine is basically idle. Seems overkill.
I was thinking of moving my older PC that is running an Intel 4700K (2013 ish?) to a VM on the X13SAE-F as it is more or less doing nothing also. The only thing I use it for is light weight video editing from my dive trips. Figured I could save some energy by retiring the desktop.
The X13SAE-F has a cheap Nvidia Quadro that Plex uses for transcoding and I believe there is a second PCI slot if I wanted to pass through video. I think the last time I tried this on a test VM it didn't work. Curious if anyone else is doing something similar.
Juice may not be worth the squeeze.
What OS are you running? I haven't had any issues passing through a GPU with Unraid. The integrated gpu on the cpu will be much better at transcoding than your Quadro and use less power.
I am running Ubuntu and the VM was using LXC if I remember correctly. I will have to look at see if I can tell Plex to use the integrated gpu. TY for the tip.
