From: Brandon Philips <brandon@ifup.org>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Unable to set number of SCO buffers : please upgrade your Kernel !
Date: Sun, 15 Apr 2007 02:57:29 -0700 [thread overview]
Message-ID: <20070415095728.GA6212@ifup.org> (raw)
Hello-
I am running 2.6.21-rc6 with sco-flowcontrol-v4.2.diff applied and I am
getting the following error when trying to use my Platronics 640
headset. The computer is a Thinkpad x60s running Debian unstable.
Any suggestions? I am willing to test patches, etc.
Cheers,
Brandon
philips@plankton:~$ aplay -D headset /usr/share/sounds/ekiga/busytone.wav
Playing WAVE '/usr/share/sounds/ekiga/busytone.wav' : Signed 16 bit
Little Endian, Rate 8000 Hz, Mono
ALSA lib pcm_sco.c:273:(sco_headset_hw_params) Unable to set number of
SCO buffers : please upgrade your Kernel !
aplay: set_params:965: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 16
CHANNELS: 1
RATE: 8000
PERIOD_TIME: 3000
PERIOD_SIZE: 24
PERIOD_BYTES: 48
PERIODS: 167
BUFFER_TIME: 501000
BUFFER_SIZE: 4008
BUFFER_BYTES: 8016
TICK_TIME: [0 0]
philips@plankton:~$ headsetd -n
headsetd[6326]: Bluetooth headset daemon version 0.5
headsetd[6326]: Configuration phase ended: target bdaddr is
00:03:89:59:DE:F9, timeout is 6000 ms
headsetd[6326]: Changing state: Idle-->Paging
headsetd[6326]: Changing state: Paging-->Connecting
headsetd[6326]: Changing state: Connecting-->Ready
headsetd[6326]: Changing state: Ready-->Opening
headsetd[6326]: SCO channel opened handle=0x0001 mtu=64
headsetd[6326]: Changing state: Opening-->Streaming
headsetd[6326]: Appli closed socket
headsetd[6326]: Changing state: Streaming-->Zombie
headsetd[6326]: Nobody uses SCO channel anymore, closing it.
headsetd[6326]: Changing state: Zombie-->Connected
Relevant dmesg output:
hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
~/.asoundrc
pcm.headset {
@args [BDADDR TIMEOUT]
# The Bluetooth device address for target headset, used for
# Audio Gateway (PC) initiated connections
# Please note that this value is ignored when the connection is
# Headset initiated
@args.BDADDR {
type string
default 00:03:89:59:XX:XX # XX:XX for privacy
}
# This value represents how long we will try to reach the
# headset, until we give up.
# Value is in milliseconds
@args.TIMEOUT {
type integer
default 6000
}
type sco
bdaddr $BDADDR
timeout $TIMEOUT
}
ctl.headset {
type sco
}
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-04-15 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 9:57 Brandon Philips [this message]
2007-04-15 18:34 ` [Bluez-devel] Unable to set number of SCO buffers : please upgrade your Kernel ! Brad Midgley
2007-04-16 7:35 ` Brandon Philips
2007-04-24 18:48 ` Marc Haber
2007-04-29 12:34 ` Klaus
2007-04-29 16:17 ` Klaus
2007-04-29 16:18 ` Brad Midgley
2007-04-29 20:58 ` Klaus
-- strict thread matches above, loose matches on Subject: below --
2007-04-22 6:52 John Frankish
2007-04-22 16:50 ` Brad Midgley
2007-04-23 4:07 ` John Frankish
2007-04-24 13:45 ` Brad Midgley
2007-04-25 5:56 ` John Frankish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070415095728.GA6212@ifup.org \
--to=brandon@ifup.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox