-
Notifications
You must be signed in to change notification settings - Fork 68
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
Cannot correct padding error on Asus Maximus V Gene #220
Comments
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 NVME5 and NVStrapsRebar module too. |
Thanks for trying, but on inspection with UEFITool, this is not correct. There are padding errors. Upon inspection, the PciBus and PciHostBridge modules are different sizes from the original BIOS, with the PciBus module not having a compressed section at all. |
I checked again right now and the padding looks the same like in the original BIOS file from Asus. Where do you see the errors? |
Can you try BIOS flashback? Then I can upload the cap file for you and you can test it and flash your original if it doesn´t work. |
I just downloaded the original file from ASUS and there it looks exactly the same like in my modified file. |
How does it look exactly the same? Via which app? |
UEFI Tool |
Ok anyway, you can try the mod file if you want or not. That´s ok too of course, I just tried to help. :) |
Which version? |
System
Description
I have succesfully injected the RebarDxe FFS module, modified the BIOS menu to show PCI Settings -> Above 4G Decoding option but cannot use UEFIPatch to correct the various issues with limited BAR size on my Ivy Bridge / Z77 platform.
As described in the guide, the patches are applied but padding errors are introduced. I have tried to follow the further "fixes" but these lead to a Hex edit to move the changes from the patched (but glitched) file to the original file. This does not work as the PciBus and PciHostBridge modules are compressed and the file sizes are different. If I extract the "Body only" with UEFITool then I can see that the body data is the same size, with the hex editor confirming the correct changes, however the header/compression (?) has somehow been altered and the total size is different so the whole structure beyond the PciBus module is corrupt, including the padding errors.
I've not been able to work out how to fix this issue as MMTool does the exact same thing.
I see in the list of compatible motherboards that a user (who is no longer an active username on github?!) has confirmed this motherboard works with UEFIPatch. I can confirm Resizable BAR is enabled, but limited to 2GB until I can get the UEFI patches to work.
Any help would be greatly appreciated as I have Rebar enabled with 2GB but the system fails to boot if I set it to >=4GB.
The text was updated successfully, but these errors were encountered: