Recent content by bilditup1

I had this same problem moving from 5104 to 5128. After experimenting for a while fruitlessly, including by reverting back to earlier versions of CLOVERX64.efi, I checked the installer log, which told me it had replaced AptioMemoryFix.efi with OpenRuntime.efi. Removing OpenRuntime and placing...

After updating to 10.15.7 from 10.15.3, my WiFi card, a BCM94352, stopped being recognized. Adding the AirportBrcmFixup.kext did the trick though, no other configuration needed.

At risk of flogging the dead horse here, using the proper SMBIOS and shikigva bootflags also solved my issues. In my case, I had a Haswell machine that I was trying to get to work with a couple of different known-good cards (RX 570, GT 710). The RX 570, I didn't have the iGPU set as headless in...

Does this work with Apple DRM, i.e. for Apple TV? I've been trying to find a cheap card for this purpose. ED: Looks like, no, per this new-ish chart. Drag. https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Chart.md

Installed without issues. Using the latest versions of AppleALC (1.4.5), WEG (1.3.6), and Lilu (1.4.1) w/Haswell integrated graphics (no DRM for Apple video apps but that's not new/I'll live) and on-board audio (ALC898). Pro-tip, if you've limited your USB patches to load with a specific version...

This is basically what I understood was happening--thanks for confirming! It may be something to bring up at bios-mods or win-raid, but they, too, may not want to touch this. Any case, at least for reference--win-raid has a bunch of ME-related resources that are kept continuously up-to-date...

Also, quick note: in WEG 1.3.5 + Lilu 1.4.0, shikigva flag 16 has been repurposed (as above github link shows). If you have it on in conjunction with flag 8 or 32 on a system with only Intel iGPU, you will KP with the error: It looks like there is no hope for iGPU DRM, at least not for Haswell...

Quick q: vit9696 says that iGPU DRM is not something they're gonna attempt to fix or work on, and will require flashing and provisioning Apple's ME, as per this comment at github: https://github.com/acidanthera/WhateverGreen/commit/7d30dd8a624d0d3b2d4882fcc689b9db4964efd5#r36079118 Any idea...

Yeah I hope so. But much more important is that they make one that works with FIS-based port multipliers. I have two ripping/burning/scanning towers that use them. The current card I have cost me maybe $20, plus another $10-15 for an extra eSATA bracket. Probably I will revert back to Sierra...

I was having some issues with KPs because of a kext for a now-incompatible peripheral (le sigh). I had kept it around in the my 10.11 and 10.12 folders under EFI/Clover/kexts, and it might have been in some old cache as well. I solved this by deleting the /OSX Install Data folder, removing the...

Right, I guess if it isn't detected, there's no reason for the kext to load. But I didn't want to unplug it; I was actively using the card in Windows 10. Does this Sonnet card support SiI port multipliers? ED: This is a $200 card. Even if it did work, I wouldn't pay that much.

Thanks for this, it got me halfway there. The other half was figuring out how to remove an errant kext (for an SiI3132 SATA/eSATA card that supports port multipliers) and rebuild caches from outside the regular environment, which I hadn't had to do in ages. More on that here. It appears that...

Can confirm that the SiI 3132 driver posted here causes High Sierra to kernel panic at boot after the initial half of the installation. Had to remove boot into a backup of Sierra, delete the kext *on the Sierra backup* *and* from /S/L/E on the High Sierra partition, and then run kextcache -i...

Finally! I had the same problem on El Capitan (yes, I'm upgrading now, but I wanted to have a complete El Cap system, including the recovery partition, on a USB key before moving on) and Sierra. Deleting and recreating the partition using that famous script did nothing for me. There should be a...

It appears that you posted after my last edit, which made clear that I went with #1, and then changed CsrActiveConfig to 0x43, per your previous post. Thanks for following up though :)