sudo rmmod btusb
and then reload it again
sudo modprobe btusb
and thus the bluetooth works, it is not the final solution, and should be done every time the machine is turned on but where is the problem.
]]>I tried to run hid2hci. But like Asarorschach I was not able to find a valid devpath. I also tried comment #9 of MadCat_X without success.
This problem looks similar to a bug that appeared in late 2011 with Broadcom bluetooth hardware too:
http://launchpad.net/bugs/839157
https://bugzilla.redhat.com/show_bug.cgi?id=747575
If you find further details about this problem, please help by reporting them to one of these bug trackers.
]]>$dmesg | grep usb > usb0 <------turned BT off
$dmesg | grep usb > usb1 <------turned BT on
$diff -c usb0 usb1 > diffrent
$cat diffrent
*** usb0 2011-11-30 23:07:03.605704808 +0800
--- usb1 2011-11-30 23:07:12.919038557 +0800
***************
*** 77,79 ****
--- 77,86 ----
[ 7468.338669] usb 1-1.1.4: USB disconnect, device number 16
[ 7468.717482] usb 1-1.1: new full speed USB device number 17 using ehci_hcd
[ 7469.189445] usb 1-1.1: device not accepting address 17, error -32
+ [ 7497.997151] usb 2-1.6: new full speed USB device number 12 using ehci_hcd
+ [ 7498.349705] usb 2-1.6.1: new full speed USB device number 13 using ehci_hcd
+ [ 7498.437790] input: HID 413c:8161 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.1/2-1.6.1:1.0/input/input29
+ [ 7498.438012] generic-usb 0003:413C:8161.0010: input,hidraw0: USB HID v1.11 Keyboard [HID 413c:8161] on usb-0000:00:1d.0-1.6.1/input0
+ [ 7498.502696] usb 2-1.6.2: new full speed USB device number 14 using ehci_hcd
+ [ 7498.592664] input: HID 413c:8162 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0/input/input30
+ [ 7498.592800] generic-usb 0003:413C:8162.0011: input,hidraw1: USB HID v1.11 Mouse [HID 413c:8162] on usb-0000:00:1d.0-1.6.2/input0 <-----MY BT 413c:8162
idVendor=413c,idProduct=8162
I read the rules file of hid2hci in /lib/udev/rules.d/97-bluetooth-hid2hci.rules.My BT is in the supported devices list: 413c:8154, 413c:8158, 413c:8162.
The devpath is : /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0/
So I run the follow command:
# /lib/udev/hid2hci --mode=hci --method=dell --devpath=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0
But nothing happened.
]# hcitool dev
Devices:
# hcitool scan
Device is not available: No such device
Is there some bugs in the bluez 4.96-1?Or,the --devpath of hid2hci is wrong? Please help me!
]]>lspci
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 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 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 04f2:b008 Chicony Electronics Co., Ltd USB 2.0 Camera
Bus 008 Device 002: ID 08ff:1600 AuthenTec, Inc. AES1600
Bus 008 Device 003: ID 0930:0200 Toshiba Corp. <-- My BT device
Using VID and PID from lsusb
udevadm trigger --dry-run --subsystem-match=usb --attr-match=idVendor=0930 --attr-match=idProduct=0200 --verbose
/sys/devices/pci0000:00/0000:00:1d.2/usb8/8-2
There I go.
My BT device works out of the box so I can't check if it's exactly the path hid2hci expects.
]]>after manually modprobing a driver DO NOT reboot.
test if you have the desired functionality, and if so add btusb to the modules array in rc.conf so it will be loaded at next boot also.
After I manually modprobe the btusb ,I had checked using hcitool.However got this:
$ hcitool dev
Devices:
$ hcitool scan
Device is not available: No such device
Just as MadCat_X said,I should switch the Bluetooth mode from HID to HCI using hid2hci.But I couldn't find DEVPATH of bluetooth,when using hid2hci.Any advise?Buy the way,hal is deprecated and has been dropped from the official repositories,so I can't use lshal.
]]># /lib/udev/hid2hci
error: --devpath= and --method= must be defined
Usage: hid2hci [options]
--mode= mode to switch to [hid|hci] (default hci)
--devpath= sys device path
--method= method to use to switch [csr|logitech-hid|dell] (I have a logitech keyboard)
--help
It' said that the parameters of hid2hci must be defined.I searched online.Someone says run the command lshal,could find the devpath.The lshal include in hal,but the hal is deprecated and has been dropped from the official repositories.It' in AUR now.I'm a newcomer from Debian,and I don't know how to use AUR.Can you tell me other way to got the DEVPATH?And other thing should I pay attention when I run hid2hci.
]]>test if you have the desired functionality, and if so add btusb to the modules array in rc.conf so it will be loaded at next boot also.
]]>If I'm not mistaken, this BT device should be supported by "
hci_usb" driver. Do you have the driver enabled in the kernel? Can you modprobe it manually?EDIT: The driver's name is actually "btusb", I'm sorry for any confusion.
MadCat_X ,thanks.I think you may right.I had modprobe btusb,and rebooted my computer.It didn't work.Here is my driver in /lib/modules/3.1.2-1-ARCH/kernel/drivers/bluetooth/
$ls /lib/modules/3.1.2-1-ARCH/kernel/drivers/bluetooth
ath3k.ko.gz bpa10x.ko.gz btsdio.ko.gz dtl1_cs.ko.gz
bcm203x.ko.gz bt3c_cs.ko.gz btuart_cs.ko.gz hci_uart.ko.gz
bfusb.ko.gz btmrvl.ko.gz btusb.ko.gz hci_vhci.ko.gz
bluecard_cs.ko.gz btmrvl_sdio.ko.gz btwilink.ko.gz
Should I modprob other to enable in the kernel?Or shoud I do some other jobs?
]]>EDIT: The driver's name is actually "btusb", I'm sorry for any confusion.
]]>$ rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
$ dmesg | grep Bluetooth
[ 19.930320] Bluetooth: Core ver 2.16
[ 19.930343] Bluetooth: HCI device and connection manager initialized
[ 19.930346] Bluetooth: HCI socket layer initialized
[ 19.930347] Bluetooth: L2CAP socket layer initialized
[ 19.930353] Bluetooth: SCO socket layer initialized
[ 19.948634] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 173.805548] Bluetooth: RFCOMM TTY layer initialized
[ 173.805554] Bluetooth: RFCOMM socket layer initialized
[ 173.805556] Bluetooth: RFCOMM ver 1.11
$ hcitool dev
Devices:
$ hcitool scan
Device is not available: No such device
$ lsusb | grep Bluetooth
Bus 002 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
$lsmod | grep bluetooth
bluetooth 150884 10 rfcomm,bnep
rfkill 15498 6 bluetooth,cfg80211,dell_laptop
crc16 1359 2 bluetooth,ext4
Anyone can help me?
]]>