-
Notifications
You must be signed in to change notification settings - Fork 12
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
Issue with the output of UEFIPatch. #21
Comments
Doesn't the ReBarUEFI guide say to ignore any errors from UEFIPatch ? |
I got concerned because I didn't see any output file as in the guide. "4. You'll get a new file created with .patched as the extension. This file will be used for the next steps if there isn't pad file issue. If you used the USB 3 patch make sure there is no file with extension .patched.patched." Then if it doesn't find any changes to make, it doesn't generate any files. |
But it does say to continue to next step DSDT patching if you get nothing to patch |
The patch and the DSDT is not needed for this mobo aparently? DSDT is only needed if you have a mobo for intel? just install the firmware update after you inserted the .ff file inside the bios file? |
yes |
Try this: #61 |
System
Description
Firstly, I want to say what a great job is being done here. Congratulations to everyone involved.
I followed all the steps to build the .ffs and .exe files successfully and also inserted the ffs into the new firmware mod, so far so good. But when I tried to apply the patch using UEFIPatch, I received the following result:
"PS D:\Bios Mod\BarMod - Copia\UEFIpatch> .\UEFIPatch.exe .\PRIME-B450M-GAMING-BR-SI-4401-MOD.CAP
parseImageFile: Aptio capsule signature may become invalid after image modifications
parseBios: one of volumes inside overlaps the end of data
parseBios: one of volumes inside overlaps the end of data
parseSection: GUID defined section with unknown processing method
parseSection: GUID defined section can not be processed
No patches can be applied to input file"
My question is: can these errors be ignored or are they issues to be resolved?
I read elsewhere that the "parseBios: one of volumes inside overlaps the end of data" error could be ignored, but I couldn't find any information regarding the others.
If anyone can help, I would appreciate it.
The text was updated successfully, but these errors were encountered: