RE: [Bluez-devel] Problem with hci_usb

RE: [Bluez-devel] Problem with hci_usb

[Williams, Richard]

>>>James Courtier-Dutton wrote:

SCO support in bluez is still in development.
Once it works correctly in 2.6.x, someone might back port it to 2.4.x,=20
but there is no point in back porting something until it is finished.
Everything you describe above is "known issues".

Cheers
James

<<<<<<<<

Hi all,

I'm trying to get my Linux machine to support audio to a headset. =
There's
been several replies in the last week to my questions about SCO support=20
in Linux. But I haven't found a package or instructions that explain how
to get it to work. A couple of people have said "hstest" or "scotest", =
but
nothing really works. Now I see the above posting. Does this mean I =
should=20
abandon my headset work until SCO is working ?

Regards,

Rich


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

RE: [Bluez-devel] Problem with hci_usb

[Marcel Holtmann]

Hi Richard,

> I'm trying to get my Linux machine to support audio to a headset. There's
> been several replies in the last week to my questions about SCO support 
> in Linux. But I haven't found a package or instructions that explain how
> to get it to work. A couple of people have said "hstest" or "scotest", but
> nothing really works. Now I see the above posting. Does this mean I should 
> abandon my headset work until SCO is working ?

everything depends on what you are trying to achieve. In general we have
SCO support, but it is not perfect and not very easy to use.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with hci_usb

[James Courtier-Dutton]

Williams, Richard wrote:
> 
>>>>James Courtier-Dutton wrote:
> 
> 
> SCO support in bluez is still in development.
> Once it works correctly in 2.6.x, someone might back port it to 2.4.x, 
> but there is no point in back porting something until it is finished.
> Everything you describe above is "known issues".
> 
> Cheers
> James
> 
> <<<<<<<<
> 
> Hi all,
> 
> I'm trying to get my Linux machine to support audio to a headset. There's
> been several replies in the last week to my questions about SCO support 
> in Linux. But I haven't found a package or instructions that explain how
> to get it to work. A couple of people have said "hstest" or "scotest", but
> nothing really works. Now I see the above posting. Does this mean I should 
> abandon my headset work until SCO is working ?
> 
> Regards,
> 
> Rich
> 

Steps required to get a headset paired and play/record sounds from it: -
You have to have: -
kernel 2.6.4 or 2.6.3 with bluez patches. (It might work with 2.4.x 
kernels, but I have no idea if it works or not with them.)
Make sure you are root user for all of the following.

modprobe hci_usb   (If you have a usb dongle)
modprobe rfcomm
modprobe sco
hcid
sdpd
hciconfig hci0 up
bluepin <- Should return "ERR", if it returns some other error, get a 
different version of bluepin.
remove any current "link_key" and "pin" files from /etc/bluetooth.

Get your headset into to "set up pairing" mode. (for me I just keep my 
finger on the power on butter for 15 seconds, and it then flashes red/greed)

hcitool scan
That should return something like "00:0A:D9:48:00:6E       HBH-30"
00:0A:D9:48:00:6E is the bdaddr and will be used in following commands, 
so substitute your own bdaddr.
l2ping  00:0A:D9:48:00:6E   <- This should pop up a window asking for 
your pin.
Enter 0000 <- for may headset.
You should then get something like: -
l2ping  00:0A:D9:48:00:6E
Ping: 00:0A:D9:48:00:6E from 00:A0:96:1F:42:BF (data size 20) ...
20 bytes from 00:0A:D9:48:00:6E id 200 time 28.18ms
20 bytes from 00:0A:D9:48:00:6E id 201 time 20.93ms
20 bytes from 00:0A:D9:48:00:6E id 202 time 15.99ms
20 bytes from 00:0A:D9:48:00:6E id 203 time 27.02ms

This means you now have your devices paired.
This will create a "/etc/bluetooth/link_key" file.

hstest record test1.wav 00:0A:D9:48:00:6E 1
This should output: -
Voice setting: 0x0060
RFCOMM channel connected
SCO audio channel connected (handle 43, mtu 64)
AT*ECBP=?
AT+VGS=15


and then record sound from the headset.

hstest record test1.wav 00:0A:D9:48:00:6E 1
to playback to the sound on the headset.

Cheers
James












-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

RE: [Bluez-devel] Problem with hci_usb

[Williams, Richard]

James,

Thanks very much for the instructions. I'll try this out today.

Best Regards,

Rich

-----Original Message-----
From: James Courtier-Dutton [mailto:James@superbug.demon.co.uk]
Sent: Tuesday, March 02, 2004 7:53 PM
To: Williams, Richard
Cc: BlueZ Mailing List
Subject: Re: [Bluez-devel] Problem with hci_usb


Williams, Richard wrote:
>=20
>>>>James Courtier-Dutton wrote:
>=20
>=20
> SCO support in bluez is still in development.
> Once it works correctly in 2.6.x, someone might back port it to 2.4.x, =

> but there is no point in back porting something until it is finished.
> Everything you describe above is "known issues".
>=20
> Cheers
> James
>=20
> <<<<<<<<
>=20
> Hi all,
>=20
> I'm trying to get my Linux machine to support audio to a headset. =
There's
> been several replies in the last week to my questions about SCO =
support=20
> in Linux. But I haven't found a package or instructions that explain =
how
> to get it to work. A couple of people have said "hstest" or "scotest", =
but
> nothing really works. Now I see the above posting. Does this mean I =
should=20
> abandon my headset work until SCO is working ?
>=20
> Regards,
>=20
> Rich
>=20

Steps required to get a headset paired and play/record sounds from it: -
You have to have: -
kernel 2.6.4 or 2.6.3 with bluez patches. (It might work with 2.4.x=20
kernels, but I have no idea if it works or not with them.)
Make sure you are root user for all of the following.

modprobe hci_usb   (If you have a usb dongle)
modprobe rfcomm
modprobe sco
hcid
sdpd
hciconfig hci0 up
bluepin <- Should return "ERR", if it returns some other error, get a=20
different version of bluepin.
remove any current "link_key" and "pin" files from /etc/bluetooth.

Get your headset into to "set up pairing" mode. (for me I just keep my=20
finger on the power on butter for 15 seconds, and it then flashes =
red/greed)

hcitool scan
That should return something like "00:0A:D9:48:00:6E       HBH-30"
00:0A:D9:48:00:6E is the bdaddr and will be used in following commands,=20
so substitute your own bdaddr.
l2ping  00:0A:D9:48:00:6E   <- This should pop up a window asking for=20
your pin.
Enter 0000 <- for may headset.
You should then get something like: -
l2ping  00:0A:D9:48:00:6E
Ping: 00:0A:D9:48:00:6E from 00:A0:96:1F:42:BF (data size 20) ...
20 bytes from 00:0A:D9:48:00:6E id 200 time 28.18ms
20 bytes from 00:0A:D9:48:00:6E id 201 time 20.93ms
20 bytes from 00:0A:D9:48:00:6E id 202 time 15.99ms
20 bytes from 00:0A:D9:48:00:6E id 203 time 27.02ms

This means you now have your devices paired.
This will create a "/etc/bluetooth/link_key" file.

hstest record test1.wav 00:0A:D9:48:00:6E 1
This should output: -
Voice setting: 0x0060
RFCOMM channel connected
SCO audio channel connected (handle 43, mtu 64)
AT*ECBP=3D?
AT+VGS=3D15


and then record sound from the headset.

hstest record test1.wav 00:0A:D9:48:00:6E 1
to playback to the sound on the headset.

Cheers
James












-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] Problem with hci_usb

[Nils Faerber]

Hi!
I just found a quite strange problem with the hci_usb driver.
We have a Fujitsu Siemens Lifebook with builtin Bluetooth here. This
seems to be a CSR chipset connected via USB internally.
The problem is that the chipset is set to SCO-PCM not SCO-HCI.
Subsequently when SCO is enabled in the hci_usb driver something goes
wrong and the usb-uhci driver constanly generates interrupts which are
accounted to the UHCI and as ERR interrupts (in /proc/interrupts).
Enabling debugging for USB does not produce anything new.
What helped a lot is to disable the SCO option for the hci_usb driver.
But this solution is quite unsatisfying since externally connected USB
Bluetooth dongles would bow also not be able to use SCO over HCI even if
they support it.

This is kernel 2.4.25 without additional patches.

The hci_usb in 2.6.3 must be somewhat different.
It reports unsupported isochronous URBs (sorry, might be wrong, this is
from my memory since I do not have 2.6.3 logs anymore) and disbled it at
device startup. No more unnecessary interrupts and especially no ERR
interrupts here.

So, are those changes also available as patch to fix the 2.4.25 driver?
The current 2.4.25-mh1 patch at least does not seem to include a fix for
this problem...

Apart from that, works like a charm! (Oh, I had to increase the USB
hub.c DEBOUNCE_TIMEOUT from 400 to 1500 to make the device detect
work...)

CU
  nils faerber

-- 
kernel concepts          Tel: +49-271-771091-12
Dreisbachstr. 24         Fax: +49-271-771091-19
D-57250 Netphen          D1 : +49-170-2729106
--



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with hci_usb

[Marcel Holtmann]

Hi Nils,

> I just found a quite strange problem with the hci_usb driver.
> We have a Fujitsu Siemens Lifebook with builtin Bluetooth here. This
> seems to be a CSR chipset connected via USB internally.
> The problem is that the chipset is set to SCO-PCM not SCO-HCI.
> Subsequently when SCO is enabled in the hci_usb driver something goes
> wrong and the usb-uhci driver constanly generates interrupts which are
> accounted to the UHCI and as ERR interrupts (in /proc/interrupts).
> Enabling debugging for USB does not produce anything new.
> What helped a lot is to disable the SCO option for the hci_usb driver.
> But this solution is quite unsatisfying since externally connected USB
> Bluetooth dongles would bow also not be able to use SCO over HCI even if
> they support it.

these are the ISOC transfers. The fix is to submit the ISOC URB's only
when we really have a SCO connection and don't consume USB bandwith with
ISOC URB's when they are not needed.

> The hci_usb in 2.6.3 must be somewhat different.
> It reports unsupported isochronous URBs (sorry, might be wrong, this is
> from my memory since I do not have 2.6.3 logs anymore) and disbled it at
> device startup. No more unnecessary interrupts and especially no ERR
> interrupts here.

This should be fixed in 2.6.4-rc1 and 2.6.3-mh3.

> So, are those changes also available as patch to fix the 2.4.25 driver?
> The current 2.4.25-mh1 patch at least does not seem to include a fix for
> this problem...

Currently there is no real fix for it and once we have one, I have no
plans to backport it to 2.4.

> Apart from that, works like a charm! (Oh, I had to increase the USB
> hub.c DEBOUNCE_TIMEOUT from 400 to 1500 to make the device detect
> work...)

This should be send to the USB guys.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with hci_usb

[Nils Faerber]

Am Di, den 02.03.2004 schrieb Marcel Holtmann um 18:30:
> Hi Nils,
Hi!

> > The hci_usb in 2.6.3 must be somewhat different.
> > It reports unsupported isochronous URBs (sorry, might be wrong, this is
> > from my memory since I do not have 2.6.3 logs anymore) and disbled it at
> > device startup. No more unnecessary interrupts and especially no ERR
> > interrupts here.
> This should be fixed in 2.6.4-rc1 and 2.6.3-mh3.
> > So, are those changes also available as patch to fix the 2.4.25 driver?
> > The current 2.4.25-mh1 patch at least does not seem to include a fix for
> > this problem...
> Currently there is no real fix for it and once we have one, I have no
> plans to backport it to 2.4.

Why that?
2.4 is still the stable kernel and used by many users, so I think it
would be worth the effort.
Would you accept a patch given that someone else does the backport?

> > Apart from that, works like a charm! (Oh, I had to increase the USB
> > hub.c DEBOUNCE_TIMEOUT from 400 to 1500 to make the device detect
> > work...)
> This should be send to the USB guys.

Sure ... just mentioned it for completeness...

> Regards
> Marcel
CU
  nils faerber

-- 
kernel concepts          Tel: +49-271-771091-12
Dreisbachstr. 24         Fax: +49-271-771091-19
D-57250 Netphen          D1 : +49-170-2729106
--

Re: [Bluez-devel] Problem with hci_usb

[Marcel Holtmann]

Hi Nils,

> > Currently there is no real fix for it and once we have one, I have no
> > plans to backport it to 2.4.
> 
> Why that?
> 2.4 is still the stable kernel and used by many users, so I think it
> would be worth the effort.

the current stable kernel is 2.6 and it seems that 2.4 will be closed
with 2.4.27.

> Would you accept a patch given that someone else does the backport?

For this feature you need first to backport the voice setting patch from
2.6 and you have to add the notify framework patch. Both are HCI core
changes and I think these are 2.6 changes only, but if anyone builds a
clean set of patches for 2.4 we can talk again.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Problem with hci_usb

[James Courtier-Dutton]

Nils Faerber wrote:
> Hi!
> I just found a quite strange problem with the hci_usb driver.
> We have a Fujitsu Siemens Lifebook with builtin Bluetooth here. This
> seems to be a CSR chipset connected via USB internally.
> The problem is that the chipset is set to SCO-PCM not SCO-HCI.
> Subsequently when SCO is enabled in the hci_usb driver something goes
> wrong and the usb-uhci driver constanly generates interrupts which are
> accounted to the UHCI and as ERR interrupts (in /proc/interrupts).
> Enabling debugging for USB does not produce anything new.
> What helped a lot is to disable the SCO option for the hci_usb driver.
> But this solution is quite unsatisfying since externally connected USB
> Bluetooth dongles would bow also not be able to use SCO over HCI even if
> they support it.
> 
> This is kernel 2.4.25 without additional patches.
> 
> The hci_usb in 2.6.3 must be somewhat different.
> It reports unsupported isochronous URBs (sorry, might be wrong, this is
> from my memory since I do not have 2.6.3 logs anymore) and disbled it at
> device startup. No more unnecessary interrupts and especially no ERR
> interrupts here.
> 
> So, are those changes also available as patch to fix the 2.4.25 driver?
> The current 2.4.25-mh1 patch at least does not seem to include a fix for
> this problem...
> 
> Apart from that, works like a charm! (Oh, I had to increase the USB
> hub.c DEBOUNCE_TIMEOUT from 400 to 1500 to make the device detect
> work...)
> 
> CU
>   nils faerber
> 

SCO support in bluez is still in development.
Once it works correctly in 2.6.x, someone might back port it to 2.4.x, 
but there is no point in back porting something until it is finished.
Everything you describe above is "known issues".

Cheers
James



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel