[bluetooth] hcitool Can't init device hci0: Device or resource busy

blackdeagle · 2011-09-16 17:29:21

Hi guys,

I've bought a cheap blutooth dongle yesterday, today it came but I can't get it to work.

$ lsusb
(...)
Bus 002 Device 025: ID 0a5c:3500 Broadcom Corp. 
Bus 002 Device 026: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 027: ID 0a5c:3502 Broadcom Corp. 
Bus 002 Device 028: ID 0a5c:3503 Broadcom Corp. 
(...)

hciconig -a says:

$ hciconfig -a
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:03:C9:80:08:0B  ACL MTU: 377:10  SCO MTU: 16:0
        DOWN 
        RX bytes:2752 acl:0 sco:0 events:80 errors:0
        TX bytes:320 acl:0 sco:0 commands:80 errors:0
        Features: 0xff 0xff 0x0d 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: 
        Link mode: SLAVE ACCEPT

Now when I try to power up the bluetooth device, I get:

# hciconfig hci0 up
Can't init device hci0: Device or resource busy (16)

At this point, I don't know what to do. I tried the Device on every USB port I have, it didn't work..
When I plug the device in, /var/log/messages.log says:

Sep 16 19:27:48 localhost kernel: [15306.457463] usb 2-1.1: new full speed USB device number 38 using ehci_hcd
Sep 16 19:27:48 localhost kernel: [15306.542428] hub 2-1.1:1.0: USB hub found
Sep 16 19:27:48 localhost kernel: [15306.542574] hub 2-1.1:1.0: 3 ports detected
Sep 16 19:27:49 localhost kernel: [15306.807266] usb 2-1.1.1: new full speed USB device number 39 using ehci_hcd
Sep 16 19:27:54 localhost bluetoothd[7670]: HCI dev 0 registered
Sep 16 19:27:54 localhost bluetoothd[7670]: Listening for HCI events on hci0
Sep 16 19:27:54 localhost kernel: [15311.981087] usb 2-1.1.2: new full speed USB device number 40 using ehci_hcd
Sep 16 19:28:04 localhost kernel: [15322.125560] usb 2-1.1.2: new full speed USB device number 41 using ehci_hcd

Hope, anyone can help^^

the sad clown · 2011-09-17 00:51:33

hciconfig looks like it is up already. Have you tried

hciconfig dev

What is the output?

blackdeagle · 2011-09-17 00:53:15

the sad clown wrote:

hciconfig looks like it is up already. Have you tried
hciconfig dev
What is the output?

output:

$ hciconfig dev
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:03:C9:80:08:0B  ACL MTU: 377:10  SCO MTU: 16:0
        DOWN 
        RX bytes:688 acl:0 sco:0 events:20 errors:0
        TX bytes:80 acl:0 sco:0 commands:20 errors:0

the sad clown · 2011-09-17 01:09:10

That looks fine, your interface is already up. The next step is just to scan for external devices. Try

hcitool scan

Then you just have to pair with the device.

blackdeagle · 2011-09-17 01:11:04

I'm not sure if the device is up, because hciconfig dev says in the third line:
DOWN

Anyway, this is the output of hcitool scan:

$ hcitool scan
Device is not available: No such device

the sad clown · 2011-09-17 01:30:37

Try this:

hciconfig hci0 piscan

Then try "hciconfig -a" again and see if it makes a difference.

blackdeagle · 2011-09-17 01:33:42

# hciconfig hci0 piscan
Can't set scan mode on hci0: Network is down (100)

$ hciconfig -a
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:03:C9:80:08:0B  ACL MTU: 377:10  SCO MTU: 16:0
        DOWN 
        RX bytes:688 acl:0 sco:0 events:20 errors:0
        TX bytes:80 acl:0 sco:0 commands:20 errors:0
        Features: 0xff 0xff 0x0d 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: 
        Link mode: SLAVE ACCEPT

I really have NO idea what the problem is bluetooth dongle is detected but can't be powered up..Whyyy?? (

the sad clown · 2011-09-17 01:49:59

Well, that was pretty conclusive, wasn't it. Try

hciconfig hci0 reset

Don't panic. You have a BD Address and that's a good thing. We just have to get the interface up.

blackdeagle · 2011-09-17 01:52:30

# hciconfig hci0 reset
Can't init device hci0: Device or resource busy (16)

I also tried every other USB port I have.. No one works

the sad clown · 2011-09-17 02:02:55

What is the output for lsmod?

blackdeagle · 2011-09-17 02:03:50

$ lsmod
Module                  Size  Used by
fuse                   67290  3 
btusb                  11577  1 
bnep                    9245  2 
bluetooth             139297  10 btusb,bnep
ipv6                  290791  26 
uvcvideo               64963  0 
nouveau               698515  0 
videodev               78006  1 uvcvideo
media                  10437  2 uvcvideo,videodev
v4l2_compat_ioctl32     8292  1 videodev
ttm                    54360  1 nouveau
i915                  707339  8 
drm_kms_helper         25409  2 nouveau,i915
snd_hda_codec_hdmi     22092  1 
joydev                  9895  0 
drm                   183380  6 nouveau,ttm,i915,drm_kms_helper
arc4                    1410  2 
ath9k                  86536  0 
sdhci_pci               8530  0 
snd_hda_codec_conexant    46356  1 
mac80211              216021  1 ath9k
ath9k_common            1770  1 ath9k
ath9k_hw              275564  2 ath9k,ath9k_common
sdhci                  22194  1 sdhci_pci
asus_laptop            14162  0 
intel_agp              10904  1 i915
sparse_keymap           3088  1 asus_laptop
serio_raw               4294  0 
mxm_wmi                 1393  1 nouveau
mmc_core               73353  1 sdhci
i2c_algo_bit            5199  2 nouveau,i915
i2c_core               20133  6 nouveau,videodev,i915,drm_kms_helper,drm,i2c_algo_bit
ath                    14667  2 ath9k,ath9k_hw
wmi                     8347  1 mxm_wmi
intel_ips              11213  0 
psmouse                55192  0 
button                  4470  2 nouveau,i915
intel_gtt              14423  3 i915,intel_agp
jmb38x_ms               8449  0 
video                  11228  2 nouveau,i915
sg                     25557  0 
battery                10905  0 
ac                      3265  0 
thermal                 7863  0 
snd_hda_intel          22122  5 
snd_hda_codec          77927  3 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel
processor              24256  0 
mei                    31313  0 
jme                    34731  0 
pcspkr                  1819  0 
evdev                   9530  12 
memstick                6846  1 jmb38x_ms
iTCO_wdt               12717  0 
mii                     3995  1 jme
iTCO_vendor_support     1929  1 iTCO_wdt
snd_hwdep               6325  1 snd_hda_codec
snd_pcm                73888  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer              19416  1 snd_pcm
snd                    57818  16 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore               6146  1 snd
snd_page_alloc          7121  2 snd_hda_intel,snd_pcm
cfg80211              160740  3 ath9k,mac80211,ath
rfkill                 15402  4 bluetooth,asus_laptop,cfg80211
ext4                  370398  3 
mbcache                 5817  1 ext4
jbd2                   71074  1 ext4
crc16                   1297  2 bluetooth,ext4
usbhid                 35256  0 
hid                    81635  1 usbhid
sr_mod                 14951  0 
cdrom                  36329  1 sr_mod
sd_mod                 28307  5 
ahci                   20865  4 
libahci                18885  1 ahci
libata                173297  2 ahci,libahci
scsi_mod              131546  4 sg,sr_mod,sd_mod,libata
ehci_hcd               39511  0 
usbcore               142576  5 btusb,uvcvideo,usbhid,ehci_hcd

the sad clown · 2011-09-17 02:05:15

What is your device?

blackdeagle · 2011-09-17 02:07:00

$ lsusb -v

Bus 002 Device 027: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
(...)
idVendor           0x0a12 Cambridge Silicon Radio, Ltd
idProduct          0x0001 Bluetooth Dongle (HCI mode)
(...)

Do you mean this? ^^

Last edited by blackdeagle (2011-09-17 02:07:09)

the sad clown · 2011-09-17 02:12:26

Well, I was hoping for a manufacturer and model number.

blackdeagle · 2011-09-17 02:15:40

the sad clown wrote:

Well, I was hoping for a manufacturer and model number.

Hmm, that thing is really cheap. I bought it from eBay and on the Dongle itself there's only "Bluetooth" written, nothing more (oh and the bluetooth icon). The article on eBay is here.
I'm sorry, I don't have more information available..

the sad clown · 2011-09-17 02:37:49

It's ok. Try a coldplug. Turn off the computer, plug in the usb and then turn the computer back on and try the usual commands to see if it works. It might be a hotplug issue and not a bluetooth matter.

Last edited by the sad clown (2011-09-17 02:38:54)

blackdeagle · 2011-09-17 02:48:38

This is what I did:
I unplugged the device, shut down my computer. Then I plugged the device in and booted up, logged into KDE typed following commands in a shell:

$ hcitool dev
## to see if the Device was detected

$ hcitool scan
## to see if the Device is able to do anything, got an error:
Device is not available: No such device

# hciconfig hci0 up
## to power on the device, got an error:
Can't init device hci0: Device or resource busy (16)

# hciconfig hci0 piscan
Can't set scan mode on hci0: Network is down (100)

# hciconfig hci0 reset
Can't init device hci0: Device or resource busy (16)

And now I'm stuck again..
I have Windows 7 installed on this machine, the Dongle works perfectly there, even a VirtualMachine with WinXp installed can deal with the bluetooth device!

the sad clown · 2011-09-17 03:06:23

Try restarting the bluetooth:

sudo /etc/rc.d/bluetooth restart

blackdeagle · 2011-09-17 03:09:55

# /etc/rc.d/bluetooth restart
:: Stopping bluetooth subsystem:  pand dund rfcomm hidd  bluetoothd                  [DONE] 
:: Starting bluetooth subsystem:  bluetoothd                                         [DONE]

And tried all the commands from above again but they all give me the same error!

Last edited by blackdeagle (2011-09-17 03:10:43)

the sad clown · 2011-09-17 03:16:40

What is the output of "dmesg | grep tooth" and "dmesg | grep hci0"

Last edited by the sad clown (2011-09-17 03:37:21)

blackdeagle · 2011-09-17 11:54:34

$ dmesg | grep tooth
[    7.994901] Bluetooth: Core ver 2.16
[    7.994930] Bluetooth: HCI device and connection manager initialized
[    7.994933] Bluetooth: HCI socket layer initialized
[    7.994935] Bluetooth: L2CAP socket layer initialized
[    7.995003] Bluetooth: SCO socket layer initialized
[    8.005673] Bluetooth: Generic Bluetooth USB driver ver 0.6
[   18.035732] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

kjslag · 2011-12-22 07:25:54

I have the same problem, except my device worked fine last week and doesn't this week. Windows can't get it to work either. Did you ever get yours to work blackdeagle?

$ dmesg | grep tooth
[ 5.379223] Bluetooth: Core ver 2.16
[ 5.379717] Bluetooth: HCI device and connection manager initialized
[ 5.379722] Bluetooth: HCI socket layer initialized
[ 5.379725] Bluetooth: L2CAP socket layer initialized
[ 5.379735] Bluetooth: SCO socket layer initialized
[ 5.392483] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 7.458005] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 7.473665] Bluetooth: RFCOMM TTY layer initialized
[ 7.473675] Bluetooth: RFCOMM socket layer initialized
[ 7.473678] Bluetooth: RFCOMM ver 1.11

'dmesg | grep hci0' didn't output anythin

blackdeagle · 2011-12-22 12:30:06

Hi kjslag,

Your bluetooth device might be broken or else it should work on windows, shouldn't it?
Mine still does not work under arch, I use a VM with Windows XP if I need bluetooth support. That's not the best way of using it but it works

kjslag · 2011-12-23 04:05:22

i got it to work on windows, but linux still doesn't work

i'm amazed it works in a VM. you're running windows xp on top of linux?

I also noticed this:
grep tooth /var/log/everything
Dec 22 14:39:02 J kernel: [ 6.199410] Bluetooth: Core ver 2.16
Dec 22 14:39:02 J kernel: [ 6.199454] Bluetooth: HCI device and connection manager initialized
Dec 22 14:39:02 J kernel: [ 6.199461] Bluetooth: HCI socket layer initialized
Dec 22 14:39:02 J kernel: [ 6.199467] Bluetooth: L2CAP socket layer initialized
Dec 22 14:39:02 J kernel: [ 6.199482] Bluetooth: SCO socket layer initialized
Dec 22 14:39:02 J kernel: [ 6.218660] Bluetooth: Generic Bluetooth USB driver ver 0.6
Dec 22 14:39:02 J bluetoothd[922]: Bluetooth daemon 4.96
Dec 22 14:39:02 J bluetoothd[922]: Starting SDP server
Dec 22 14:39:02 J bluetoothd[922]: Listening for HCI events on hci0
Dec 22 14:39:02 J kernel: [ 9.130148] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Dec 22 14:39:02 J bluetoothd[922]: HCI dev 0 up
Dec 22 14:39:02 J kernel: [ 9.197344] Bluetooth: RFCOMM TTY layer initialized
Dec 22 14:39:02 J kernel: [ 9.197358] Bluetooth: RFCOMM socket layer initialized
Dec 22 14:39:02 J kernel: [ 9.197364] Bluetooth: RFCOMM ver 1.11
Dec 22 14:39:02 J laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/bluetooth.
Dec 22 14:39:02 J bluetoothd[922]: HCI dev 0 down
Dec 22 14:39:02 J bluetoothd[922]: Adapter /org/bluez/922/hci0 has been disabled
Dec 22 14:39:21 J pulseaudio[2645]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod
Dec 22 14:39:21 J pulseaudio[2645]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod
Dec 22 14:39:21 J pulseaudio[2645]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod
Dec 22 18:34:12 J bluetoothd[922]: Can't init device hci0: Connection timed out (110)
Dec 22 20:01:26 J bluetoothd[922]: Can't init device hci0: Connection timed out (110)

here are the lines that look bad:
during boot:
Dec 22 14:39:02 J bluetoothd[922]: HCI dev 0 up
Dec 22 14:39:02 J bluetoothd[922]: HCI dev 0 down
Dec 22 14:39:02 J bluetoothd[922]: Adapter /org/bluez/922/hci0 has been disabled

when i try to enable bluetooth using bluedevil:
Dec 22 20:01:26 J bluetoothd[922]: Can't init device hci0: Connection timed out (110)

Last edited by kjslag (2011-12-23 04:06:04)

blackdeagle · 2011-12-23 12:09:14

Windows installed the bluetooth device itself, I didn't do anything
Yeah, I use WinXP on linux and it really works fine there:

Looks like this issue is a thing^^ I have no idea why the bluetooth can't be powered up!
Which bluetooth dongle do you have?

Arch Linux

#1 2011-09-16 17:29:21

[bluetooth] hcitool Can't init device hci0: Device or resource busy

#2 2011-09-17 00:51:33

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#3 2011-09-17 00:53:15

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#4 2011-09-17 01:09:10

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#5 2011-09-17 01:11:04

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#6 2011-09-17 01:30:37

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#7 2011-09-17 01:33:42

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#8 2011-09-17 01:49:59

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#9 2011-09-17 01:52:30

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#10 2011-09-17 02:02:55

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#11 2011-09-17 02:03:50

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#12 2011-09-17 02:05:15

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#13 2011-09-17 02:07:00

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#14 2011-09-17 02:12:26

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#15 2011-09-17 02:15:40

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#16 2011-09-17 02:37:49

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#17 2011-09-17 02:48:38

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#18 2011-09-17 03:06:23

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#19 2011-09-17 03:09:55

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#20 2011-09-17 03:16:40

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#21 2011-09-17 11:54:34

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#22 2011-12-22 07:25:54

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#23 2011-12-22 12:30:06

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#24 2011-12-23 04:05:22

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

#25 2011-12-23 12:09:14

Re: [bluetooth] hcitool Can't init device hci0: Device or resource busy

Board footer