dortania / dortania/bugtracker
msr-lock.html: 1 Error; 2 Missing steps; Inconsistencies
- Dominant language
- No language data
- Stars
- 123
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
* Guide in question: OpenCore Post-Install/ Fixing CFG Lock
* Link to page with the issue: https://dortania.github.io/OpenCore-Post-Install/misc/msr-lock.html
First of all: **100 thousand x THANK YOU for your awesome guide** !!!!
**1.** Let's start with the **error** first:
> At this point, run either reset in the shell
change to
> At this point, while still in the shell, type `reboot` and press `ENTER`
reason: reset is not a valid command and will do nothing, + 'run' can be defined more clearly for more optimal user-friendliness
**2. Missing steps:**
> 1. Open your firmware with UEFITool and then find `CFG Lock` as a Unicode string. If nothing pops up then your firmware doesn't support `CFG Lock`, otherwise continue on.
> 1. You'll find that this string is found within a Setup folder, right-click and export as `Setup.bin` (or even Setup.`sct`)
change to
> 1. Open your firmware with UEFITool and then find `CFG Lock` as a Unicode string. If nothing pops up then your firmware doesn't support `CFG Lock`, otherwise continue on.
>
> 2. Double-click onto the line with the search result in the bottom pane.
>
> 3. You'll find that this string is found within a Setup folder. Right-click onto the `Setup` entry, click onto `Export as is` and export as `Setup.bin` (or even Setup.`sct`)
**3. Inconsistencies:** on my Laptop (Asus VivoBook S15 with x510UAR UEFI BIOS) the exact opposite to the explanations applies!
via UEFITool > ifrextract, my FW's MSR E2 register is at `0x527`. Via modified GRUB Shell
```
setup_var 0x527
```
=> `error: offset is out of range` ->
```
setup_var2 0x527
```
=> `error: offset is out of range` ->
```
setup_var_3 0x527
```
=> finally NO `offset is out of range` error, therefore accdg. to the instructions:
```
setup_var_3 0x527 0x00
```
exit > OC > `VerifyMsrE2`:
```
This firmware has LOCKED MSR 0xE2 register!
```
-> continue to boot macOS, reboot (because accdg. to some it sometimes needs 1 reboot for the register to show as UNLOCKED), recheck via `VerifyMsrE2` - still
```
This firmware has LOCKED MSR 0xE2 register!
```
As per hint from a fellow VivoBook hackintosher with same UEFI BIOS type & version as mine:
```
setup_var 0x527 0x00
```
exit > OC > `VerifyMsrE2` - lo-and-behold, despite of `error: offset is out of range`, finally:
```
This firmware has UNLOCKED MSR 0xE2 register!
```
Next: in UEFI BIOS, load Setup Defaults > `VerifyMsrE2` => LOCKED as expected/ supposed >
```
setup_var2 0x527 0x00
```
exit > OC > `VerifyMsrE2` - again, despite of `error: offset is out of range`, also:
```
This firmware has UNLOCKED MSR 0xE2 register!
```
_______________________
Does this reverse-logic only apply to Asus Laptops? Or to others, too? No matter what, this indicates that the guide needs some adaptations.
Let me know if you need any more info 🔢
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.