ls -al /dev/input
total 0
drwxr-xr-x 4 root root 240 Nov 5 14:31 .
drwxr-xr-x 16 root root 3720 Nov 5 14:31 …
drwxr-xr-x 2 root root 120 Nov 5 14:31 by-id
drwxr-xr-x 2 root root 140 Nov 5 14:31 by-path
crw-rw---- 1 root input 13, 64 Nov 5 14:31 event0
crw-rw---- 1 root input 13, 65 Nov 5 14:31 event1
crw-rw---- 1 root input 13, 66 Nov 5 14:31 event2
crw-rw---- 1 root input 13, 67 Nov 5 14:31 event3
crw-rw---- 1 root input 13, 68 Nov 5 14:31 event4
crw-rw---- 1 root input 13, 63 Nov 5 14:31 mice
crw-rw---- 1 root input 13, 32 Nov 5 14:31 mouse0
crw-rw---- 1 root input 13, 33 Nov 5 14:31 mouse1
[quote=“gvolt, post:69, topic:11265”]
ls -al /usr/share/X11/xorg.conf.d
/total 24
drwxr-xr-x 2 root root 4096 Nov 4 00:11 .
drwxr-xr-x 1 root root 4096 Nov 4 00:12 …
-rw-r–r-- 1 root root 1350 Nov 11 2016 10-quirks.conf
-rw-r–r-- 1 root root 788 Sep 30 2016 40-libinput.conf
-rw-r–r-- 1 root root 2747 Oct 28 2016 70-wacom.conf
-rw-r–r-- 1 root root 607 Dec 7 2016 99-fbturbo.conf
ls -al /etc/X11/xorg.conf.d
/total 12
drwxr-xr-x 2 root root 4096 Nov 5 14:32 .
drwxr-xr-x 1 root root 4096 Nov 4 00:18 …
-rw-r–r-- 1 root root 316 Nov 5 14:32 95-touch_display-plugin.conf
Looks normal.
Please execute
cat /dev/input/event*
and touch the screen. Do you see cryptic signs then in the terminal window?
You can exit the running “cat” command with Ctrl+c.
nothing happens
Hm, according to this in a thread that covers the same screen as yours nothing more should need to be adjusted than “/boot/userconfig.txt”.
BTW did you add the line break in “/boot/userconfig.txt” I mentioned above and reboot? If not, try that first. If touch still should not work maybe you need to install xserver-xorg-input-evdev
sudo apt-get install xserver-xorg-input-evdev
After that execute
sudo cp /usr/share/X11/xorg.conf.d/10-evdev.conf /usr/share/X11/xorg.conf.d/45-evdev.conf
and reboot.
gvolt, thanks. Touch is working fine now. My son is enjoying Volumio in his toolshed
Ben
1 Like
Have fun!yes i did
Touch still is not working I assume. (?)
Are you referring to the line break in “/boot/userconfig.txt” or installing "xserver-xorg-input-evdev”?
Do you have any other hardware connected that possibly uses the Raspberry’s pin 22 (GPIO25)? This might interfere with the touch panel which also uses this pin to detect / signal touches (penirq=25).
no not unless innomaker dac uses the pin 22.
Doesn’t seem like that.
Is your display an original Waveshare or a clone?
Hi I have a question: I got everything running, thanks to the many tips here. The longest task was the touch screen mirrored on the x axis which I corrected the
99-calibration.conf file:
Section “InputClass”
Identifier “calibration”
MatchProduct “ADS7846 Touchscreen”
Option “Calibration” “268 3880 227 3936”
Option “SwapAxes” “0”
Option “InvertX” “1”
Driver “evdev”
EndSection
The only problem I have and I do not find the config file. I would also like to control the “Browse library” by the touchscreen but I can’t. I can control everything through the browser but when I am in “Stand alone” mode, I would like also to be able to choose the music… How can I do this ???
Do I need to buy a bigger tft ?
Thanks and best regards
What config file do you mean? The files named “config.txt” and “userconfig.txt” both reside in “/boot”.
The local display should show the same UI like in a browser on another device. It could be that the mobile version of th UI is shown if you are using your touch screen in portait mode but you should be able to reach “Browse library” nonetheless.
If you should be using the “contemporary” UI theme you could try the “classic” theme which might fit a small screen better.
Hi. Thanks a lot for the quick answer. In fact it was by clicking the “classic” theme which resolved the issue.
With the contemporary theme I am not able to browse on the 3.5" tft…
Best regards
Christoph
Good it’s solved. 
I tried to follow this tutorial, but as soon as I do the LCD-Show for setup, the raspberry reboots and comes back with a kernel panic.
Is this just me or one of the latest updates?
Don’t use that script.
It modifies /boot/cmdline.txt and renders Volumio unbootable. It is possible to “repair” that but typically it is faster / easier to just start with a fresh Volumio system. Then don’t run LCD-Show but do the necessary steps manually. What is necessary depends on your screen.
What is the brand and exact model name of your screen?
I got mine from amazon and I guess I’ll debug in the kernel crash as I suspect that model isn’t what it pretends to be.
Maybe I misread your previous post: How far does the boot process go until it crashes?