Volumio 4 Feedback Thread

Thanks Balbuzie,

I tested it again late last night. It’s fixed itself… praise the Lord :slight_smile: Normally, one restart is all it takes; it has all its connections and is playing again. This time it was “offline” for hours, which is very unusual.

Happy New Year!

Hi all, does anyone managed to install Volumio on a Surface Laptop from Microsoft, Version Pro 1?
It looks like that the WLAN Chip of this laptop is not supported. It’s an Marvell Avastar and I do get the message “sudo /bin/systemctl restart wireless.service failed”. Would be great to know this before I install Volumio on the SSD.
Thx a lot in advance, Axel

A total non-issue but I’m sure I’m not the only one whose OCD is triggered by it…lol…

Top left logo is misaligned on the webui when I open the left menu

image

Hi, here is the topics to investigate:
• Log link from http://volumio.local/dev - http://logs.volumio.org/volumio/2dIu56Jlm.html
• Hardware: Holo Audio RED, with CM4
• Music source: NAS Synology DS923+ mount type NFS, device mounted and clearly visible from Volumio
• Filesystem on NAS: Btrfs
• Library size: approximate track count more then 420000 tracks
• Filenames: maybe there is non-ASCII characters such as Cyrillic and Japanese
• File formats: mix of all formats - FLAC, ALAC, APE, MP3, M4A and others

Full rescan of database was initiated twelve hours ago, now there is no end of this process. The spinning wheel is constantly on web interface. Thank you, now I going to restart the device.

Nothing new after restart. Database is not visible

Hey @learner,

I have analyzed the full log. Here are the findings:

1. SMB 3.11 Discovery Failures

Volumio is attempting SMB share discovery with the problematic SMB3_11 protocol:

Dec 27 20:38:21 volumiored volumio[996]: info: Executing SMB command: smbclient --no-pass --debuglevel=0 -L DiskStation3.local. -m SMB3_11
...
Dec 27 20:38:27 volumiored volumio[996]: info: Error browsing device DiskStation3 for shares: Command failed

This is the known Bookworm/kernel 6.12 SMB regression. SMB 3.11 introduces encrypted sessions and metadata overhead causing severe performance degradation. Even though your music mount uses NFS, these failing SMB discovery commands block the UI.

2. Synology #recycle Folder Being Indexed

MPD is scanning thousands of files from your NAS trash bin:

2025-12-27T20:39:43 update: added NAS/NAS/#recycle/ROCK MUSIC N-Z/...
2025-12-27T20:39:43 update: added NAS/NAS/#recycle/НАШИ/Рок/Ария/...

This wastes significant scan time on deleted files.

3. UTF-8 Encoding Failure with Cyrillic

NAS/NAS/#recycle/НАШИ/\xd0 ок/Ария/mp3/2003 Легенды \xd0 усского рока

This should display as “Рок” and “Русского”. The broken UTF-8 sequences indicate encoding negotiation failure.

4. MPD Exception at Startup

2025-12-27T20:37:52 exception: No such directory

MPD references a directory that no longer exists on the NAS.

Recommended Actions:

  1. Check NFS mount encoding settings:

Go to Settings > Sources > Network Drives > Edit your NAS mount > Advanced Options

Verify or add: iocharset=utf8

  1. For any CIFS/SMB mounts or future additions:

In Advanced Options, specify: vers=2.0 or vers=2.1

Do NOT use vers=3.0 or vers=3.11 - these cause the performance regression.

  1. Create .mpdignore to exclude #recycle and Synology metadata:
ssh volumio@volumio.local
echo "#recycle" | sudo tee /mnt/NAS/NAS/.mpdignore
echo "@eaDir" | sudo tee -a /mnt/NAS/NAS/.mpdignore
  1. After adding .mpdignore, rebuild the database:
sudo rm /var/lib/mpd/tag_cache
sudo systemctl restart mpd
  1. Trigger rescan from Volumio UI and send new log.

Questions:

  1. How much content is in #recycle? This could represent a large portion of your 420,000 tracks.
  2. Do you need DiskStation3 and DiskStation4 visible in Volumio? If not, removing unused SMB shares from Sources would eliminate the discovery failures.
  3. How much RAM does the CM4 have?

Kind Regards,

I screwed up and am very frustrated. I borked my old volumio install and had to re-image. Now I can’t get the touchscreen to be recognized. I seemingly can’t even remove and re-install the plugin. Display works fine for console output and worked previously on an older version of the plugin. Any help would be appreciated

 75.242] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    75.242] (II) no primary bus or device found
[    75.242] (II) LoadModule: "glx"
[    75.253] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    75.350] (II) Module glx: vendor="X.Org Foundation"
[    75.350] 	compiled for 1.21.1.7, module version = 1.0.0
[    75.350] 	ABI class: X.Org Server Extension, version 10.0
[    75.350] (II) LoadModule: "modesetting"
[    75.357] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    80.696] (II) Module modesetting: vendor="X.Org Foundation"
[    80.696] 	compiled for 1.21.1.7, module version = 1.21.1
[    80.696] 	Module class: X.Org Video Driver
[    80.696] 	ABI class: X.Org Video Driver, version 25.2
[    80.696] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    80.708] (WW) Falling back to old probe method for modesetting
[    80.709] (EE) open /dev/dri/card0: No such file or directory
[    80.709] (WW) Falling back to old probe method for modesetting
[    80.709] (EE) open /dev/dri/card0: No such file or directory
[    80.709] (EE) No devices detected.
[    80.709] (EE) 
Fatal server error:
[    80.709] (EE) no screens found(EE) 
[    80.709] (EE) 

@Steve_K

We’re excited to help you out, but right now, we’re playing a guessing game with 10,000 possible answers. :sweat_smile:

So far, we know:
:white_check_mark: Volumio V4.073 installed on something
:white_check_mark: A display that’s gone on strike

That’s a great start, but we’ll need a few more clues to crack the case. Think of it like detective work, help us narrow it down so we can get you rocking again!

Please read below topic, and help us help you.

Sorry, I thought I tagged it:

Raspberry Pi 3 Model B Plus Rev 1.4 w/ classic 7" display.

Please provide details as mention in the shared link.
Without it we are not able to support you.
also a classic 7" inch display, gives me 800+ results.

Apologies, I am trying to provide as much as possible. Display is HAMTYSAN
Model Number: HCTG070V.P01 connected off the board’s display connector. Installation was done via Pi imager on new 32GB micro-sd card.

systemctl status -l volumio-kiosk.service
× volumio-kiosk.service - Volumio Kiosk
     Loaded: loaded (/lib/systemd/system/volumio-kiosk.service; disabled; preset: enabled)
     Active: failed (Result: exit-code) since Sun 2025-12-28 18:23:17 CST; 9min ago
   Duration: 15.198s
    Process: 12373 ExecStart=/usr/bin/startx /etc/X11/Xsession /opt/volumiokiosk.sh -- -nocursor (code=exited, status=1/FAILURE)
   Main PID: 12373 (code=exited, status=1/FAILURE)
        CPU: 382ms

Dec 28 18:23:02 volumio-lr startx[12408]:          at http://wiki.x.org
Dec 28 18:23:02 volumio-lr startx[12408]:  for help.
Dec 28 18:23:02 volumio-lr startx[12408]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Dec 28 18:23:02 volumio-lr startx[12408]: (EE)
Dec 28 18:23:02 volumio-lr startx[12408]: (EE) Server terminated with error (1). Closing log file.
Dec 28 18:23:17 volumio-lr startx[12407]: xinit: giving up
Dec 28 18:23:17 volumio-lr startx[12407]: xinit: unable to connect to X server: Connection refused
Dec 28 18:23:17 volumio-lr startx[12407]: xinit: server error
Dec 28 18:23:17 volumio-lr systemd[1]: volumio-kiosk.service: Main process exited, code=exited, status=1/FAILURE
Dec 28 18:23:17 volumio-lr systemd[1]: volumio-kiosk.service: Failed with result 'exit-code'.

cat /var/log/Xorg.0.log 
[  2966.831] 
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[  2966.831] Current Operating System: Linux volumio-lr 6.12.47-v7+ #1904 SMP Mon Sep 15 13:05:52 BST 2025 armv7l
[  2966.831] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=800 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  splash plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 quiet console=ttyS0,115200 console=tty1 imgpart=UUID=dafa3844-b779-48cd-9b4c-01ecfd09e0f4 imgfile=/volumio_current.sqsh bootpart=UUID=3B89-0B23 datapart=UUID=581e6074-f623-4ac1-93d2-0e98dc575c7f uuidconfig=cmdline.txt pcie_aspm=off pci=pcie_bus_safe rootwait bootdelay=7 logo.nologo vt.global_cursor_default=0 net.ifnames=0 snd-bcm2835.enable_compat_alsa= snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 loglevel=0 nodebug use_kmsg=no
[  2966.831] xorg-server 2:21.1.7-3+rpt3+deb12u11 (https://www.debian.org/support) 
[  2966.831] Current version of pixman: 0.44.0
[  2966.831] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  2966.831] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2966.831] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 28 18:23:02 2025
[  2966.834] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  2966.834] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2966.845] (==) No Layout section.  Using the first Screen section.
[  2966.845] (==) No screen section available. Using defaults.
[  2966.845] (**) |-->Screen "Default Screen Section" (0)
[  2966.845] (**) |   |-->Monitor "<default monitor>"
[  2966.846] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[  2966.846] (**) |   |-->Device "kms"
[  2966.846] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[  2966.846] (**) Option "Debug" "dmabuf_capable"
[  2966.846] (==) Automatically adding devices
[  2966.846] (==) Automatically enabling devices
[  2966.846] (==) Automatically adding GPU devices
[  2966.846] (==) Automatically binding GPU devices
[  2966.847] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  2966.847] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  2966.847] 	Entry deleted from font path.
[  2966.847] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[  2966.847] (==) ModulePath set to "/usr/lib/xorg/modules"
[  2966.847] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[  2966.847] (II) Loader magic: 0x215080
[  2966.847] (II) Module ABI versions:
[  2966.847] 	X.Org ANSI C Emulation: 0.4
[  2966.847] 	X.Org Video Driver: 25.2
[  2966.847] 	X.Org XInput driver : 24.4
[  2966.847] 	X.Org Server Extension : 10.0
[  2966.855] (--) using VT number 2

[  2966.855] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[  2966.855] (II) no primary bus or device found
[  2966.855] (II) LoadModule: "glx"
[  2966.860] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  2966.911] (II) Module glx: vendor="X.Org Foundation"
[  2966.911] 	compiled for 1.21.1.7, module version = 1.0.0
[  2966.911] 	ABI class: X.Org Server Extension, version 10.0
[  2966.911] (II) LoadModule: "modesetting"
[  2966.913] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  2967.108] (II) Module modesetting: vendor="X.Org Foundation"
[  2967.108] 	compiled for 1.21.1.7, module version = 1.21.1
[  2967.108] 	Module class: X.Org Video Driver
[  2967.108] 	ABI class: X.Org Video Driver, version 25.2
[  2967.108] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  2967.113] (WW) Falling back to old probe method for modesetting
[  2967.113] (EE) open /dev/dri/card0: No such file or directory
[  2967.113] (WW) Falling back to old probe method for modesetting
[  2967.113] (EE) open /dev/dri/card0: No such file or directory
[  2967.113] (EE) No devices detected.
[  2967.113] (EE) 
Fatal server error:
[  2967.113] (EE) no screens found(EE) 
[  2967.113] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[  2967.113] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  2967.113] (EE) 
[  2967.122] (EE) Server terminated with error (1). Closing log file.

Thank you, a great work, I will try and make a new report to you.

So, I’ve tried forcing hdmi in boot.cfg and setting the output and resolution in cmdline.txt with no change. I may try downgrading to an older image, as it may simply be bookworm cannot deal with the HDMI display do to some EDID issue which I can’t figure out.

Solved, I think. Added priority and dtoverlay to boot/config.txt

cat /boot/config.txt 
### 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
hdmi_force_hotplug=1
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt
#### Volumio i2s setting below: do not alter ####
dtoverlay=vc4-kms-v3d
disable_overscan=1

Don’t add anything to /boot/config.txt, it’s written there for a reason, if you update your installation you can start over again as it will be lost.

### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###

Add these to /boot/userconfig.txt:

dtoverlay=vc4-kms-v3d
disable_overscan=1

Hi, @nerd thanks for your patience. Glad to report that 4.084 fixed this issue! It’s been working reliably for a few days now. I’ve just been using the spotify plugin so haven’t tested other playback options.

Will there be a beta channel or similar for Volumio 4 at primo?
I have the Primo v1 which more or less killed the interest of listening to music, I get shorts interrupts in music playback even if it’s connected by wire to same 1Gbps switch as the NAS is connected to.

I was recommended to wipe the installation and start all over long time ago, but haven’t found the time yet. Would be a perfect time to switch to Volumio 4 also for this. Then I’ll also be able to include the primo in multiroom together with the 4 pies now running v4

Raspberry pi 3 with weak WiFi connection to the same nas handles the playback without issues.

Hi

Update field from version 3 (complete reinstallation)

Volumio 4.073 x86. Problem when selecting the music section - a blank page opens. Via the web and on the touchscreen connected to the device.

http://logs.volumio.org/volumio/HZS4baU.html

Please advise how this can be fixed.
Thank you.

Hi!

As I accidently messed up my old Volumio 3 setup, I updated my CM4 eMMC based box with Waveshare 7.9" widescreen to 4.073 today. Now it does not seem to boot up. Screen is scrambled, no WiFi or Ethernet seem to work. Hotspot seems to be disabled and when I connect it to Ethernet, it doesn’t show up in the network. Tried to unlplug HDMI and restarted, nothing.
All ideas are welcome.

Where did you get the Volumio image from, as you can’t update from V3 to V4 and which version did you load (please don’t reply with the latest)
Bookworm is very strict on power limits, Buster was way more forgiving.

And please look here to get the information we need to support you: