[PLUGIN] Touch Display

New error on my side: I wasn’t connected to the raspi.
Now new connected. Here comes the list after the command

ls -al

total 53
drwxr-xr-x 1 volumio volumio 1024 Feb 5 19:56 .
drwxr-xr-x 1 root root 1024 Dec 16 09:29 …
-rw------- 1 volumio volumio 101 Feb 5 19:56 .Xauthority
-rw------- 1 volumio volumio 274 Feb 5 19:55 .bash_history
-rw-r–r-- 1 volumio volumio 220 Apr 18 2019 .bash_logout
-rw-r–r-- 1 volumio volumio 3526 Apr 18 2019 .bashrc
drwxr-xr-x 5 volumio volumio 1024 Feb 5 15:56 .cache
-rw-r–r-- 1 volumio volumio 49 Dec 16 09:31 .cdcdrc
-rw-r–r-- 1 volumio volumio 171 Dec 16 09:31 .cdserverrc
drwx------ 4 volumio volumio 1024 Feb 5 15:56 .config
drwx------ 3 volumio volumio 1024 Feb 5 15:56 .gnupg
drwxr-xr-x 3 volumio volumio 1024 Feb 5 16:46 .local
drwx------ 3 volumio volumio 1024 Feb 5 15:56 .pki
-rw-r–r-- 1 volumio volumio 807 Apr 18 2019 .profile
-rw------- 1 volumio volumio 34164 Feb 5 19:56 .xsession-errors
-rw-r–r-- 1 volumio volumio 50 Feb 5 19:55 userconfig.txt
and here after ls -al /boot

total 82070
drwxrwxrwx 5 root root     5120 Jan  1  1970 .
drwxrwxrwx 1 root root     1024 Jan  1  1970 ..
drwxrwxrwx 3 root root      512 Feb  5 13:32 .Spotlight-V100
-rw-rw-rw- 1 root root       41 Dec 16 09:34 .bootloader_revision
-rw-rw-rw- 1 root root       41 Dec 16 09:34 .firmware_revision
drwxrwxrwx 2 root root      512 Feb  5 13:32 .fseventsd
-rw-rw-rw- 1 root root    30696 Dec 16 09:34 bcm2708-rpi-b-plus.dtb
-rw-rw-rw- 1 root root    30055 Dec 16 09:34 bcm2708-rpi-b-rev1.dtb
-rw-rw-rw- 1 root root    30393 Dec 16 09:34 bcm2708-rpi-b.dtb
-rw-rw-rw- 1 root root    30012 Dec 16 09:34 bcm2708-rpi-cm.dtb
-rw-rw-rw- 1 root root    31873 Dec 16 09:34 bcm2708-rpi-zero-w.dtb
-rw-rw-rw- 1 root root    30006 Dec 16 09:34 bcm2708-rpi-zero.dtb
-rw-rw-rw- 1 root root    32390 Dec 16 09:34 bcm2709-rpi-2-b.dtb
-rw-rw-rw- 1 root root    32181 Dec 16 09:34 bcm2709-rpi-cm2.dtb
-rw-rw-rw- 1 root root    32519 Dec 16 09:34 bcm2710-rpi-2-b.dtb
-rw-rw-rw- 1 root root    35346 Dec 16 09:34 bcm2710-rpi-3-b-plus.dtb
-rw-rw-rw- 1 root root    34711 Dec 16 09:34 bcm2710-rpi-3-b.dtb
-rw-rw-rw- 1 root root    32298 Dec 16 09:34 bcm2710-rpi-cm3.dtb
-rw-rw-rw- 1 root root    33688 Dec 16 09:34 bcm2710-rpi-zero-2-w.dtb
-rw-rw-rw- 1 root root    33688 Dec 16 09:34 bcm2710-rpi-zero-2.dtb
-rw-rw-rw- 1 root root    56156 Dec 16 09:34 bcm2711-rpi-4-b.dtb
-rw-rw-rw- 1 root root    56160 Dec 16 09:34 bcm2711-rpi-400.dtb
-rw-rw-rw- 1 root root    38405 Dec 16 09:34 bcm2711-rpi-cm4-io.dtb
-rw-rw-rw- 1 root root    56640 Dec 16 09:34 bcm2711-rpi-cm4.dtb
-rw-rw-rw- 1 root root    53443 Dec 16 09:34 bcm2711-rpi-cm4s.dtb
-rw-rw-rw- 1 root root    81451 Dec 16 09:34 bcm2712-rpi-5-b.dtb
-rw-rw-rw- 1 root root    81407 Dec 16 09:34 bcm2712-rpi-500.dtb
-rw-rw-rw- 1 root root    81815 Dec 16 09:34 bcm2712-rpi-cm5-cm4io.dtb
-rw-rw-rw- 1 root root    81877 Dec 16 09:34 bcm2712-rpi-cm5-cm5io.dtb
-rw-rw-rw- 1 root root    81856 Dec 16 09:34 bcm2712-rpi-cm5l-cm4io.dtb
-rw-rw-rw- 1 root root    81918 Dec 16 09:34 bcm2712-rpi-cm5l-cm5io.dtb
-rw-rw-rw- 1 root root    81455 Dec 16 09:34 bcm2712d0-rpi-5-b.dtb
-rw-rw-rw- 1 root root    52476 Dec 16 09:34 bootcode.bin
-rw-rw-rw- 1 root root      607 Feb  5 13:32 cmdline.txt
-rw-rw-rw- 1 root root      351 Feb  5 15:46 config.txt
-rw-rw-rw- 1 root root     7327 Dec 16 09:34 fixup.dat
-rw-rw-rw- 1 root root     5456 Dec 16 09:34 fixup4.dat
-rw-rw-rw- 1 root root     3230 Dec 16 09:34 fixup4cd.dat
-rw-rw-rw- 1 root root     8454 Dec 16 09:34 fixup4db.dat
-rw-rw-rw- 1 root root     8454 Dec 16 09:34 fixup4x.dat
-rw-rw-rw- 1 root root     3230 Dec 16 09:34 fixup_cd.dat
-rw-rw-rw- 1 root root    10295 Dec 16 09:34 fixup_db.dat
-rw-rw-rw- 1 root root    10295 Dec 16 09:34 fixup_x.dat
-rw-rw-rw- 1 root root  7063744 Dec 16 09:34 kernel.img
-rw-rw-rw- 1 root root  7406184 Dec 16 09:34 kernel7.img
-rw-rw-rw- 1 root root  7834064 Dec 16 09:34 kernel7l.img
-rw-rw-rw- 1 root root  9331442 Dec 16 09:34 kernel8.img
-rw-rw-rw- 1 root root      205 Feb  5 13:32 network-.con
drwxrwxrwx 2 root root    29696 Dec 16 09:34 overlays
-rw-rw-rw- 1 root root      162 Dec 16 09:30 partconfig.json
-rw-rw-rw- 1 root root  2984352 Dec 16 09:34 start.elf
-rw-rw-rw- 1 root root  2260192 Dec 16 09:34 start4.elf
-rw-rw-rw- 1 root root   812668 Dec 16 09:34 start4cd.elf
-rw-rw-rw- 1 root root  3757832 Dec 16 09:34 start4db.elf
-rw-rw-rw- 1 root root  3007816 Dec 16 09:34 start4x.elf
-rw-rw-rw- 1 root root   812668 Dec 16 09:34 start_cd.elf
-rw-rw-rw- 1 root root  4829672 Dec 16 09:34 start_db.elf
-rw-rw-rw- 1 root root  3731464 Dec 16 09:34 start_x.elf
-rw-rw-rw- 1 root root      499 Feb  5 13:32 user-data
-rw-rw-rw- 1 root root       90 Dec 16 09:35 userconfig.txt
-rw-rw-rw- 1 root root 28761071 Dec 16 09:42 volumio.initrd
-rw-rw-rw- 1 root root      366 Dec 16 09:36 volumioconfig.txt

“/boot/userconfig.txt” is there. So

nano /boot/userconfig.txt

should open the file… It should work even without using “sudo” but you may try

sudo nano /boot/userconfig.txt

(password is volumio)

Great: It works.
The two lines were good!
My error was that I tried to modify userconfig.txt in the root directory and not in the /boot/ directory.
Second error: After rebooting, I forgot to connect me once again.
Thanks gvolt

1 Like

Hi Folks,

today I saw my touch display is not working anymore.
I checked it with the normal raspios and here it works.
So I tried to reinstall the touch display plugin.
Uninstall works fine, but the installation fails with:

The following packages have unmet dependencies:
chromium-browser : Depends: chromium-codecs-ffmpeg-extra (= 92.0.4515.98~buster-rpt2) but it is not going to be installed or
chromium-codecs-ffmpeg (= 92.0.4515.98~buster-rpt2) but it is not going to be installed
Depends: libraspberrypi0 but it is not installable
Recommends: chromium-browser-l10n but it is not going to be installed
Installation of Chromium failed
Plugin failed to install!
Cleaning up...

I also tried this, but there’s no beta version:
Raspberry Pi Touch Display didn´t work any more

How can I fix that to bring my display back to life?

The display is an official Raspberry Pi 7 Display.

Many thanks

Could you perform a factory reset or reinstall Volumio to test if the error occurs again?

BTW: What is your Pi model and Volumio version?

Factory reset means I have to copy 90GB music files again?

Depends where the music files have been stored.

Files are stored in /data/INTERNAL/.
It’s a raspi 3b and the Volumio version is 3.785.

According to “When the Factory Reset of the unit is requested?” the files should be preserved, if I understand correctly. But I would say be prepared to lose the data anyway.

Edit: A factory reset deletes files in “/data/INTERNAL”, too, as @Buzzzz reported.

If you want to avoid any risk that use another SD card to install a new Volumio system for testing purposes. I would say that this would be the preferred way anyway.

I did fresh new installation on a second SD card. Plugin installation works now, but not the display.

Do you receive the same error message as reported before during the plugin installation?

No, there was no error during the installation.
Plugin is installed. But no screen. I did no changes on userconfig.

I use this 7’ display:

Please add

dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-7inch

to “/boot/userconfig.txt”.

I flashed an old backup what I found from 2023 on this the display works.
After a system update the display don´t work again.
With you parameters I got an error on webscreen the touch display plugin cannot communicate with x-server.
I’ll check that with the default image again.

Yes, please try with a new Volumio 3.785 installation.

Ok Volumio 3.785 and Touch Display plugin 3.5.1 installed.
Plugin is activated, no display screen.
My userconfig.txt:

volumio@volumio:~$ cat /boot/userconfig.txt 
# Add your custom config.txt options to this file, which will be preserved during updates
volumio@volumio:~$ 

So I added:

dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-7inch

After a reboot I got a screen. I’ll try to set my other card to factory. Otherwise I’ll do a fresh installation.

Many thanks for you help an for you plugin. :person_raising_hand:

1 Like

And for information, the factory reset delete´s everything!

Thank you for clarifying this. I edited my previous post accordingly.

I change the screen rotation to 180 degrees and after a reboot, my userconfig.txt looks like:

# Add your custom config.txt options to this file, which will be preserved during updates

#### Touch Display rotation setting below: do not alter ####
lcd_rotate=2
display_hdmi_rotate=2

I have to add the display activation parameters again.

That should not happen just by changing the screen rotation. Will check that.