Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About muttonhead411

  • Rank
    Advanced Member

The recent visitors block is disabled and is not being shown to other users.

  1. Hi @Hervé, Looks like EC patching is already in place, as per your Catalina specific ACPI patches. Still have no idea what else to try to get this working. Here's my Clover folder as well, let me know if you can see something I cant. Or suggest how else I should troubleshoot. Thank you once again CLOVER.zip
  2. Whops I found the thread. I’ll check again. Maybe I’ll post by clover folder next. Seems like a Catalina specific issue.
  3. @Hervé apologies but which thread are you referring to on our home page? I have checked both the pinned post, don’t see anything related to this. Also I’m still on DW1820A, so its probably not that issue. Odd though, because I am able to boot clover and launch my Mojave’s installation fine, its just not able to boot Catalina installer. Freezes at some point with the no entry sign...
  4. I basically used your catalina boot pack as it is without changing anything. How can I check to confirm @Hervé?
  5. Hi, I'm also facing the same issue as above, but deleting DSDT.aml did not help. I'm stuck at boot with this on screen, before it freezes. Any guidance on what else to try? Its odd cause my Mojave installer boots up fine
  6. Thanks @Jake Lo and @nickhx for setting the context. Looks like still some ways of work to go... Thanks again!
  7. May we know what issue you are referring to? Also could you share a bit of your knowledge why you are using a combination of 3 of these kext? as rehabman usually recommends a combination of either an injector or patchram, but not both together..
  8. I'm not sure how you did it... but you somehow got it to work.... I'm gonna keep testing for now... Wondering if you could make a version that works via L/E if possible... Thanks.
  9. @tazorac8 Bluetooth working reliably on our card hasn’t have a permanent fix yet. Only known way so far is to get the drivers loaded from windows, then reboot to Mac OS for Bluetooth to work stable. To do this you need an injector on Mac side, without firmware upload functionalities. Otherwise yep DW1560 seems to be a popular card for full functionalities. Note that it’s not plug and play OOB functionality. You will need kext to get it working...
  10. A few questions for you... how does the device work on windows with pin masked and not masked? If they work normally then it’s more than likely a configuration issue on your Hackintosh. also Herve mentioned before that the functiontionality of wifi and Bluetooth are different. All DW1820A will have Bluetooth detected as long as you have rehabman kext loaded. Getting Bluetooth usable with a connected device is the tricky one. Pin masking is required for your version of card to work with WiFi.
  11. I've been doing further testing on my latitude, and this is still the only reliable way of getting bluetooth to work on DW1820A, via @Naidis I tried extracting the exact .hex file from windows and attempting to upload it on MacOS, but that exhibits the same unstable behaviour as other firmwares unfortunately. Hopefully we find a better way forward somehow...
  12. Looks like we're making very good progress today... very happy. For the adventurous who prefer to keep kext in L/E, feel free to try the attached files and report back with your results for bluetooth. If firmware was uploaded successfully, you should see the following version in Sys Info: BrcmPatchRAM2.kext.zipBrcmFirmwareRepo.kext.zip
  13. @Naidis - you were spot on about the root cause being firmware uploads not working correctly using rehabman kext. I've managed to upload firmware from windows, and keep it persistent in Mac OS, version 4689 on both windows and Mac. Wireless bluetooth mouse now works correctly. I'm going to continue to test it out over a few days.
  14. @Naidis am I understanding correctly that with your suggestion, we would need to boot windows first every time before booting mac os?
  15. Since we have it a bit of roadblock with bluetooth, I decided to go out and buy a bluetooth dongle to test out. I bought the following CSR Bluetooth USB dongle: Steps that I followed: - removed all traces of Rehabman's kext so that bluetooth is not showing in System Information - plugged in bluetooth dongle What happens next is surprising: - Bluetooth dongle lights up, it is working - Bluetooth shows up on menubar, bluetooth is functioning But... when it try to connect to my bluetooth mouse, it does NOT work. It exhibits the same behaviour as DW1820a! Device discovery is fine, but it cannot connect to any device. I'm beginning to think it is not a hardware issue (since both dongle and dw1820a both don't work), but the way we are configuring bluetooth on our machines Paging for @Hervé @Jake Lo. Any thoughts on what could be happening?
  • Create New...