-
Notifications
You must be signed in to change notification settings - Fork 238
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
nothing changes #188
Comments
Update: It does NOT work properly.
Afterwards, my custom image was shown as it is supposed to be. |
Your log file shows that the boot order gets reset so that the Windows boot loader stays first. So after installing with the default method, you need to boot into UEFI Setup (available in the setup menu) to manually choose HackBGRT over Windows boot loader. Apparently, some computers even have a setting for this feature, "Boot Order Lock", while some simply refuse to update the boot order. Looks like my computer has now gained the same feature, so BootOrder cannot be changed automatically anymore (not even from Linux or UEFI Shell) and it has to be changed manually. Once again OEMs are making things more difficult. I will have to add this step into the instructions.
HackBGRT is designed for "cold boot". It cannot work with suspend. Hibernation or Fast Startup (Hiberboot) or other Windows quirks may or may not work, it depends on how they are implemented in Windows. HackBGRT does not modify the firmware or the Windows boot loader, and never will. If it does not work for your use case, then it's unfortunately a dead end for you.
This is a known problem in the shim boot loader (necessary for Secure Boot). If you cannot use the first options to properly install and change BootOrder, and if you have disabled Secure Boot, then you can use |
I did look for it, after checking out other issues on this repository, but it did not appear there. I only had Windows default boot loader as an option. Unless, I am confusing whatever you mean by "UEFI Setup"?
Fortunately, it wasn't, as patching boot logo in MSI bios is extremely simple and I just did that. Anyway, the issue can be closed now, I suppose? Unless you want me to install HackBGRT with different .bmp and doing some stuff for testing purposes. |
What happens?
Absolutely nothing changes, although setup is successful.
How this happens?
Explain exactly the steps you did:
Log file
Run the setup again and select menu option
L
(or add parametershow-boot-log
on command line). Attach thesetup.log
to this report.setup.log
Fast Boot is disabled.
Secure Boot is disabled.
Board is MSI MAG Z390 TOMAHAWK.
The text was updated successfully, but these errors were encountered: