Volumio X86/ Debian Buster debugging party (BETA)

Aha, I was to hasty in my first boot and exploration(s) as I didn’t have a heatsink. :neutral_face:

I rechecked again now and, WiFi is working out of the box, not sure why inxi doesn’t see it though?

volumio@volumio:~$ sudo lshw -class network
  *-network
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: eth0
       version: 07
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168e-3_0.0.4 03/27/12 ip=192.168.1.158 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
       resources: irq:16 ioport:e000(size=256) memory:91804000-91804fff memory:91800000-91803fff
  *-network
       description: Wireless interface
       physical id: 1
       logical name: wlan0
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=brcmfmac driverversion=7.45.18 firmware=01-6a2c8ad4 ip=192.168.211.1 multicast=yes wireless=IEEE 802.11

I wasn’t that lucky with the audio though - I checked and you are right - the snd_soc_nau8824 drivers are already present as you mentioned, but it seems to fail to register the card with alsa.

volumio@volumio:~$ lsmod | grep snd_soc
snd_soc_sst_cht_bsw_nau8824    16384  0
snd_soc_sst_atom_hifi2_platform    65536  1 snd_intel_sst_core
snd_soc_acpi_intel_match    20480  1 snd_intel_sst_acpi
snd_soc_nau8824        45056  1 snd_soc_sst_cht_bsw_nau8824
snd_soc_acpi           16384  2 snd_intel_sst_acpi,snd_soc_acpi_intel_match
snd_soc_core          167936  3 snd_soc_nau8824,snd_soc_sst_cht_bsw_nau8824,snd_soc_sst_atom_hifi2_platform
regmap_i2c             16384  1 snd_soc_nau8824
snd_compress           20480  1 snd_soc_core
ac97_bus               16384  1 snd_soc_core
snd_pcm                77824  5 snd_hdmi_lpe_audio,snd_soc_nau8824,snd_soc_sst_cht_bsw_nau8824,snd_soc_sst_atom_hifi2_platform,snd_soc_core
snd                    57344  11 snd_compress,snd_seq,snd_hdmi_lpe_audio,snd_soc_sst_cht_bsw_nau8824,snd_timer,snd_soc_sst_atom_hifi2_platform,snd_seq_device,snd_soc_core,snd_pcm
i2c_core               53248  8 i2c_designware_core,i2c_algo_bit,regmap_i2c,snd_soc_nau8824,i2c_designware_platform,i915,drm_kms_helper,drm

It does try and probe for the card multiple times but fails?

volumio@volumio:~$ dmesg | grep cht-bsw
[   29.115169] cht-bsw-nau8824 cht-bsw-nau8824: ASoC: CODEC DAI nau8824-hifi not registered
[   29.115179] cht-bsw-nau8824 cht-bsw-nau8824: snd_soc_register_card failed -517
<Appears a few more times>
[   31.155251] cht-bsw-nau8824 cht-bsw-nau8824: ASoC: CODEC DAI nau8824-hifi not registered
[   31.155261] cht-bsw-nau8824 cht-bsw-nau8824: snd_soc_register_card failed -517

If I understood you correctly, there won’t be any audio if the right ALSA UCM isn’t initialised for a device?
Looking at bytcr-init.sh, if I am reading it right - the DAC has to be registered first correct?
So if it’s not showing up to alsa in aplay then there isn’t much the script can do?

I also plugged it into a HDMI capable speaker, and had no dice with that.
Will try and play around a bit more with this x86 board - I’m not used to these non device-tree x86 stuff, so I hope you don’t mind if I read up a bit and then come back to trouble you!

Sound on baytrail/cherrytrail was new to me and I did not get much chance to play with it, but ask. Yes, it seems the dac has to be registered, error -517 always occurs when things are not done in the right order, in this case it is ok. You can experiment with the byctr-init script, I got as far as playing music in chipmunk mode, but there have been many UCM and driver/firmware dates since.
I’m supposed to get a Larkbox soon, this means I can have a closer look.

1 Like

I also got a RockPi X, it woks fine with Lubuntu.

I tried latest Buster image and it never reaches the UI on the screen, it goes black and stays like that.

Do you have some new images to test with it?

which kernel version does your Lubuntu install have?

Lubuntu is running on kernel 5.4.0-45

I think it’s worth to mention latest Jessie for X86 works fine, even being with very old kernel. Unfortunately audio DAC and WiFi do not work, I had to use an external USB dongle.

That’s interesting, first time report that jessie with old kernel works and buster with new does not.
When the UI “goes black”, does Volumio actually work, can you access it from an external browser?

The current buster version has kernel 4.19.y, 5.4.y is still planned.
Perhaps I missed specific firmware for the graphics card, drivers should all be there.
Could you create a log from the dev page (when volumio does work without UI) or give me the output from the commands I listed in the opening post?
That would be a big help

sure, no problem!

I’ll let you know the outcome

I did some more testing with latest buster beta on RockPi X, here the outcome:

  • I confirm UI is not showing up, but I noticed that before having a black screen there is a dark gray one with mouse cursor (I can even move it). screen turns full black when the system crashes, ssh is not responsive anymore.
  • WiFi works out-of-the-box! This was not true for Lubuntu/Debian (I had to manually add one .txt file to have it working). I didn’t test streaming performance due to stability issues.
  • HDMI audio works out-of-the box. Embedded DAC does not.
  • system is very unstable, I could connect to Volumio via web interface on a PC a couple of times only (I could finalize the setup wizard and reboot once),
  • most of the times the system crashes and becomes unresponsive, the only thing I could do is power-cycle.
  • once I managed to login via ssh before the crash and perform a dump of dmesg. right after the dump the system crashed. here the log:

dmesg.txt (67.3 KB)

I tried several times to have a successful boot again, to perform the dump you requested, but after ~10 attempts I gave up.

I tried again latest Volumio x86 jessie and it never crashes

so far as i see it hangs on :

46.004111] [drm] GPU HANG: ecode 8:0:0x0cf3b8f3, in Xorg [1162], reason: han g on rcs0, action: reset
[ 46.005197] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
volumio@volumio-x86:~$ dmesg > dmes

yes, I could not type the complete command again because the system became unresponsive

the i915 seems a pain in the bud… 5.x.x has that problem to…
if you needs some i915

Ah, I wonder what I was doing wrong… Didn’t get any audio when I hooked it up to my TV. Stock Buster worked fine OOTB…

Now I just feel silly. I just assumed it was headless as usual and didn’t really follow up on the blank/grey screen with just the mouse cursor!

I booted up a stock Buster image and compared it to the dumps from inxi in Volumio X86/ Debian Buster debugging party (BETA)

inxi reports 1.85 GiB of memory in this image compared to stock Buster’s 3.78 GiB
– There might be something amiss with the graphic card/firmware?

# Buster x86 Volumio
Graphics:  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers driver: i915
           v: kernel bus ID: 00:02.0 chip ID: 8086:22b0
           Display: tty server: X.org 1.20.4 driver: modesetting unloaded: fbdev,vesa tty: 183x58
           Message: Unable to show advanced data. Required tool glxinfo missing.
# Buster stock 
System:    Host: debian Kernel: 4.19.0-10-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Console: tty 1 dm: GDM3 3.30.2
           Distro: Debian GNU/Linux 10 (buster)
Graphics:  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers driver: i915
           v: kernel bus ID: 00:02.0 chip ID: 8086:22b0
           Display: tty server: X.org 1.20.4 driver: i915 compositor: gnome-shell tty: 143x46
           Message: Advanced graphics data unavailable in console. Try -G --display

do you also experience stability issues?

I’m going to try again soon, this afternoon I’ve added a heatsink on the processor

I can’t add any help here, I don’t have this board and it appears unlikely Radxa is going to send me one.
Therefore Radxa PI X remains unsupported, please note.


2020-02-27, version 2.775

Problem:
1- cannot prepare system for resize
2- Plugin Not show

Linux volumio 4.19.106+ #1 SMP Mon Feb 17 12:34:48 CET 2020 i686
___
/_ \ __
__ __ //\ \ __ __ ___ ___ /_\ ___
/\ /\ \ / __\\ \ \ /\ \/\ \ /' __ __\/\ \ / __
\ \ _/ |/\ \L\ \
\ _\ \ _\ /\ /\ /\ \ \ /\ \L\
\ _
/ \ _//_\ _/\ _\ _\ _\ _\ _/
// // // // /////////___/

         Free Audiophile Linux Music Player - Version 2.0

      C 2015 Michelangelo Guarise - Volumio Team - Volumio.org

Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
volumio@volumio:~$ volumio plugin install

This command will install the plugin on your device

Compressing the plugin
Plugin succesfully compressed
^[[A^[[B^C
volumio@volumio:~$ volumio plugin install

This command will install the plugin on your device

Compressing the plugin
Plugin succesfully compressed
inxi -vFzxxx
^C
volumio@volumio:~$ 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: Desktop Mobo: ASRock model: H310CM-ITX/ac serial: UEFI: American Megatrends v: P4.10
date: 05/14/2019
CPU: Topology: Dual Core model: Intel Pentium Gold G5400 bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 4096 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 29568
Speed: 3700 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 3700 2: 3701 3: 3701 4: 3701
Graphics: Device-1: Intel vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3e90
Display: tty server: X.org 1.20.4 driver: modesetting unloaded: fbdev,vesa tty: 237x63
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio: Device-1: Intel 200 Series PCH HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3
chip ID: 8086:a2f0
Device-2: XMOS type: USB driver: snd-usb-audio bus ID: 1-3:4 chip ID: 20b1:0002
Sound Server: ALSA v: k4.19.106+
Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6
chip ID: 8086:15b8
IF: eth0 state: up speed: 1000 Mbps duplex: full mac:
Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel port: e000 bus ID: 02:00.0
chip ID: 8086:24fb
IF: wlan0 state: down mac:
Drives: Local Storage: total: 123.00 GiB used: 5.25 GiB (4.3%)
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLV128HCGR-000L2 size: 119.24 GiB speed: 31.6 Gb/s lanes: 4
serial: rev: 5L0QBXV7 scheme: GPT
ID-2: /dev/sda type: USB vendor: Generic model: Flash Disk size: 3.75 GiB serial: rev: 8.07 scheme: MBR
Partition: ID-1: / size: 112.55 GiB used: 114.2 MiB (0.1%) fs: overlay source: ERR-102
ID-2: /boot size: 486.0 MiB used: 42.1 MiB (8.7%) fs: vfat dev: /dev/nvme0n1p1
Sensors: Missing: Required tool sensors not installed. Check --recommends
Info: Processes: 153 Uptime: 18m Memory: 1.86 GiB used: 417.6 MiB (21.9%) Init: systemd v: 241 runlevel: 5 default: 2
Compilers: gcc: N/A Shell: bash v: 5.0.3 running in: tty 0 (SSH) inxi: 3.0.32

Not sure if this is a known issue or related to the plugin I’m developing… but I’m noticing issues with this beta with the track lengths as reported on the Volumio UI and also via the backend API (http://localhost:3000/api/v1/getstate)

During playback, when the issue occurs, a track may list with a duration that is either too long or too short. It could be out by 20-30 seconds or several minutes. The end result is that the playback of the track is cut short (on to next track) or there is a silence period after the track finishes before the next track starts.

My Chromecast plugin (python script) calls the getstate API every 1 second and uses that to monitor what it being played back locally and then drives the casting of the current track to a selected external chromecast. Then every 10 seconds, it performs a local seek on Volumio to try and sync its local playback position to be closer to where the chromecast is located on its progress. I won’t get into the specifics of this entire process here.

That seek trick invokes this API call…
api/v1/commands/?cmd=seek&position=NNNN

Maybe it’s 1/sec state calls and seek commands (every 10s) that trigger this problem. But sometimes when the track changes, the next track will end up with a shorter or longer duration being reported by the Volumio getstate API and bring about the short playback or gap scenario.

I’ve manually checked track durations and in all cases, the Chromecast always reports the correct length with Volumio being the one getting the wrong readings.

My script used to work on the standard official images until the age of Jessie caught up and the python3 version fell out of sync with several of the required Python packages. The end result was I had to switch to the new beta images on Buster to get a python3 environment.

Hopefully someone will have an idea of the root cause here.

Hi , first of all thank you very much for your awesome work!
my experience with volumio x86 debian buster was very satisfactory.

here is my data:

inxi -vFzxxx
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LANG = "es_AR.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
System:    Host: volumio Kernel: 4.19.126 i686 bits: 32 compiler: gcc v: 8.3.0 Console: tty 0 dm: N/A 
           Distro: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: LENOVO product: 20126 v: Ideapad S110 serial: <filter> Chassis: type: 10 
           v: Type2 - Board Serial Number serial: <filter> 
           Mobo: LENOVO model: 123456789 v: Type1Sku0 serial: <filter> BIOS: LENOVO v: 5BCN29WW date: 4/10/2012 
Battery:   ID-1: BAT1 charge: 5.1 Wh condition: 5.1/23.1 Wh (22%) volts: 10.9/10.8 model: CPT-ES3 LNV-L10C3Z11 type: Unknown 
           serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Atom N2600 bits: 32 type: MT MCP arch: Saltwell rev: 1 L2 cache: 512 KiB 
           flags: nx pae sse sse2 sse3 ssse3 bogomips: 12768 
           Speed: 681 MHz min/max: 600/1600 MHz Core speeds (MHz): 1: 892 2: 1425 3: 1295 4: 1071 
Graphics:  Device-1: Intel Atom Processor D2xxx/N2xxx Integrated Graphics vendor: Lenovo driver: gma500 v: N/A bus ID: 00:02.0 
           chip ID: 8086:0be1 
           Display: tty server: X.org 1.20.4 driver: modesetting unloaded: fbdev,vesa tty: 141x20 
           Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:27d8 
           Device-2: Thesycon System & Consulting type: USB driver: snd-usb-audio bus ID: 1-1:2 chip ID: 152a:8750 
           Sound Server: ALSA v: k4.19.126 
Network:   Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet vendor: Lenovo RTL810xE driver: r8169 v: kernel 
           port: 4000 bus ID: 01:00.0 chip ID: 10ec:8136 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce v: kernel port: 3000 bus ID: 02:00.0 
           chip ID: 10ec:8176 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 2.14 TiB used: 243.01 GiB (11.1%) 
           ID-1: /dev/sda vendor: Seagate model: ST320LT020-9YG142 size: 298.09 GiB speed: 3.0 Gb/s rotation: 5455 rpm 
           serial: <filter> rev: LVM1 scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 3.0 size: 28.82 GiB serial: <filter> scheme: GPT 
           ID-3: /dev/sdd type: USB vendor: Western Digital model: WD Elements 2620 size: 1.82 TiB serial: <filter> rev: 1018 
           scheme: GPT 
Partition: ID-1: / size: 24.79 GiB used: 168.2 MiB (0.7%) fs: overlay source: ERR-102 
           ID-2: /boot size: 486.0 MiB used: 46.0 MiB (9.5%) fs: vfat dev: /dev/sdb1 
Sensors:   Missing: Required tool sensors not installed. Check --recommends 
Info:      Processes: 161 Uptime: 53m Memory: 1.95 GiB used: 422.4 MiB (21.1%) Init: systemd v: 241 runlevel: 5 default: 2 
           Compilers: gcc: N/A Shell: bash v: 5.0.3 running in: tty 0 (SSH) inxi: 3.0.32 

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 5: D50s [D50s], device 0: USB Audio [USB Audio]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

volumio@volumio:~$ 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=Intel
    HDA Intel, ALC269VB Analog
    Default Audio Device
front:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    Front speakers
surround21:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    4.0 Surround output to Front and Rear speakers
surround41:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
dmix:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    Direct sample mixing device
dsnoop:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    Direct sample snooping device
hw:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    Direct hardware device without any conversions
plughw:CARD=Intel,DEV=0
    HDA Intel, ALC269VB Analog
    Hardware device with all software conversions
usbstream:CARD=Intel
    HDA Intel
    USB Stream Output
sysdefault:CARD=D50s
    D50s, USB Audio
    Default Audio Device
front:CARD=D50s,DEV=0
    D50s, USB Audio
    Front speakers
surround21:CARD=D50s,DEV=0
    D50s, USB Audio
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=D50s,DEV=0
    D50s, USB Audio
    4.0 Surround output to Front and Rear speakers
surround41:CARD=D50s,DEV=0
    D50s, USB Audio
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=D50s,DEV=0
    D50s, USB Audio
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=D50s,DEV=0
    D50s, USB Audio
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=D50s,DEV=0
    D50s, USB Audio
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=D50s,DEV=0
    D50s, USB Audio
    IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=D50s,DEV=0
    D50s, USB Audio
    Direct sample mixing device
dsnoop:CARD=D50s,DEV=0
    D50s, USB Audio
    Direct sample snooping device
hw:CARD=D50s,DEV=0
    D50s, USB Audio
    Direct hardware device without any conversions
plughw:CARD=D50s,DEV=0
    D50s, USB Audio
    Hardware device with all software conversions
usbstream:CARD=D50s
    D50s
    USB Stream Output
**********

Only fault is wifi no function , only no connect with hotspot
I connect via ethernet ok.
Plug in was dissapear, no Spotify, wich intresting me so much.
DSD direct is perfect recognize the topping D50s perfectly!! the original version of volumio x86 dont work in DSD direct , only with dop…
Thanks very much!

Please add Plug-ins (Spotify)… is there a way that a user without much experience can do it without compiling the kernel? …I mean add Spotify

sorry, beta versions do not have plugins enabled at the moment as external development is not supporting it yet.

Thanks, very much gkkpch ,I´m will waiting for future advances