![]() ![]() You can find the size of every microcode listed in UefiTool’s FIT table as shown above. Your going to need to know the difference in size between the old and new later. Its important to take note of their sizes by scrolling to the end of the file in Hxd edit. Also load in HxD the new microcode update revision you downloaded from the repository and copy all of its content into memory. Load your master microcode file into a hex editor. Step 3 - Edit master Microcode rom file in HxD Edit: However in most cases it is easier just to use the location data in the FIT table to locate each microcode file but you need to know the size in hex of the old microcode file (listed in the hex table inside UefiTool) and the size of the new file using Hxd edit. This is not absolutely necessary but by copying the first 16 bytes of the old header and searching for it you can find where it exists in the master file. If you can find your actual existing microcode file inside Ubu module folder, or from an extracted Intel Linux release open it up inside Hxd Edit for the purpose of searching for the start location inside the master microcode file. The other microcodes I believe are for other generation + server based processors which for most of us not needed. Even though my FIT table detailed four modules you really need to update just the one for your particular cpu. Go to the CPU Microcode repository and locate the cpu microcode modules that are appropriate for your platform. Step 2 - Extract Body of master microcode module and save: ![]() Just ‘Replace Body’ in UefiTool will be sufficient. In the case of individual microcode rom modules its a lot easier to manage in that probably you won’t need to copy paste the microcode hex values in a hex editor. Sometimes you may find each microcode in their own individual rom module: In my case my master microcode file resides in the rom module with GUID ‘17088572-377F-44EF-8F4E-B09FFF46A070’. Select the first microcode entry in the FIT table by doubling clicking item #2 as illustrated above and you will note that UEFITool A40 will automatically finds the actual master microcode file for us to manipulate. Then you have a number of references to the location of the actual microcode entries followed by possibly Bios initialization and ACM modules, Bootgaurd modules, and TPM/TXT modules of which may or may not be present depending on the bios. Take note that there will be a number of entries with the first one being a reference to ‘FIT’ table. I have test BIOS ready to send you once we hear back from plutomaniac about checking BootGuard enabled or not on this system.Load your bios file in UEFITool A57 and select the ‘FIT’ tab on the lower panel. We need to find out if BootGuard is enabled on this system before you flash anything anyway, especially in this case because microcodes are in the most secure volume. This is very involved mod, I had to use several tools, find several methods to juggle around and find way that didn’t break BIOS, and allowed correct FIT corrections too, but all break things bootguard checks so that needs to be looked at immediately. I checked, and UEFITool 25 does break it, so MMTool must be used instead, you can do one by one in CPU patch tab or extract main microcode module near bottom and update that way.ĭoing this is more involved for user, due to you must update checksum, module size, and be sure footer remains, so I suggest doing the CPU patch tab way if you’re not familiar with BIOS modding/hex editing etc. If UEFITool 25 breaks BIOS with things I mentioned above, I would use MMTool instead, either way then you must fix FIT once you are done. I mod BIOS like this for CPU microcodes - Update CPU Microcode + Fix FIT Using UEFITool / HexĪnd at first I would not use all latest microcodes, maybe after confirming it’s working, then you can try updated all to latest. I do believe the above BIOS I checked would fail with any CPU, since it’s broken in several ways, but you could be lucky and it works… hard to know for sure without testing it, but I’d put money on it being a bricked BIOS. How do you know your BIOS mods fail, aside from what I said above about that BIOS? Did you flash any before? If yes, how did they fail? I mean could you boot with other known compatible CPU and just not the ES ones, or did it not work with any CPU’s? Yes, you can always recover with programmer, if you have one now make a backup and confirm it’s valid then you never have to worry. ![]() Always flash from DOS or from Qflash if this board has Qflash within BIOS. You should not flash any BIOS in windows, not even stock one. And sorry, I meant to say 50652 in my comment above at #142 It’s no problem to put all those in there, I mainly wanted to focus on the CPU’s you actually have in hand right now so you can see if it’s working or not, but no problem to do them all. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |