Closed wuwuwu223 closed 1 year ago
I don't get the point of opening this issue when clearly you're using:
while Dortania's bugtracker requirements clearly say that only OpenCore and Lilu configuration are supported.
SSDT-CPUR has nothing to matter in your case as you can see below :/
P.S. is there any specific reason you're using FakeSMC rather than VirtualSMC?
I don't get the point of opening this issue when clearly you're using:
- Clover
- SSDT-RTC0 without correcting the paths
while Dortania's bugtracker requirements clearly say that only OpenCore and Lilu configuration are supported.
SSDT-CPUR has nothing to matter in your case as you can see below :/
P.S. is there any specific reason you're using FakeSMC rather than VirtualSMC?
I'm using open core 0.7.4 ,use fakesmc kext it show clover,I'll retry to get true error log again later.When I use VirtualSMC Lilu show found dead device gfx0
I don't get the point of opening this issue when clearly you're using:
- Clover
- SSDT-RTC0 without correcting the paths
while Dortania's bugtracker requirements clearly say that only OpenCore and Lilu configuration are supported.
SSDT-CPUR has nothing to matter in your case as you can see below :/
P.S. is there any specific reason you're using FakeSMC rather than VirtualSMC?
I'm using open core 0.7.4 ,use fakesmc kext it show clover,I'll retry to get true error log again later.When I use VirtualSMC Lilu show found dead device gfx0
This is now beta9 and opencore0.7.4 and lilu1.5.6 and virtualsmc,show this and reboot automatic. Can u give some help please, thanks!
Restrictevents has now the ability to fix these issues. Please read the release notes of latest restrictevents.
Hello! Please post on forums for support.
All worked fine below this version,I think the CPUR.aml has something wrong.![2EBEB04A-E6DD-40CB-BB5F-1904A572849E](https://user-images.githubusercontent.com/81224214/137083542-9bee77e9-b8fa-4bd7-b159-0e6b235dc830.jpeg)