You are not logged in.
oops, it looks like you have something different going on
I get different output
$ sudo hciconfig hci0 up
Password:
Can't init device hci0: Connection timed out (110)
what's your output of
$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
if your bluetooth is soft blocked, you can unblock it with rfkill to fix your bluetooth. i saw someone on another thread fix it that way
my bluetooth is built into my HP ENVY 17 laptop
Offline
# rfkill list
2: phy2: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
weird, it's not blocked..
Offline
Hi,
i got the same problems with my bluetooth device ("Can't init device hci0: Connection timed out (110)", blablabla). I think, it is just a bug in bluez <= 4.96. As of 23rd December there is a new release, bluez-4.97 (not yet available in the arch repos). I installed it, and everything works fine.
Offline
Same error with my stick.
lsusb -v says :
Bus 007 Device 005: ID 1310:0001 Roper Class 1 Bluetooth Dongle
libusb couldn't open USB device /dev/bus/usb/007/005: Permission denied.
libusb requires write access to USB device nodes.
Couldn't open device, some information will be missing .....
hciconfig hci0 up says Can't init device hci0: Connection timed out (110)
(reset, down & up same error)
Device is always down, but it worked before (maybe 1 or 2 years ago :-) didnt use a long time)
Offline
in xubuntu kernel 2.6.. and bluez-ubuntu 4.60 the dongle worked without problems
Offline
Same issue here. "hciconfig -a" shows the hci0 adapter, but trying to enable it via "up" or "reset" gives always the 110 error. Also tried bluez-git, same issue.
Offline
I have the exact same problem. Same messages. Same symptoms.
My guess is that the device is in HID mode not HCI since I get this in dmesg :
[ 8312.145938] usb 2-3: new full-speed USB device number 19 using ohci_hcd
[ 8312.342017] hub 2-3:1.0: USB hub found
[ 8312.344894] hub 2-3:1.0: 3 ports detected
[ 8312.647887] usb 2-3.1: new full-speed USB device number 20 using ohci_hcd
[ 8312.883961] usb 2-3.2: new full-speed USB device number 21 using ohci_hcd
[ 8313.002223] input: HID 0a5c:3502 as /devices/pci0000:00/0000:00:04.0/usb2/2-3/2-3.2/2-3.2:1.0/input/input21
[ 8313.002364] generic-usb 0003:0A5C:3502.0009: input,hidraw4: USB HID v1.11 Keyboard [HID 0a5c:3502] on usb-0000:00:04.0-3.2/input0
[ 8313.073884] usb 2-3.3: new full-speed USB device number 22 using ohci_hcd
[ 8318.159898] usb 2-3.3: device descriptor read/all, error -110
[ 8318.229889] usb 2-3.3: new full-speed USB device number 23 using ohci_hcd
[ 8318.335328] input: HID 0a5c:3503 as /devices/pci0000:00/0000:00:04.0/usb2/2-3/2-3.3/2-3.3:1.0/input/input22
[ 8318.335568] generic-usb 0003:0A5C:3503.000A: input,hidraw5: USB HID v1.11 Mouse [HID 0a5c:3503] on usb-0000:00:04.0-3.3/input0
There are 2 lines showing that it registered HID devices (My Dell wireless keyboard and mouse). I tried /lib/udev/hid2hci but I don't know what device path I'm supposed to provide.
I tried running :
/lib/udev/hid2hci --devpath=/devices/pci0000:00/0000:00:04.0/usb2/2-3/2-3.1 --method=dell
but then I can't even list the adapter anymore.
Offline
I just got my hopes up :
- I saw that there is a bluez-firmware package for BCM203x adapters (mine is a BCM2035).
pacman -S --noconfirm bluez-firmware
installed it in a matter of seconds.
- I have tested my adapter on an old WinXP box and I managed to successfully pair it to my cellphone and transfer some files. This means that the physical device works and that it can run in HCI mode.
I thought that maybe just plugging in the dongle after having installed the firmware might have done the trick, but it behaves just as it did before. :'(
Offline
Hi there,
same symptoms here...
My device is onboard (USB). It's a Lite-On Technology Corp, ID 04ca:3002.
It works under Windows, so it's not a hardware problem.
The device seems to be in HCI mode, so it's probably not the same problem as Prozzaks's.
Here comes the strange thing:
I borrowed an bluetooth dongle a few days ago - which worked fine - with the external device plugged in the internal one worked as well!
Bug in the driver ?
Edit: did some more tests. The external dongle mitght not have anything to do with it all (can't try it right now).
I found out that, if I boot to Windows 7 first, then reboot to Archlinux it works!
After a "cold boot" the problem is there again...
Last edited by lupylucke (2012-04-06 10:35:33)
Offline
It is the same here, with a built-int Atheros Adapter on a Sony VAIO VPCCA2S1E. Definitely annoying, if I want to use it then it is available only after I reboot from win7. (Tried the commands listed on the first page).
lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Seymour [Radeon HD 6400M Series]
01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Caicos HDMI Audio [Radeon HD 6400 Series]
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 SD Host controller: Ricoh Co Ltd Device e823 (rev 07)
03:00.1 System peripheral: Ricoh Co Ltd Device e232 (rev 04)
04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
05:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)
lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0489:e027 Foxconn / Hon Hai
Bus 001 Device 004: ID 05ca:18c0 Ricoh Co., Ltd
Bus 004 Device 003: ID 0458:0084 KYE Systems Corp. (Mouse Systems)
rfkill list
0: sony-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: sony-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
[szebenyib@moon ~]$ sudo hciconfig hci0
hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:9 acl:0 sco:0 commands:3 errors:0
sudo bluetoothd -n -d
bluetoothd[2405]: Bluetooth daemon 4.100
bluetoothd[2405]: src/main.c:parse_config() parsing main.conf
bluetoothd[2405]: src/main.c:parse_config() discovto=0
bluetoothd[2405]: src/main.c:parse_config() pairto=0
bluetoothd[2405]: src/main.c:parse_config() pageto=8192
bluetoothd[2405]: src/main.c:parse_config() auto_to=60
bluetoothd[2405]: src/main.c:parse_config() name=%h-%d
bluetoothd[2405]: src/main.c:parse_config() class=0x000100
bluetoothd[2405]: src/main.c:parse_config() Key file does not have key 'DeviceID'
bluetoothd[2405]: Starting SDP server
bluetoothd[2405]: src/plugin.c:plugin_init() Loading builtin plugins
bluetoothd[2405]: src/plugin.c:add_plugin() Loading audio plugin
bluetoothd[2405]: src/plugin.c:add_plugin() Loading input plugin
bluetoothd[2405]: src/plugin.c:add_plugin() Loading serial plugin
bluetoothd[2405]: src/plugin.c:add_plugin() Loading network plugin
bluetoothd[2405]: src/plugin.c:add_plugin() Loading service plugin
bluetoothd[2405]: src/plugin.c:add_plugin() Loading hciops plugin
bluetoothd[2405]: src/plugin.c:add_plugin() Loading mgmtops plugin
bluetoothd[2405]: src/plugin.c:add_plugin() Loading formfactor plugin
bluetoothd[2405]: src/plugin.c:add_plugin() Loading storage plugin
bluetoothd[2405]: src/plugin.c:add_plugin() Loading adaptername plugin
bluetoothd[2405]: src/plugin.c:add_plugin() Loading wiimote plugin
bluetoothd[2405]: src/plugin.c:plugin_init() Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[2405]: plugins/service.c:register_interface() path /org/bluez/2405/any
bluetoothd[2405]: plugins/service.c:register_interface() Registered interface org.bluez.Service on path /org/bluez/2405/any
bluetoothd[2405]: network/manager.c:read_config() /etc/bluetooth/network.conf: Key file does not have key 'DisableSecurity'
bluetoothd[2405]: network/manager.c:read_config() Config options: Security=true
bluetoothd[2405]: input/manager.c:input_manager_init() input.conf: Key file does not have key 'IdleTimeout'
bluetoothd[2405]: audio/manager.c:audio_manager_init() audio.conf: Key file does not have key 'AutoConnect'
bluetoothd[2405]: plugins/hciops.c:hciops_init()
bluetoothd[2405]: plugins/hciops.c:hciops_setup()
bluetoothd[2405]: src/main.c:main() Entering main loop
bluetoothd[2405]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 0 soft 0 hard 0
bluetoothd[2405]: src/rfkill.c:rfkill_event() RFKILL event idx 1 type 2 op 0 soft 0 hard 0
bluetoothd[2405]: src/rfkill.c:rfkill_event() RFKILL event idx 2 type 1 op 0 soft 0 hard 0
bluetoothd[2405]: src/rfkill.c:rfkill_event() RFKILL event idx 3 type 2 op 0 soft 0 hard 0
bluetoothd[2405]: plugins/hciops.c:init_known_adapters()
bluetoothd[2405]: plugins/hciops.c:init_device() hci0
bluetoothd[2405]: Listening for HCI events on hci0
bluetoothd[2405]: plugins/hciops.c:init_device() child 2406 forked
bluetoothd[2406]: Can't init device hci0: Connection timed out (110)
bluetoothd[2405]: plugins/hciops.c:child_exit() child 2406 exited
^Cbluetoothd[2405]: Terminating
bluetoothd[2405]: src/plugin.c:plugin_cleanup() Cleanup plugins
bluetoothd[2405]: plugins/service.c:unregister_interface() path /org/bluez/2405/any
bluetoothd[2405]: plugins/hciops.c:hciops_exit()
bluetoothd[2405]: plugins/hciops.c:hciops_cleanup()
bluetoothd[2405]: Stopping hci0 event socket
bluetoothd[2405]: Stopping SDP server
bluetoothd[2405]: Exit
sudo hciconfig dev
hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:12 acl:0 sco:0 commands:4 errors:0
$ hcitool scan
Device is not available: No such device
$ sudo hciconfig hci0 piscan
Can't set scan mode on hci0: Network is down (100)
$ sudo hciconfig hci0 reset
Can't init device hci0: Connection timed out (110)
$ dmesg | grep tooth
[ 16.235348] Bluetooth: Core ver 2.16
[ 16.235368] Bluetooth: HCI device and connection manager initialized
[ 16.235371] Bluetooth: HCI socket layer initialized
[ 16.235374] Bluetooth: L2CAP socket layer initialized
[ 16.235380] Bluetooth: SCO socket layer initialized
[ 31.662012] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 2210.712680] Bluetooth: RFCOMM TTY layer initialized
[ 2210.712687] Bluetooth: RFCOMM socket layer initialized
[ 2210.712689] Bluetooth: RFCOMM ver 1.11
Offline
The bug is on the Kernel Bug Tracker: #42932
Doesn't look like somebody has looked into it yet...
Offline
Thanks for the notification! I really hope that there is a way to fix it.
Offline
There supposed to be a patch for this in kernel 3.7. Can't wait
Offline
I just bought a cheap dongle and I'm having exactly same problem with kernel 3.8.4.
edit: to be more specific, I can't get the device up, hciconfig says it down and when trying to bring it up it says Can't init device hci0: Connection timed out (110).
e2: nvm, updated kernel to 3.8.5 and changed usb-port and it just started to work
Last edited by harbind (2013-04-05 08:23:15)
Offline