From: Michael Frey <mfrey@pepper.com>
To: BlueZ List Mailing <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] btsco with 2.6.12
Date: Tue, 9 Aug 2005 16:09:44 -0400 [thread overview]
Message-ID: <AF23A417-8600-4F53-87AC-359586BD2AB1@pepper.com> (raw)
All,
I am using a stock 2.6.12.3 kernel and just built btsco. I am
getting an error when trying to run it and do not know what it means.
root@(none):~# ./btsco
Error: hwdep next device (hw:0): Operation not permitted
Error: control open (hw:1): No such device
Error: Can't find device. Bail
I do have alsa set up and can play audio. Am I just missing
something in my /etc/asound.conf?
Michael
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-08-09 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 20:09 Michael Frey [this message]
2005-08-10 14:51 ` [Bluez-devel] btsco with 2.6.12 Michael Frey
2005-08-11 8:38 ` [Bluez-devel] " Marcus Better
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=AF23A417-8600-4F53-87AC-359586BD2AB1@pepper.com \
--to=mfrey@pepper.com \
--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