When I try to play a file on my headset via bluetooth I get
that message. I don't have libasound_module_pcm_bluetooth.so. I run
Slackware 10.2 with kernel 2.6.23.1; I had all the bluez-* packages
(3.22: Slackware's most recent version) installed. I uninstalled all
the bluez-* packages, downloaded the latest source from http://www.bluez.org,
built it, had the same result. I found some likely source for
libasound_module_pcm_bluetooth.so in bluez-utils-3.24, ran:
configure --enable-alsa --enable-usb --enable-avctrl --enable-audio
(I don't know that I needed all of those, perhaps just the
'--enable-alsa') rebuilt, and still had the same problem. I figured
out my sound apps were looking only in /usr/lib/alsa while the build
had put the libraries in /usr/local/lib/alsa. I linked the contents
of /usr/local/lib/alsa to /usr/lib/alsa and my apps were happy
(perhaps rebuilding the apps, or other libraries they use, would have
solved the problem too) - at least they didn't complain about not
finding the library, only about not finding a target: I still haven't
figured out how to make a permanent connection to my headset.
russell bell
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
On Thu, 24 Jan 2008, Russell A. Bell wrote:
-> When I try to play a file on my headset via bluetooth I get
-> that message. I don't have libasound_module_pcm_bluetooth.so. I run
-> Slackware 10.2 with kernel 2.6.23.1; I had all the bluez-* packages
-> (3.22: Slackware's most recent version) installed.
I have those, but I can't remember if it was built in the alsa stuff or the
bluez stuff. The dates are newer on the libasound_module* files, and I
upgraded bluez stuff last. Mine was built from source, both alsa and all bluez
stuff. If you have a full install of both those, you should have the files.
Possibly you don't have a full (alsa) install or one is not available from
Slackware that supports bluetooth?
-> I uninstalled all
-> the bluez-* packages, downloaded the latest source from http://www.bluez.org,
-> built it, had the same result.
What happens if you build + install alsa from source, *then* build install
bluez? Sometimes what is built depends on support you already have in-system.
-> I still haven't
-> figured out how to make a permanent connection to my headset.
Same problem here, with a Jabra; but I'm not sure what I'm trying is even
possible. hcitool cc <addr> connects for about a 1/2 second. Anything else
says 'Not connected'. I know the pin to be '0000', but the device doesn't show
up on a scan. The only way I got the address was from when it paired with a
phone.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users