-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ASUS Sabertooth X99 pad-file issue #214
Comments
I've used another version of mmtool to replace pcibus and now bios is free of padding issue, but beware: |
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. |
It is for your board, what else? |
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). |
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. |
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. |
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:
![image](https://private-user-images.githubusercontent.com/475807/340121747-83f15255-422b-4a0d-818d-36b069c88461.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ3MzkyMTYsIm5iZiI6MTcyNDczODkxNiwicGF0aCI6Ii80NzU4MDcvMzQwMTIxNzQ3LTgzZjE1MjU1LTQyMmItNGEwZC04MThkLTM2YjA2OWM4ODQ2MS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODI3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyN1QwNjA4MzZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zZTJlYjVhZTQ0ZTI0ZjJiZDg4NTQ4ZGM5ZTc5Y2M4OGUwN2I3YTYyMjQ1OGQ5OTBiZGU1YmIyNTAxYzVmM2VkJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.kE5hTEKHldALXR2bDQ2zv-GgLw7tUbaAB2T7sS5JOlc)
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?
The text was updated successfully, but these errors were encountered: