Volumio3 and TFT 3.5 screen

Hi all! My name is Osvaldo from Chile.

I have a Volumio premium account. Recently buy a TFT 3,5 screen touch (GPIO) in my RPI 3, but in a version 2.777 of Volumio, follow the steps on the post of Ago '21 in this thread Volumio with 3.5" TFT Touch Screen (GPIO) RPi 3B+ - #162 by gvolt

But, when I tried to install the screen in a fresh Volumio 3 install, not working. Same results when I updated from Volumio 2.777 to Volumio 3.

I need help please.

Is it correct that the screen did work on a previous installation of Volumio 2.777 with the settings from the link you mentioned? If not: What is the brand and exact model name of your display?

What version of the plugin do you have installed currently?

Did you enable the Touch Display plugin after installing it?

Do you see an error message on Volumio’s UI when you start the plugin? If so, what is the content of that message?

Also please post the result of

cat /var/log/Xorg.0.log

yes, I have an SD with volumio 2.777 and it’s working, screen and touch.

I don’t know. It’s from Volumio 2.777 install in option miscellanea.

Yes. When I tried to install the touchscreen in Volumio 3, I follow the step by step guide from the theard mentioned above: Fresh volumio 3 → Install Touch Dsiplay and enabled → Via ssh the steps from the thread mentioned.
The steps are the same than Volumio 2.777, but when enter de line “sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf”, says that fil not exist. Copy from my another setup and follow. The rest no problem.
However, when reboot, the screen is complete black and show nothing and send this message imagen

cat /var/log/Xorg.0.log
[ 47.335]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[ 47.336] Build Operating System: Linux 5.10.17-v8+ aarch64 Raspbian
[ 47.336] Current Operating System: Linux volumio 5.4.83-v7+ #1379 SMP Mon Dec 14 13:08:57 GMT 2020 armv7l
[ 47.336] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=640 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=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh rootwait bootdelay=5 elevator=noop logo.nologo vt.global_cursor_default=0 net.ifnames=0 snd-bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 loglevel=0
[ 47.336] Build Date: 19 April 2021 03:23:36PM
[ 47.336] xorg-server 2:1.20.4-1+rpt3+deb10u3 (Debian -- Support)
[ 47.336] Current version of pixman: 0.36.0
[ 47.336] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 47.336] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 47.337] (==) Log file: “/var/log/Xorg.0.log”, Time: Mon Jan 3 02:56:39 2022
[ 47.349] (==) Using config directory: “/etc/X11/xorg.conf.d”
[ 47.349] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 47.358] (==) No Layout section. Using the first Screen section.
[ 47.358] (==) No screen section available. Using defaults.
[ 47.358] (
) |–>Screen “Default Screen Section” (0)
[ 47.358] () | |–>Monitor “”
[ 47.366] (==) No device specified for screen “Default Screen Section”.
Using the first device section listed.
[ 47.366] (
) | |–>Device “Allwinner A10/A13/A20 FBDEV”
[ 47.366] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
[ 47.366] (==) Automatically adding devices
[ 47.366] (==) Automatically enabling devices
[ 47.366] (==) Automatically adding GPU devices
[ 47.373] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 47.375] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
[ 47.375] Entry deleted from font path.
[ 47.377] (==) 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
[ 47.378] (==) ModulePath set to “/usr/lib/xorg/modules”
[ 47.378] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 47.378] (II) Loader magic: 0x1fdf80
[ 47.378] (II) Module ABI versions:
[ 47.378] X.Org ANSI C Emulation: 0.4
[ 47.378] X.Org Video Driver: 24.0
[ 47.378] X.Org XInput driver : 24.1
[ 47.378] X.Org Server Extension : 10.0
[ 47.382] (–) using VT number 2

[ 47.382] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 47.383] (II) no primary bus or device found
[ 47.383] (II) LoadModule: “glx”
[ 47.389] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 47.483] (II) Module glx: vendor=“X.Org Foundation”
[ 47.483] compiled for 1.20.4, module version = 1.0.0
[ 47.483] ABI class: X.Org Server Extension, version 10.0
[ 47.483] (II) LoadModule: “fbturbo”
[ 47.487] (WW) Warning, couldn’t open module fbturbo
[ 47.487] (EE) Failed to load module “fbturbo” (module does not exist, 0)
[ 47.487] (EE) No drivers available.
[ 47.487] (EE)
Fatal server error:
[ 47.488] (EE) no screens found(EE)
[ 47.488] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 47.488] (EE) Please also check the log file at “/var/log/Xorg.0.log” for additional information.
[ 47.488] (EE)
[ 47.488] (EE) Server terminated with error (1). Closing log file.

Please edit the file “/usr/share/X11/xorg.conf.d/99-fbturbo.conf” by changing the driver from “fbturbo” to “fbdev”:

Driver          "fbdev"

Save the file, then disable and re-enable the Touch Display plugin or maybe reboot.

1 Like

Working!

I have a Volumio 3 on my RPI3 with the screen and touch working.

Thank you very much.

Thanks for your feedback!

So changing the driver to “fbdev” was the solution?

P.S. If true, please mark the thread as solved.

Yes. Change the driver to fbdev was the solution.

1 Like