Comment 14 for bug 37288

Revision history for this message
Ketil Malde (ketil-ii) wrote :

I have a Dell Latitude D620, which included (according to the "Compatible systems" link at the bottom of http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R129472&SystemID=LATITUDE%20D620&servicetag=&os=WW1&osl=en&deviceid=7388&devlib=0&typecnt=0&vercnt=2&catid=-1&impid=-1&formatcnt=1&libid=5&fileid=172476
) a Dell 350 Bluetooth module.

BT is enabled in the BIOS, and the BT LED on my computer is shining happily.

However: 'hciconfig' gives no output, 'hcitool dev' shows only the 'Devices:' header, and 'hcitool scan' tells me that "Device is not available: No such device". However, the BT device shows up on the USB bus, 'lsusb' tells me:

   Bus 001 Device 005: ID 413c:8105 Dell Computer Corp.

Apparently, this can be caused by a Vista-specific firmware "upgrade" from Dell that sabotages the BT module, see http://ubuntuforums.org/showthread.php?p=2308248

Like the participant in that thread, I no longer have Vista or XP installed. I tried to download the Windows driver from Dell to download it with dfutool http://www.holtmann.org/linux/bluetooth/dfu.html. The file, R129472.EXE, can be 'unzip'ped to
BtSwSP2.exe, which 'cabextract' can decompose into a set of DLLs and such. I'm not sure how to proceed from there, though.

(dfutool is not packaged with bluez-utils in Ubuntu, should I file that as a separate feature request/bug?)

-k