Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/09/2020 in all areas

  1. I just removed a couple of garbage posts - Please stop pollute the topic, if you want to help, then just do it with kindness or just leave pls. BR fantomas
    3 points
  2. Funny you say that. I was so invested in having Netflix work in Safari yet the last time I watched Netflix on my PC was probably back in the mid 2000s...lol Also, I don't even use Safari.
    2 points
  3. @WizeMan Thanks for that buddy, that will stop DRMGATE for a few days but that’s all it will do because people can’t let it go...lol i guarantee that by the end of the week and when the post is lost in a sea of posts it will come up again. I have a real Mac (19,1) in the office that has the exact same problem so get off the subject people and just except that under various smbios it’s broken until Apple and or WEG fixes it. I don’t believe that even 5% of the people trying to make it Work are ever going to watch prime or Netflix on it anyway. It’s your TV, Tablet or your phone so what’s the big deal? I don’t get it,,,,, It’s 7.30am and I’ve just woken up and feel I need too take a minutes time out from my break/work in Vegas/CES to make this post as I can’t believe DRMGATE has reappeared on the thread again. yikes!!!!
    2 points
  4. I have done multiple exercises on Multiple SMBIOS's and EFIs for our builds as I had a Sapphire RX 580 Pulse 8GB and I just bought a Radeon Vega 56 two days ago. To save you all some time (and keep @AudioGod from having to answer multiple times about DRMGate) I am posting the report: The Verdict for macOS Catalina (10.15.2) with latest Lilu (1.4.1) + WhateverGreen (1.3.6 - latest commit 79398ee) pulled from the master branch is: Polaris Cards (e.g. Radeon RX580): The only thing you can get is Apple TV(+). Netflix and Prime Video as well as other DRM protected content does not work on Safari. You can try other browsers like Chrome or Firefox where you will be able to watch, but the resolution is not Full HD. To get Apple TV(+) you need SMBIOS iMac19,1 (@AudioGod's latest RX Polaris EFI is perfect) and instead of shikigva=80 use: shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 You will have Apple TV(+) working and NO CRASHES when trying to play DRM content on Safari. It will just not play, it won't crash. Navi & Vega Cards (e.g. RX 5700XT, Vega 56, Vega 64): There are two different routes you can go: Use SMBIOS iMac19,1 (the latest and greatest by @AudioGod is perfect) and leave shikigva=80 boot argument as is. This way you'll have Apple TV(+) AND Netflix on Safari. Amazon Prime does not work (the webpage reloads on a loop saying there was a problem) nor other DRM test streams (e.g. the BitMovin) which is a bummer but WEG development is in a good way and I think our patience and the developer's hard work will give fruits sooner or later. Use SMBIOS iMacPro1,1 (the last iMacPro1,1 EFI by @AudioGod is perfect even if it is not using ocQuirks but you can also get @AudioGod's latest iMac19,1 EFI and change the SMBIOS information and remove the shikigva boot flags using Clover Configurator) and disable your iGPU. You will have Apple TV(+), Netflix and Amazon Prime Video working on Safari in HD, but: SMBIOS iMacPro1,1 is not the Perfect match for our hardware and Power Management is not close to Coffee Lake CPU as the iMacPro1,1 is packing a XEON You lose SideCar (which might not be that big of a deal, but it is noteworthy) Other DRM test streams still not work (e.g. BitMovin Demo or EzDRM) which means it is not as perfect as it seems.
    2 points
  5. @vector sigma Please create a separate topic for HWMonitorSMC2. I think it it is necessary because someone is too angry.
    2 points
  6. I'm just going to run through some of the changes I made to RehabMan's BrcmPatchRAM project for it to function in macOS Catalina. I don't really have time to go any further with it but hopefully my research and testing can help get an official working version out. I'm using BrcmFirmwareData.kext, BrcmPatchRAM2.kext and BrcmBluetoothInjector.kext and place them inside EFI/CLOVER/kexts/Other BrcmBluetoothInjector.kext was not required on previous macOS releases but is on Catalina because of the following missing IOCatalogue methods: kxld[com.no-one.BrcmPatchRAM2]: The following symbols are unresolved for this kext: kxld[com.no-one.BrcmPatchRAM2]: IOCatalogue::addDrivers(OSArray*, bool) kxld[com.no-one.BrcmPatchRAM2]: IOCatalogue::removeDrivers(OSDictionary*, bool) kxld[com.no-one.BrcmPatchRAM2]: IOCatalogue::startMatching(OSDictionary*) Since these methods are no longer available they must be removed from the project. The easiest way to do this is to comment out publishPersonality() and publishResourcePersonality() methods from BrcmPatchRAM.cpp / BrcmPatchRAM.h. Also remove all calls to these methods in BrcmPatchRAM.cpp. The next issue is dealing with the 0xe00002c2 error when reading and writing to the BRCM hardware. Starting with BrcmPatchRAM::continuousRead() and BrcmPatchRAM::readCompletion() we need to add an kIODirectionIn option. ie. mReadBuffer = IOBufferMemoryDescriptor::inTaskWithOptions(kernel_task, kIODirectionIn, 0x200); IOReturn result = mReadBuffer->prepare(kIODirectionIn); IOReturn result = me->mReadBuffer->complete(kIODirectionIn); Next in BrcmPatchRAM::bulkWrite we need to add kIODirectionOut options. if (IOMemoryDescriptor* buffer = IOMemoryDescriptor::withAddress((void*)data, length, kIODirectionOut)) if ((result = buffer->prepare(kIODirectionOut)) == kIOReturnSuccess) if ((result = buffer->complete(kIODirectionOut)) != kIOReturnSuccess) Now that we don't have IOCatalogue::addDrivers, IOCatalogue::removeDrivers and IOCatalogue::startMatching methods to switch from using the uploader driver to native macOS driver we have to use BrcmBluetoothInjector.kext instead. So my Bluetooth device is a BCM20702A0 with VendorID 0x0A5C and ProductID 0x216F (Dell DW1560 4352+20702 M.2) located in internal USB port HS14. So I'll use it as an example for the following modifications. In BrcmPatchRAM2-Info.plist we need the following entry. Note the addition of the IOProbeScore. When the kext is loaded it will call BrcmPatchRAM::probe which will update the firmware and return NULL and then the BrcmBluetoothInjector.kext should load instead. <key>0a5c_216f</key> <dict> <key>CFBundleIdentifier</key> <string>com.no-one.$(PRODUCT_NAME:rfc1034identifier)</string> <key>DisplayName</key> <string>DW1560 Bluetooth 4.0 LE</string> <key>FirmwareKey</key> <string>BCM20702A1_001.002.014.1443.1572_v5668</string> <key>IOClass</key> <string>BrcmPatchRAM2</string> <key>IOMatchCategory</key> <string>BrcmPatchRAM2</string> <key>IOProviderClass</key> <string>IOUSBHostDevice</string> <key>IOProbeScore</key> <integer>4000</integer> <key>idProduct</key> <integer>8559</integer> <key>idVendor</key> <integer>2652</integer> </dict> In BrcmBluetoothInjector-Info.plist we need the following entry. Note again the addition of the IOProbeScore. We want the BrcmBluetoothInjector.kext to load the macOS kext after the firmware has been uploaded to the hardware. Since BrcmBluetoothInjector.kext has not been updated in a long time you may need to add your hardware manually to the plist. Note that your Bluetooth device VendorID / ProductID is not the same as your WiFi hardware and will not show up in your PCI list. You will need to look at the USB ports to get this info. <key>0a5c_216f</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport</string> <key>IOClass</key> <string>BroadcomBluetoothHostControllerUSBTransport</string> <key>IOProviderClass</key> <string>IOUSBHostDevice</string> <key>IOProbeScore</key> <integer>3000</integer> <key>idProduct</key> <integer>8559</integer> <key>idVendor</key> <integer>2652</integer> </dict> You will know the firmware is uploaded when its version in About This Mac->System Report...->Bluetooth shows something like: Firmware Version: v14 c5668 If it shows 4096 then the upload has failed. I will attach my compiled versions for people to help test. I'm not 100% sure if this is method is going to work so I'd appreciate feedback on it. Downloads (acidanthera)
    1 point
  7. Today we are publishing NVMeFix, a set of patches for IONVMeController. It currently only improves power management of non-Apple NVMe SSDs, but we will also be willing to fix other SSD incompatibility issues. If you observe a third-party SSD misbehaving, feel free to provide as much information as you can at our bugtracker https://github.com/acidanthera/bugtracker/. APST is short for Autonomous Power State Transition, a feature found in many modern SSDs. It allows the SSD to significantly reduce the power consumption when it detects the device has been idle for some time. Apple NVM driver, IONVMeFamily, does support third-party SSDs, but only uses PCI power management for them, so power is not conserved unless the computer sleeps or hibernates. For Apple SSD controllers, IONVMeFamily uses a vendor-specific command to switch to low-power mode. NVMeFix attempts to auto-detect APST support and configure the controller accordingly. Unfortunately, some SSDs have broken APST support; in this case NVMeFix will try to disable it. You may inject 8 byte property ps-max-latency-us=0 to the parent PCI device IODeviceTree entry in order to force disable APST. NVMeFix reports APST status via "apst" property of the IONVMeController in the IOService plane. Additionally, DEBUG configuration of the kext will log the used APST tables. The source code is available at https://github.com/acidanthera/NVMeFix. There is currently no builds available, as NVMeFix is only compatible with the latest, unreleased version of Lilu. Note that besides APST and PCI power management, NVMe also supports host-managed power setting, which should decrease power usage even more. Unfortunately, we could not yet get it to work reliably yet: if you're interested in technical details, let us know in the bugtracker. You may also find this on real Macs if you are using a third-party SSD. The kext should be compatible with stock bootloader -- just install it and Lilu to /Library/Extensions. Unfortunately, on Macs with the old NVMHCI DXE driver hibernation cannot be fixed from kernel side, as the bootloader hangs before it gets to the OS. This was at least the case in my tests with full-disk encryption on; I don't know if boot gets any farther without encryption.
    1 point
  8. @bdv Nice! I'm so glad to hear this. To be honest, I never expected this thread to have such a big impact on users. I thought it would be buried under other threads, few weeks after launch. I'm really happy to see people still finding it useful and being able to fix this annoying issue using this thread.
    1 point
  9. Extract bios video card into windows and place here
    1 point
  10. Thanks a lot This whole thread saved my day! I recently switch from Config1 to Config0, upgrading to 10.14.6 along the way. Got the problem with Quicklook and jpg, now solved using whatevergreen shiki parameters. Insanelymac is always my first stop when searching for information and help. SMBIOS configured as iMac 18,3: runs fine, sleeps and wakes ok, last remaining glitches to solve are writing custom SSDT for USB ports and pushing proc to 5GHz.
    1 point
  11. VirtualSMC is another topic https://www.insanelymac.com/forum/topic/335292-virtualsmc-—-smc-emulator/
    1 point
  12. Buon di , inizia col creare la USB con dentro Istall macOS e Clover bootloader cosi da rendere la USB bootabile .................... Copia questa EFI in USB , devi montare la partizione EFI della USB con Clover Configurator .......... Ho impostato la EFI x istallare quindi se tutto funziona successivamente devi procedere alla Post istallazione cercando di attivare le periferiche compatibili WI-FI NON compatibile e lettore SD NON va in Mac EFI.zip
    1 point
  13. Thanks for pointing out. Sadly you did not specify what that means actually. It's easy to miss something, that's why I suggested to make a diagram of ports of your comp. Please keep in mind that some ports are internal, until you haven't connected anything to these you can just disable these. Download motherboard images/manuals, make a good diagram with all ports listed and test all ports out with USB2/USB3 devices and make your choices and create USB ports configuration with Hackintool.
    1 point
  14. @Matgen84 , would you mind and redownload this EFI and just replace the SN,MLB,UUID and your DSDT for RX5xx. I replaced the USBPorts.kext from the older version so if it work, it should now work as well. i myself do not have a master board so i'm unable to verify anything. But i like to have the EFI's ready when @AudioGod returns next weekend ;-) Thank you for your testing again OpenCore-Fork-19,1-Aorus-Z390-Master-Navi-Vega.zip
    1 point
  15. Version 2.1

    3,383 downloads

    This app can be used to edit or create custom versions of the voodoo tsc sync kext, i have created it because i have seen many times peoples having troubles in finding the right version of voodoo tsc sync for their cpu, so i created a mac app that lets to edit or create a voodoo tsc kext and configure it for your system, i have included 3 ways to edit the kext: 1) configure using one of the existing templates (just chose one of the cpu models listed) 2) specifying the number of logical cores (threads) 3) manually editing the info.plist of the kext using the editor (still experimental, needs some improvements) This app uses a copy of the VoodooTSCSync in his Resourches folder, or you can open an existing version of VoodooTSC and edit it, there are some other useful features to discover, and new ideas are also welcome to improve this program, i know that with a plist editor you can do what this app does, but this is designed to be more user friendly than editing a plist file manually and just for accomplish the task of configuring this kext for your machines without looking on the web for that specific pre-configured version you need, just download this program and follow a few steps. Reference topic: VoodooTSCSync Configurator, create a custom version of voodoo tsc sync
    1 point
  16. Rev 4653 Fixed potential icon problem for apfs and hfs partition. Clover automatically detect partition icon according to partition type.
    1 point
×
×
  • Create New...