After a second try, i got it to stutter again.
Before I chase down logs etc. Are there any fundamental configuration changes in version 4 (4.069) that affect a Touchscreen ? I have an Eletek 11.9ā 1280 x 800 - HDMI screen which functions with 3.8.76 Touchsceen plugin - using the same parameters from userconfig.txt on version 4, I get the Volumio startup screen but the user interface does not show - Any hints would be most welcome,
Try adding
dtoverlay=vc4-kms-v3d
to ā/boot/userconfig.txtā.
@nerd , @Wheaten
Wifi Dongle still not working in V4.071
I connected with wire and then sshād here is the debug info you asked for last time:
dmesg > /data/dmesg.txt
0.000000] OF: reserved mem: 0x0000000028c00000ā¦0x000000002cbfffff (65536 >
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000000000-0x000000002fffffff]
[ 0.000000] Normal empty
[ 0.000000] HighMem [mem 0x0000000030000000-0x000000007fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x0000000037ffffff]
[ 0.000000] node 0: [mem 0x0000000040000000-0x000000007fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 6.12.47-v7l+ (dom@buildbot) (arm-linux-gnueabihf-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU >
[ 0.000000] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.1
[ 0.000000] random: crng init done
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] Reserved memory: created CMA memory pool at 0x0000000028c00000, size 64 MiB
[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[ 0.000000] OF: reserved mem: 0x0000000028c00000ā¦0x000000002cbfffff (65536 KiB) map reusable linux,cma
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000000000-0x000000002fffffff]
[ 0.000000] Normal empty
[ 0.000000] HighMem [mem 0x0000000030000000-0x000000007fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
journalctl > /data/journalctl.txt
nano 7.2 /data/journalctl.txt
Nov 17 11:31:40 volumio4 kernel: Booting Linux on physical CPU 0x0
Nov 17 11:31:40 volumio4 kernel: Linux version 6.12.47-v7l+ (dom@buildbot) (arm-linux-gnueabihf-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11>
Nov 17 11:31:40 volumio4 kernel: CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d
Nov 17 11:31:40 volumio4 kernel: CPU: div instructions available: patching division code
Nov 17 11:31:40 volumio4 kernel: CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Nov 17 11:31:40 volumio4 kernel: OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.1
Nov 17 11:31:40 volumio4 kernel: random: crng init done
Nov 17 11:31:40 volumio4 kernel: Memory policy: Data cache writealloc
Nov 17 11:31:40 volumio4 kernel: Reserved memory: created CMA memory pool at 0x0000000028c00000, size 64 MiB
Nov 17 11:31:40 volumio4 kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Nov 17 11:31:40 volumio4 kernel: OF: reserved mem: 0x0000000028c00000ā¦0x000000002cbfffff (65536 KiB) map reusable linux,cma
Nov 17 11:31:40 volumio4 kernel: Zone ranges:
Nov 17 11:31:40 volumio4 kernel: DMA [mem 0x0000000000000000-0x000000002fffffff]
Nov 17 11:31:40 volumio4 kernel: Normal empty
Nov 17 11:31:40 volumio4 kernel: HighMem [mem 0x0000000030000000-0x000000007fffffff]
Nov 17 11:31:40 volumio4 kernel: Movable zone start for each node
Nov 17 11:31:40 volumio4 kernel: Early memory node ranges
Nov 17 11:31:40 volumio4 kernel: node 0: [mem 0x0000000000000000-0x0000000037ffffff]
Nov 17 11:31:40 volumio4 kernel: node 0: [mem 0x0000000040000000-0x000000007fffffff]
Nov 17 11:31:40 volumio4 kernel: Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff]
Nov 17 11:31:40 volumio4 kernel: OF: reserved mem: 0x000000003ef73360ā¦0x000000003ef7374f (0 KiB) nomap non-reusable nvram@0
Nov 17 11:31:40 volumio4 kernel: OF: reserved mem: 0x000000003ef73120ā¦0x000000003ef7331f (0 KiB) nomap non-reusable nvram@1
Nov 17 11:31:40 volumio4 kernel: percpu: Embedded 19 pages/cpu s45772 r8192 d23860 u77824
Nov 17 11:31:40 volumio4 kernel: pcpu-alloc: s45772 r8192 d23860 u77824 alloc=19*4096
Nov 17 11:31:40 volumio4 kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Nov 17 11:31:40 volumio4 kernel: Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable>
Nov 17 11:31:40 volumio4 kernel: cgroup: Disabling memory control group subsystem
cat /proc/cmdline > /data/config.txt
coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_>coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable>
cat /boot/config.txt >> /data/config.txt
coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.ena>
DO NOT EDIT THIS FILE
APPLY CUSTOM PARAMETERS TO userconfig.txt
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt
Volumio i2s setting below: do not alter
dtoverlay=hifiberry-dacplus
cat /boot/volumioconfig.txt >> /data/config.txt
coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.ena>
DO NOT EDIT THIS FILE
APPLY CUSTOM PARAMETERS TO userconfig.txt
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt
Volumio i2s setting below: do not alter
dtoverlay=hifiberry-dacplus
DO NOT EDIT THIS FILE
APPLY CUSTOM PARAMETERS TO userconfig.txt
[cm4]
dtoverlay=dwc2,dr_mode=host
otg_mode=1
[pi5]
dtoverlay=vc4-kms-v3d-pi5
dtparam=uart0_console # Disabled by default
dtparam=nvme
cat /boot/userconfig.txt >> /data/config.txt
coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.ena>
DO NOT EDIT THIS FILE
APPLY CUSTOM PARAMETERS TO userconfig.txt
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt
Volumio i2s setting below: do not alter
dtoverlay=hifiberry-dacplus
DO NOT EDIT THIS FILE
APPLY CUSTOM PARAMETERS TO userconfig.txt
[cm4]
dtoverlay=dwc2,dr_mode=host
otg_mode=1
[pi5]
dtoverlay=vc4-kms-v3d-pi5
dtparam=uart0_console # Disabled by default
dtparam=nvme
The issue isnāt resolved on the Raspberry Pi yet, only x86 is currently fixed.
Iāve run some tests on the Pi, and the results look promising, but itās not ready for mainstream release just yet.
2 Likes
I tried to play a 24/96 m4a file and while it does play, it takes an ungody amount of time to load. At least 20 seconds. I have also had random delays when loading 16/44 flac files as well, but nothing I would be able to reproduce. The m4a long load time is consistent.
I am using a RP3 with Volumio 4.071. I tried it on a RP5 and the load time was exactly the same so it does not appear to be a performance bottleneck.
The load time using the same hardware on Volumio 3 was normal so this does seem to be a Volumio 4 problem.
Hi,
Please refer to post 3 for instructions on how to report an issue. This helps us avoid going in blind when investigating potential problems.
So far, Iāve tested CUE, DSD, FLAC (up to 384kHz), MP3, MP4, OGG, and WAV, all without issues. (No M4A though.)
To proceed, weāll need more detailed information.
Soooooo you didnāt test the one thing I said was broken and now you need more info?
Also getting the same 20 second delay(I actually timed it) when going from track to track which is the reason Iām back to version 3 for now. If you can confirm m4a files working on your set up I will send you more information about my set up.
Just send the log or stop xxxxxxx. A lot of the community were invested in the testing.
Letās keep it friendly.
If users start setting conditions just so Iām āallowedā to ask something or give supportā¦
wellā¦ thatās a bit of a slippery slope, isnāt it?
Dear Volumionauts,
I want to take a moment to address something important about how this community works.
We are volunteers.
The people who test features, investigate bugs, and help troubleshoot problems are community members volunteering their time. We test what we can test, with the hardware we have, when we have time. No one here is paid to debug your specific issue on demand.
We are not a support desk.
When someone volunteers to help investigate a problem, they are doing you a favor. They are not your personal tech support. They are not obligated to test your specific file format before you provide diagnostic information. That is not how volunteer communities operate.
Proper bug reports are required.
When you report a problem, you provide logs. This is not negotiable. This is the foundation of how investigation works in any open source project.
Logs show what the system is actually doing. Without them, we are guessing. If you want help, you provide the information needed to investigate. If you refuse to provide logs, then there is no investigation. It is that simple.
Respect is mandatory.
Multiple community members invested months of testing to make Volumio 4 happen. Volunteers continue to invest time helping users troubleshoot issues every single day.
Sarcastic responses to people trying to help you are unacceptable. Dismissive language toward volunteers is unacceptable. Demanding tests before providing basic diagnostic information is unacceptable.
How this works:
- You report a problem with complete information (device model, version, logs, reproduction steps)
- Community members investigate when they have time
- We work together to find solutions
- Everyone treats each other with respect
What does not work:
- Demanding immediate testing from volunteers
- Refusing to provide diagnostic information
- Using sarcastic or dismissive language
- Acting like providing logs is doing us a favor
If you want help:
Provide the information requested. Follow the guidelines. Respect peopleās time. Cooperate.
If you cannot do that:
You are in the wrong place.
This community works because people cooperate, contribute what they can, and respect each otherās time and effort. That is the standard. If you cannot meet it, do not expect help.
Kind Regards,
15 Likes
I am testing v4.071 with a RPi 3 A+ and have no significant delays playing M4a 48kHz files
do you have any other ideas what i could test, regarding my multiroom stuttering?
Otherwise, can someone giva me a download link to the latest volumio V3, so i can make a rollback?
Kindest regards
Hi, installed 4.071 on Pi4 with2Gb ram and transport pi digi. Everything was normal expect pi4 couldnt connect to wifi. Because cable connection make some degradation in my setup i installed version from pi imager which is working ok. Didnt make logs, because I didnt see it was 4.0 (only newer release than from pi imager - 17,11 vs 12.11). After typing wifi password nothing happend, and my wifi was still on the list and no connection. Best Regards
BTW - actual version is best sounding pi system in my opinion, congratulations 
use pi imager and choose volumio from available systems
Please donāt give people bad information.
The images provided by Raspberry Pi Imager, are a known source for problems.
Due to the way the flashing process is different then when flashing a *.img file.
1 Like
Hello, the update to version 4.071 has been available for a few days now, but my version 3.874 doesnāt show this update. It says the final and latest version is installed. Why is this happening? Iāve never had any problems with updates. Iām using x86.
Kind Regards,
never had a problem with image from pi imager. but there is a problem with new 4.0 release, dont give people bad information 
Just release download for 3 and 4 together, and everyone can choose