Hello, Volumio doesn’t display or work with the 8.8 inch touchscreen. I’ve enabled the plugins, and I’ve even changed the code in the folder that’s listed on the screen’s website (specifically for Raspberry Pi), but it doesn’t work. The screen is just black and barely illuminated. I’ve been trying to connect it for two months now. My devices are: Raspberry Pi 3B+ and an 8.8-inch HDMI touchscreen monitor with a long, wide 1920x480 resolution. The PC has a temperature display, a touch panel, an RPi AIDA display, and a small monitor extension.
Welcome to the Volumio forum, great to have you here! Since we can’t see your setup (and you’re clearly diving deep into a screen salad 
), we’ll need a few details to help untangle the mystery box.
Here’s your quick onboarding checklist:
Volumio version , Which version are you running? And please don’t just say “latest”, we like specifics. Precision is our friend here.
Screen soup confusion , You’ve mentioned HDMI 1920x480, rPi AIDA, a temperature display, a touchscreen monitor, and a small monitor extension. Are these five separate screens? Or just one magical chimera written in multiple ways? Help us visualize your beast of a setup.
Screen info, Could you share a link to the screen you’re using, preferably with some technical specs? That’ll help us figure out compatibility, resolutions, and the secret sauce it needs.
Config files , Drop us the output of:
cat /boot/config.txt
cat /boot/userconfig.txt
That’s where the Pi hides some clues.
System log , And finally, once the system’s fully booted, please send us a Volumio log. It’s our backstage pass to everything that’s going wrong (or right!).
Once we’ve got that, we’ll be much closer to decoding your multi-monitor mystery!
Looking forward to helping you get things singing
V4.014-4.016 works with Touch Display 3.5.4 (and older) without VC4 KMS. (in my case).
It worked unexpectedly. 4.016+3.5.5. Turn on-off-on.
userconfig.txt:
display_auto_detect=1
dtoverlay=vc4-kms-v3d
dtoverlay=tft35a,rotate=270
99-fbturbo.conf:
Driver “fbturbo”
Option “fbdev” “/dev/fb1”
My screen is: 3.5” RPi Display(MPI3501)
Thanx.
disable hdmi_force_hotplug=1 in /boot/config.txt, so it looks like:
#hdmi_force_hotplug=1
Add to /boot/userconfig.txt
dtparam=spi=on
Reboot, does it show something during boot?
what is the output of:
ls -l /dev/fb*
cat /var/log/Xorg.0.log | grep fb
Nothing shows on boot.
ls -l /dev/fb*
crw-rw---- 1 root video 29, 0 Jul 15 19:29 /dev/fb0
crw-rw---- 1 root video 29, 1 Jul 15 19:30 /dev/fb1
cat /var/log/Xorg.0.log | grep fb
[ 38.019] (II) LoadModule: “fbturbo”
[ 38.019] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
[ 38.022] (II) Module fbturbo: vendor=“X.Org Foundation”
[ 38.022] (II) FBTURBO: driver for framebuffer: fbturbo
[ 38.028] (WW) Falling back to old probe method for fbturbo
[ 38.028] (II) Loading sub module “fbdevhw”
[ 38.028] (II) LoadModule: “fbdevhw”
[ 38.028] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 38.030] (II) Module fbdevhw: vendor=“X.Org Foundation”
[ 38.030] (II) FBTURBO(0): using /dev/fb1
“Default Screen Section” for depth/fbbpp 16/16
[ 38.030] (II) FBTURBO(0): hardware: fb_ili9486 (video memory: 300kB)
[ 38.030] (**) FBTURBO(0): Option “fbdev” “/dev/fb1”
[ 38.031] (II) Loading sub module “fb”
[ 38.031] (II) LoadModule: “fb”
[ 38.031] (II) Module “fb” already built-in
and do not work again - nothing on LCD. Have to switch on-off couple of times. Not so interesting.
Hi display guru, any suggestion?
You could try substituting the current content of “/boot/userconfig.txt” with
dtparam=spi=on
dtoverlay=piscreen,speed=18000000,drm,rotate=270
to check if that alternative overlay works. You may test this with and without
dtoverlay=vc4-kms-v3d
at the beginning of “/boot/userconfig.txt”.
Also check the effect of removing 99-fbturbo.conf from /usr/share/X11/xorg.conf.d.
Just yeeted that piscreen,speed=18000000,drm overlay onto my tiny 3.5" screen for laughs and the boot logo rose from the ashes like a pixelated phoenix.
Before this, that part of my setup was basically the Bermuda Triangle of boot sequences: mysterious, frustrating, and totally logo-less. Now? It’s showing off like it just won a beauty pageant.
1 Like
Great! Is this with
dtoverlay=vc4-kms-v3d?
No only:
volumio@rpi4-es9039q2m:~$ cat /boot/userconfig.txt
# Add your custom config.txt options to this file, which will be preserved during updates
dtparam=spi=on
dtoverlay=piscreen,speed=18000000,drm,rotate=0
#### Touch Display rotation setting below: do not alter ####
display_lcd_rotate=3
display_hdmi_rotate=3
Only need to sort out how to get rid off the white screen when the Touch Plugin is loaded.
Need to run some tests.
adding dtoverlay=vc4-kms-v3d turns the screen fully black, removing it turns it white with a visible mouse.
Update:
Modified userconfig.txt with:
volumio@rpi4-es9039q2m:~$ cat /boot/userconfig.txt
# Add your custom config.txt options to this file, which will be preserved during updates
#dtoverlay=vc4-kms-v3d
dtparam=spi=on
dtoverlay=piscreen,speed=16000000,drm,xohms=100,rotate=0
Installed Touch Display, without doing any additional installs (fbturbo, x-server, …)
And the volumio GUI lit up.
After configuring the scale for 100 to 60, it restarted and only shows a white screen for approx. 7 minutes, then the GUI pops up again. go figure…
After reboot all is working.
I loaded my userconfig file will the following commands:
Add your custom config.txt options to this file, which will be preserved during updates
Touch Display gpu_mem setting below: do not alter
gpu_mem=128
Touch Display rotation setting below: do not alter
display_lcd_rotate=3
display_hdmi_rotate=3
hdmi_cvt=480 1920 60
hdmi_drive=1
hdmi_mode=87
hdmi_group=2
max_framebuffer_width=1920
max_framebuffer_height=1920
framebuffer_width=1920
framebuffer_height=480
enable_uart=1
dtoverlay=disable-bt
I am using the GPIO button plugin to turn off the raspPI and now the light is on while the RaspPI is running. That is now solved.
With the userconfig file loaded the screen has the correct orientation and it shows the Volumio boot up sequence but it stops at the login prompt.
The only issue I have now is the Peppy screensaver 2.2.1 is not working. It shows under the installed plugin list and I can change settings but nothing happens. Is there another plugin I need to run. My screen is not a touch screen so I did not install the touch screen plugin.
You need to install the Touch Display Plugin. Regardless if it is a touchscreen or not.
Does it matter which order I install the touch screen plugin or Peppy screensaver?
There is YT video and they install Volumio, add the screen plug-in, enable SSH and then load Peppy.
Are my user configured commands still valid? They are to correct the screen size, orientation, turn on the power light and allow the RaspPi to be turned off.
When I install the display plugin and reboot the RaspPi I see the Volumio startup screen but then it goes black. The only time I see the login prompt is when the display plugin is not installed.
I tried adding the following to the userconfig file but no luck
hdmi_group=2
hdmi_mode=87
hdmi_cvt 1920 1080 60 3 0 0 0
hdmi_drive=2
I am using a Benq GL2780-B desktop monitor 1920 x 1080
what commands should I use?
With my RPi MPI3501 or
boot logo with dtoverlay=piscreen,drm,rotate=0
or
play info with dtoverlay=tft35a,rotate=270
not both.
Based on the information in this thread I am assuming that you use a Pi 4. If that is correct, try adding
dtoverlay=vc4-kms-v3d-pi4
at the top of your “/boot/userconfig.txt”.
With such a sparse description it’s hard to help. What does the display look like after the boot logo has been displayed and the Touch Display plugin has been started? Is it black or white or…? When watching the Volumio UI in a browser on another device: Is any error message displayed when starting the plugin?
Did you also play around with the “speed” setting of the overlay? If so, what effects did the different speed values have?
Do I understand correctly that
means that Volumio’s UI is displayed when only “dtoverlay=tft35a,rotate=270” is used in “/boot/userconfig.txt”?
When Pi4 turned on, the screen is bright, then it darkens and the boot logo animation occurs. After that, the screen brightens and darkens again. And remains dark (not turned off). The Volumio screen does not show. Other “screens” (MacBook and tablet) work. No errors.
Changing fbdev to fbturbo and fb0 to fb1 in the 99-fbturbo.conf does not affect the display of the logo during boot, but it also does not show the main Volumio screen. Obviously (in my case), dtoverlay=piscreen,drm works under Raspberry and don’t in Touch Display.
dtoverlay=tft35 on the contrary does not work under Raspberry, but works under Touch Display.
userconfig is minimal:
dtparam=i2c_arm=on
dtparam=spi=on
display_auto_detect=1
dtoverlay=tft35a,rotate=270
#dtoverlay=piscreen,drm,rotate=0
Yes, when userconfig is:
dtparam=i2c_arm=on
dtparam=spi=on
display_auto_detect=1
dtoverlay=tft35a,rotate=270
and
99-fbturbo.conf:
Driver “fbturbo”
Option “fbdev” “/dev/fb1”
Version 3.5.4. With my LCD it’s working good with 4.016
1 Like