It is a rev 2. I would post a picture but it is going be awkward to remove. would be last resort
Not necessary if you already know the revision.
Please execute
sudo curl -L https://github.com/waveshare/LCD-show/raw/master/waveshare35b-v2-overlay.dtb -o /boot/overlays/waveshare35b-v2.dtbo
and in “/boot/userconfig.txt” change
dtoverlay=waveshare35b
to
dtoverlay=waveshare35b-v2
Then reboot.
1 Like
That has worked, its just the touch thats not working now 
Also the pi seems to now be crashing. Unresponsive and after so long black screen.
Has anyone else experienced their pi unresponsive after installing one of these displays?
So, from messing about with it. if I toggle the touch display in volumio the display comes back on temporarily then goes off again.
Is this possibly the screensaver? Does the display stay on with “Screensaver Timeout” set to 0?
I have set it to 0 already for the screensaver.
Seems to be random issues.
Im going to try diagnose and let you know.
So far ive had internal server error on the web ui when trying to play web radio.
Same scenario ive had the web radio play then do the following on the video below.
Ive removed the ssd and the same happens
Ive removed the dac and the same happens
Device is powered by a 45w usb c charger.
I have also tested volumio without installing the display drivers and it runs flawlessly.
Update, enabling the gpu memory settings worked for a bit longer but hanged and got this message when touching the screen
Unfortunately the update from 3.757 to 3.779 hasn’t worked for me. The display stopped working. Uninstalling and reinstalling the plugin stopped with an libraspberrypi0 error in chromium-codecs-ffmpeg-extras.
After a complete reinstall the plugin is installing fine but the display keeps black. Volumio itself is working via the netinterface.
My hardware is a RPi3 and the original Raspberry touch display (1?).
Now I am not sure where to continue to fix it.
A technical notes on releases from v 3.779 onwards
Volumio-OS for the Raspberry Pi SBC family embraced latest upstream kernel. As such, benefits from a complete i2c clocks overhaul, vc4 and DKMS re-design. Without going into the technical details, this has a long lasting impact, where part of it is simplified framebuffer → video chain. For most of the scenarios there is no need to change anything in:
/boot/cmdline.txt
/boot/config.txt
/boot/volumioconfig.txt
Changes should only be only carried in:
/boot/userconfig.txt
The first step will be to ensure that userconfig.txt contains only:
[all]
display_auto_detect=1
Only when, if there is no reaction from SPI/DSI/HDMI attached displays explicit overlays should be used (force rotation, some out of this world screen chipset overlay, etc).
Kind Regards,
Thanks for the information from the forum! every thing works fine! I have solved most of the problems except the touch function.
The touch function only works if I plug in the power cord form the display after raspberry starts.
I have Raspberry 4B 4GB and this 14.5" Visidisplay 2560x720 exactly the same as the user RUE
I’m good at Windows and networking and just a little bit at Linux.
So i need helb in this case.
Thanks!!
- Version of Volumio: 3.779
- Kernel: 6.6.56-v7l+
You refer to someone else having the same screen, but yet open a new topic??? For sure I can’t remember all topics, so no clue to what you’re referring to.
Please post a log when booting your rpi with everything connected.
Hi Weaten, thank you for the fast reply!!!
my LOG
http://logs.volumio.org/volumio/YTYsqlmeW.html
The topic was:
Hi Wheaten, I found the solution!!
I am not allowed to supply the display with additional power (as suggested in the manual) but rather directly from the Raspberry via the USB touch connection.
That’s it!
Please excuse the new toping and the associated work you had! 
but I rarely write in forums!
Kind regards and thank you!!!
1 Like
no problem.
Once you mention the reference topic I moved it to the correct topic.
Rue didn’t respond anymore and you provided the solution.
So thank you!!
thanks for the help.
meanwhile i observed it’s not an plugin error, it’s a kernel problem. the display keeps completely dark also at boot (no kernel messages).
reinstalling 3.757 with latest touch plugin is working smooth.
it seems that raspberry display (1st) support isn’t in the kernel or not working properly.
I am confused about the best way to turn the system off. I suppose switching off the mains power in the back after turning off in software is the easiest way to do it.
I have just edited the title of the thread to add my second question. How can I program the Raspberry to turn the LCD off after an arbitrary time, say one hour? Then how can I turn it back on? It has touch screen so it should be listening to a touch event. Or playing music might wake it up. Any suggestions? Thank you!
The touch display already has that feature build in.
Then when you start playing music it will become active again.
The best way:
- Shut down Volumio via the menu
- Next flip your power switch to Off
You can also opt for a hardware solutions, which will never shutdown the rPi but put it in a stand-by mode.