Contribute
Register

The bluetooth of BCM94352z does not work after sleep

Status
Not open for further replies.

Attachments

  • BrcmPatch_log.txt
    56.7 KB · Views: 135
  • kernel.log.zip
    5.5 MB · Views: 121
Last edited:
lucienpan said:
I extracted the log for BrcmPatchRam as BrcmPatch_log.txt.
Also, I put the complete log file for today here as kernel.log.zip, just in case.
Click to expand...

You will need to isolate the BrcmPatchRAM logs that apply only to the failure case.
Impossible for me to know which specific logs to look at as I have no knowledge regarding when the problem occurred.
 
RehabMan said:
You will need to isolate the BrcmPatchRAM logs that apply only to the failure case.
Impossible for me to know which specific logs to look at as I have no knowledge regarding when the problem occurred.
Click to expand...
Sorry for that. I put here the BrcmPatch_log file within the file a brief explanation.
 

Attachments

  • BrcmPatch_log.txt
    50 KB · Views: 155
lucienpan said:
Sorry for that. I put here the BrcmPatch_log file within the file a brief explanation.
Click to expand...

No idea what you mean by "boot procedure was interrupted"...
 
RehabMan said:
No idea what you mean by "boot procedure was interrupted"...
Click to expand...
As explained in #24"
And I have found the same phenomenon if I interrupt a booting process (by pressing the power button at the screen with terminal outputs when booting with "-v" flag) and then boot again."

If I interrupt the booting procedure like this, the similar phenomenon (bluetooth unavaliable) happens, just the same as what happens in the long sleeping procedure.
 
lucienpan said:
Sorry, attached again.
Click to expand...

Comments:
- MacBookPro14,3 is a poor choice. Use MacBookPro14,1 or MacBookPro11,1
- VoodooTSCSync should not be needed (remove)
- IGPU not connected to anything? (if so, you should disable it or use an ig-platform-id with no connectors)
- NVMe may cause delay at boot/other problems (try with SATA M.2 instead)
- you forgot to install SATA-100-series-unsupported.kext
- SBUS Fix patch (SSDT-SMBUS.aml) not applicable to your hardware, remove
- your ACPI configuration is wrong (if you disassemble your patchmatic -extract, you will see duplicate symbols: iasl -da -dl *.aml)
- your drivers64UEFI content is wrong (see laptop Clover guide)
 
RehabMan said:
Comments:
- MacBookPro14,3 is a poor choice. Use MacBookPro14,1 or MacBookPro11,1
- VoodooTSCSync should not be needed (remove)
- IGPU not connected to anything? (if so, you should disable it or use an ig-platform-id with no connectors)
- NVMe may cause delay at boot/other problems (try with SATA M.2 instead)
- you forgot to install SATA-100-series-unsupported.kext
- SBUS Fix patch (SSDT-SMBUS.aml) not applicable to your hardware, remove
- your ACPI configuration is wrong (if you disassemble your patchmatic -extract, you will see duplicate symbols: iasl -da -dl *.aml)
- your drivers64UEFI content is wrong (see laptop Clover guide)
Click to expand...
Thank you very much, Rehabman.
-I have changed the smbios to MacbookPro 11.1. But why 14.3 is a poor choice? Is it because that the serial number of the macbookpro 14.3 can be collide with a real mac most probably?
-Cannot remove VoodooTSCSync. Once removed, I cannot loggin the system.
-Yes, the IGPU do not connect to anything, this is a G-sync panel. seems that the IGPU has been by-passed physically.
I use an ig-platform-id with 0x12345678 in clover now.
- Maybe a future plan to install a SATA M.2 :)
-What is SATA-100-series-unsupported.kext for? My SSD and HDD seem work fine without it already.
-Have removed the SSDT-SMBUS.aml.
-Have fixed the ACPI configuration.
-removed unused .efi in driver64UEFI

And the bluetooth problem still exist in the sleeping procedure. I think this is due to the firmware uploading failure.

I am going to give up. (Not a big problem, just a little bit not perfect...)
 

Attachments

  • debug_741.zip
    3.8 MB · Views: 141
Last edited:
lucienpan said:
But why 14.3 is a poor choice?
Click to expand...

It is dual GPU.

-Cannot remove VoodooTSCSync. Once removed, I cannot loggin the system.
Click to expand...

Might be BIOS setting issue regarding C-states.

-Yes, the IGPU do not connect to anything, this is a G-sync panel. seems that the IGPU has been by-passed physically.
I use an ig-platform-id with 0x12345678 in clover now.
Click to expand...

You should use an ig-platform-id without any connectors, such as 0x59120003.

-What is SATA-100-series-unsupported.kext for? My SSD and HDD seem work fine without it already.
Click to expand...

It causes correct drivers to load for your SATA device.
Your ioreg shows incorrect drivers.

And the bluetooth problem still exist in the sleeping procedure. I think this is due to the firmware uploading failure.
Click to expand...

The ioreg you attached shows BT working.
 
lucienpan said:
Thank you very much, Rehabman.
-I have changed the smbios to MacbookPro 11.1. But why 14.3 is a poor choice? Is it because that the serial number of the macbookpro 14.3 can be collide with a real mac most probably?
-Cannot remove VoodooTSCSync. Once removed, I cannot loggin the system.
-Yes, the IGPU do not connect to anything, this is a G-sync panel. seems that the IGPU has been by-passed physically.
I use an ig-platform-id with 0x12345678 in clover now.
- Maybe a future plan to install a SATA M.2 :)
-What is SATA-100-series-unsupported.kext for? My SSD and HDD seem work fine without it already.
-Have removed the SSDT-SMBUS.aml.
-Have fixed the ACPI configuration.
-removed unused .efi in driver64UEFI

And the bluetooth problem still exist in the sleeping procedure. I think this is due to the firmware uploading failure.

I am going to give up. (Not a big problem, just a little bit not perfect...)
Click to expand...

Did you get the solution for this?
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top