Recent content by muffie8

Fixed the issue by updating FakeSMC. But, still a lot to do as takes ages to shutdown. Probably it's a kext mess (Library/Extensions ; CLOVER/Other ; ...) plus some SMBIOS/DSDT details. *PS* The only reason why I'm "afraid" of OpenCore is: I have 1 NVMe (Windows 10), 3 SSDs (being one with an...

Thank you. Will try that @ night. *PS* I recorded a 60fps video of the KP and, looks like it’s CPU sensors related…

Thank you for the response. I did tried to clean NVRAM by pressing F11 on Clover + trying to use sudo nvram -c while on safe mode. same error, same "incomplete" KP screen. I assume that, with CLOVER I need to edit my DSDT configuration, correct?

Nvram are not those “fixed files”? I remember using something like that when I first configured it (I’m stuck at HS due to my 1080). My processor is “equivalent” to a 9900k. With slower memory (2800mhz). I managed to squeeze 5ghz turbo on 2 cores and up to 4.6 on all 8.

Any idea about how can I check that message in a log file? Or maybe page up?

Using Clover It was working fine until I updated my BIOS to receive the mutant i9 mobile processor (qtj1). Boots ok in Safe Mode but I don’t remember how to check any logs. Normal boot gives me a KP. I was able to take a picture of the KP screen. Any tips about how can I debug and fix it...

Well, ok. Two days of intensive work. My CLOVER is cleaner, I'm using less Kexts, and NVRAM is correctly working. I manually checked rc.scripts at /etc/rc.shutdown.d/ (called: 80.save_nvram_plist.local), and it's all fine. I'll take care about iMessage later, but what's really annoying me now...

rc scripts seems to be working just fine. now I'll check for their execution on shutdown log.

Well, I always select the same BOOT disk (then, the same CLOVER) when I want to load high sierra. But I think the problem Im having is on shutdown/restart. As EFI partition is not automatically mounted during my regular usage. Isn't that the case?

Yep. Check the diskutil list disk3s1 is my EFI partition where nvram.plist is. disk3s2 is my main hbSierra (High Sierra, as I have a 1080) installation. disk3s1 is not normally mounted during operation. So, that's probably why is not being able to save neither shutdown. It's probably trying...

nvram.plist is @ my EFI partition, not on my "High Sierra" partition. And, my EFI partition is not always mounted when Im using my hackintosh. Only during boot.

I think Im getting the logic of it. nvram.plist is just a text file database containing nvram variables. theres something to load those at boot and something else to save to it on shutdown/restart. Im pretty sure it's a matter of what's available during boot and shutdown/restart process. For...

Well, as for post #1, that was exactly what I had used in the first place. I'm able to retrieve TestVar between reboots. As for RC Scripts, I also already have it installed at my main boot volume. Actually, as I have several different SSDs on my machine, I always choose the one I want to use...

Thanks Thanks. I already have RC Scripts. Maybe I have too much stuff inside Clover's drivers64UEFI and some APTIO is conflicting with RC? About the run exactly, I'm really sorry. Its a 9 page post with several tries and nothing conclusive. I really don't know exactly what to try...