Ok, I used the overlay drivers from: swkim01/waveshare-dtoverlays: WaveShare SpotPear 3.2" and 3.5/4.0" TFT LCD overlays for the Raspberry PI and PI 2 (github.com)
And changed my config.txt to
dtoverlay=waveshare32b:rotate=90,swapxy=1,invertx=1
And now everything works as before…
So I think that the drivers provided in the image are broken?
How can I change the setting in the Web interface?
It seems that some recent kernel update have broken the drivers included with the zynthian image, They are not mainstream drivers. I will update the drivers and config in the zynthian image.
Thanks for the patch!
You could open an issue with the solution in the issue tracker:
It’s best practice for having traceability of changes.
Thanks again!
I’ve the modifications ready to commit. Awaiting for the ticket ID.
Thanks!
Pushed!! Update and test, please.
So, I probably did something stupid and changed the repo for the webui to testing and now I am locked out from the web-UI. The page refuses to connect (ERR_CONNECTION_REFUSED).
Can I fix this?
journalctl -u zynthian-webconf gives me:
Mar 17 00:56:48 zynthian systemd[1]: zynthian-webconf.service: Service RestartSec=5s expired, scheduling restart.
Mar 17 00:56:48 zynthian systemd[1]: zynthian-webconf.service: Scheduled restart job, restart counter is at 318.
Mar 17 00:56:48 zynthian systemd[1]: Stopped Zynthian Webconf.
Mar 17 00:56:48 zynthian systemd[1]: Started Zynthian Webconf.
Mar 17 00:56:49 zynthian zynthian_webconf.sh[7421]: ----------------------------------------------
Mar 17 00:56:49 zynthian zynthian_webconf.sh[7421]: Linux Version: buster
Mar 17 00:56:49 zynthian zynthian_webconf.sh[7421]: Kernel Version: 5.15.70-v7l+
Mar 17 00:56:49 zynthian zynthian_webconf.sh[7421]: ZynthianOS Version: 2211
Mar 17 00:56:49 zynthian zynthian_webconf.sh[7421]: Virtualization: none
Mar 17 00:56:49 zynthian zynthian_webconf.sh[7421]: Hardware Architecture: armv7l
Mar 17 00:56:49 zynthian zynthian_webconf.sh[7421]: Hardware Model: Raspberry Pi 4 Model B Rev 1.1
Mar 17 00:56:49 zynthian zynthian_webconf.sh[7421]: ----------------------------------------------
Mar 17 00:56:49 zynthian zynthian_webconf.sh[7421]: INFO:zynthian_gui_config.: ZYNTHIAN-UI CONFIG …
Mar 17 00:56:49 zynthian zynthian_webconf.sh[7421]: INFO:zynthian_gui_config.: Wiring Layout MCP23017_ENCODERS
Mar 17 00:56:51 zynthian zynthian_webconf.sh[7421]: INFO:audio_config_handler.: RBPi Device Name: ‘Headphones’
Mar 17 00:56:51 zynthian zynthian_webconf.sh[7421]: Traceback (most recent call last):
Mar 17 00:56:51 zynthian zynthian_webconf.sh[7421]: File “./zynthian_webconf.py”, line 47, in
Mar 17 00:56:51 zynthian zynthian_webconf.sh[7421]: from lib.kit_config_handler import KitConfigHandler
Mar 17 00:56:51 zynthian zynthian_webconf.sh[7421]: File “/home/pi/zynthian-webconf/lib/kit_config_handler.py”, line 35, in
Mar 17 00:56:51 zynthian zynthian_webconf.sh[7421]: from lib.wiring_config_handler import WiringConfigHandler
Mar 17 00:56:51 zynthian zynthian_webconf.sh[7421]: File “/home/pi/zynthian-webconf/lib/wiring_config_handler.py”, line 36, in
Mar 17 00:56:51 zynthian zynthian_webconf.sh[7421]: from zyngui.zynthian_gui import zynthian_gui
Mar 17 00:56:51 zynthian zynthian_webconf.sh[7421]: ModuleNotFoundError: No module named ‘zyngui.zynthian_gui’
Mar 17 00:56:51 zynthian systemd[1]: zynthian-webconf.service: Main process exited, code=exited, status=1/FAILURE
Mar 17 00:56:51 zynthian systemd[1]: zynthian-webconf.service: Failed with result ‘exit-code’.
Ok, after a git commit and git pull in the zynthiun-ui folder I got the webconf up and running again.
Setting the display works like it should, thanks!
But, each time I set the display it changes also my 99-calibration.conf in the xorg.con.d folder and my touchscreen calibrations is off and I have to enter the right TransformationMatrix. Is it posible to at least comment current values, so the user can reverse more easily?
Thanks for this update and cheers again as always!
Kees
Have you tried the touch calibration in the admin menu?
Yes, but that does not work in my instance (axis are swapped). Perhaps because I have my screen at 90° rotation.
Did you try? I remember some work to handle reversed axis.
It should be solved now.
Regards,
And it is!