Replies: 9 comments 5 replies
-
|
I've used another version of mmtool to replace pcibus and now bios is free of padding issue, but beware: |
Beta Was this translation helpful? Give feedback.
-
Thanks for the response! So the zip you provided is for which board? Highly doubt I can use it if it's a BIOS for another model. |
Beta Was this translation helpful? Give feedback.
-
|
It is for your board, what else? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, opening it in UEFITool NE does show that the pad-file is not there, so it looks pretty good (I'm assuming both the PciBus and the NvramSmiDxe patches were applied). |
Beta Was this translation helpful? Give feedback.
-
|
The cause of the added pad file is that after the patch you applied the module has changed his size causing it to be unaligned, hence needing to add a pad file to realign the other module after the patched one. There is more than one solution to this: I went through the same issue. Here is the post that concludes all the process, in case this would be helpful to you. |
Beta Was this translation helpful? Give feedback.
-
|
Hey I tried to modify the BIOS file from Asus. I don´t own this board and can´t test it, but you can try if you want. I added the NVStrapsRebar module too. |
Beta Was this translation helpful? Give feedback.
-
|
For my Asus X99-A, after many tries of different suggestions scattered all over the place (including this discussion and other places), using MMTool in different permutations with UEFITool... what worked for me was: UEFITool / UEFIPatch 0.28.0
|
Beta Was this translation helpful? Give feedback.
-
|
Just to report back, I was unable to flash @ZOXZX BIOS file, it simply wouldn't work with flashback. Not sure what it didn't like from that file, but it didn't. as well as the new RebarDxe module. After flashing, I was able to enable Rebar at level 32 (maximum) and everything works as it should. Before that, I took a chance and flashed the one with the pad file and that was breaking my AMD HD Audio. Now that the pad file is fixed, it seems to have fixed that issue. For those that want the file (including the two patched modules I used), it's here: |
Beta Was this translation helpful? Give feedback.
-
|
Hey @gravufo, Any chance you could guide me through this on discord or something? I've got the same username on all platforms. I've got an Intel Arc B580 with a Sabertooth X99 and a i7-5930K that I plan to upgrade to an Intel Xeon E5-2687W v4, but I need this to actually get any use out of my GPU and I'm worried reading through all this that perhaps I might not be technical enough to do it alone. I've modded a few things in the past so I'm not super scared off, but I'd love a step by step guide or maybe to call and have you walk me through it. Thanks! |
Beta Was this translation helpful? Give feedback.








Uh oh!
There was an error while loading. Please reload this page.
-
System
Description
First off, thanks a lot for this repo and all the effort put into the wiki. It was really helpful!
I have successfully flashed a BIOS with the ReBarSmiDxe module as well as the NvramSmiDxe patch (required for X99).
However, I end up with no video at POST and I can't see anything if I manage to enter the UEFI settings (similar to issue #4 ).
I realise that the UEFIPatch was also trying to patch my PciBus with the patch
PciBus | Don't downgrade 64-bit BARs to 32-bit, which is probably what is causing the no video issue.Unfortunately, if I apply that patch whether it's through UEFIPatch, UEFITool or even MMTool 5.x (can't use 4.x on my BIOS), it seems to add a new pad-file that wasn't there before:

I have even tried messing around with the hex editor, however I can only do that on the extracted uncompressed version of the module, so it ends up being the same problem at the end.
Any idea how I could proceed to fix that?
Beta Was this translation helpful? Give feedback.
All reactions