Contribute
Register

Bluetooth dongle takes long time to load (Kext problem?)

Status
Not open for further replies.
Joined
Oct 20, 2011
Messages
2
Motherboard
Gigabyte P55-UD5
CPU
3.2 Ghz Intel Core i7
Graphics
ATI Radeon HD 5870
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Hey!!

I finally installed Mountain Lion 10.8.2 and everything (even onboard audio codecs) seem to work.

My only hitch so far is that my bluetooth dongle (D-link DBT-122) takes a couple of minutes to load after the OS has started. Upon doing a "sudo kextcache -v 1 -a i386 -a x86_64 -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions" I got the following output:

IOBluetoothUSBDFU.kext - no compatible dependency found for com.apple.iokit.IOUSBFamily.
IOBluetoothUSBDFU.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
AppleUSBAudio.kext - no compatible dependency found for com.apple.iokit.IOUSBFamily.
AppleUSBAudio.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
Created mkext archive /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext.

Can anyone help resolve this with me?

All the best and thanks for a great site!

I fixed both of these by removing them and using KextBeast to re-install!
 
Hi guys,
Here is my guide I posted elsewhere, but as you can see, i'm having a couple of issues.

*EDIT* Currently working on fixing computer waking itself up immediately after forcing it to "sleep", when this occurs bluetooth gets knocked out as well for a few seconds. Currently only bullet point 3 100% working. I will let it hibernate and report back.


*Edit 2*
Computer display will turn off, but computer will not completely hibernate. Side scroll bug was present during one of the tests.


Hi guys,


if anyone was in same boat as me:



  • bluetooth wouldn't work properly after sleep - side scrolling stopped working
  • bluetooth delay on startup, had to wait several seconds to become operational.
  • allow bluetooth devices to wake this computer greyed out
I have the fix ( Full credit to Gonzo here (link removed as per forum rules)


Ok, to the guide:


Step 1:
You need to obtain (In dec, not hex) your DeviceID, and ProductID.
Go to system profiler and under bluetooth hardware settings note your broadcom devices productID, and vendorID
These will be in Hex, so we need to convert them to dec.


Go here: http://www.binaryhexconverter.com/hex-to-decimal-converter


Convert both values, and copy them somewhere.


Step 2:
Navigate to S/L/E and locate IOBluetoothFamily.kext
BACK IT UP


Next, using the duplicate you've presumably saved to your desktop in a folder called BACKUP right click on it and 'Show Package Contents'


Go to plugins, and do the same to the file called 'BroadcomBluetoothHCIControllerUSBTransport'


Go to Contents


Navigate to the Info.plist file


Step 3:


Open it up in your favourite text editor (I Use PListEditor Pro)


We have a bunch of jargon, but we need to add our newly created device string
<key>Broadcom BCM92045USBBluetoothHCIController</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport</string>
<key>IOClass</key>
<string>BroadcomBluetoothHCIControllerUSBTransport</string>
<key>IOProviderClass</key>
<string>IOUSBDevice</string>
<key>LMPLoggingEnabled</key>
<false/>
<key>idProduct</key>
<integer>61697</integer>
<key>idVendor</key>
<integer>2001</integer>
</dict>
You can put it wherever I guess, mine went just after the string of code that ends:
<key>DTXcode</key>
<string>0440</string>
<key>DTXcodeBuild</key>
<string>4F250</string>
<key>IOKitPersonalities</key>
<dict>
Step 4:


When this is done, save the new Info.plist (You will have to duplicate I think) somewhere else, and replace the one we just opened.


To finish, drop it into kextutility and let it replace the one in S/L/E


from there, reboot, and you'll be sweet
smile.png



Attached my modified IOBluetooth file (Though you should follow my instructions and do it yourself, number 1 because it's better to learn, and number two because I'm not sure if product and device IDs are unique.


Enjoy! And please, backup your {censored} as I am no expert and take no responsibilities if you mess anything up.
 
Status
Not open for further replies.
Back
Top