Jump to content

dolgarrenan

Members
  • Content Count

    25
  • Joined

  • Last visited

About dolgarrenan

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

629 profile views
  1. dolgarrenan

    X299X Designare 10G build

    That's a shame, but don't worry, we will make it work somehow! I have tried the SmallTree.kext and I can say it work as expected, .kext has to be located in L/E/, it don't work through clover injection.
  2. dolgarrenan

    X299X Designare 10G build

    I'll try asap! BTW, I have tried with the SSDT you posted and its giving me an error, it stays on: apfs_module_start_1683: Any ideas?
  3. dolgarrenan

    X299X Designare 10G build

    This is awesome work! SSDT much better than just clover on the fly dsdt patch, thanks for the explanation!
  4. dolgarrenan

    Help,X550-T2 LAN driver

    I have moved the three .kext to the EFI partition and they work as expected on 10.15.3 but I am still not sure if this will unlock full potential, I think I'm not getting full bandwitch this way, perhaps with just the SmallTree driver instead of having to load 3 extensions just for one device. I have tried to swap subsystemID's with ubuntu to no avail, for some reason ethtool does nothing when entering the correct code... Any ideas? @MaLd0n@liuhongxin1993??
  5. dolgarrenan

    X299X Designare 10G build

    Oh yeah I know it works, I'm currently using it, I wanted to credit someone for the patch in another post. How did you managed to find out where to look to replace? In the ACPI patch post there isn't much explanation I think..
  6. dolgarrenan

    X299X Designare 10G build

    Are you the creator of the patch?
  7. dolgarrenan

    X299X Designare 10G build

    Code is to be added to you DSDT section in .plist
  8. dolgarrenan

    X299X Designare 10G build

    Can you please share your BIOS settings and EFI settings?? I have not been able to make it work so far
  9. Weird indeed, I didn't notice tbh! this is nuts... and this is the output from log with hackintool 2019-07-24 08:57:47.752615+0200 localhost kernel[0]: (BroadcomBluetoothHostControllerUSBTransport) <BroadcomBluetoothHostControllerUSBTransport`BroadcomBluetoothHostControllerUSBTransport::start(IOService*)> **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed (matched on Device) -- 0xc000 **** There is only one mention, and not even the same value as yours I will this a shot and see what comes up, also I'd like to mess around with the "how to" explanation you have in your github repo I don't think that is an issue either.. Prior to writing in this post, I tried also to remove (with rehabman's set of kext) all other instances of frimwares and id's, just to leave the one I need and use the uncompressed .hex (which should work) and nothing happened.. BTW, why it only shows v4689 instead of v8785?? that is an odd behaviour isn't it? EDIT: Today, as I turn on the pc it welcomes with a working BT.. I'm very confused, it didn't work last night when I turned off the computer... Here is the log, but as you mentioned, it still loads BcrmPatchRAM2 twice¿?¿? BrcmFWData+BrcmRAM2+BrcmBTInjector release V 24-07 - BT loaded and working.rtf EDIT: Tried a complete power cycle and reboot, again, BT detected but only working for 30 seconds, after it stops BT functionality.. here is the log BrcmFWData+BrcmRAM2+BrcmBTInjector release V 24-07 - BT loaded not working.rtf An here is the log of BroadcomBluetoothHostControllerUSBTransport 2019-07-24 09:34:02.848833+0200 localhost kernel[0]: (BroadcomBluetoothHostControllerUSBTransport) <BroadcomBluetoothHostControllerUSBTransport`BroadcomBluetoothHostControllerUSBTransport::start(IOService*)> **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed (matched on Device) -- 0x3000 ****
  10. I've seen it, but still works funny. Thats where the kext are located, thats what I meant by C/K/O I mean that once I cold reboot even if prior to cold boot it was working, it just stops working, BT loads but "connected devices" don't work, they just show as connected and, for instance, the magic mouse 2 shows erratic battery percentage, goes from full, to empty, to disconnected to connected and so forth, but It doesn't work.. Tried that and it is a no go, no difference so far. I've tried to replicate the "working" method without success again, I wanted to capture a log of when the device is working properly but I just haven't been able.. I've done everything the same way I did yesterday without even one success.. At any rate, I've done several trials and have saved all the logs. Every log has a little explanation of what was used when the log was created. Every log was recorded after a cold boot, to have things from scratch (removed power for 30 secs and made sure the was nothing connected to the pc), all kext where located at C/K/O, nothing in L/E. Hope they help somehow, today is even worse than yesterday Logs.zip EDIT: it worked once after a reboot and adding couple of arguments on plist (brcmfx-driver=2 and compatible device 14e4,43a0), below the log. Cold booted again and no BT joy... Again Log BrcmFWData+BrcmRAM2+BrcmBTInjector release version - BT loaded and working.rtf
  11. Hi there, thank you for all your help so far! Yep, on Mojave there is just no way this damn DW1820A activates the BT after cold boot. The only way seems to be pre-loading firmware in W10, then booting up macOS.. @RehabMan has been a no show, so i'm guessing he is tired of all the wining and complaining from people, so I guess it will have to be a Catalina upgrade at a sooner-than-expected time.. Well, I hope someone smart can really figure out what is going on and how to fix it.
  12. I have already tried, they are a no go with DW1820A, bluetooth is impossible, wifi works correctly. I'm going desperate..
  13. Indeed. I've had several cards installed in this same build and other similar builds (DW1560), right now is sort of working with your .kexts but it has to be right next to the antena, otherwise it won't work at all, as soon as i move the device away, there is choppy behaviour or connection loss... I have looked over at the Dell website and the latest I could find is the 12.0.1.1105, which is the one I have loaded, but still it doesn't work as it should.. Perhaps moving to Catalina would make the difference?? I don't see why this kext wouldn't work under Mojave 10.14.6... Perhaps you've modified the BrcmBluetootInjector.kext in a way that only runs in Catalina?? I've looked everywhere and could not find the kext, I've even posted an issue at @RehabMan repo but have received no reply.. Unfortunately for me moving to Catalina is not an option yet (apps and whatnot) but I need this bluetooth functionality.. Here the .kext with the latest firmware, which by chance is v4689 as it is loaded by windows correctly. BrcmFirmwareRepo.kext.zip BrcmPatchRAM2.kext.zip
  14. Here is the log without firmware update from Windows. Here is the IOReg screen Funny because I try to manually edit BrcmPatchRAM2.plist in order to load latest Firmware in your repo (v6820) but it just doesn't work shows fw V4096.. I'll try your firmware with old set of .kext (RehabMan's) to see if any difference..
  15. Hi there @headkaze I have mixed results with your method, at the end, in order to have the DW1820A work (0xa5c_6412) I have to boot into W10 or Linux, then it works. If I turn off the computer and cut the power (like a power cycle) when turns on again my Bluetooth doesn't work anymore.. Here is a screenshot of log (.kext are located at /CLOVER/Kext/Other y previously had them inside /Library/Extensions/)
×