![]() ![]() I saw the guide before, but it did not work for me that well. Update CPU Microcode + Fix FIT Using UEFITool / Hex ![]() (Do not worry about the legacy Option ROM stuff, I did not have it configured to UEFI in this - Upload your mod BIOS and I can fix FIT for you, or here, I made a guide phase)Ġ0:00.160ĐxA1Ĝollect info such as SBSP,Boot Mode,Reset type etcĠ0:00.160ĐxA3 Setup minimum path between SBSP & other socketsĠ0:00.160ĐxA7 Topology discovery and route calculationĠ0:00.160ĐxA9 Program final IO SAD settingsĠ0:00.160ĐxAA Protocol layer and other uncore settingsĠ0:01.850ĐxB4Ğvaluate RAS modes and save rank informationĠ0:02.020ĐxB3 Program registers on the memory controller levelĠ0:02.020ĐxB6 Perform the JEDEC defined init sequenceĠ0:03.610ĐxB9 Hardware memory test and initĠ0:23.790ĐxBAĞxecute software memory initĠ0:34.050ĐxBB Program memory map and interleavingĠ0:53.150Đx85ĝXE PCI Bus resource requestedĠ0:54.980ĐxC2ĝXE Legacy Option ROM InitĠ1:16.380ĐxC2ĝXE Legacy Option ROM Init Not every "microcode update" is relevant for the CPU, so for example the first line can ignored (probably ME or something, does not break the hack).Ġ0:00.030Đx06Ğarly CPU init (Sec. I can look up the addresses in UEFITool, but what would I have to do? Would I replace a DXE driver or the file of an "Other Option ROM in FFS" in the terms of UBU? Would it be sufficient to to fill the original address space with zeros and insert my code at the start or would I need to modify something that it actually gets called? The code is small, but I need to make sure that it gets called as early as possible and before the microcode update. Irrespective of the FIT problem, I could probably do it manually in HEX by replacing some unneeded DXE driver or module (not sure about the terminology, I am not familiar with this) and replacing it with the ffs. I tried the Phoenixtool and structure view and it kind of works, as it rearranges some data, but the resulting image does not boot. I know this can be fixed, but how do I calculate the correct values?Ģ. I cannot modify via UEFI Tool because the FIT-table is not correct. I have already found a nice combination of the new Bios and manually replaced old microcode that would work together with the turbo-hack, as long as I applied them in the correct order.ġ. However, I would like to use a newer Bios that does not boot well without any microcode loaded during the initial boot. ![]() ffs), by masking the existing microcode in the Bios, and then loading the hack via EFI and the actual microcode in Linux (it is important to first apply the "hack" and then a microcode of a certain age). I was using the all core turbo exploit (I have this both as. cap UEFI Bios files(different from the Intel-Board thread). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |