Ok, then no addition to the “vc4-kms-dsi-ili9881-7inch” should be required.
Could you check if using
dtoverlay=vc4-kms-v3d-pi5,nohdmi
changes something?
@gvolt nothing better 
A post was split to a new topic: Use of HDMI Touch screen with Primo 2
In “working HDMI” screen scenario please show output:
aplay -l
Clarification required:
When using HDMI output as screen - can you confirm that the actual display is attached to the Denon AVR-X2000?
If the answer is yes - I think we should split this topic, as the problem seems to be related to the amplifier EDID rather than touch screen.
Kind Regards,
Thank you, I will try the aplay-l commande and give the log here.
When using HDMI output as screen :
RaspBerry Pi 5 is connected to the screen with 22-way to 15-way FFC and Raspberry Pi 5 is connected to AVR-X2000 with micro-HDMI to HDMI cable.
In “/boot/userconfig.txt” replace
dtoverlay=vc4-kms-dsi-7inch
with
dtoverlay=vc4-kms-dsi-ili9881-7inch
Hello,
I am assembling a second Raspberry + Volumio for my father. On mine I have the Touch Display 1, for his I can either buy the Touch Display 2 or version 1 second hand. Is there a real advantage for version 2 over version 1 when using Volumio?
Thanks !
Hey @Sty_X,
It is down to your personal preference. The Raspberry Pi Touch Display 2 offers a higher resolution and a portrait orientation by default, making it challenging to operate as console screen only. However It simplifies setup by drawing power directly from the Raspberry Pi, eliminating the need for a separate power supply. However, it’s important to note that it is not compatible with the Raspberry Pi Zero series.
Comparison Table Raspberry Pi Touch Display vs. Raspberry Pi Touch Display 2
| Feature | Raspberry Pi Touch Display | Raspberry Pi Touch Display 2 |
|---|---|---|
| Display Size | 7 inches | 7 inches |
| Resolution | 800 × 480 pixels | 720 × 1280 pixels |
| Aspect Ratio | 15:9 | 9:16 (Portrait orientation) |
| Touch Support | 10-point capacitive touch | 5-point capacitive touch |
| Surface Treatment | Not specified | Anti-glare |
| Power Supply | Separate power supply required (GPIO power limited) | Powered via Raspberry Pi GPIO |
| Compatibility with Volumio OS | Works with Volumio OS with standard DSI overlay | Requires specific overlays for correct display and touch support |
| Default Orientation | Landscape | Portrait |
| Supported Overlays in Volumio OS | vc4-kms-dsi-7inch |
vc4-kms-dsi-ili9881-7inch |
Overlays for Raspberry Pi Touch Display 2 in Volumio OS
To enable the Raspberry Pi Touch Display 2 in Volumio OS, modify /boot/userconfig.txt and add the appropriate overlay:
Default (Portrait Mode)
[all]
display_auto_detect=1
dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-ili9881-7inch
Landscape Mode (90° Rotation)
[all]
display_auto_detect=1
dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-ili9881-7inch,rotation=90
Landscape Mode (270° Rotation)
[all]
display_auto_detect=1
dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-ili9881-7inch,rotation=270
After making changes, reboot the system for the new settings to take effect.
Kind Regards,
1 Like
Thanks for your complete answer!
The only thing that bothers me about the Display Touch 1 is the touch-sensitive keyboard :
-
I don’t find it very responsive.
-
the key management is poorly thought out: for example, when I press the “a” key, the keyboard directly proposes all the possibilities “a”, “à”, etc… I then have to click a second time to select “a”. I’d prefer it if, when I press “a”, the keyboard directly selected “a” and the alternatives were proposed on a long press.
I wonder if touch keyboard management has been improved on version 2.
Hey @Sty_X,
I think that you are discussing an on-screen keyboard actions installed with the Touch Display plugin. There is a dedicated thread here:
Kind Regards,
Good evening,
a quick information regarding the Pi Touch Display V2 - which I just have got to work (for me 
).
I was a little bit confused because in the beginning of this thread there are two different statement how to configure this display (caused by some trouble with Pi4+).
Finally I’ve used the original one which is reflected in Post #51 by @nerd .
I picked up the right-rotate version and put the described parameters in userconfig.txt as well as in cmdline.txt (this part isn’t refernced anymore?).
On boot the display works (! ) for the first time (after SEVERAL trials…)
BUT Display was in portrait mode.
So I’ve used the touchscreen plugin - remembering a rotation setting is present in this plugin.
Rotation with these settings worked like a charme (indeed it works without reboot).
BUT Touch worked - but x/y inverted.
So I tried to figure out how to swap the input coordinates - this seemed to be really complex and complicated
Than I remembered that I had configured a 270 degree rotation in dtoverlay AND with the plugin module…
Finally I reverted the dtoverlay-rotation to 0 (zero) and left the line from plugin as is.
NOW everything works as wanted.
So my tip: use dtoverly unrotated and do the rotation in the plugin…
Warm regards,
Ralf
Keep in mind that every addition to cmdline.txt will be reverted when performing an OTA update of Volumio.
It has also no added value for the Kiosk mode in Volumio, only when booting the logo is in the right position.
Thanks Nerd! I’ll check this topic.
Does anyone have a picture of Volumio on a Touch Display 2 to see what it looks like with a higher resolution than the Touch Display 1.
Based on the details in this thread and capabilities of VolumioOS 3 (Debian Buster, Raspberry Pi Kernel 6.6.62), here’s a breakdown of the clarification:
1. /boot/cmdline.txt - Init and Console Only
- The parameters added in
/boot/cmdline.txtonly affect the bootloader stage and console (TTY). - This means settings like
video=DSI-1:720x1280@60,rotate=90for display-related configurations will not impact the GUI once the Volumio UI is running. - This file is processed before Xorg (or the framebuffer-based Volumio UI) starts.
2. Plymouth (Boot Splash) - Too Old for Rotation
- Plymouth, used for the boot splash screen, is too outdated on Buster to support rotation options.
- If you rotate the screen in
/boot/cmdline.txtor/boot/userconfig.txt, the Plymouth splash will not respect it (i.e., the boot logo will appear in the default orientation). - This limitation is due to the older version of Plymouth in Debian Buster.
3. dtoverlay - Console Only
dtoverlaysettings (such asvc4-kms-dsi-ili9881-7inch,rotation=XXorlcd_rotate) only apply to the console (TTY) and init stage.- When the Volumio GUI starts, the framebuffer or Xorg settings override these parameters.
- Important: If you apply a rotation overlay at the boot level, the touchscreen plugin might get locked in that orientation.
4. Touch Plugin Rotation - GUI Only
- The Volumio Touch Display Plugin has a rotation setting that only affects the GUI (i.e., Chromium’s display).
- This means:
- It does not affect the bootloader, console (TTY), or Plymouth.
- You must still manually rotate the console separately if needed.
Practical Summary
| Setting | Affects Boot/Console? | Affects GUI? |
|---|---|---|
/boot/cmdline.txt rotation (video=DSI-1:720x1280@60,rotate=90) |
 Yes (init, console) |
 No |
/boot/userconfig.txt rotation (display_rotate, lcd_rotate) |
Yes (console only) |
No |
| Plymouth splash screen rotation | No (too old) |
No |
dtoverlay rotation |
Yes (console only) |
No (GUI ignores it) |
| Volumio Touch Plugin rotation | No |
Yes (GUI only) |
Solution if You Need Full Rotation
-
For Boot + Console: Modify
/boot/userconfig.txt:lcd_rotate=2or
display_rotate=2(Note: Only works for the console, not Plymouth or GUI.)
-
For GUI Rotation: Adjust the Touch Plugin settings in Volumio.
-
For Plymouth (if needed):
- There’s no direct way to rotate it in Buster.
- A workaround is using a custom splash screen image that is pre-rotated.
Kind Regards,
1 Like
Dear @nerd ,
thanks for this clarification and your effort!
Extremely useful and highly appreciated.
One question (for my better understanding): Several YT-Videos as well as the original install installation (here) sounds that there are no pre-requiremens to run this 7’’ touch display.
But this is (at least in my case) not true.
On initial hardware installation the display is NOT fired up at all.
(tried this on two different PI4 and one PI3 with several bootimages (to be sure that not Volumio is the root cause).
To get the display working I must enter a driver-line in config.txt (userconfig.txt for Volumio).
Another - much cheaper - China-Clone (unfortunately at much lower resolution) works without any configuration.
In your table you are stating that modification in userconfig.txt don’t affect GUI.
What’s the reason that my display won’t start without those modification in exact this place?
The vendor wasn’t aware of this “fact” as well - he suggested to do a PI-System update (which wasn’t useful, because already newest version).
Sorry for being this dumb…
And thanks for any insight.
Warm regards,
Ralf
Hey @rkorell,
The Raspberry Pi Foundation’s operating system, Raspberry Pi OS, is based on Debian 12 “Bookworm”. In contrast, Volumio is built upon Debian 10 “Buster”. Despite this older base, Volumio backports necessary functionalities to support various hardware components, including display screens.
Volumio is primarily designed for audio playback, with many users operating it in a headless mode (without a display) or connecting it to screens via HDMI. Its graphical user interface (GUI) is provided through a kiosk mode or available plugins, rather than a full desktop environment. Consequently, Volumio’s default configuration, by design, excludes certain elements present in Raspberry Pi OS that facilitate desktop detection and display integration.
For Digital Serial Interface (DSI) displays, such as the official Raspberry Pi Touch Display or Touch Display 2, proper functionality requires the Direct Rendering Manager (DRM) kernel mode setting (KMS) driver. To enable this in Volumio, users need to add specific overlay configurations to the /boot/userconfig.txt file. This involves adding lines like dtoverlay=vc4-kms-v3d and dtoverlay=vc4-kms-dsi-7inch (for Touch Display) or dtoverlay=vc4-kms-dsi-ili9881-7inch (Touch Display 2) to ensure the system correctly recognizes and drives the DSI display. These overlays load the necessary drivers and settings for the display to function properly.
In summary, while Raspberry Pi OS includes comprehensive configurations for desktop and display support by default, Volumio’s focus on audio playback means users may need to manually configure settings, especially when integrating DSI displays.
Kind Regards,
1 Like
Thanks for this explanation!
Ralf
1 Like
It’s me again, sorry…
Now for today I got a new challenge.
I’ve played around with my new touchscreen and - as mentioned - got it get work.
Today - because for some strange reason the (display-wise working) Volumio installation on an USB-SDD Drive do not execute a “sudo reboot” - I’ve switched back to the original installation on a SD-card.
In THIS installation I am not able to get the touch-funtionality working.
Have done the exact same modifications as in SDD-installation:
/boot/userconfig.txt
added:
[all]
display_auto_detect=1
#display 7Zoll
dtoverlay=vc4-kms-v3d-pi4,nohdmi
dtoverlay=vc4-kms-dsi-ili9881-7inch
/boot/cmdline.txt
added:
video=DSI-1:720x1280M@60
What I’missing to enable touch?
THANKS!
Ralf
annotation: the whole thingi seems to be kind of “sensitive” …
a fast switching from SD card to USB SDD results in a “greyish” screen …
Switching off, waiting and than switching on - works …
Hey @rkorell,
I don’t think that the Touch Screen 2 or overlays are problem here.
Since you are using Raspberry Pi 4B - this is the USB boot problem you are facing.
Kind Regards,
A post was merged into an existing topic: [Guide] Prepare Raspberry Pi for boot from USB/NVMe