From: Sebastian Roth <sebiroth@web.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: strange btsco error
Date: Sun, 20 Feb 2005 17:18:16 +0100 [thread overview]
Message-ID: <cvad1d$8tb$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0502200852440.15784@block.bubble>
Hi Florian,
I think your answer is a bit confusing.
> 1. No, it isn't. However, this should not matter, as I stated that this
> error happens _before_ any bluetooth specific code is executed, in
> btsco.c, line 356: snd_hwdep_open().
>
> 2. cat /proc/asound/cards:
>
> 0 [CK8 ]: NFORCE - NVidia CK8
> NVidia CK8 with ALC650F at 0xe8000000, irq 21
> 1 [U0x46d0x8b0 ]: USB-Audio - USB Device 0x46d:0x8b0
> USB Device 0x46d:0x8b0 at usb-0000:00:02.0-2.4, full speed
> 2 [Headset ]: Bluetooth SCO - BT Headset
> BT Headset 1
As your output of 2. shows it _is_ in the list. That's good!
I found a thread in the mailing list:
http://thread.gmane.org/gmane.linux.bluez.devel/4000
Are you able to open the device using alsamixer as suggested by Lars
Grunewaldt?
Best regards,
Sebastian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-02-20 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 10:25 [Bluez-users] strange btsco error Florian Echtler
2005-02-19 21:05 ` [Bluez-users] " Sebastian Roth
2005-02-20 7:59 ` Florian Echtler
2005-02-20 16:18 ` Sebastian Roth [this message]
2005-02-22 9:50 ` Florian Echtler
2005-02-22 11:41 ` Florian Echtler
2005-02-22 20:42 ` Brad Midgley
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='cvad1d$8tb$1@sea.gmane.org' \
--to=sebiroth@web.de \
--cc=bluez-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.