Jump to content

Bcm943602CS bluetooth question on Monterey


Recommended Posts

Posted

This is my Hackintosh :

i5 9600k

Gigabyte z370 aorus ultra gaming

Asus rx580 4gb

BCM943602CS

 

I have some question. Hope I can find answer

1. On monterey. When I sleep then wake. Magic mouse scroll won’t work. I read something on Apple site. This is bug on Monterey ?
 

2. I tried to wake my Hackintosh with bluetooth device (magic mouse, bluetooth keyboard… ). But dont work. When Hackintosh sleep. Wifi/BT card is off. Dont have energy. Both of Hackintosh and Windows. Cannot wake by bluetooth devices. I read a topic from tonyx86 site. They said : This problem by wifi card bcm943602cs. Then they use fenvi t919 bcm94360cd. They can wake by bluetooth devices. <—- is it right ???? I wanna make sure then i can trade my wifi/bt card

hope i can find some good information. Thanks olarila

Posted (edited)

I tested with 3 ways

1. Only add bluetoolfixup.kext <--- after sleep/wake magic mouse can't scroll

2. Add bluetoolfixup.kext + BrcmFirmwareData.kext + BrcmPatchRAM3.kext <--- after sleep/wake magic still can't scroll

3. Add bluetoolfixup.kext + BrcmFirmwareData.kext + BrcmPatchRAM3.kext + BrcmNonPatchRAM2.kext <--- after sleep/wake magic still can't scroll

Edited by LilCe
  • Administrators
Posted

u need solution from devs

Enjoy!

  • Thanks 1

-Guides and Tutorials HERE

-Hackintosh Tutorial Database - HERE

-The largest EFI folder collection for Hackintosh HERE

-Support Olarila Vanilla Hackintosh by making a donation HERE

-Professional Hackintosh Support since 2006 HERE

Posted

I use sleepwatcher with this:

https://github.com/acidanthera/bugtracker/issues/1821#issuecomment-1001007081

Actually you are installing a launchd daemon that emulates the behavior of old versions of SleepWatcher (executes rc.wakeup, rc.sleep and other scripts). It's unnecessary, as you can put the action directly into the launchd plist. Here is the example that I promised:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Label</key>
	<string>de.bernhard-baehr.sleepwatcher</string>
	<key>ProgramArguments</key>
	<array>
		<string>/usr/local/sbin/sleepwatcher</string>
		<string>-w</string>
		<string>bash -c "sleep 5 &amp;&amp; killall -9 bluetoothd BlueTool"</string>
	</array>
	<key>RunAtLoad</key>
	<true/>
	<key>KeepAlive</key>
	<true/>
</dict>
</plist>

Put int into /Library/LaunchDaemons with a .plist extension.

However, restarting bluetoothd and BlueTool doesn't always solve the issues. Sometimes the module itself seems to get stuck and can't be enabled even by restarting macOS, it needs shutdown and cold boot.

  • Like 1

MacOS X 10.7 on Biostar TH55XE, Intel Core i3 560 3,3 Ghz, Transcend HyperX 2x2 Gb DDR3, HIS Radeon HD5770 1 Gb DDR5, SATA: HDD 1 Gb, DVD-RW LG

Posted
On 12/26/2021 at 3:12 PM, Creo said:

I use sleepwatcher with this:

https://github.com/acidanthera/bugtracker/issues/1821#issuecomment-1001007081

Actually you are installing a launchd daemon that emulates the behavior of old versions of SleepWatcher (executes rc.wakeup, rc.sleep and other scripts). It's unnecessary, as you can put the action directly into the launchd plist. Here is the example that I promised:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Label</key>
	<string>de.bernhard-baehr.sleepwatcher</string>
	<key>ProgramArguments</key>
	<array>
		<string>/usr/local/sbin/sleepwatcher</string>
		<string>-w</string>
		<string>bash -c "sleep 5 &amp;&amp; killall -9 bluetoothd BlueTool"</string>
	</array>
	<key>RunAtLoad</key>
	<true/>
	<key>KeepAlive</key>
	<true/>
</dict>
</plist>

Put int into /Library/LaunchDaemons with a .plist extension.

However, restarting bluetoothd and BlueTool doesn't always solve the issues. Sometimes the module itself seems to get stuck and can't be enabled even by restarting macOS, it needs shutdown and cold boot.

Tks bro. I fixed that bug with this way. But still waiting for apple devs fix it or kext for fix it.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...