Quote:
Originally Posted by gesser
Hi! Just want to share how to enable bluetooth on Dell Studio 1535.
From the Fedora 10 to the beginning of the Fedora 11, I was successfully enabling bluetooth device on my Dell laptop by putting hid2hci command as a system startup module:
Code:
# echo "/usr/sbin/hid2hci" > /etc/sysconfig/modules/bluetooth.modules
But the latest hid2hci command in bluez package now displays help information instead of turning on the (default?) bluetooth device:
Code:
# rpm -qf /usr/sbin/hid2hci
bluez-4.42-1.fc11.i586
# /usr/sbin/hid2hci
ERROR: Vendor ID, Product ID, and Switching Method must all be defined.
Usage:
hid2hci [options]
Options:
-h, --help Display help
-q, --quiet Don't display any messages
-r, --mode= Mode to switch to [hid, hci]
-v, --vendor= Vendor ID to act upon
-p, --product= Product ID to act upon
-m, --method= Method to use to switch [csr, logitech, dell]
To fix this, first you need to find the vendor ID and Device id of your internal bluetooth device by using lsusb command. Here the example output (my laptop):
Code:
# lsusb
Bus 002 Device 003: ID 05ca:18a1 Ricoh Co., Ltd
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 008: ID 413c:8156 Dell Computer Corp.
Bus 003 Device 007: ID 413c:8158 Dell Computer Corp.
Bus 003 Device 006: ID 413c:8157 Dell Computer Corp.
Bus 003 Device 005: ID 0a5c:4500 Broadcom Corp.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems)
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I've tried first two "Dell Computer Corp." devices, and with 413c:8158 (first part is vendor id, second - product id) I had a luck (the Id of your device may very).
Then second step is just an update of a module file to:
Code:
/usr/sbin/hid2hci -v 413c -p 8158 -r hci -m dell
Now your bluetooth device should be enabled during startup. Only one problem still exists, the state of the bluetooth device will be reset if you will turn it off using the hardware turnoff button. If you will turn it on again, you will be required to enter hid2hci command manually.
That's all. Hope it was helpful.
P.S. Look forward to hear for a better solution.
P.P.S. Sorry for my English. Дякую за увагу 
|
Thanks for this info, I had been using bluetooth with no problems at all, however 2 or three weeks ago I noticed problems with mi bluetooth mouse, an just recently noticed that the bluetooth-applet was not showed in gnome-panel. I don't know why this happened. However, following your instructions I could reenable my Dell bluetooth wireless 370 module:
[root@amturing ~]# hid2hci -v 413c -p 8158 -r hci -m dell
Attempting to switch device 413c:8158 to HCI mode was successful
/var/log/messages:
Aug 6 22:13:57 amturing kernel: usb 3-1.3: new full speed USB device using uhci_hcd and address 5
Aug 6 22:13:57 amturing kernel: usb 3-1.3: new full speed USB device using uhci_hcd and address 5
Aug 6 22:13:57 amturing kernel: usb 3-1.3: New USB device found, idVendor=413c, idProduct=8156
Aug 6 22:13:57 amturing kernel: usb 3-1.3: New USB device found, idVendor=413c, idProduct=8156
Aug 6 22:13:57 amturing kernel: usb 3-1.3: New USB device found, idVendor=413c, idProduct=8156
Aug 6 22:13:57 amturing kernel: usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 6 22:13:57 amturing kernel: usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 6 22:13:57 amturing kernel: usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 6 22:13:57 amturing kernel: usb 3-1.3: Product: Dell Wireless 370 Bluetooth Mini-card
Aug 6 22:13:57 amturing kernel: usb 3-1.3: Product: Dell Wireless 370 Bluetooth Mini-card
Aug 6 22:13:57 amturing kernel: usb 3-1.3: Product: Dell Wireless 370 Bluetooth Mini-card
Aug 6 22:13:57 amturing kernel: usb 3-1.3: Manufacturer: Dell Computer Corp
Aug 6 22:13:57 amturing kernel: usb 3-1.3: Manufacturer: Dell Computer Corp
Aug 6 22:13:57 amturing kernel: usb 3-1.3: Manufacturer: Dell Computer Corp
Aug 6 22:13:57 amturing kernel: usb 3-1.3: configuration #1 chosen from 1 choice
Aug 6 22:13:57 amturing kernel: usb 3-1.3: configuration #1 chosen from 1 choice
Aug 6 22:13:57 amturing kernel: usb 3-1.3: configuration #1 chosen from 1 choice
Aug 6 22:13:57 amturing kernel: Bluetooth: Generic Bluetooth USB driver ver 0.5
Aug 6 22:13:57 amturing kernel: Bluetooth: Generic Bluetooth USB driver ver 0.5
Aug 6 22:13:57 amturing kernel: Bluetooth: Generic Bluetooth USB driver ver 0.5
Aug 6 22:13:57 amturing kernel: usbcore: registered new interface driver btusb
Aug 6 22:13:57 amturing kernel: usbcore: registered new interface driver btusb
Aug 6 22:13:57 amturing kernel: usbcore: registered new interface driver btusb
Aug 6 22:13:57 amturing bluetoothd[2351]: HCI dev 0 registered
Aug 6 22:13:57 amturing bluetoothd[2351]: HCI dev 0 registered
Aug 6 22:13:57 amturing bluetoothd[2351]: HCI dev 0 up
Aug 6 22:13:57 amturing bluetoothd[2351]: HCI dev 0 up
Aug 6 22:13:57 amturing bluetoothd[2351]: Starting security manager 0
Aug 6 22:13:57 amturing bluetoothd[2351]: Starting security manager 0
Aug 6 22:13:57 amturing kernel: Bluetooth: RFCOMM socket layer initialized
Aug 6 22:13:57 amturing kernel: Bluetooth: RFCOMM socket layer initialized
Aug 6 22:13:57 amturing kernel: Bluetooth: RFCOMM socket layer initialized
Aug 6 22:13:57 amturing kernel: Bluetooth: RFCOMM TTY layer initialized
Aug 6 22:13:57 amturing kernel: Bluetooth: RFCOMM TTY layer initialized
Aug 6 22:13:57 amturing kernel: Bluetooth: RFCOMM TTY layer initialized
Aug 6 22:13:57 amturing kernel: Bluetooth: RFCOMM ver 1.11
Aug 6 22:13:57 amturing kernel: Bluetooth: RFCOMM ver 1.11
Aug 6 22:13:57 amturing kernel: Bluetooth: RFCOMM ver 1.11
Aug 6 22:13:57 amturing bluetoothd[2351]: probe failed with driver input-headset for device /org/bluez/2351/hci0/dev_00_1E_4C_DE_DA_B5
Aug 6 22:13:57 amturing bluetoothd[2351]: probe failed with driver input-headset for device /org/bluez/2351/hci0/dev_00_1E_4C_DE_DA_B5
Aug 6 22:13:57 amturing bluetoothd[2351]: Adapter /org/bluez/2351/hci0 has been enabled
Aug 6 22:13:57 amturing bluetoothd[2351]: Adapter /org/bluez/2351/hci0 has been enabled
Aug 6 22:13:57 amturing bluetoothd[2351]: return_link_keys (sba=00:23:4D:E7

E:2E, dba=00:12:5A:69:3D:18)
Aug 6 22:13:57 amturing bluetoothd[2351]: return_link_keys (sba=00:23:4D:E7

E:2E, dba=00:12:5A:69:3D:18)
Aug 6 22:13:57 amturing bluetoothd[2351]: return_link_keys (sba=00:23:4D:E7

E:2E, dba=00:12:5A:69

9:EE)
Aug 6 22:13:57 amturing bluetoothd[2351]: return_link_keys (sba=00:23:4D:E7

E:2E, dba=00:12:5A:69

9:EE)
Aug 6 22:13:57 amturing kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Aug 6 22:13:57 amturing kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Aug 6 22:13:57 amturing kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Aug 6 22:14:04 amturing kernel: input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/bluetooth/hci0/hci0:11/input17
Aug 6 22:14:04 amturing kernel: input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/bluetooth/hci0/hci0:11/input17
Aug 6 22:14:04 amturing kernel: input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/bluetooth/hci0/hci0:11/input17
Aug 6 22:14:04 amturing kernel: generic-bluetooth 0005:045E:0700.0003: input,hidraw1: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 00:23:4D:E7

E:2E
Aug 6 22:14:04 amturing kernel: generic-bluetooth 0005:045E:0700.0003: input,hidraw1: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 00:23:4D:E7

E:2E
Aug 6 22:14:04 amturing kernel: generic-bluetooth 0005:045E:0700.0003: input,hidraw1: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 00:23:4D:E7

E:2E