* [Bluez-devel] btsco and connection problems
@ 2006-06-11 20:03 Sweta Vasudevan
2006-06-11 20:50 ` Brad Midgley
0 siblings, 1 reply; 8+ messages in thread
From: Sweta Vasudevan @ 2006-06-11 20:03 UTC (permalink / raw)
To: bluez-devel
[-- Attachment #1.1: Type: text/plain, Size: 2101 bytes --]
Hi all,
I am trying to get audio-bluetooth working on my linux system-I was hoping
that you could help me out with the errors I'm getting. I am using a Fedora
Core4 2.6.16 kernel, DLink DBT 120 USB(revision B3) and Jabra BT 250
headset.
The headset is detected(hcitool scan), but I'm not able to connect to it:
[root@lirr ~]# hciconfig -a
hci0: Type: USB
BD Address: 00:0D:88:AC:18:A7 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:107 acl:0 sco:0 events:14 errors:0
TX bytes:300 acl:0 sco:0 commands:13 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'lirr.cs.columbia.edu-0'
Class: 0x120104
Service Classes: Networking
Device Class: Computer, Desktop workstation
HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver:
0x20d
Manufacturer: Cambridge Silicon Radio (10)
[root@lirr ~]# hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:0D:88:AC:18:A7 ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.4
Chip version: BlueCore02-External
Max key size: 56 bit
SCO mapping: HCI
[root@lirr ~]# hcitool info 00:07:A4:26:8D:3F
Requesting information ...
Can't create connection: Connection timed out
[root@lirr ~]# hcidump -X
HCI sniffer - Bluetooth packet analyzer ver 1.18
device: hci0 snap_len: 1028 filter: 0xffffffff
(this one hangs forever)
[root@lirr ~]# btsco 00:07:A4:26:8D:3F
Error: Failed to connect to SDP server: Function not implemented
Assuming channel 2
Can't connect RFCOMM channel: Resource temporarily unavailable
[root@lirr ~]# btsco -v 00:07:A4:26:8D:3F
btsco v0.42
Device is 1:0
Error: Failed to connect to SDP server: Function not implemented
Assuming channel 2
Voice setting: 0x0060
Can't connect RFCOMM channel: Resource temporarily unavailable
I made sure that hcid and sdpd are running.
I must be missing something obvious, but can't seem figure it out.
Thanks,
sv.
[-- Attachment #1.2: Type: text/html, Size: 3137 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [Bluez-devel] btsco and connection problems
2006-06-11 20:03 [Bluez-devel] btsco and connection problems Sweta Vasudevan
@ 2006-06-11 20:50 ` Brad Midgley
2006-06-15 3:49 ` Sweta Vasudevan
0 siblings, 1 reply; 8+ messages in thread
From: Brad Midgley @ 2006-06-11 20:50 UTC (permalink / raw)
To: BlueZ development
Sweta
> [root@lirr ~]# hcitool info 00:07:A4:26:8D:3F
> Requesting information ...
> Can't create connection: Connection timed out
> [root@lirr ~]# btsco 00:07:A4:26:8D:3F
> Error: Failed to connect to SDP server: Function not implemented
> Assuming channel 2
>
> Can't connect RFCOMM channel: Resource temporarily unavailable
something more fundamental is wrong with your setup if you can't get the
rfcomm channel connected or an sdp scan. is the headset in pairing mode
when you are trying this stuff?
make sure /etc/bluetooth/hcid.conf has not been customized, try
restarting the bluez utils, etc. that's the sort of thing I do, but
there are probably more systematic ways of narrowing down the problem.
brad
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Bluez-devel] btsco and connection problems
2006-06-11 20:50 ` Brad Midgley
@ 2006-06-15 3:49 ` Sweta Vasudevan
2006-06-15 20:28 ` Brad Midgley
0 siblings, 1 reply; 8+ messages in thread
From: Sweta Vasudevan @ 2006-06-15 3:49 UTC (permalink / raw)
To: BlueZ development
[-- Attachment #1.1: Type: text/plain, Size: 2777 bytes --]
Hello Brad
Yes, the headset is in the pairing mode. I'm not sure if my hcid.conf file
is right:
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $
#
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security user;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
#pin_helper /usr/bin/bluepin;
# D-Bus PIN helper
dbus_pin_helper;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";
# Local device class
class 0x120104;
#class 0x3e0100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# Authentication and Encryption (Security Mode 3)
auth disable;
encrypt disable;
}
Any suggestion will be of great help.
Thanks
sweta
On 6/11/06, Brad Midgley <bmidgley@xmission.com> wrote:
>
> Sweta
>
> > [root@lirr ~]# hcitool info 00:07:A4:26:8D:3F
> > Requesting information ...
> > Can't create connection: Connection timed out
>
> > [root@lirr ~]# btsco 00:07:A4:26:8D:3F
> > Error: Failed to connect to SDP server: Function not implemented
> > Assuming channel 2
> >
> > Can't connect RFCOMM channel: Resource temporarily unavailable
>
> something more fundamental is wrong with your setup if you can't get the
> rfcomm channel connected or an sdp scan. is the headset in pairing mode
> when you are trying this stuff?
>
> make sure /etc/bluetooth/hcid.conf has not been customized, try
> restarting the bluez utils, etc. that's the sort of thing I do, but
> there are probably more systematic ways of narrowing down the problem.
>
> brad
>
>
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
[-- Attachment #1.2: Type: text/html, Size: 6472 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [Bluez-devel] btsco and connection problems
2006-06-15 3:49 ` Sweta Vasudevan
@ 2006-06-15 20:28 ` Brad Midgley
2006-06-16 17:11 ` David Greaves
2006-06-23 1:40 ` Sweta Vasudevan
0 siblings, 2 replies; 8+ messages in thread
From: Brad Midgley @ 2006-06-15 20:28 UTC (permalink / raw)
To: BlueZ development
Sweta
> Yes, the headset is in the pairing mode. I'm not sure if my hcid.conf
> file is right:
the config all looks good.
it's frustrating when even the basic stuff won't go. you could try
another headset or try removing an old pairing if present (see
bluetooth-alsa.sf.net). i switch dongles as one thing to test when
having this kind of trouble...
brad
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Bluez-devel] btsco and connection problems
2006-06-15 20:28 ` Brad Midgley
@ 2006-06-16 17:11 ` David Greaves
2006-06-18 22:59 ` Sweta Vasudevan
2006-06-23 1:40 ` Sweta Vasudevan
1 sibling, 1 reply; 8+ messages in thread
From: David Greaves @ 2006-06-16 17:11 UTC (permalink / raw)
To: BlueZ development
Brad Midgley wrote:
> Sweta
>
>
>> Yes, the headset is in the pairing mode. I'm not sure if my hcid.conf
>> file is right:
>>
>
> the config all looks good.
>
> it's frustrating when even the basic stuff won't go. you could try
> another headset or try removing an old pairing if present (see
> bluetooth-alsa.sf.net). i switch dongles as one thing to test when
> having this kind of trouble...
>
lsmod??
looking for rfcomm
David
--
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Bluez-devel] btsco and connection problems
2006-06-16 17:11 ` David Greaves
@ 2006-06-18 22:59 ` Sweta Vasudevan
0 siblings, 0 replies; 8+ messages in thread
From: Sweta Vasudevan @ 2006-06-18 22:59 UTC (permalink / raw)
To: BlueZ development
[-- Attachment #1.1: Type: text/plain, Size: 2292 bytes --]
Hello David,
> lsmod??
>
> looking for rfcomm
>
>
> David
>
> --
rfcomm did show up. output of lsmod:
Module Size Used by
snd_bt_sco 15020 1
snd_hwdep 9797 1 snd_bt_sco
hci_usb 17109 2
i2c_i810 5445 0
i2c_algo_bit 9161 1 i2c_i810
i915 19521 1
drm 69589 2 i915
parport_pc 27437 1
lp 12929 0
parport 36489 2 parport_pc,lp
autofs4 19653 1
rfcomm 37333 0
l2cap 24641 5 rfcomm
bluetooth 48165 7 hci_usb,rfcomm,l2cap
sunrpc 149093 1
dm_mod 55765 0
video 15429 0
button 6609 0
battery 9413 0
ac 4933 0
ipv6 249601 20
uhci_hcd 32465 0
ehci_hcd 33101 0
hw_random 5977 0
i2c_i801 8909 0
i2c_core 22081 2 i2c_algo_bit,i2c_i801
snd_intel8x0 31965 1
snd_ac97_codec 88673 1 snd_intel8x0
snd_ac97_bus 2496 1 snd_ac97_codec
snd_seq_dummy 3781 0
snd_seq_oss 30885 0
snd_seq_midi_event 7233 1 snd_seq_oss
snd_seq 49677 5
snd_seq_dummy,snd_seq_oss,snd _seq_midi_event
snd_seq_device 9292 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 48625 0
snd_mixer_oss 17473 1 snd_pcm_oss
snd_pcm 84933 4
snd_bt_sco,snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 25029 2 snd_seq,snd_pcm
snd 52513 15
snd_bt_sco,snd_hwdep,snd_intel8x0,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 9633 1 snd
snd_page_alloc 10825 3 snd_bt_sco,snd_intel8x0,snd_pcm
tulip 51041 0
3c59x 44777 0
b44 24653 0
mii 5697 2 3c59x,b44
floppy 63869 0
ext3 128969 2
jbd 57173 1 ext3
Thanks,
Sweta.
Thanks,
Sweta.
[-- Attachment #1.2: Type: text/html, Size: 5197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Bluez-devel] btsco and connection problems
2006-06-15 20:28 ` Brad Midgley
2006-06-16 17:11 ` David Greaves
@ 2006-06-23 1:40 ` Sweta Vasudevan
1 sibling, 0 replies; 8+ messages in thread
From: Sweta Vasudevan @ 2006-06-23 1:40 UTC (permalink / raw)
To: BlueZ development
[-- Attachment #1.1: Type: text/plain, Size: 1116 bytes --]
Hello Brad
>
> the config all looks good.
>
> it's frustrating when even the basic stuff won't go. you could try
> another headset or try removing an old pairing if present (see
> bluetooth-alsa.sf.net). i switch dongles as one thing to test when
> having this kind of trouble...
>
> brad
>
>
> I had already tried this with 2 other dongles(different vendors,
compatible with linux). The d-link dongle - jabra headset combination seems
to have been successful for bluetooth-audio programming, which is why I'm
hoping to get this working. Did you mean trying it with another dongle of
the same model as this one?
I tried to remove the pairing, but there is no link_key entry in
/etc/bluetooth and no bluetooth folder /var/lib; also, the pin file in
/etc/bluetooth was blank. Does this mean that the headset has not been
paired? I've tried re-pairing it by following the instructions in the jabra
manual, but wasn't asked for the passkey again.
I had also tried configuring the security settings like Marcel Holtmann had
suggested to someone else on the mailing-list, but that didn't help
either...
Thanks,
Sweta.
[-- Attachment #1.2: Type: text/html, Size: 1478 bytes --]
[-- Attachment #2: Type: text/plain, Size: 299 bytes --]
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bluez-devel] btsco and connection problems
@ 2006-06-10 23:42 Sweta Vasudevan
0 siblings, 0 replies; 8+ messages in thread
From: Sweta Vasudevan @ 2006-06-10 23:42 UTC (permalink / raw)
To: Bluez-devel
[-- Attachment #1.1: Type: text/plain, Size: 2101 bytes --]
Hi all,
I am trying to get audio-bluetooth working on my linux system-I was hoping
that you could help me out with the errors I'm getting. I am using a Fedora
Core4 2.6.16 kernel, DLink DBT 120 USB(revision B3) and Jabra BT 250
headset.
The headset is detected(hcitool scan), but I'm not able to connect to it:
[root@lirr ~]# hciconfig -a
hci0: Type: USB
BD Address: 00:0D:88:AC:18:A7 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:107 acl:0 sco:0 events:14 errors:0
TX bytes:300 acl:0 sco:0 commands:13 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'lirr.cs.columbia.edu-0'
Class: 0x120104
Service Classes: Networking
Device Class: Computer, Desktop workstation
HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver:
0x20d
Manufacturer: Cambridge Silicon Radio (10)
[root@lirr ~]# hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:0D:88:AC:18:A7 ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.4
Chip version: BlueCore02-External
Max key size: 56 bit
SCO mapping: HCI
[root@lirr ~]# hcitool info 00:07:A4:26:8D:3F
Requesting information ...
Can't create connection: Connection timed out
[root@lirr ~]# hcidump -X
HCI sniffer - Bluetooth packet analyzer ver 1.18
device: hci0 snap_len: 1028 filter: 0xffffffff
(this one hangs forever)
[root@lirr ~]# btsco 00:07:A4:26:8D:3F
Error: Failed to connect to SDP server: Function not implemented
Assuming channel 2
Can't connect RFCOMM channel: Resource temporarily unavailable
[root@lirr ~]# btsco -v 00:07:A4:26:8D:3F
btsco v0.42
Device is 1:0
Error: Failed to connect to SDP server: Function not implemented
Assuming channel 2
Voice setting: 0x0060
Can't connect RFCOMM channel: Resource temporarily unavailable
I made sure that hcid and sdpd are running.
I must be missing something obvious, but can't seem figure it out.
Thanks,
sv.
[-- Attachment #1.2: Type: text/html, Size: 3123 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2006-06-23 1:40 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-11 20:03 [Bluez-devel] btsco and connection problems Sweta Vasudevan
2006-06-11 20:50 ` Brad Midgley
2006-06-15 3:49 ` Sweta Vasudevan
2006-06-15 20:28 ` Brad Midgley
2006-06-16 17:11 ` David Greaves
2006-06-18 22:59 ` Sweta Vasudevan
2006-06-23 1:40 ` Sweta Vasudevan
-- strict thread matches above, loose matches on Subject: below --
2006-06-10 23:42 Sweta Vasudevan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).