guidol

Hi @guidol We figured it out, it had nothing to do with the networking but how it created volumes when using other devices other than HDDS like USB Sticks and mmc memory it would not detect them properly since we were using smartctl to scan for storage devices, now we have used a much better approach using lsblk to list all block devices. I noticed because of the screenshot at the top you sent me had garbled info under select disk. Please give SimpNAS one more shot of testing when you get time. Your testing is helping the project tremendously and we appreciate you!!

Just my perosonal cents:
I got some NanoPis from FriendlyARM with Allwinner-Chips like H2+, H3 , H5 and A64 and they do work alll very well and since years 24/7 - but I got some Rockchip devices from other companys and they are the "black sheeps" of my SBCs - so Iam do not buy Rockchip-devices anymore.
So when try to buy Allwinner devices from FriendlyARM - but isnt that easy anymore without new H5-devices and no real successor in the near future

Nice job!

how about to "not touch" the network configuration?
Some dont like to have the system changed by an "additional" app like SimpNAS.
 
Pihole also doesnt change the network configuration.
 
armbian is normally using networkmanager and Iam personally like the old fashioned way of the /etc/network/interfaces because I dont like to run a service for every little OS puzzle part. Inlikeca short process-list in htop/top
 
some of my non-armbian ARM systems use pnly under 32MB for bootup.
 
So maybe add a option "let network as it is" and DONT TOUCH the ssh access, because thats for the most the way to access their device (no TTL-RS232)
 
Why ist SSH disabled? Doesnt systemd networkd work together with OpenSSH-server?

32bit already builds, 64bit still some problems ... will commit later on.

NOPE doesnt work....

I got a working network-configuration (static) via /etc/network/interfaces...

But the install-routine via web-interface is also asking for the complete network-configuration (cant take the actual).
After going through the webinterface-setup the webinterface say reboot. ssh is also disconnecting BUT the BPi M2 Berry isnt rebooting (is pingable).... and after power off/on the BPi M2 Berry doenst boot anymore
 
Grandma would be very anry with Grandpa 
 
Tested on a BananaPi Me Berry with armbian debian buster Kernel 5.6.16
 
Now I will return to my manually installed working SAMBA-Server  
 

I did download the image, flashed it to a 8GB(SLC) Toshiba SD-HC Card and boot.
DHCP is OK:
 
 
System diagnosis information has been uploaded to http://ix.io/2pFz 
 
@Igor Iam missing the last times the possibility to insert a code-fragment in the forum editor
Is that due to answer on questions from new members? because it isnt helpful to give a answer when it cant be formatted in mono-font when copying something from the console  
 

I think I've found the problem :
 
Those "of_chosen" symbol dependencies came in the @megi commit https://github.com/megous/linux/commit/4ea85aef763727ab40791ae3c0c8dd1bb87ef577
But the "of_chosen" symbol export is not provided in driver/of/base.c like suggested by a guy 4 years ago :
https://lore.kernel.org/patchwork/patch/710174/
 
I'm now compiling new 5.7.y build and will let you know if it is succeeded ...

Because we are downloading one package from there. 
https://github.com/armbian/build/pull/1982

put and save the follwing in /etc/asound.conf and reboot:
 
pcm.!default { type hw card 2 device 1 } ctl.!default { type hw card 2 } after reboot check the volume-level with alsamixer...

is that issue current with kernel 4.4.180 and RTL8211E ( though for 5.6 ) ?
Perhaps " ethtool -K eth0 tso off " disabling TCP Segmentation Offloading will solve this,
however not sure how that impacts performance also if you consider this board will be primarily used as a wireguard vpn/ pihole server.
Can one try to see if that helps/ is acceptable for speeds over 100Mbit?

You dont have a Raspberry Pi 4 with armbian These are Rockchip64 SBCs  
because there is no armbian for the Raspberry Pi

Here is another version :-)
 

Thanks for the suggestion! I just forked the repo and will provide a PR.
 

First you have to enable analog audio...
 
sudo armbian-config ->System ->Hardware -> mark analog-codec ... sudo reboot If you need /etc/asound.conf , you have to create by you own...

I have the same problem on an OrangePi One (H3) with Armbian_20.02.0-rc0_Orangepione_bionic_current_5.4.12. I changed the board, the SD-card and the patch cord, but not the power-supply. I also tried the last archived legacy Image for the OrangePi One. I always got the same problem. I fiddled around with ethtool and found that turning off the auto-negotiation for the ethernet-connection fixed it for me. I don't know whats going on in the background. As I understand it,  depending on the other side of the connection the connection could end as 10 Mbps half duplex if the auto-negotiation is turned off. But in my case (Fritzbox) the connection is rock-solid and the speed is also good. So maybe this solution that i found in some forum helps you too:
 

Hello.
 
Armbian_5.35_Orangepizero_Ubuntu_xenial_default_3.4.113.7z
Orange Pi Zero 256
 
I am rading the bootlog via serial console.
 
[FAILED] Failed to start Load Kernel Modules. See 'systemctl status systemd-modules-load.service' for details.
 
# systemctl status systemd-modules-load.service â systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-modules-load.service.d ââ10-timeout.conf Active: failed (Result: exit-code) since Sun 2018-12-30 00:20:40 CET; 3min 8s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 167 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 167 (code=exited, status=1/FAILURE) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. Warning: systemd-modules-load.service changed on disk. Run 'systemctl daemon-reload' to reload units. # journalctl -f -b _PID=167 -- Logs begin at Sun 2018-12-30 00:20:45 CET. -- Dec 30 00:20:45 opi-06-app-c13 systemd-modules-load[167]: Failed to insert 'xradio_wlan': Connection timed out Dec 30 00:20:45 opi-06-app-c13 systemd-modules-load[167]: Inserted module 'g_serial' Dec 30 00:20:45 opi-06-app-c13 systemd-modules-load[167]: Inserted module 'xradio_wlan' ^C # cat /etc/modules #w1-sunxi #w1-gpio #w1-therm #sunxi-cir xradio_wlan g_serial xradio_wlan  
If I remove any xradio_wlan, then wlan0 is not available at boot.
 
Is there a way to fix the boot error message, without loosing wlan0 ?
 
Obviously, some one is aware of an issue, because some dev has put the same line twice in modules ...

Thank you for this!  Works great on my NanoPi NEO Black.  Will be updating a couple of Nano Pi NEO and NEO2 from FriendlyARM to Armbian using this also!
 
Ray
 

If you know the movie "Wargames" then you may know the computer of "David Lightman" a IMSAI 8080
 
Udo Munk did create the software z80pack (last version from 2017 v1.36 at https://www.autometer.de/unix4fun/z80pack/ )
which does include
- IMSAI 8080
- Altair
- Cromemco Z1
and 
- cpmsim
Emulation.
 
Against the text based cpmsim emulation the other features a graphical frontpanel with "blinken lights"
 
Yesterday I did try to compile/start my favourite IMSAI 8080.
I did follow the instructions - which I collect and wrote for me - see attached to this message.
 
But yesterdy I only got limited success (after many "bad" compiles with missing dependencies) in starting the IMSAI 8080 emulation.
I did get the graphical frontend *yeah* - but after POWERON/RUN the computer I didnt get any terminal-output
 
After MANY retries I did give up  
Today I did the same compile-session on a PC with Ubuntu MATE 20.04LTS and it did work in the first try  
 
At first I got no idea what wasnt working....but then I discovered that - when moving the graphical frontpanel - the terminal-output was written VERY SLOWLY to the terminal-screen *Aha*
 
Because the garphical frontpanel seem to work perfectly (and did also compile very well) I searched inside the directorys of imsaisim and found in the "conf"-directory the file system.conf
 
There in system.conf is a line where the FPS-rate of the frontpanel as default is configured to 60 FPS (Frames per second).
While taking a look at htop the NanoPi A64 (where my armbian buster Desktop does run) the cpu-utilization is near 90%
 
So my gut instinct did tell me thats to much and the NanoPi has to much work with the frontpanel than writing to the terminal.
 
I changed the framerate in
- for the IMSAI 8080: ~/z80pack-1.36/imsaisim/conf/systemconf
- for the Altair: ~/z80pack-1.36/altairsim/conf/systemconf
- for the Cromemco Z1: ~/z80pack-1.36/cromemcosim/conf/systemconf
to
# front panel framerate fp_fps 10 After that change all 3 emulators with graphical frontend did startup and give output on the terminal
 
I contacted Udo Munk via email about this topic and he already knew it
He wrote that he had implemented the FPS option, because some lower-spec systems had problems to achieve the power for producing a framerate of 60 FPS for the frontpanel.
 
 
Here my write-up / documentation how I did compile /  successfully start the IMSAI 8080 emulation:
(many thanks to John Kennedy from the FB-Group Altair 8800 for double-checking my instructions!)
====================================================================== My normal evironment for compiling source: ====================================================================== apt install gcc libncurses5-dev liblua5.3-dev git make zip unzip -y ====================================================================== Getting z80pack-source: ====================================================================== cd ~ wget https://www.autometer.de/unix4fun/z80pack/ftp/z80pack-1.36.tgz tar -xvf z80pack-1.36.tgz cd ~/z80pack-1.36/ ====================================================================== Dependencies named by z80pack: ====================================================================== libjpeg X11 OpenGL c++ compiler (g++) libpthread ====================================================================== Packages for the z80pack-dpendencies: ------------------------------------- apt install libjpeg-dev x11-common libpthread-stubs0-dev libxmu-dev apt install mesa-common-dev z80asm libglu1-mesa-dev freeglut3-dev ====================================================================== ==> <== ==> I built all packages of z80pack in the following order: <== ==> <== ==> ATTENTION: for some commands you may have to use sudo <== ====================================================================== 1.) FRONTPANEL ====================================================================== cd ~/z80pack-1.36/frontpanel/ make -f Makefile.linux NOTE: Be sure to copy libfrontpanel.so to a shared library path! NOTE: cp ~/z80pack-1.36/frontpanel/libfrontpanel.so /usr/lib make -f Makefile.linux clean ====================================================================== 2.) CPMSIM ====================================================================== cd ~/z80pack-1.36/cpmsim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean ====================================================================== 3.) CPMSIM-TOOLS ====================================================================== if you are user root: mkdir /root/bin if you are user pi: mkdir /home/pi/bin cd ~/z80pack-1.36/cpmsim/srctools make make install NOTE: (does install in /root/bin/) NOTE: Tools installed in /root/bin, make sure it is NOTE: included in the systems search PATH NOTE: export PATH=$PATH:/root/bin NOTE: or NOTE: export PATH=$PATH:/home/pi/bin make clean ====================================================================== 4.) ALTAIRSIM ====================================================================== cd ~/z80pack-1.36/altairsim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/altairsim/conf/system.conf ====================================================================== 5.) CROMEMCOSIM ====================================================================== cd ~/z80pack-1.36/cromemcosim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/cromemcosim/conf/system.conf ====================================================================== 6.) IMSAISIM ====================================================================== cd ~/z80pack-1.36/imsaisim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/imsaisim/conf/system.conf ====================================================================== PREPARE 1st start of imsaisim; ====================================================================== cp ~/z80pack-1.36/frontpanel/libfrontpanel.so /usr/lib cd ~/z80pack-1.36/imsaisim rm conf ln -s conf_2d conf export PATH=$PATH:/root/bin NOTE: maybe add the export-command to your ~/.bashrc ====================================================================== START of IMSAI 8080 CPM v2.2 from the x-terminal on the desktop (needs to be a "x-terminal) for connecting to the X-Server for creating the graphical frontpanel: ====================================================================== ./cpm22 NOTE: maybe root has to give access-rights: NOTE: chmod -R 666 ~/z80pack-1.36/imsaisim/disks NOTE: on the x-terminal root and the to the desktop logged in user can NOTE :start the application and connect to the X-server on a NOTE: SSH-terminal ONLY the to the desktop logged in user can start the NOTE: application and connect to the X-server to give root access to NOTE: the X-server from a SSH-terminal the he to the desktop logged NOTE: in user has to give root access via the xhost command: NOTE: xhost SI:localuser:root ====================================================================== POWER-UP the IMSAI 8080 in the graphical frontpanel ====================================================================== Press "POWER ON " upper part on the first switch on the right side (POWER ON / POWER OFF) Press "RUN" upper part of the third (red) switch (RUN/STOP) ====================================================================== Exit the IMSAI 8080 ====================================================================== Enter "bye" on the CP/M-commandline OR press "POWER OFF " lower part on the first switch on the right side (POWER ON / POWER OFF) OR close the graphical frontpanel with the close button X (Window-Manager-close)  
Pictures (screenshots are done with Mirage as you can see) of my "success"

If you know the movie "Wargames" then you may know the computer of "David Lightman" a IMSAI 8080
 
Udo Munk did create the software z80pack (last version from 2017 v1.36 at https://www.autometer.de/unix4fun/z80pack/ )
which does include
- IMSAI 8080
- Altair
- Cromemco Z1
and 
- cpmsim
Emulation.
 
Against the text based cpmsim emulation the other features a graphical frontpanel with "blinken lights"
 
Yesterday I did try to compile/start my favourite IMSAI 8080.
I did follow the instructions - which I collect and wrote for me - see attached to this message.
 
But yesterdy I only got limited success (after many "bad" compiles with missing dependencies) in starting the IMSAI 8080 emulation.
I did get the graphical frontend *yeah* - but after POWERON/RUN the computer I didnt get any terminal-output
 
After MANY retries I did give up  
Today I did the same compile-session on a PC with Ubuntu MATE 20.04LTS and it did work in the first try  
 
At first I got no idea what wasnt working....but then I discovered that - when moving the graphical frontpanel - the terminal-output was written VERY SLOWLY to the terminal-screen *Aha*
 
Because the garphical frontpanel seem to work perfectly (and did also compile very well) I searched inside the directorys of imsaisim and found in the "conf"-directory the file system.conf
 
There in system.conf is a line where the FPS-rate of the frontpanel as default is configured to 60 FPS (Frames per second).
While taking a look at htop the NanoPi A64 (where my armbian buster Desktop does run) the cpu-utilization is near 90%
 
So my gut instinct did tell me thats to much and the NanoPi has to much work with the frontpanel than writing to the terminal.
 
I changed the framerate in
- for the IMSAI 8080: ~/z80pack-1.36/imsaisim/conf/systemconf
- for the Altair: ~/z80pack-1.36/altairsim/conf/systemconf
- for the Cromemco Z1: ~/z80pack-1.36/cromemcosim/conf/systemconf
to
# front panel framerate fp_fps 10 After that change all 3 emulators with graphical frontend did startup and give output on the terminal
 
I contacted Udo Munk via email about this topic and he already knew it
He wrote that he had implemented the FPS option, because some lower-spec systems had problems to achieve the power for producing a framerate of 60 FPS for the frontpanel.
 
 
Here my write-up / documentation how I did compile /  successfully start the IMSAI 8080 emulation:
(many thanks to John Kennedy from the FB-Group Altair 8800 for double-checking my instructions!)
====================================================================== My normal evironment for compiling source: ====================================================================== apt install gcc libncurses5-dev liblua5.3-dev git make zip unzip -y ====================================================================== Getting z80pack-source: ====================================================================== cd ~ wget https://www.autometer.de/unix4fun/z80pack/ftp/z80pack-1.36.tgz tar -xvf z80pack-1.36.tgz cd ~/z80pack-1.36/ ====================================================================== Dependencies named by z80pack: ====================================================================== libjpeg X11 OpenGL c++ compiler (g++) libpthread ====================================================================== Packages for the z80pack-dpendencies: ------------------------------------- apt install libjpeg-dev x11-common libpthread-stubs0-dev libxmu-dev apt install mesa-common-dev z80asm libglu1-mesa-dev freeglut3-dev ====================================================================== ==> <== ==> I built all packages of z80pack in the following order: <== ==> <== ==> ATTENTION: for some commands you may have to use sudo <== ====================================================================== 1.) FRONTPANEL ====================================================================== cd ~/z80pack-1.36/frontpanel/ make -f Makefile.linux NOTE: Be sure to copy libfrontpanel.so to a shared library path! NOTE: cp ~/z80pack-1.36/frontpanel/libfrontpanel.so /usr/lib make -f Makefile.linux clean ====================================================================== 2.) CPMSIM ====================================================================== cd ~/z80pack-1.36/cpmsim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean ====================================================================== 3.) CPMSIM-TOOLS ====================================================================== if you are user root: mkdir /root/bin if you are user pi: mkdir /home/pi/bin cd ~/z80pack-1.36/cpmsim/srctools make make install NOTE: (does install in /root/bin/) NOTE: Tools installed in /root/bin, make sure it is NOTE: included in the systems search PATH NOTE: export PATH=$PATH:/root/bin NOTE: or NOTE: export PATH=$PATH:/home/pi/bin make clean ====================================================================== 4.) ALTAIRSIM ====================================================================== cd ~/z80pack-1.36/altairsim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/altairsim/conf/system.conf ====================================================================== 5.) CROMEMCOSIM ====================================================================== cd ~/z80pack-1.36/cromemcosim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/cromemcosim/conf/system.conf ====================================================================== 6.) IMSAISIM ====================================================================== cd ~/z80pack-1.36/imsaisim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/imsaisim/conf/system.conf ====================================================================== PREPARE 1st start of imsaisim; ====================================================================== cp ~/z80pack-1.36/frontpanel/libfrontpanel.so /usr/lib cd ~/z80pack-1.36/imsaisim rm conf ln -s conf_2d conf export PATH=$PATH:/root/bin NOTE: maybe add the export-command to your ~/.bashrc ====================================================================== START of IMSAI 8080 CPM v2.2 from the x-terminal on the desktop (needs to be a "x-terminal) for connecting to the X-Server for creating the graphical frontpanel: ====================================================================== ./cpm22 NOTE: maybe root has to give access-rights: NOTE: chmod -R 666 ~/z80pack-1.36/imsaisim/disks NOTE: on the x-terminal root and the to the desktop logged in user can NOTE :start the application and connect to the X-server on a NOTE: SSH-terminal ONLY the to the desktop logged in user can start the NOTE: application and connect to the X-server to give root access to NOTE: the X-server from a SSH-terminal the he to the desktop logged NOTE: in user has to give root access via the xhost command: NOTE: xhost SI:localuser:root ====================================================================== POWER-UP the IMSAI 8080 in the graphical frontpanel ====================================================================== Press "POWER ON " upper part on the first switch on the right side (POWER ON / POWER OFF) Press "RUN" upper part of the third (red) switch (RUN/STOP) ====================================================================== Exit the IMSAI 8080 ====================================================================== Enter "bye" on the CP/M-commandline OR press "POWER OFF " lower part on the first switch on the right side (POWER ON / POWER OFF) OR close the graphical frontpanel with the close button X (Window-Manager-close)  
Pictures (screenshots are done with Mirage as you can see) of my "success"

I downloaded
https://dl.armbian.com/orangepizeroplus/archive/Armbian_20.02.1_Orangepizeroplus_buster_current_5.4.20.7z
unzipped it with 7Zip and flashed the .img with Ether to the card and it does boot and work on my
OPi Zero Plus (H5):
System diagnosis information has been uploaded to http://ix.io/2nVF
 
login as: root root@192.168.6.98's password: ___ ____ _ _____ ____ _ / _ \| _ \(_) |__ /___ _ __ ___ | _ \| |_ _ ___ | | | | |_) | | / // _ \ '__/ _ \ | |_) | | | | / __| | |_| | __/| | / /| __/ | | (_) | | __/| | |_| \__ \ \___/|_| |_| /____\___|_| \___/ |_| |_|\__,_|___/ Welcome to Armbian buster with Linux 5.4.20-sunxi64 package bsp-kernel[20.02.1] u-boot[20.02.1] dtb [20.02.1] firmware [20.02.1] config[20.02.1] branch[current] System load: 0.19 0.06 0.02 Up time: 1 min Memory usage: 18 % of 479MB IP: 192.168.6.98 CPU temp: 59°C Usage of /: 17% of 7.2G Last login: Sun May 31 16:29:52 2020 from 192.168.6.17  

@TCH My first message in this thread is more than 2 years old and since I did try BlueALSA
Today I rechecked the instructions and did get the same errors while using HCI and DEV entrys in the commands aplay and mpg123.
 
I found out that we only have to set bluealsa as device and not the HCI and DEV config
I also have now a working /etc/asound.conf for bluealsa.
 
OK - here now a not very formatted NEW instruction-set, which did work for me today
 
Dependencies: =================================================== apt-get install libasound2 libasound2-dev dh-autoreconf libortp-dev bluez bluez-tools libbluetooth-dev libusb-dev libglib2.0-dev libudev-dev libical-dev libreadline-dev libsbc1 libsbc-dev bluetooth libfdk-aac-dev libdbus-1-dev Installation: =================================================== git clone https://github.com/Arkq/bluez-alsa.git cd bluez-alsa/ autoreconf --install mkdir build && cd build ../configure --enable-aac --enable-ofono (without --enable-debug to get rid of the ebug messages while starting/conencting) OR For systems with aarch64-cpu-type (like the Allwinner H5 or A64 = 64bit): ------------------------------------------------------------------------- ../configure --enable-aac --enable-ofono --with-alsaplugindir=/usr/lib/aarch64-linux-gnu/alsa-lib ( /usr/lib/aarch64-linux-gnu/alsa-lib is generated while compiling ) make && make install Starting BlueALSA 1st time: =================================================== bluealsa --profile=a2dp-source --a2dp-force-audio-cd & Pairing and trusting BT-device: =================================================== bluetoothctl scan on [NEW] Device 00:11:67:3F:9B:18 BTLS9001 scan off pair 00:11:67:3F:9B:18 trust 00:11:67:3F:9B:18 quit REBOOT: (maybe) =================================================== reboot Starting BlueALSA 2nd time: =================================================== export LIBASOUND_THREAD_SAFE=0 bluealsa --profile=a2dp-source --a2dp-force-audio-cd & Connect truested speaker manually: =================================================== echo -e "connect 00:11:67:3F:9B:18\nquit" | bluetoothctl NEW syntax for aplay and mpg123 (without HCI and DEV): =================================================== aplay -D bluealsa /home/guido/espeak.wav mpg123 -v -a bluealsa -@ /home/guido/iradio/MP3_FFH80s CREATING a BlueALSA /etc/asound.conf: # ================================================= pcm.!default "bluealsa" ctl.!default "bluealsa" defaults.bluealsa.interface "hci0" defaults.bluealsa.device "00:11:67:3F:9B:18" defaults.bluealsa.profile "a2dp" # ================================================= Info about bluealsa: =================================================== amixer -D bluealsa Set the volume in alsamixer: =================================================== alsamixer -D bluealsa aplay and mpg123 AFTER creating a BlueALSA /etc/asounf.conf: =================================================== aplay /home/guido/espeak.wav mpg123 -v -@ /home/guido/iradio/MP3_FFH80s Disconnecting the trusted/connected BT-device: =================================================== echo -e "disconnect 00:11:67:3F:9B:18\nquit" | bluetoothctl and here the messages while compiling about the Libraries in /usr/lib/aarch64-linux-gnu/alsa-lib:
 
 
 
So - this should help you and me and anyone who will try BlueALSA in the (near) future

I did short test and the problem with the BT-address parse seems to occur only with bluealsa-aplay
bluealsa-aplay: E: Couldn't parse BT addresses: Invalid argument
I paired/truted a second BT-speaker with bluetoothctl and now I can adress a different speaker with:
 
aplay -D bluealsa:DEV=00:11:67:3F:9B:18 ./espeak.wav aplay -D bluealsa:DEV=78:44:05:00:69:9A ./espeak.wav OR mpg123 -v -b1024 -a bluealsa:DEV=00:11:67:3F:9B:18 -@ /home/guido/iradio/MP3_FFH80s mpg123 -v -b1024 -a bluealsa:DEV=78:44:05:00:69:9A -@ /home/guido/iradio/MP3_FFH80s My Bluetooth-USB-Transceiver connected to the NanoPi A64: --------------------------------------------------------- root@npi-a64-116(192.168.6.116):~# lsusb Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) root@npi-a64-116(192.168.6.116):~# dmesg |grep -i blue [ 7.341576] Bluetooth: Core ver 2.22 [ 7.341667] Bluetooth: HCI device and connection manager initialized [ 7.341685] Bluetooth: HCI socket layer initialized [ 7.341691] Bluetooth: L2CAP socket layer initialized [ 7.341706] Bluetooth: SCO socket layer initialized [ 17.611736] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 17.611746] Bluetooth: BNEP filters: protocol multicast [ 17.611769] Bluetooth: BNEP socket layer initialized As I did see Bluetooth Ethernet I blacklisted it :) nano /etc/modprobe.d/blacklist.conf --> insert the lines and reboot: # blacklist bluetooth ethernet bnep blacklist bnep
 
 
MP3_FFH80s

Yesterday I did get a new little Bluetooth-Speaker, but without AUX - I rechecked some Bluetooth-Commands.
But could never connect,  because the Pi missed the protocol A2DP - which was only available with PulseAudio as Bluetooth-Module
 
So I used my 2nd OrangePi One with USB-Bluetooth-Dongle and mainline-kernel for this challenge:
ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.18-sunxi
Linux opi-one-main 4.14.18-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l GNU/Linux

I like ALSA more than PulseAudio - I searched for ALSA and Bluetooth-Audio - and did found no good news about Audio and Bluetooth while using ALSA.
At the second search I did found the Project
BlueALSA (formerly know as BluezALSA) :  https://github.com/Arkq/bluez-alsa
 
While BlueALSA isnt available as .deb-package (and if then only on the RPi) I did use the following sites for documentation:
 
As Dependencies I had to install the following packages:
apt-get install libasound2-dev dh-autoreconf libortp-dev bluez bluetooth bluez-tools libbluetooth-dev libusb-dev libglib2.0-dev libudev-dev libical-dev libreadline-dev libsbc1 libsbc-dev libfdk-aac-dev
 
libfdk-aac-dev is one more than at the RPi-Documetation page.
 
For creating / compiling BlueALSA I did use the follwoing commands:
cd /home/guido
git clone https://github.com/Arkq/bluez-alsa.git
cd bluez-alsa/
autoreconf --install
mkdir build && cd build
../configure --disable-hcitop --with-alsaplugindir=/usr/lib/arm-linux-gnueabihf/alsa-lib
make && sudo make install
 
When BlueALSA has been created, then you can start BlueALSA as background task:
bluealsa --disable-hfp &
 
Now - for using your bluetooth-speaker/headset - with BlueALSA you have to intoduce the device to the bluetooth-stack using bluetoothctl:
bluetoothctl >
scan on
[NEW] Device 30:23:23:F4:48:2C TH-S10U
scan off
pair 30:23:23:F4:48:2C
trust 30:23:23:F4:48:2C
exit
 
After that power off&on the bt-speaker device and the device will connect automatically as a trusted device.
 
Before we try our first audio-command we had to export one thing to make BlueALSA mor system-friendly:
export LIBASOUND_THREAD_SAFE=0because of a message while compiling:
 
Now you can try your first commands for getting audio out of the device:
 
Text to speech:
espeak "Hello, how are you?" -w /home/guido/espeak.wav -s145
aplay -D bluealsa:HCI=hci0,DEV=30:23:23:F4:48:2C,PROFILE=a2dp /home/guido/espeak.wav
 
Internetradio:
mpg123 -a bluealsa:HCI=hci0,DEV=30:23:23:F4:48:2C,PROFILE=a2dp -@ /home/guido/ffh80s.pls
 
For shorting the command you could create a ~/.asoundrc with the following content:
defaults.bluealsa.interface "hci0"
defaults.bluealsa.device "30:23:23:F4:48:2C"
defaults.bluealsa.profile "a2dp"
defaults.bluealsa.delay 10000
 
Now you can the shorter version of the command:
mpg123 -a bluealsa -@ /home/guido/ffh80s.pls
 
For set the volume of such a device you have to know the "real" name of the device out of the bluetoothctl and the name of the used protocol:
Device: 30:23:23:F4:48:2C TH-S10U
Protocol: A2DP
amixer -D bluealsa sset 'TH-S10U - A2DP ' 70%
 
Here as information the dmesg-part of my bluetooth-dongle: