@gvolt can you help with this?
What did you add?
dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-7inch,dsi0
Can you confirm that the display is connected via a display and not via a camera DSI cable?
Does the display work if connected to DSI1? In that case dtoverlay=vc4-kms-dsi-7inch,dsi0 needs to be changed to dtoverlay=vc4-kms-dsi-7inch.
If possible post pictures of the DSI cable connections made to display and Pi.
Hi @gvolt
I’m terribly sorry for this late reply and I apologise for this (had some family issues).
I’ve checked connections again, did complete reinstall, added dtoverlays to userconfig and now everything works (I’ve definitely messed something up last time).
But I now have another problem sort of (sorry).
Currently I’m trying nvme boot and I can’t get touch plugin to work with volumio ver. 3.639 (I know it’s alpha) booting from nvme drive.
The screen works fine until volumio boots than it goes blank (no picture and no backlight) if I disable the plugin I get the usual screen (Welcom to volumio, WebUI available etc.).
I’ve made a log, hope this can help: http://logs.volumio.org/volumio/mSFYB8l.html
From the system running Volumio 3.639 post the output of
cat /boot/config.txt
and
cat /boot/userconfig.txt
Which DSI port is the display connected to?
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
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt
userconfig.txt:
Add your custom config.txt options to this file, which will be preserved during updates
dtoverlay=vc4-kms-v3d-pi5
dtoverlay=vc4-kms-dsi-7inch, dsi0
dtparam=nvme
dtparam=pciex1_gen2
Display is connected to DSI port 0.
I don’t expect that to be the solution, but please try removing
dtoverlay=vc4-kms-v3d-pi5
from “/boot/userconfig.txt”.
Is the DSI cable a display (or camera) cable?
Did you try connecting the display to DSI1?
I’ve tried everything you suggested but still not working.
Display is working on RpiOS on DSI 0 and DSI 1 ports without a problem ( cable is display cable not camera cable ).
On Volumio ( v.3.639 ) it’s “working” ( when the plugin is inactive ) only on DSI 0 on DSI1 it doesn’t even start ( I’ve removed dsi0 from dtoverlay ).
The attached picture is display when booting volumio and the second one is when volumio completes its boot ( plugin inactive otherwise display is dead ).
Is that on an Odroid device?
The error messages “Unknown operand” have no meaning. It is an init script deficiency, which has been corrected in the soon the be released startup overhaul.
Please post the output of
lsmod
and
cat /etc/X11/xorg.conf.d/99-vc4.conf
Module Size Used by
nft_chain_nat 16384 4
xt_REDIRECT 16384 1
nf_nat 49152 2 nft_chain_nat,xt_REDIRECT
nf_conntrack 147456 2 nf_nat,xt_REDIRECT
nf_defrag_ipv6 20480 1 nf_conntrack
nf_defrag_ipv4 16384 1 nf_conntrack
xt_tcpudp 16384 1
bnep 24576 2
nft_compat 20480 2
nf_tables 249856 5 nft_compat,nft_chain_nat
nfnetlink 20480 2 nft_compat,nf_tables
8021q 32768 0
joydev 28672 0
garp 16384 1 8021q
stp 16384 1 garp
llc 16384 2 stp,garp
rpi_panel_attiny_regulator 16384 5
regmap_i2c 16384 1 rpi_panel_attiny_regulator
edt_ft5x06 28672 0
spidev 20480 0
tc358762 16384 0
vc4 372736 7
snd_soc_hdmi_codec 20480 2
hci_uart 53248 0
drm_display_helper 16384 1 vc4
cec 53248 1 vc4
btbcm 24576 1 hci_uart
bluetooth 565248 24 hci_uart,btbcm,bnep
snd_soc_core 274432 2 vc4,snd_soc_hdmi_codec
raspberrypi_hwmon 16384 0
snd_compress 20480 1 snd_soc_core
snd_pcm_dmaengine 20480 1 snd_soc_core
snd_pcm 139264 4 snd_soc_hdmi_codec,snd_compress,snd_soc_core,snd _pcm_dmaengine
ecdh_generic 16384 2 bluetooth
ecc 36864 1 ecdh_generic
brcmfmac 327680 0
pisp_be 32768 0
rpivid_hevc 53248 0
aes_ce_blk 32768 1
v4l2_mem2mem 45056 1 rpivid_hevc
brcmutil 24576 1 brcmfmac
snd_seq 73728 0
i2c_brcmstb 16384 0
snd_seq_device 16384 1 snd_seq
aes_ce_cipher 16384 1 aes_ce_blk
snd_timer 36864 2 snd_seq,snd_pcm
cfg80211 929792 1 brcmfmac
videobuf2_dma_contig 20480 2 pisp_be,rpivid_hevc
snd 106496 11 snd_seq,snd_seq_device,snd_soc_hdmi_codec,snd_t imer,snd_compress,snd_soc_core,snd_pcm
drm_rp1_dsi 20480 1
spi_bcm2835 20480 0
ghash_ce 20480 0
videobuf2_memops 16384 1 videobuf2_dma_contig
gf128mul 16384 1 ghash_ce
rfkill 32768 6 bluetooth,cfg80211
drm_dma_helper 20480 2 drm_rp1_dsi,vc4
libaes 16384 4 aes_ce_cipher,bluetooth,ghash_ce,aes_ce_blk
drm_kms_helper 204800 7 drm_dma_helper,drm_rp1_dsi,vc4,tc358762
sha2_ce 16384 0
videobuf2_v4l2 32768 3 pisp_be,rpivid_hevc,v4l2_mem2mem
sha256_arm64 24576 1 sha2_ce
fb_sys_fops 16384 1 drm_kms_helper
pwm_fan 20480 0
videobuf2_common 69632 6 pisp_be,videobuf2_dma_contig,videobuf2_v4l2,rpiv id_hevc,v4l2_mem2mem,videobuf2_memops
sha1_ce 16384 0
syscopyarea 16384 1 drm_kms_helper
v3d 90112 0
sysfillrect 16384 1 drm_kms_helper
gpu_sched 49152 1 v3d
panel_simple 86016 0
drm_shmem_helper 24576 1 v3d
videodev 274432 5 pisp_be,videobuf2_v4l2,videobuf2_common,rpivid_h evc,v4l2_mem2mem
drm 581632 13 gpu_sched,drm_kms_helper,panel_simple,drm_dma_h elper,v3d,drm_rp1_dsi,vc4,tc358762,drm_shmem_helper,drm_display_helper
gpio_keys 20480 0
sysimgblt 16384 1 drm_kms_helper
raspberrypi_gpiomem 16384 0
i2c_designware_platform 16384 0
rp1_adc 16384 0
mc 61440 6 videodev,pisp_be,videobuf2_v4l2,videobuf2_common ,rpivid_hevc,v4l2_mem2mem
i2c_designware_core 24576 1 i2c_designware_platform
drm_panel_orientation_quirks 28672 1 drm
backlight 24576 2 rpi_panel_attiny_regulator,drm
nvmem_rmem 16384 0
uio_pdrv_genirq 16384 0
uio 24576 1 uio_pdrv_genirq
i2c_dev 20480 0
ip_tables 32768 0
x_tables 53248 4 nft_compat,xt_tcpudp,ip_tables,xt_REDIRECT
ipv6 557056 75
fuse 135168 1
squashfs 49152 1
overlay 126976 1
Section "OutputClass"
Identifier "vc4"
MatchDriver "vc4"
Driver "modesetting"
Option "PrimaryGPU" "true"
EndSection
Stop the Touch Display plugin and change the content of “/etc/X11/xorg.conf.d/99-vc4.conf” to
Section "OutputClass"
Identifier "rp1"
MatchDriver "rp1-vec|rp1-dsi|rp1-dpi"
Driver "modesetting"
Option "PrimaryGPU" "true"
EndSection
Then start the Touch Display plugin.
That did it!! 
I’m truly grateful for your amazing help.
Thank you very much. 
Hm, the correct settings in “99-vc4.conf” should be applied automatically by the Touch Display plugin…
Has this been a fresh Volumio installation?
What version of the Touch Display plugin did you install?
Yeah, fresh install.
I used guide from: https://community.volumio.com/t/beta-raspberry-pi-boot-from-usb-nvme/65699
The plugin is version 3.4 (stable).
As I said before this happens only on this version of volumio ( 3.639 RC-Testing ), on the official release (3.631) the plugin worked flawlessly.
Thank you once more.
Ok, could you please PM me the output of
cat /proc/modules
from both 3.631 and 3.639?
From the 3.639 system also post the result of
cat /etc/os-release
Sure, no problem. 
Hope you don’t mind but I will do this tomorrow after work.
1 Like