Hello hondagx35,
I'm using your image from 14 Mar 2016 and it works like a treat. I don't know if you have tried to further enable the bluetooth module on the rpi3, so I'll just post my findings here. Perhaps it is of some help (and if not, then at least I've learned a bit more about bluez and about building packages on Arch
)
Attention:
I've compiled the following information as best as I could, but I'll not take any responsibility for your actions. Always remember to take a backup of your system before doing anything with pacman or be prepared to cry, wipe and start over (trust me, I know what I'm talking about...).
Also, since RuneAudio (or better mpd-rune) does not use pulseaudio, the use cases for the bluetooth'll be limited.
So now for some fun... For the rpi3 bluetooth to work, one need all patches from pelwell (
https://gist.github.com/pelwell/c8230c48ea24698527cd) applied to the bluez (I used 5.39) package. The PKGBUILD file to create the modified bluez package. I've uploaded it to a gist, since the board does not allow me to upload files without extensions
bluez:
https://gist.github.com/laszloh/3c25466 ... e-pkgbuildOn raspbian, the systemd service "pi-bluetooth.hciuart.service" is responsible of loading the firmware over hci before the bluetooth service starts up. It can be found in the package pi-bluetooth (source is here:
http://archive.raspberrypi.org/debian/p ... bluetooth/) under the BSD3 license. Unfortunately the source-path in the copyright points to 404 (
https://github.com/RPi-Distro/rpi-bluetooth). So I've created a custom package, which gets the source code from the debian repo and assembles an arch package out of it (not my preffered option, but it does the job):
pi-bluetooth:
https://gist.github.com/laszloh/3c25466 ... le-pkbuildI used makepkg to build both packages directly on the rpi3 and since arch has a
fabulous wiki about the packaging tool, I won't dwell on it. Basically issue "makepkg", then install all missing dependencies and after the package is build install them with "pacman -U <package-name>" (I just love makepkg, in contrast debian package seem like using sticks and stones). To speed up the build process, enable parallelisation by modifying the following line in the /etc/makepkg.conf to read like this:
- Code: Select all
MAKEFLAGS="-j5"
To be on the safe sind, enable the bluetooth service by calling "systemctl enable bluetooth". I took be almost an hours to realise why bluetoothctl did not work. Save yourself the time...
After that, restart your pi and keep your fingers crossed. Issue "hciconfig hci0" and look at the output, it should be something like this:
- Code: Select all
hci0: Type: BR/EDR Bus: UART
BD Address: B8:27:EB:70:76:87 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
[...]
If it did not work, consult dmesg to see, if the drivers were loaded correctly. If not, issue "systemctl --failed" to see, if any of the new services failed to start.
If all went well, then it's time to take the module out for a spin. Now you should try run
bluetoothctl and pair your headset. But as stated above, you'll not hear any sound, since bluez5 only supports pulseaudio.
I'm currently working on changing my pi to support both alsa and pulseaudio (yeah I know, latency and no, I don't care
) output. I'll propably give dmix (or pulseaudio-alsa, whichever works better) a spin as I also want to use my system as A2DP sink (so my friends can stream music over bluetooth). After (or
if) I succeed, I'll start a thread describing the hack, if there is demand.
Greetings,
Simon
