I found that you have to modify the mce.py to add back in the old “-ubu” switch that was taken out of the script. I can successfully run the latest MCE now.
Line 111: self.mce_ubu = False
Line 129: if '-ubu' in source : self.mce_ubu = True # Hidden
Line 881: if param.mce_ubu : return
Line 946: pt.left_padding_width = padd if not param.mce_ubu else 0
Line 947: pt.right_padding_width = padd if not param.mce_ubu else 0
Line 958: if param.mce_ubu : padd = 0
Line 997: if not param.mce_ubu : sys.excepthook = show_exception_and_exit
Line 1066: if not param.mce_ubu :
Line 1301: if not param.mce_ubu :
Line 1561: if not param.mce_ubu and not os.path.exists(extr_dir_int) : os.makedirs(extr_dir_int)
Line 1747: if not param.mce_ubu and not os.path.exists(extr_dir_amd) : os.makedirs(extr_dir_amd)
Line 1869: if not param.mce_ubu and not os.path.exists(extr_dir_via) : os.makedirs(extr_dir_via)
Line 2000: if not param.mce_ubu and not os.path.exists(extr_dir_fsl) : os.makedirs(extr_dir_fsl)
Line 2122: mce_exit(mc_nr if param.mce_ubu else 0)
@srialmaster
We/some users have knowledge of several ways…
but this is a user project and we respect such project as it IS, as also the user who
develops it.
I’m sure that developer also reads this thread don’t you think…
Anyway, thank you for sharing your experience, all the best.
I was wondering if it’s possible to add the updated MCE db to the newer releases?
I also wanna ask if anyone with AMD had any success with MC updates? I can’t seem to process them as all it says it has found the codes (2) but processed none (0). “mcE found 2 mCodes - Processed 0 mCodes”
For the record, 4700u, AMI BIOS, CPUID: 860F01
current microcode: 8600106 20200619
possible update: 860010C 20231007 (if it had the newest db)
@KotTHECat@MeatWar@srialmaster@ghostfella
Since >this< thread has been designed just for the UBU guide and its updates, I have moved your posts into this better matching UBU Discussion thread.
In general, the Gigabit driver is initially implemented for I219. This driver is not very suitable for previous chips (82579/217/218)
In this version 0.2.xx, I219 is explicitly specified. It is not a fact that this driver will work correctly instead of previous versions (0.0.xx/0.1.xx)…
Replacing two GOP Drivers (v17 and v9_1) removed at some point past 1.80.a5? newer versions only detect SKL-CML but not Xe for replacement for LGA 1200 systems.
Interesting, copying the IntelGopDriver.efi from “v17” into the “Usr_GOP” directory already offers it (EFI GOP Driver Xe - 17.0.1085). And it is not strange that it recommends EFI GOP Driver 9.0.1112, since it is in the “database”.
And there would be something wrong with the replacement. A GOP Driver replacement would replace both GOPs.
Ah yeah, I know that about the 1.5.90 Boot Agent, I got it from somewhere on this forum a while ago then someone pointed out the only difference was the version number and has since been deleted from this forum. Never bothered to change it back to what came bundled with UBU
Having an issue where it says “mcE found 2 mCodes - Processed 0 mCodes”. This is the only thing I actually want to do as my CPU microcode is 3 years old.
current microcode: 8600106 20200619
latest microcode: 860010C 20231007 (if it had the newest MCE.db)
Everything else can be updated by the tool, it’s just that one single, useful thing, that doesn’t want to budge.
At first I thought the reason UBU didn’t replace it was because it had the same version in its own files, but that’s not the solution. I replaced it with the latest version, but it still does not replace it. As far as I can tell, the solution is that the microcodes are not separate in the BIOS, but are part of other content. Anyway, I replaced it manually for you.
Nothing special. Hex editor. I deleted the old version and pasted the new one. It is not encrypted. However, you might need some experience, it’s easy to make a faulty BIOS.
@SoniX can UBU be made to insert NEW option rom, or maybe can you do a guide how to do it manually? I want to add VIA VT6421A option rom into the bios. The PCI Card is connected with a PCIE to 2XPCI to z690 UD DDR4. The “option rom” tab in MMTOOL I think is for EFI rom not legacy, and it makes the new saved bios invalid for BIOS UPDATE.
I simply added V041312.rom data to the end of my OROM body, forced bios flash(using recovery mode) and it did not work, the sata drive is not in the Bios boot menu,
You talked about “Size OROM”, do I need now to find hex value representing this in my OROM and increase it by the amount of V041312.rom size?, this is what I don’t understand, size as ‘bytes’, how is the hex representing this, example number 85 in hex normally as 38 35, or switched 35 38?
(it is the same GUID for me 365C62BA-05EF-4B2E-A7F7-92C1781AF4F9, in my OROM I see text ‘RAID’, ‘USB’, NVME, SATA, PCI, CD-ROM, FLOPPY, this:
.AMIBIOS(C)2010 American Megatrends, Inc. …BIOS Date: 12/24/18 09:42:34 Ver: 08.00.10 )
I tried with rambios(to load the rom and init it) I can access the ROM menu and see the sata drive connected, but FDISK or XFDISK hangs when attempting to access the new visible drive, and grub4dos does not see it(for it to then to boot from it)
