Volumio X86/ Debian Buster debugging party (BETA)

There is a new version out for testing: http://updates.volumio.org/x86/volumiobuster/2.781/volumiobuster-2.781-2020-06-16-x86.img.zip

No platform changes, just Volumio updates to the latest level

I will be changing to a new major kernel version the next few days (5.4.y) and see how this works. Hope for help from people with issues (which there will be).

Problem: I cannot install Volumio to NVMe. Platform - MSI Cubi.
Message: Install to Disk failed: Cannot prepare system for resize.
Any ideas?

Update: it’s funny, but system WAS installed and can be booted. Got a small problem/inconvenience: data partition is only 13GB while SSD is 240GB. Now I am reading manual how to resize partition in Debian…

Yes, this is correct. It is only the resizing of the data partition which failed, The system should work ok, 13GB is not what is should be though :wink:
Could you check the boot partition and see if the resize-datapartition sentinel file is still there? If it is, it will retry the resize with each boot.
Strange, but I remember some people have hit this problem before.
Honestly no idea yet what the cause may be.

Thank you for your beta img. My wifi adapter is bcm4360,it needs driver broadcom-sta(wl),but after make && make install ,modprobe wl , and after reboot,pc stop at start up.
Does it need some other firmware?

please read the OP and supply the requested info

dpkg -i linux-kernel-headers from github.
there are errors.
volumio@volumio:/usr/src/broadcom-sta-6.30.223.271$ sudo make
KBUILD_NOPEDANTIC=1 make -C /lib/modules/4.19.106+/build M=pwd
make[1]: Entering directory ‘/usr/src/linux-headers-4.19.106+’
CFG80211 API is prefered for this kernel version
Using CFG80211 API
Kernel architecture is X86_32
CC [M] /usr/src/broadcom-sta-6.30.223.271/src/shared/linux_osl.o
/bin/sh: 1: scripts/basic/fixdep: Exec format error
make[2]: *** [scripts/Makefile.build:304: /usr/src/broadcom-sta-6.30.223.271/src/shared/linux_osl.o] Error 2
make[1]: *** [Makefile:1522: module/usr/src/broadcom-sta-6.30.223.271] Error 2
make[1]: Leaving directory ‘/usr/src/linux-headers-4.19.106+’
make: *** [Makefile:177: all] Error 2
volumio@volumio:/usr/src/broadcom-sta-6.30.223.271$
can you update github linux-kernel-headers, i make my kernel ,there are no errors.thank you!
volumio@volumio:/usr/src$ ls -l
total 32
drwxr-xr-x 5 root root 4096 Jun 24 08:09 broadcom-sta-6.30.223.271
drwxr-xr-x 4 root root 4096 Jun 19 06:50 googletest
lrwxrwxrwx 1 root root 21 Jan 12 2019 gtest -> googletest/googletest
drwxr-xr-x 24 root root 4096 Jun 19 03:44 linux-headers-4.19.106
drwxr-xr-x 24 root root 4096 Jun 24 08:09 linux-headers-4.19.106+

Could you please start with supplying the info we ask for in the Opening Post?
And tell us which version you have used?
And where did you copy the header files from?

kernel-header from

i use volumiobuster-2.775-2020-05-07-x86.img

uname -a
Linux volumio 4.19.106+ #1 SMP Mon Feb 17 12:34:48 CET 2020 i686 GNU/Linux

volumio@volumio:/lib/firmware/brcm$ inxi -vFzxxx
System: Host: volumio Kernel: 4.19.106+ i686 bits: 32 compiler: gcc v: 8.3.0 Console: tty 0 dm: N/A
Distro: Debian GNU/Linux 10 (buster)
Machine: Type: Vmware System: VMware product: VMware Virtual Platform v: N/A serial:
Chassis: No Enclosure type: 1 serial:
Mobo: Intel model: 440BX Desktop Reference Platform serial: BIOS: Phoenix v: 6.00
date: 07/29/2019
CPU: Topology: 4x Single Core model: Intel Core i7-9750H bits: 64 type: SMP arch: Kaby Lake rev: A
L2 cache: 48.0 MiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 20736
Speed: 2592 MHz min/max: N/A Core speeds (MHz): 1: 2592 2: 2592 3: 2592 4: 2592
Graphics: Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0 bus ID: 00:0f.0
chip ID: 15ad:0405
Display: tty server: X.org 1.20.4 driver: vmware unloaded: fbdev,modesetting,vesa tty: 108x55
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio: Device-1: Ensoniq ES1371/ES1373 / Creative Labs CT2518 driver: snd_ens1371 v: kernel
bus ID: 02:02.0 chip ID: 1274:1371
Sound Server: ALSA v: k4.19.106+
Network: Device-1: Intel 82371AB/EB/MB PIIX4 ACPI vendor: VMware Virtual Machine type: network bridge
driver: N/A port: 1060 bus ID: 00:07.3 chip ID: 8086:7113
Device-2: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT Single Port driver: e1000
v: 7.3.21-k8-NAPI port: 2000 bus ID: 02:01.0 chip ID: 8086:100f
IF: eth0 state: up speed: 1000 Mbps duplex: full mac:
Drives: Local Storage: total: 40.00 GiB used: 20.52 GiB (51.3%)
ID-1: /dev/sda vendor: VMware model: Virtual SATA Hard Drive size: 40.00 GiB speed: 6.0 Gb/s
serial: rev: 0001 scheme: GPT
Partition: ID-1: / size: 35.64 GiB used: 18.45 GiB (51.8%) fs: overlay source: ERR-102
ID-2: /boot size: 486.0 MiB used: 486.0 MiB (100.0%) fs: vfat dev: /dev/sda1
Sensors: Missing: Required tool sensors not installed. Check --recommends
Info: Processes: 229 Uptime: 3h 52m Memory: 2.95 GiB used: 442.8 MiB (14.7%) Init: systemd v: 241
runlevel: 5 default: 2 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3
running in: tty 0 (SSH) inxi: 3.0.32

volumio@volumio:/lib/firmware/brcm$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: AudioPCI [Ensoniq AudioPCI], device 1: ES1371/2 [ES1371 DAC1]
Subdevices: 1/1
Subdevice #0: subdevice #0
volumio@volumio:/lib/firmware/brcm$

volumio@volumio:/lib/firmware/brcm$ aplay -L
default
Playback/recording through the PulseAudio sound server
null
Discard all samples (playback) or generate zero samples (capture)
jack
JACK Audio Connection Kit
pulse
PulseAudio Sound Server
sysdefault:CARD=AudioPCI
Ensoniq AudioPCI, ES1371 DAC2/ADC
Default Audio Device
front:CARD=AudioPCI,DEV=0
Ensoniq AudioPCI, ES1371 DAC2/ADC
Front speakers
rear:CARD=AudioPCI,DEV=0
Ensoniq AudioPCI, ES1371 DAC1
Rear speakers
surround40:CARD=AudioPCI,DEV=0
Ensoniq AudioPCI, ES1371 DAC2/ADC
4.0 Surround output to Front and Rear speakers
iec958:CARD=AudioPCI,DEV=0
Ensoniq AudioPCI, ES1371 DAC2/ADC
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=AudioPCI,DEV=0
Ensoniq AudioPCI, ES1371 DAC2/ADC
Direct sample mixing device
dmix:CARD=AudioPCI,DEV=1
Ensoniq AudioPCI, ES1371 DAC1
Direct sample mixing device
dsnoop:CARD=AudioPCI,DEV=0
Ensoniq AudioPCI, ES1371 DAC2/ADC
Direct sample snooping device
dsnoop:CARD=AudioPCI,DEV=1
Ensoniq AudioPCI, ES1371 DAC1
Direct sample snooping device
hw:CARD=AudioPCI,DEV=0
Ensoniq AudioPCI, ES1371 DAC2/ADC
Direct hardware device without any conversions
hw:CARD=AudioPCI,DEV=1
Ensoniq AudioPCI, ES1371 DAC1
Direct hardware device without any conversions
plughw:CARD=AudioPCI,DEV=0
Ensoniq AudioPCI, ES1371 DAC2/ADC
Hardware device with all software conversions
plughw:CARD=AudioPCI,DEV=1
Ensoniq AudioPCI, ES1371 DAC1
Hardware device with all software conversions
usbstream:CARD=AudioPCI
Ensoniq AudioPCI
USB Stream Output
volumio@volumio:/lib/firmware/brcm$

no sentinel files… only resize-datapart.log

I think I found the bug.

df reports normal size:
overlay 246G 2.1G 231G 1% /

but when I mount Internal storage using another volumio it seems cifs reports random numbers instead of real size.

Version 4.19.106+ is obsolete
I updated the git repo with 4.19.126 headers, it needs volumio version >= 2.781
Whether you need additional firmware I cannot say.
Read the kernel log with dmesg and check. There should be a message about missing firmware if it is the case.

1 Like

thank you! I’v solved questions!
I make 4.19.126kernel,than use your new 2781 img,
sudo apt-get install broadcom-sta-dkms, BCM4360 work well.
The new img seems include all firmwares.

Hi, i just installed volumiobuster-2.781-2020-06-16-x86.img and it works fine for me for the moment, but i don’t see anything in the ‘search plugins’ section. Is this normal for the beta releases?

Regards,

I am still having random skipping while playing multiple different 192khz/24bit FLAC files. This is music local to Volumio. No network involved. I am able to play the same file from the same HDD across the network on my windows PC using VLC just fine.

No other services are using this HDD, it is dedicated to music. Volumio has settings at 8MB buffer and 40% prior to playing. I’m on the latest OTA.

How do I help troubleshoot? :slight_smile:

Interesting.
I will test but could you first please confirm that the file you linked is a legal public copy? Otherwise please look for one that is.

Here is a public file from: https://archive.org/details/Furthur2010-11-21.ARM.AKG480BCK69SD744T192-24.TapSecFlac24-192

I right click, save as this file from the above page https://archive.org/download/Furthur2010-11-21.ARM.AKG480BCK69SD744T192-24.TapSecFlac24-192/Fur2010-11-21akgarms103CumberlandBlues.flac

Pressing play, playback starts in less than 0.5 seconds.

Playthrough:

  1. Stutter time: 2:44…it will skip multiple times each playthrough.

  2. Stutter Time: 1:59, 2:18, 2:51… etc

  3. Stutter Time: 2:13, 4:17, etc.

The computer running Volumio has had no workload changes, no extra HDD streams, no new tasks. The only button I clicked was “back” to start the song over for each playthrough.

Is there a way to view Volumio’s resource utilization to see where it is bottlenecking or what it is running out of? Is there a way to test/verify if the buffer size and % selected in settings are actually getting put into effect? I did a restart and a full shutdown/start of Volumio to ensure that wasn’t the problem.

First, Windows is completely different from Linux (different OS, different drivers etc), better not to draw conclusions from comparing the two. You’re only saying that it works on a specific windows setup. Many suppliers make sure Windows works and leave the rest to the Linux community.
With Linux it is a bit more complicated, it depends on which audio card you are using and the available alsa drivers with it.

Tried your tracks, no issues with my setups (Intel NUC, HP and Asus Notebook, Gigabyte and ASRock motherboard based own builds).
Not sure what your setup is and what your audio output is

Is it possible with this version to install Volumio on a m.2 nvme disk?

Yes, that should be ok when you take the beta version. Please give us a little feedback, also when it works,
On my AsRock based PC this works fine on an M2 connector.

Thanks, I will.

Which beta version? I already use volumiobuster-2.775-2020-05-07-x86 because my wifi module doesn’t work with the regular version. I have an asrock h370m-itx/ac.

I see there is also a newer one? volumiobuster-2.781-2020-06-16-x86. Should I use that one?