Bluetooth not detected (USB) BCM94352Z

[Enigmahack]

There is macbuild.tool.

Assuming you have Xcode installed, usage:

./macbuild.tool

Awesome - thanks for that.

So I downloaded it, compiled, installed, and tested. It's the same error unfortunately, so I reverted back to what was slower but worked without KP on shutdown.

 

[RehabMan]

Awesome - thanks for that.

So I downloaded it, compiled, installed, and tested. It's the same error unfortunately, so I reverted back to what was slower but worked without KP on shutdown.

You might want to report the problem to vit9696 for further investigation.
Of course, it might be an indication of something else wrong in your setup...

 

[Enigmahack]

You might want to report the problem to vit9696 for further investigation.
Of course, it might be an indication of something else wrong in your setup...

You're absolutely correct. I'll report to Vit9696 anyway, and if we're able to identify either A: another problem in my setup or B: a problem in the memory efi, I see either situation as a win. I just don't really want to waste time going down the wrong rabbit hole. (Trying to troubleshoot with a broken configuration)

Thanks

 

[RehabMan]

You're absolutely correct. I'll report to Vit9696 anyway, and if we're able to identify either A: another problem in my setup or B: a problem in the memory efi, I see either situation as a win. I just don't really want to waste time going down the wrong rabbit hole. (Trying to troubleshoot with a broken configuration)

Thanks

If you want me to check what you have, attach "Problem reporting" files (with AptioMemoryFix.efi setup).

 

[Enigmahack]

If you want me to check what you have, attach "Problem reporting" files (with AptioMemoryFix.efi setup).

I definitely will - Thanks RehabMan.

 

[Enigmahack]

If you want me to check what you have, attach "Problem reporting" files (with AptioMemoryFix.efi setup).

Okay, here are the error reporting logs for the AptioMemoryFix.efi.

Note this error only occurs after a shutdown. Restarts work fine, and it seems to KP after the shutdown process starts. From a user-perspective, there is no obvious indication that anything went wrong until you start the PC again, and are greeted with the "Your system shut down" dialog during boot, and again after logging in with the KP logs. (Also included)

 

[RehabMan]

Okay, here are the error reporting logs for the AptioMemoryFix.efi.

Note this error only occurs after a shutdown. Restarts work fine, and it seems to KP after the shutdown process starts. From a user-perspective, there is no obvious indication that anything went wrong until you start the PC again, and are greeted with the "Your system shut down" dialog during boot, and again after logging in with the KP logs. (Also included)

Strange that your ioreg shows 10.12.6 installed when this thread is in the High Sierra forum...
Same panic if you actually install 10.13.3?

Note that you have work to do regarding ACPI patching (eg. _OSI("Darwin") handling). Suggest _OSI->XOSI + SSDT-XOSI.aml. Remove Fixes/FixDarwin and Fixes/FixUSB.

Note that if you open your patchmatic -extract DSDT.aml, you find a lot of troublesome errors:

// /*
// Error: Unknown opcode 0x40 at table offset 0x5226, context:
//   5216: 44 54 47 50 68 69 6A 6B 71 60 A4 60 45 53 01 00  // DTGPhijkq`.`ES..
//   5226: 40 19 00 0D 4D 57 31 33 01 4D 57 31 34 01 00 11  // @...MW13.MW14...
//   5236: 00 20 00 0D 4D 42 31 33 01 4D 42 31 34 01 00 11  // . ..MB13.MB14...
//  */
// /*
// Error: Unknown opcode 0x19 at table offset 0x5227, context:
//   5217: 54 47 50 68 69 6A 6B 71 60 A4 60 45 53 01 00 40  // TGPhijkq`.`ES..@
//   5227: 19 00 0D 4D 57 31 33 01 4D 57 31 34 01 00 11 00  // ...MW13.MW14....
//   5237: 20 00 0D 4D 42 31 33 01 4D 42 31 34 01 00 11 00  //  ..MB13.MB14....
//  */
// /*
// Error: Unknown opcode 0x20 at table offset 0x5237, context:
//   5227: 19 00 0D 4D 57 31 33 01 4D 57 31 34 01 00 11 00  // ...MW13.MW14....
//   5237: 20 00 0D 4D 42 31 33 01 4D 42 31 34 01 00 11 00  //  ..MB13.MB14....
//   5247: 40 0E 50 52 32 5F 20 50 52 32 4D 20 50 52 33 5F  // @.PR2_ PR2M PR3_
//  */
// /*
// Error: Unknown opcode 0x40 at table offset 0x5247, context:
//   5237: 20 00 0D 4D 42 31 33 01 4D 42 31 34 01 00 11 00  //  ..MB13.MB14....
//   5247: 40 0E 50 52 32 5F 20 50 52 32 4D 20 50 52 33 5F  // @.PR2_ PR2M PR3_
//   5257: 20 50 52 33 4D 20 08 58 46 4C 54 00 14 09 5F 53  //  PR3M .XFLT..._S
//  */
// /*
// Error: Unknown opcode 0x40 at table offset 0x5226, context:
//   5216: 44 54 47 50 68 69 6A 6B 71 60 A4 60 45 53 01 00  // DTGPhijkq`.`ES..
//   5226: 40 19 00 0D 4D 57 31 33 01 4D 57 31 34 01 00 11  // @...MW13.MW14...
//   5236: 00 20 00 0D 4D 42 31 33 01 4D 42 31 34 01 00 11  // . ..MB13.MB14...
//  */
// /*
// Error: Unknown opcode 0x19 at table offset 0x5227, context:
//   5217: 54 47 50 68 69 6A 6B 71 60 A4 60 45 53 01 00 40  // TGPhijkq`.`ES..@
//   5227: 19 00 0D 4D 57 31 33 01 4D 57 31 34 01 00 11 00  // ...MW13.MW14....
//   5237: 20 00 0D 4D 42 31 33 01 4D 42 31 34 01 00 11 00  //  ..MB13.MB14....
//  */
// /*
// Error: Unknown opcode 0x20 at table offset 0x5237, context:
//   5227: 19 00 0D 4D 57 31 33 01 4D 57 31 34 01 00 11 00  // ...MW13.MW14....
//   5237: 20 00 0D 4D 42 31 33 01 4D 42 31 34 01 00 11 00  //  ..MB13.MB14....
//   5247: 40 0E 50 52 32 5F 20 50 52 32 4D 20 50 52 33 5F  // @.PR2_ PR2M PR3_
//  */
// /*
// Error: Unknown opcode 0x40 at table offset 0x5247, context:
//   5237: 20 00 0D 4D 42 31 33 01 4D 42 31 34 01 00 11 00  //  ..MB13.MB14....
//   5247: 40 0E 50 52 32 5F 20 50 52 32 4D 20 50 52 33 5F  // @.PR2_ PR2M PR3_
//   5257: 20 50 52 33 4D 20 08 58 46 4C 54 00 14 09 5F 53  //  PR3M .XFLT..._S
//  */

Those errors are not in native DSDT, so it must be caused by some of the "Fixes" you're applying from Clover. The two I mention are not recommended.

And KextsToPatch should be cleaned up. Don't include patches for other versions, especially if not protected with MatchOS.

Are your kexts installed to /L/E (not /S/L/E)?

 

[Enigmahack]

Strange that your ioreg shows 10.12.6 installed when this thread is in the High Sierra forum...
Same panic if you actually install 10.13.3?

Funny story. Maybe not funny. When I started this thread, it *was* High Sierra. There was a boot problem I couldn't get past because I installed a kext I shouldn't have but had no way into the OS to remove it (nor from externally bootable drives due to APFS) so decided to start from scratch and follow your guides more closely to try and eliminate errors. I haven't bothered to go 'up' to High Sierra again, but didn't know how to move this thread over to the appropriate area.

Note that you have work to do regarding ACPI patching (eg. _OSI("Darwin") handling). Suggest _OSI->XOSI + SSDT-XOSI.aml. Remove Fixes/FixDarwin and Fixes/FixUSB.

Okay - I'll investigate this more closely.

Note that if you open your patchmatic -extract DSDT.aml, you find a lot of troublesome errors:

**Truncated code**

Those errors are not in native DSDT, so it must be caused by some of the "Fixes" you're applying from Clover. The two I mention are not recommended.

Totally understood.

And KextsToPatch should be cleaned up. Don't include patches for other versions, especially if not protected with MatchOS.

Agreed, will clean up.

Are your kexts installed to /L/E (not /S/L/E)?

Most but not all. There are a couple (The FakePCIID_Broadcom ones for wifi) that don't work from within L/E for whatever reason. They start working as soon as I put them into S/L/E however. I wouldn't think this should matter, but it seems to. I'll re-review and try and move them all over and troubleshoot if they're not working. Perhaps it was a cache/permission issue, will reinvestigate. Right now, the only ones that are in S/L/E are FakePCIID, FakePCIID_Broadcom_Wifi and Lilu.

 

[RehabMan]

Most but not all. There are a couple (The FakePCIID_Broadcom ones for wifi) that don't work from within L/E for whatever reason. They start working as soon as I put them into S/L/E however. I wouldn't think this should matter, but it seems to. I'll re-review and try and move them all over and troubleshoot if they're not working. Perhaps it was a cache/permission issue, will reinvestigate. Right now, the only ones that are in S/L/E are FakePCIID, FakePCIID_Broadcom_Wifi and Lilu.

FakePCIID.kext + FakePCIID_Broadcom_WiFi.kext work just fine in /L/E.