Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
stevealexrs committed Dec 3, 2021
1 parent f1261ac commit e7973b7
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# OpenCore-Legion-5i-17IMH05H

This repository contains EFI files for OpenCore 0.7.5 for Legion-5i-17IMH05H with macOS Monterey 12.0.1

This is the main guide I follow: [OpenCore Dortania](https://dortania.github.io/OpenCore-Install-Guide/)
Expand Down Expand Up @@ -37,7 +37,7 @@ Note: This repo contains extra properties files added by Mac. (.DS_STORE, .\__fi
| Mac App Store Login | Not working |

## Debug Vs Release
The main differences are debug logging and opencanopy gui. Release also disable opencore from applying smbios data to windows.
The main differences are debug logging and opencanopy gui. Release also disable opencore from applying smbios data to windows and added openlinuxboot.efi and other relevant files/settings.

## Troubleshooting
Make sure you have followed all recommended steps in Dortania guide before continuing.
Expand All @@ -47,7 +47,7 @@ You need 3 additional things to fix this (in order):
2. Set DevirtualiseMmio = False
3. Disable unsupported SkHynix NVMe

Adding CpuTscSync.kext and setting DevirtualiseMmio = false in config.plist are quite straightforward. Disabling NVMe takes some time. You can first verify whether the NVMe SSD is actually causing issue by adding *nvme=-1* to (probably) disable all ssd in boot-args. If the kernel panic is gone, then the culprit is the NVMe SSD. However, this will stop other NVMe SSD too so you need to add an ssdt.
Adding CpuTscSync.kext and setting DevirtualiseMmio = false in config.plist are quite straightforward. Disabling NVMe takes some time. You can first verify whether the NVMe SSD is actually causing issue by adding *nvme=-1* to (probably) disable all ssd in boot-args. If the kernel panic is gone, then the culprit is the NVMe SSD. However, this will stop other NVMe SSD too so you need to add an ssdt.

Go to Device Manager on Windows and click *Storage Controllers*. There will be multiple *Standard NVM Express Controller* under it. The controller that stores Window is the one with driver that cannot be disabled. Then, go to *Details* and search for *BIOS device name*. You should see this:

Expand All @@ -72,7 +72,7 @@ DefinitionBlock ("", "SSDT", 2, "hack", "NVMe-Pcc", 0x00000000)
Return (Package (0x02)
{
"class-code",
"class-code",
Buffer (0x04)
{
0xFF, 0x08, 0x01, 0x00
Expand Down Expand Up @@ -105,4 +105,3 @@ Likely can be fixed by following this guide to add [SSDT-XOSI](https://dortania.

### Weird Error Message But Still Boot
Unknown

0 comments on commit e7973b7

Please sign in to comment.