Recent content by dloprios97

Well I never thought that the apfs note was the cause. Because sometimes appears, sometimes not. Thank you so freaking much! Fixed! I mean, every single day I learn something new about this. I thought that the clover H_EC to EC patch was enough. Is this for USB power?

Hi guys. How you doing today? I hope very well. I'm here asking for help. I have a laptop: HP AC132LA with a i7 6500u (integrated graphics: 520) Samsung SSD, that has travelled with me since I learnt how to vanilla hackintosh. Somewhat since macOS Sierra. But now, since Catalina came along, I...

That is amazing.. It really is.. Many people have had success with this card due to the way different laptop brands handle PCI requests. If you what to know why your build is crashing. Just boot with verbose activated.

Maybe, what we need to figure out is why the system gets locked using the 4360 kext from Mojave.. It works perfectly fine for a hour or two..

What about when is used the vanilla 4360 driver in Mojave. After spoofing the card with a compatible id. In Mojave, 4360 is, at least, the only driver that works best for this card for almost two hours before blocking the system. No kernel panics whatsoever...

Before apply any kind of patch or kext into your system, you have to understand its behaviour and changes made. Just restore original kexts.

How has been your experience? Have you done this method?

No working at all... Just freezes the system

Did you got it working using your method (Yosemite kexts)? Or with Mojave kexts?

Using any of these methods slows the system and make it unusable after some minutes. And by using yours, crash the system at any given moment, especially at boot process.

So, now you got your WIFi working normally or just the AirPortBrcmNIC.kext is loaded?

I don't know what happens with this card, and why it doesnt load the right driver (AirPortBrcmNIC.kext).

Are you experiencing some kind of slowdown of your build in general using this patch?

@livacore Hell yeah! I don't use both methods in tandem. Right now, I'm working with the SSDT patch (used without any modification on S/L/E). Both methods result in slowdowns from time to time, but not kernel panics

Ill take that advice