Recent content by Lord Kamina

If you're not using a dgpu my ig-platform-id obviously was not going to work as it tells the OS the IGPU has no physical connectors.

Rename PEG0.PEGP to PEG0.GFX0

If you don't have the same hardware I doubt it's the same issue. Anyway, first I made sure to unlock MSR Ex02 as per the AptioMemoryfix readme. DSDT patches I used Fixregions, Fixmutex, Fixheaders, FixIPIC (don't know if actually required), FixHPET, FixRTC, FixTMR and FixShutdown. Dropped only...

Well, finally! Never figured out the exact problem but it must have been something in my static DSDT/SSDT edits that was the issue. I ended up fixing everything via hotpatches (except for renaming PXSX but I can live without that) and it worked. For the record, in case somebody wonders in the...

Could somebody maybe share their CLOVER folders? I'd like to compare them with mine to see if I can get some insight on why I cannot boot with either F11b nor F8.

Things I've tried the last ctouple days: Changed DVMT to 128 (and also to 256 just to test) Replaced OsxAptioFix3 with AptioMemoryFix (and followed readme: removed slide=0 and followed the steps to disable the hidden CFG-Lock) Used the UHD 630 mobile ID and desktop and mobile ig-platforms...

I assume it's related to NVME because when I try to boot the original install I get no errors other than some NVME asserts followed by the "prohibited" sign and panic when the root volume is not found. The mojave installer has no Clover on it because it's a 100% vanilla installer created with...

No. There is no Clover on the USB stick; Clover is installed on the EFI partition of the NVME drive. What did you change in the file tree? I see you changed Aptiofix3 for aptiomemoryfix; and removed the partition driver and a couple others. Why? On the Kexts, you deleted all sensors...

I am now also unable to boot a Mojave installer (apparently iGPU issue), but I posted another thread for that. You can check that thread for my CLOVER folder, though. https://www.tonymacx86.com/threads/cant-boot-mojave-usb-gioscreenlockstate-3-panic-on-safe-mode.271697/

First: This was a previously-working HS install. I've been having trouble booting lately (related to NVME I think) and I wanted to boot a Mojave USB installer to take a look at a couple things. But I can't boot due to the problem mentioned above. I have tried:Enabling and disabling InjectIntel...

I'm not using the latest BIOS. Even if I was, I ran diffs of the initial BIOS revision, the one I'm using now and the latest, and the code relating to SATA and the NVME controller appears to be basically identical.

GA-Z370-HD3P What's the rationale for that or, why would the BIOS break NVME?

Update -- Here's what I did: - Edited the SSDT in question; removed references to the memory regions for the "hidden SSDTs" as well as the code that actually loaded them in memory, leaving only the the parts of code that returned values some other ssdt or the dsdt might need and then just...

Still trying to get this i7-8700 hackintosh back on its feet; previously it was working via an SSDT made with some fork of ssdtPRgen; I'm now trying to get it to work with plugin-type instead. I am currently stuck on early boot (More-or-less right after FakeSMC starts) and am not seeing any...

Ever notice how in IORegistryExplorer some devices might say compatible: <"vendor1,device1,","vendor2,device2","vendor3,device3"> The field is still of type Data; does anybody know if it's posbbile/knows the syntax to do such a thing?