Prev: TCP data not ack'ed
Next: CASH FOR CISCO - I BUY USED AND NEW EQUIPMENT & LOTS MORE
From: Mark Hobley on 12 Jul 2010 21:55
I have a Cambridge Silicon Radio bluetooth adapter and I am trying to use
bluetooth for the first time on my Debian based computer.

I have plugged the bluetooth adapter into the usb port of the computer.

I now run lsusb. This produces output as follows:

$ lsusb
Bus 002 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 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I now run bluetooth-properties.

This produces the following output:

** (bluetooth-properties:3450): WARNING **: Could not open RFKILL control
device, please verify your installation

No Bluetooth adapters present
Your computer does not have any Bluetooth adapters plugged in.

What is going wrong here? Why is my adapter not being recognized by
bluetooth-properties even though it is listed in lsusb?


--
/local/home/mark/.Signature

--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
From: Jerry Peters on 13 Jul 2010 15:45
Mark Hobley <markhobley(a)yahoo.donottypethisbit.co> wrote:
> I have a Cambridge Silicon Radio bluetooth adapter and I am trying to use
> bluetooth for the first time on my Debian based computer.
>
> I have plugged the bluetooth adapter into the usb port of the computer.
>
> I now run lsusb. This produces output as follows:
>
> $ lsusb
> Bus 002 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 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
> Dongle (HCI mode)
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> I now run bluetooth-properties.
>
> This produces the following output:
>
> ** (bluetooth-properties:3450): WARNING **: Could not open RFKILL control
> device, please verify your installation
>
> No Bluetooth adapters present
> Your computer does not have any Bluetooth adapters plugged in.
>
> What is going wrong here? Why is my adapter not being recognized by
> bluetooth-properties even though it is listed in lsusb?
>
You don't have the necessary module(s) loaded?

Jerry
From: Mark Hobley on 13 Jul 2010 22:53
On Tue, 13 Jul 2010 19:45:43 +0000, Jerry Peters wrote:

> You don't have the necessary module(s) loaded?

I don't know.

lsmod reveals:

Module Size Used by sco 5545 2
bridge 32507 0
stp 984 1 bridge bnep 7340 2
rfcomm 24404 0
l2cap 21204 6 bnep,rfcomm crc16 1027
1 l2cap btusb 7753 2
bluetooth 34343 14 sco,bnep,rfcomm,l2cap,btusb rfkill
10662 2 bluetooth nfs 202847 2
lockd 48969 1 nfs
fscache 22251 1 nfs
nfs_acl 1671 1 nfs
auth_rpcgss 24541 1 nfs
sunrpc 130859 13 nfs,lockd,nfs_acl,auth_rpcgss fuse
42755 1
loop 9565 0
snd_via82xx 15020 0
snd_ac97_codec 79244 1 snd_via82xx ac97_bus 710
1 snd_ac97_codec snd_pcm_oss 28551 0
snd_mixer_oss 10473 1 snd_pcm_oss snd_pcm 46082
3 snd_via82xx,snd_ac97_codec,snd_pcm_oss snd_page_alloc 5021 2
snd_via82xx,snd_pcm snd_mpu401_uart 4155 1 snd_via82xx
snd_seq_midi 3572 0
snd_rawmidi 12737 2 snd_mpu401_uart,snd_seq_midi
snd_seq_midi_event 3848 1 snd_seq_midi radeon 508562
2
snd_seq 35413 2 snd_seq_midi,snd_seq_midi_event ttm
31080 1 radeon drm_kms_helper 18349 1 radeon drm
111196 4 radeon,ttm,drm_kms_helper i2c_viapro
4383 0
i2c_algo_bit 3489 1 radeon snd_timer 12292 2
snd_pcm,snd_seq uhci_hcd 16021 0
i2c_core 12648 5
radeon,drm_kms_helper,drm,i2c_viapro,i2c_algo_bit snd_seq_device
3661 3 snd_seq_midi,snd_rawmidi,snd_seq ehci_hcd 27909 0
parport_pc 15747 0
sg 16467 0
psmouse 48410 0
sr_mod 10734 0
parport 22170 1 parport_pc via_rhine 14427 0
via_ircc 13279 0
shpchp 21184 0
tpm_tis 5312 0
ns558 1599 0
processor 23267 1
usbcore 98214 4 btusb,uhci_hcd,ehci_hcd tpm
8029 1 tpm_tis gameport 6105 3 snd_via82xx,ns558
cdrom 26475 1 sr_mod tpm_bios 3561 1 tpm
button 3578 0
pcspkr 1235 0
mii 2654 1 via_rhine snd 34102 10
snd_via82xx,snd_ac97_codec,snd_pcm_oss,
snd_mixer_oss,snd_pcm,snd_mpu401_uart,
snd_rawmidi,snd_seq,snd_timer,
snd_seq_device
serio_raw 2912 0
pci_hotplug 18013 1 shpchp irda 71654 1
via_ircc evdev 5520 5
soundcore 3294 1 snd
nls_base 4445 1 usbcore crc_ccitt 1039 1
irda
ext2 45198 4
mbcache 3482 1 ext2
sd_mod 25825 6
crc_t10dif 1012 1 sd_mod ata_generic 2015 0
fan 2590 0
pata_via 5721 5
thermal 9210 0
libata 117219 2 ata_generic,pata_via thermal_sys
9346 3 processor,fan,thermal scsi_mod 102265 4
sg,sr_mod,sd_mod,libata

hciconfig reveals:

hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 UP
RUNNING
RX bytes:6 acl:0 sco:0 events:1 errors:0 TX bytes:3 acl:0 sco:0
commands:6 errors:5

The BD Address of 00:00:00:00:00:00 does not look right to me.

Mark.

--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/


--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
From: Mark Hobley on 14 Jul 2010 08:23
On Wed, 14 Jul 2010 02:53:48 +0000, Mark Hobley wrote:

> hciconfig reveals:
>
> hci0: Type: BR/EDR Bus: USB
> BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 UP
> RUNNING
> RX bytes:6 acl:0 sco:0 events:1 errors:0 TX bytes:3 acl:0 sco:0
> commands:6 errors:5
>
> The BD Address of 00:00:00:00:00:00 does not look right to me.

I rebooted the computer, and I now get a mac address there. This is the
latest output:

hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING
RX bytes:413 acl:0 sco:0 events:18 errors:0
TX bytes:67 acl:0 sco:0 commands:21 errors:4
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)

Mark.

--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/


--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
From: Mark Hobley on 14 Jul 2010 09:14
On Wed, 14 Jul 2010 12:23:08 +0000, Mark Hobley wrote:

> Can't read local name on hci0: Connection timed out (110)

There was a bug in the kernel reported two years ago. Does this still
apply to the current Debian kernels?

https://bugzilla.kernel.org/show_bug.cgi?id=10126

I am currently using kernel version 2.6.32-5-486 (from the upcoming/
testing (squeeze) release).

Mark.

--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/


--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
 | 
Pages: 1
Prev: TCP data not ack'ed
Next: CASH FOR CISCO - I BUY USED AND NEW EQUIPMENT & LOTS MORE