guidol

Here is a working (USB-ports & analog Sound) patched sun50i-a64-nanopi-a64 .DTS/.DTB for Kernel 5.18.15 under armbian bullseye Dont know why these arent automatically configured at armbian/kernel-compile _ _ ____ _ _ __ _ _ | \ | | _ \(_) / \ / /_ | || | | \| | |_) | | / _ \| '_ \| || |_ | |\ | __/| | / ___ \ (_) |__ _| |_| \_|_| |_| /_/ \_\___/ |_| Welcome to Armbian 22.08.0-trunk Bullseye with Linux 5.18.15-sunxi64 No end-user support: community creations System load: 2% Up time: 16 min Local users: 2 Memory usage: 14% of 984M IP: 192.168.6.116 CPU temp: 27°C Usage of /: 24% of 15G RX today: 23.9 MiB [ General system configuration (beta): armbian-config ] Last login: Wed Sep 7 14:05:25 2022 from 192.168.6.17 root@npi-a64-116:~# uname -a Linux npi-a64-116 5.18.15-sunxi64 #trunk SMP Thu Aug 4 12:51:25 +03 2022 aarch64 GNU/Linux root@npi-a64-116:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sun50ia64audio [sun50i-a64-audio], device 0: 1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0 [1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sun9ihdmi [sun9i-hdmi], device 0: SUN9I-HDMI PCM i2s-hifi-0 [SUN9I-HDMI PCM i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 sun50i-a64-nanopi-a64_5_18_15.zip DTS_Changes_NPI_A64.doc DTS_Changes_NPi_A64.pdf

@thedocbwarren How did you start and connect to the Ordoid C2? Because I used the bullseye-cli and it booted right away - BUT I had only the "problem" (like before on C2 images) that I cant connect via SSH to the C2 for the initial setup. The initial setup is only at the HDMI-Port (and an the first boot the filesystem-resize took some time) After I completed the inital setup via HDMI and USB-Keyboad I can connect normally via SSH BTW: After a rebout I have to power off/on for the next startup (u-boot problem) u-boot seems to be actual from the new installation on the MicroSD-Card: root@odroid-c2-3:~# dd if=/dev/mmcblk0 of=/tmp/installed_uboot.bin skip=97 count=1376 1376+0 records in 1376+0 records out 704512 bytes (705 kB, 688 KiB) copied, 0.0471277 s, 14.9 MB/s root@odroid-c2-3:~# strings /tmp/installed_uboot.bin | grep "U-Boot 20" U-Boot 2022.01-armbian (Aug 30 2022 - 06:46:25 +0000) odroid-c2

CLI or Desktop (which Desktop?) ? Jammy, Bulleye or Sid? which images did you try?

doesnt it show up as wlx[MAC-address of your adapter]?

In the newer version of ser2net (like v4.3.3-1) the /etc/ser2net.conf is replaced by the /etc/ser2net.yaml which has the yaml-format OK - here is a working version in yaml-format: # A fully featured configuration file is in # /usr/share/doc/ser2net/examples/ser2net.yaml define: &banner \r\nZ80-MBC2 via Telnet on Port [\p]\r\nDevice connected to [\d]\r\n connection: &z80mbc2 accepter: telnet(rfc2217),tcp,2023 enable: on options: banner: *banner kickolduser: true telnet-brk-on-sync: true connector: serialdev, /dev/ttyUSB0, 115200n81,local

on a Sunvell R69 (H2) and a NanoPi Neo (H3) I got these "old known" eth0 Link Up/Down syndrom, but couldnt find a solution in the forum while using the search-engine armbianmonitor -u System diagnosis information will now be uploaded to Sunvell R69 - Linux sunvell-r69 5.4.0-rc8-sunxi #19.11.3 SMP Wed Nov 27 17:01:29 CET 2019 armv7l armv7l armv7l GNU/Linux : http://ix.io/232T NanoPi Neo - Linux npi-neo 5.3.3-sunxi #5.98 SMP Sat Oct 5 18:34:15 +03 2019 armv7l GNU/Linux : http://ix.io/232U in dmesg it looks like [10536.264427] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10568.008879] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [10571.081067] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10575.177000] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [10580.297247] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10604.873552] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [10607.945753] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10608.969632] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [10612.041827] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10631.498029] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [10633.546213] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10636.618141] dwmac-sun8i 1c30000.ethernet eth0: Link is Down I have the feeling its could have to do with using 1GBit/1000MBit devices on the same 100MBit-Ethernet-Hub, because I do get much mor of these messages when my armbian-build-system-PC is on (which uses a onboard GBit-Ethernet-Card). On the 100MBit-Hub there are also some othe 1GBit-Devices like the NanoPi Neo2. On the PC I did try to force the 1GBit-Card to 100MBit with ethtool -s eth0 speed 100 autoneg off But that doesnt seem to help. On other SBC-devices I could find these messages in the dmesg (and in the froum search it was a problem 4 to 2 years ago) On the other hand there was a disscussion about a new driver version for kernel 4.1.4 at https://forum.armbian.com/topic/4364-dwmac-sun8i- driver-v6/ With debian stretch armabian 5.41 and kernel 4.1.4.34 I did see that problem (and doenst feel it at a SSH-session) on the Sunvell R69.

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: