Jump to content

Dell Wireless 365/370/410 Bluetooth


84 posts in this topic

Recommended Posts

Install the kext i attached to enable turn on and off bluetooth device directly on Mac. Combined with bcc9's DellBluetoothHCI kext. Thanks very much bcc9 for your great kext.
I guess this could be handy if the antenna hotkey hasn't been set up to power cycle bluetooth? I notice that your plist only matches on the bluetooth 370. I assume this should work for the other broadcom usb bluetooth devices like with my kext. Maybe you could expand it?

 

Is it possible to port the other sections of hid2hci as well? I have a Logitech dongle that I'm looking to get working.
The logitech code in hid2hci has some ioctl code that I don't know how to port. Specifically the HIDIOCINITREPORT ioctl in switch_logitech() looks to be a problem. And HIDIOCSUSAGE in send_report().

I'll put up the source if someone else wants to give it a shot.

I guess this could be handy if the antenna hotkey hasn't been set up to power cycle bluetooth? I notice that your plist only matches on the bluetooth 370. I assume this should work for the other broadcom usb bluetooth devices like with my kext. Maybe you could expand it?

 

you're right! it can work for others bluetooth devices, what needs to do is to change the product id and vendor id.

Yea, the source would be great. :rolleyes:
Took me a bit as I had fat-fingered the 1.0->1.1 changes and had to rewrite them (very unlike me).

I added the source to the post with the hid2hci 1.1 binary, over here

 

you're right! it can work for others bluetooth devices, what needs to do is to change the product id and vendor id.
Er, you could match multiple product ids in the plist like I did.
  • 3 weeks later...

I have a HP Mini 110 with the Dell Trumobile 370 and this works like a charm. Thanks. Only if I could get this started at boot up so that it is always shown. Thanks a lot.

I have a HP Mini 110 with the Dell Trumobile 370 and this works like a charm. Thanks. Only if I could get this started at boot up so that it is always shown. Thanks a lot.
If you install my kext it runs at boot time and will switch dell bluetooth cards to HCI mode automatically.
If you install my kext it runs at boot time and will switch dell bluetooth cards to HCI mode automatically.

 

I installed the ktext but it doesn't come on with booting. I installed Ktext and also Repaired Permissions then rebooted. Turn on, doesn't work. Still have to run the little file in terminal to make it work.

I installed the ktext but it doesn't come on with booting. I installed Ktext and also Repaired Permissions then rebooted. Turn on, doesn't work. Still have to run the little file in terminal to make it work.
Boot with -v and check what the kext is reporting at boot time. If you still don't see anything then there's a problem with your kext cache.
Boot with -v and check what the kext is reporting at boot time. If you still don't see anything then there's a problem with your kext cache.

 

Did that and it didn't report anything. Or that I know of. I seen some yellow text for a second, but that was the Broadcom Wifi Card. But it went through the scrolling text and then booted into OSX. Upon boot you see it for a second in the Menu bar then it disappears. Hmmm.

 

*edit. Did restarted it again and this time didn't show. Also I was using OynX and I cleared the Caches. Could you shed some light on how I may repair the ktext caches? + When I was deleting unneeded ktexts I seen it amoung them, but didn't touch it.

I installed the ktext but it doesn't come on with booting. I installed Ktext and also Repaired Permissions then rebooted. Turn on, doesn't work. Still have to run the little file in terminal to make it work.

 

I have HP mini 110 with Dell 370 also. Just drag HID2HCI into your Login Items under SystemPrefs-Users.

Then you can write an apple scipt to close terminal.app and put it in login items also.

 

Thanks to Bcc9 for porting this over.

I have HP mini 110 with Dell 370 also. Just drag HID2HCI into your Login Items under SystemPrefs-Users.

Then you can write an apple scipt to close terminal.app and put it in login items also.

 

Thanks to Bcc9 for porting this over.

No no, just use the kext. If it doesn't print anything at boot time with -v you simply have a problem with your install.

 

*edit. Did restarted it again and this time didn't show. Also I was using OynX and I cleared the Caches. Could you shed some light on how I may repair the ktext caches? + When I was deleting unneeded ktexts I seen it amoung them, but didn't touch it.

Use kextutil to troubleshoot problems with loading of your kexts.

Make sure this one is in /System/Library/Extensions, as the dependencies don't work when it's placed in /Extra/Extensions.

No no, just use the kext. If it doesn't print anything at boot time with -v you simply have a problem with your install.

 

Nope. No problems with the install. I guess it's because we had to BIOs hack ours to make it work. It possibly doesn't show on boot. I'm not too sure.

 

Use kextutil to troubleshoot problems with loading of your kexts.

Make sure this one is in /System/Library/Extensions, as the dependencies don't work when it's placed in /Extra/Extensions.

 

I had it there and it's still there. Never removed the ktext but it never loaded upon boot. Oh well. I solved it by using SleepWatcher and for some reason, now it runs on boot and whenever it goes in and out of sleep. Thanks again for all the help. Thanks for porting it over. :star_smile:

Nope. No problems with the install. I guess it's because we had to BIOs hack ours to make it work. It possibly doesn't show on boot. I'm not too sure.
Still not convinced your kext cache is set up right. Without more debugging, I guess your problem will remain a mystery.
Still not convinced your kext cache is set up right. Without more debugging, I guess your problem will remain a mystery.

 

Hmm. It looks to me like the SleepWatcher or whatever has stopped allowing it to re-run on waking from sleep. It has seemed to disappear from the /etc/bin folder or where ever it said to be put. I am running Ktext Util. I got it to rewrite itself after deleting the Extensions.mtext or whatever. Now I will be trying to fix the rc.wakeup file to get it to work again. Thanks for helping out :wacko:

Yeah MBudden is right the provided kext doesn't load our hardware @ boot time. It's not the install or the KextCache (at least not on mine).

 

I usually just run this to make a new Kextcache-

 

KEXT_RETAIL="/System/Library/Extensions"

KEXT_EXTRA="/Volumes/HPMacOS/Extra/Extensions"

MKEXT="/Volumes/HPMacOS/Extra/Extensions.mkext"

 

kextcache -v 1 -t -l -a i386 \

-m "$MKEXT" "$KEXT_EXTRA" "$KEXT_RETAIL"

  • 1 month later...
  • 1 month later...
First post edited with a link to the new Instal Pkg :)

 

Just wanted to thank you! I have purchased a 370 card, dropped it in my HP Mini 311 (with whitelist removed) in the WLAN slot and with your ktexts it works like a charm. I have also found the Windows 7 drivers for it, and since I have dual boot (actually tri-boot, but I have not tried to configure with Linux yet) I now have bluetooth on both my hackintosh and my windows 7 image. Thank you!!!!

  • 4 months later...

I've installed the Dell 370 card into my HP Mini 311. I have a hacked bios, i've installed the kext and i can see the device listed in the usb tree as a BCM2406B1. However, I don't yet have bluetooth functionality.

 

I'm not certain how to update the kextcache. I'm running HF5 which might place things in slightly different places.

I'm not certain how to update the kextcache. I'm running HF5 which might place things in slightly different places.

I don't know what hf5 is, but under 10.6, touch /System/Library/Extensions is sufficient to get the system to rebuild the kext cache for you. See also the kextcache man page.

  • 1 month later...
This may be really stupid but when I type "hdi2hci" (no quotes) into terminal it says command not found? Am I putting the command in right? helpp

If you installed DellBlutoothHCI1.2.pkg, there is no hid2hci program, rather a driver that automatically puts the bluetooth hardware into hci mode at boot time for you.

You can nevertheless separately install and use the manual hid2hci program when you already have the driver installed. Either install hid2hci into some directory that is in your path, or type the whole pathname to run it: ./hid2hci for example.

×
×
  • Create New...