Search results

I don't have OpenCore so I am not 100% certain but it should be the same process given that it is a kext that you should make with the VGTab tool. You put it in your kext folder same you do with any other kext. I quote "https://dortania.github.io/OpenCore-Install-Guide/ktext.html#legacy-users"...

Read post #65 on topic 2. I mentioned that there

Yes, download the latest release from https://github.com/acidanthera/BrcmPatchRAM/releases

No issues with bluetooth in 10.15.5 as far as I am concerned

It seems as though you haven't been following instructions properly with each kext. You can't just throw kexts at the folder and expect your problems to be resolved. Each kext has instructions in their respective GitHub pages informing you on what to do or how to install. Also, some of these...

Which version of BrcmPatchRAM are you using? You should be using the latest release from: https://github.com/acidanthera/BrcmPatchRAM/releases Then, add the following files to your efi/clover/kexts/other: BrcmBluetoothInjector.kext BrcmFirmwareData.kext BrcmPatchRAM3.kext

I don't think you need to modify and compile it for DW1560 anymore. Just download the release, it is working. https://github.com/acidanthera/BrcmPatchRAM/releases

Nothing stands out from your EFI honestly. I assume, that the Bluetooth is working fine on Windows 10?

That's exactly how I have my DW1560 loaded. Are all your USB ports working properly? Both USB 2.0 and USB 3.1?

Video noise reduction? I just tried it on my system. No problems here. Not sure why this might be your case.

If you see "Firmware = v14 c4096" in About this Mac, you're firmware didn't update the BT card. DW1560 downloads firmware upon every boot. Rehabman and AcidAnthera explain this on their GitHub readme in the beginning (RAMUSB). In short: BrcmFirmwareData: loads upon boot BrcmPatchRam3: uploads...

Yeah I didn't have FCPX export issues with iMac19,1 but I did have iTunes, Netflix, etc DRM issues. It's up to you

The only modification I made was my Serial numbers, other than that this is my boot EFI. Good luck!

Right, I am exporting those as well with no issues. Maybe you have shiki=XXX arguments on your clover boot options? Under iMacPro1,1 you won't need those arguments.

No idea, I am using FCPX 10.4.8 and its fine. It uses both my CPU and GPU. What kind of file are you exporting? H.264?

Seems like the WhatEverGreen.kext got updated to fix some of these graphics issues so updating to the latest may work for you. However, all my issues went away when I switched my SMBIOS to iMacPro1,1. MacOS takes advantage of iGPU for rendering on FCPX (as has been explained in this thread)...

I modified it RehabMan's fork to accept Vegas 56 and 64. Here is the link from the fork I used several months ago to fix this problem. https://github.com/RehabMan/OS-X-FakeSMC-kozlek . No mods were done to HWSensors.app

I had the same problem, I actually had to modify/add missing video card declarations to add Vegas. Then compiled the app myself. I have it in my computer at home. In a few hours I can upload here, but you could do this yourself if you got Xcode and time. I will post back later with the upload

NOOOOOOOOOOOOOOOOOOOOOOO

YAAAAAAAAAAAAAAAYYYYYYYYYYYYYYYYYYYYYYYYY