@milom , try installing the Volumio-3.236-2022-03-07-orangepipc2.
He is also on H5. It should start and work.
Check it out, I’m interested myself.
3.236 run very slow on 1GB OrangePi Lite
1 Like
This is a test image for the operation of the plugin DSP.
Install the version 3.198, but the DSP plugin will not work there.
Thanks, But 3.198 is slow and frozen, too.
1 Like
On my board (1GB OrangePi Lite), both images work fast.
I checked it again yesterday - re-installed on Samsung microSD (32 Gb). It works quite speedly.
PS: some time I installed on a no name microSD card and the system was slowing down.
Many thanks @Adrii for a working plugin OLED spectrum display on Volumio 3 (OLED spectrum display on Volumio on Raspberry Pi Zero W).
Installation instructions for Volumio 3:
mpd_oled/install_volumio3_deb.md at master · antiprism/mpd_oled · GitHub
Source code:
GitHub - antiprism/mpd_oled: MPD, Volumio, RuneAudio and Moode OLED status and spectrum display for Raspberry Pi (and similar)
An example of working with the Orange Pi Lite board::
1 Like
awesome! I didn’t expect MPD OLED to be working on other platforms rather than raspberry pi
what did you do to make it working? I’d like to try on NanoPi NEO2
1 Like
I did it according to the instructions:
It’s very simple there.
The main thing is to find out the device address:
sudo i2cdetect -y 1
or
sudo i2cdetect -y 0
My address is: 3c
volumio:~$ sudo i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
And accordingly, I changed the launch of the service:
sudo mpd_oled_service_edit -o 3 -B 0 -a 3c -b 10 -g 1 -f 15
All parameters are clear from the file README.md or running
mpd_oled -h
1 Like
Hi VyacheslavS
I have installed rev 3.236 with pcm5102a on Orange Pi PC.
48kHz 16bit music sounds good.
But 96 kHz 24 bit no sound at all.
$ cat /proc/asound/card1/pcm0p/sub0/hw_params
access: MMAP_INTERLEAVED
format: S24_LE
subformat: STD
channels: 2
rate: 96000 (96000/1)
period_size: 8000
buffer_size: 48000
I checked Volumio 2 does not work too.
Please explain pcm5102a >48kHz works or not?
Thanks
@phenolog, I can hardly help you, I don’t use a pcm5102a DAC and I can’t check and change something. Once upon a time I had such a DAC, but I was not satisfied with the sound. Now I have several different USB DACs and the sound quality is much better.
I use PCM1502a successfully on rpi with modeaudio. It plays 32/192 good.
And on an Orange PI Pc it look like doesn’t work at the i2c module.
Because aplay sends a file to the DAC but there is no sound.
> alsacap
***
Card 1, ID `I2Smaster', name `I2S-master'
Device 0, ID `1c22000.i2s-pcm5102a-hifi pcm5102a-hifi-0', name `1c22000.i2s-pcm5102a-hifi pcm5102a-hifi-0', 1 subdevices (1 available)
2 channels, sampling rate 8000..192000 Hz
Sample formats: S16_LE, S24_LE
Buffer size range from 64 to 131072
Period size range from 32 to 16384
> aplay -f S24_LE -r 96000 -c 2 '05. The Great Gig In The Sky.flac'
Playing raw data '05. The Great Gig In The Sky.flac' : Signed 24 bit Little Endian, Rate 96000 Hz, Stereo
@phenolog, this problem has been going on for a long time and it seems that it has not been solved, can you read here:
Hi,
Is there a version of Volumio that works with the Orange Pi 4 lts?
thanks.
Hello, I have a problem with wifi dongle tl-wn725n. On VoluMio 2 it works perfect, but on VoluMio 3 is not recognized, how to properly install this dongle?
Currently not supported.
1 Like
Show the output of the command:
ip a
Hello! I apologize in advance for the translation through GOOGLE. I am using Volumio-3.236-orangepipc image and hifi digi+ v1.0 (wm8804g). How can I put a module on it. I can’t find a driver for it. I found only for arduino
@LechFromPL , you need to change the name of wireless network interface (wlx14… to wlan0).
How to do it is written here:
https://wiki.debian.org/NetworkInterfaceNames
PS: and you need to learn how to login via ssh, the text is easily copied there and inserted into the forum or somewhere else. Sometimes it is difficult to make out the text from the photos from the monitor.
Thank’s. I changed a name of adapter, now I can see the wifi networks but there is still error.
Now for ip a i get
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 14:eb:b6:84:b5:84 brd ff:ff:ff:ff:ff:ff
error from journalctl -xe
– The job identifier is 1780 and the job result is failed.
Jul 22 18:44:12 volumio sudo[2348]: pam_unix(sudo:session): session closed for u
Jul 22 18:44:13 volumio ntpd[2449]: Soliciting pool server 193.70.94.182
Jul 22 18:44:13 volumio kernel: R8188EU: INFO indicate disassoc
Jul 22 18:44:14 volumio ntpd[2449]: Soliciting pool server 213.199.225.40
Jul 22 18:44:14 volumio ntpd[2449]: Soliciting pool server 193.34.155.4
Jul 22 18:44:15 volumio ntpd[2449]: Soliciting pool server 213.81.129.99
Jul 22 18:44:15 volumio ntpd[2449]: Soliciting pool server 178.215.228.24
Jul 22 18:44:15 volumio ntpd[2449]: Deleting interface #4 wlan0, 192.168.31.249#
Jul 22 18:44:15 volumio ntpd[2449]: Soliciting pool server 201.217.3.85
Jul 22 18:44:16 volumio ntpd[2449]: Soliciting pool server 137.74.32.129
Jul 22 18:44:16 volumio ntpd[2449]: Soliciting pool server 185.51.192.34
Jul 22 18:44:16 volumio ntpd[2449]: Soliciting pool server 91.212.242.21
Jul 22 18:44:16 volumio ntpd[2449]: Soliciting pool server 192.36.143.130
Jul 22 18:44:17 volumio volumio[1089]: info: mDNS Browse raised the following er
Jul 22 18:44:17 volumio ntpd[2449]: Soliciting pool server 198.211.103.209
Jul 22 18:44:17 volumio ntpd[2449]: Soliciting pool server 81.21.76.27
Jul 22 18:44:17 volumio ntpd[2449]: Soliciting pool server 185.53.93.157
Jul 22 18:44:18 volumio ntpd[2449]: Soliciting pool server 147.182.158.78
Jul 22 18:44:18 volumio ntpd[2449]: Soliciting pool server 38.229.54.9
Jul 22 18:44:19 volumio ntpd[2449]: Soliciting pool server 5.34.248.225
Jul 22 18:44:19 volumio ntpd[2449]: Soliciting pool server 2a0d:5440::24
lines 1623-1645/1645 (END)
– The job identifier is 1780 and the job result is failed.
Jul 22 18:44:12 volumio sudo[2348]: pam_unix(sudo:session): session closed for user root
Jul 22 18:44:13 volumio ntpd[2449]: Soliciting pool server 193.70.94.182
Jul 22 18:44:13 volumio kernel: R8188EU: INFO indicate disassoc
Jul 22 18:44:14 volumio ntpd[2449]: Soliciting pool server 213.199.225.40
Jul 22 18:44:14 volumio ntpd[2449]: Soliciting pool server 193.34.155.4
Jul 22 18:44:15 volumio ntpd[2449]: Soliciting pool server 213.81.129.99
Jul 22 18:44:15 volumio ntpd[2449]: Soliciting pool server 178.215.228.24
Jul 22 18:44:15 volumio ntpd[2449]: Deleting interface #4 wlan0, 192.168.31.249#123, interface stats: received=0, sent=0, dropped=0, active_time
Jul 22 18:44:15 volumio ntpd[2449]: Soliciting pool server 201.217.3.85
Jul 22 18:44:16 volumio ntpd[2449]: Soliciting pool server 137.74.32.129
Jul 22 18:44:16 volumio ntpd[2449]: Soliciting pool server 185.51.192.34
Jul 22 18:44:16 volumio ntpd[2449]: Soliciting pool server 91.212.242.21
Jul 22 18:44:16 volumio ntpd[2449]: Soliciting pool server 192.36.143.130
Jul 22 18:44:17 volumio volumio[1089]: info: mDNS Browse raised the following error Error: dns service error: unknown
Jul 22 18:44:17 volumio ntpd[2449]: Soliciting pool server 198.211.103.209
Jul 22 18:44:17 volumio ntpd[2449]: Soliciting pool server 81.21.76.27
Jul 22 18:44:17 volumio ntpd[2449]: Soliciting pool server 185.53.93.157
Jul 22 18:44:18 volumio ntpd[2449]: Soliciting pool server 147.182.158.78
Jul 22 18:44:18 volumio ntpd[2449]: Soliciting pool server 38.229.54.9
Jul 22 18:44:19 volumio ntpd[2449]: Soliciting pool server 5.34.248.225
Jul 22 18:44:19 volumio ntpd[2449]: Soliciting pool server 2a0d:5440::24
$systemctl status wireless.service
● wireless.service - Wireless Services
Loaded: loaded (/lib/systemd/system/wireless.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2022-07-22 18:44:12 UTC; 2min 13s ago
Process: 2350 ExecStart=/volumio/app/plugins/system_controller/network/wireless.js start (code=exited, status=0/SUCCESS)
Process: 2452 ExecStartPost=/sbin/iw dev wlan0 set power_save off (code=exited, status=237/KEYRING)
Main PID: 2378 (code=exited, status=0/SUCCESS)
Jul 22 18:44:12 volumio wireless.js[2350]: … joined AP, wlan0 IPv4 is 192.168.31.249, ipV6 is undefined
Jul 22 18:44:12 volumio wireless.js[2350]: It’s done! AP
Jul 22 18:44:12 volumio iw[2452]: command failed: No such device (-19)
Jul 22 18:44:12 volumio systemd[1]: wireless.service: Control process exited, code=exited, status=237/KEYRING
Jul 22 18:44:12 volumio wpa_supplicant[2378]: ioctl[SIOCSIWAP]: Operation not permitted
Jul 22 18:44:12 volumio wpa_supplicant[2378]: wlan0: CTRL-EVENT-DISCONNECTED bssid=50:64:2b:0d:40:96 reason=3 locally_generated=1
Jul 22 18:44:12 volumio wpa_supplicant[2378]: ioctl[SIOCSIWAP]: Operation not permitted
Jul 22 18:44:12 volumio wpa_supplicant[2378]: wlan0: CTRL-EVENT-TERMINATING
Jul 22 18:44:12 volumio systemd[1]: wireless.service: Failed with result ‘exit-code’.
Jul 22 18:44:12 volumio systemd[1]: Failed to start Wireless Services.