I found the wifi issue. For some reason, a firmware update was triggered on the staging-2305’s first update. This shouldn’t had happened and it’s been solved now, but those who already did it, can solve the problem by running this command:
apt-get install --reinstall raspberrypi-bootloader raspberrypi-kernel
And then rebooting and updating again.
A new image is being built right now.
Regards,
A four days long week end is going to happen for me tomorrow evening, so, yeah I will dive into this new staging branch (also, it’s been a while now since I didn’t upgrade my Zynthian toys).
Now the wifi works perfectly… Thanks
Hi, because i like the rain, i’m in testing the release 
…
And i’m testing on the old V1 with much more than expected performance (and now resists over that second demo playback)
But as you know, the v1 has resistive touchscreen, i made calibration and works but doesn’t retain after a reboot. what i should save to mantain coordinates?
Calibration should be retained if you used the UI calibration tool from the admin menu. I will check here…
yes i used that. Anyway didn’t retain even on stable release.
Please post your webconf dashboard. I have checked and it is working here on my V4.
Please provide the result of ls -l /etc/X11/xorg.conf.d/99-calibration.conf and cat /etc/X11/xorg.conf.d/99-calibration.conf. Run from the command line, either ssh or using webconf terminal.
as soon as it will restart after a freeze during wifi issue repair 
Ok, this is the output after doing calibration from admin menu without restarting:
root@zynthian:/# ls -l /etc/X11/xorg.conf.d/99-calibration.conf
-rw-r--r-- 1 root root 236 May 17 15:26 /etc/X11/xorg.conf.d/99-calibration.conf
cat /etc/X11/xorg.conf.d/99-calibration.conf
Section "InputClass" # Created 2023-05-17 15:26:08.208523
Identifier "calibration"
MatchProduct "stmpe-ts"
Option "TransformationMatrix" "0.000000 -1.120000 1.024405 1.087379 0.000000 -0.027679 0.000000 0.000000 1.00000
[edit] , i tried to do a simple systemctl stop zynthian and relaunch zynthian.sh, doing again a cat, and calibration data reported is the same, but on screen calibration got lost again, means those coordinates aren’t the result of calibration…or i’m wrong? there some issue with r/w permissions?
The calibration is being saved to file and at my end the file is being used during the next startup, i.e. my screen remains calibrated. I see the product detected is “stmpe-ts”. I wonder if there is something odd with that. Please show me the extract from journalctl -uzynthian that starts X.Org X Server 1.20.4 for about 20 lines.
Hi, here is the output:
X.Org X Server 1.20.4
May 17 23:53:29 zynthian startx[502]: X Protocol Version 11, Revision 0
May 17 23:53:29 zynthian startx[502]: Build Operating System: Linux 5.4.0-109-generic armv8l Raspbian
May 17 23:53:29 zynthian startx[502]: Current Operating System: Linux zynthian 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37
May 17 23:53:29 zynthian startx[502]: Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_al
May 17 23:53:29 zynthian startx[502]: Build Date: 04 April 2023 07:50:56AM
May 17 23:53:29 zynthian startx[502]: xorg-server 2:1.20.4-1+rpt4+deb10u9 (https://www.debian.org/support)
May 17 23:53:29 zynthian startx[502]: Current version of pixman: 0.36.0
May 17 23:53:29 zynthian startx[502]: Before reporting problems, check http://wiki.x.org
May 17 23:53:29 zynthian startx[502]: to make sure that you have the latest version.
May 17 23:53:29 zynthian startx[502]: Markers: (--) probed, (**) from config file, (==) default setting,
May 17 23:53:29 zynthian startx[502]: (++) from command line, (!!) notice, (II) informational,
May 17 23:53:29 zynthian startx[502]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
May 17 23:53:29 zynthian startx[502]: (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 17 23:53:29 2023
May 17 23:53:29 zynthian startx[502]: (==) Using config directory: "/etc/X11/xorg.conf.d"
May 17 23:53:29 zynthian startx[502]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
May 17 23:53:31 zynthian startx[502]: ----------------------------------------------
May 17 23:53:31 zynthian startx[502]: Linux Version: buster
May 17 23:53:31 zynthian startx[502]: Kernel Version: 5.10.103-v7+
May 17 23:53:31 zynthian startx[502]: ZynthianOS Version: 2305
May 17 23:53:31 zynthian startx[502]: Virtualization: none
May 17 23:53:31 zynthian startx[502]: Hardware Architecture: armv7l
May 17 23:53:31 zynthian startx[502]: Hardware Model: Raspberry Pi 3 Model B Rev 1.2
meantime yesterday i tried to add elevated privileges to conf file, thinking about a read/write issue, but nothing changed.
Zynthian runs as root so permissions should not be an issue.
I don’t see anything obvious in the log except for your zynthian is not updated. It is running an old kernel 5.10.103-v7+. Mine (using the 2305 staging image and updated from UI) is using Linux zynthian1 6.1.28-v8+.
Anyway thanks, let’s say the lost calibration on this v1 is the minor issue…after i decided to solder ALL connections with fresh wires instead of dupont… and something got worse than before (obviously with pin collectors, not directly 
)Hi!
Just seen while updating the staging system via webconf:
The following signatures were invalid: EXPKEYSIG 97850188C442336A Jofemodo <fernando@zynthian.org>
Reading package lists...
W: GPG error: https://deb.zynthian.org/zynthian-testing buster InRelease: The following signatures were invalid: EXPKEYSIG 97850188C442336A Jofemodo <fernando@zynthian.org>
E: The repository 'https://deb.zynthian.org/zynthian-testing buster InRelease' is not signed.
Regards, Holger
With the latest update, the 2305 doesn’t start anymore… during the update, writings with ERROR and more passed on the display but too fast to understand…
P.S.
I take back what I said…it took a while but now it works perfectly. I’m sorry.
I dared to travel beyond the map.
Both did not work and I killed an SD card somehow with the 31mb partition issue.
2023-05-19-zynthianos-staging-2305.zip
2023-05-21-zynthianos-staging-2305.zip
Succeded using the last stable (2022-11-01-zynthianos-stable-2211.zip) on a different SD card but still from the same batch of 32gb Sandisk Ultra Micro SD cards. Before succeeding with the last stable, I tried and failed with the two staging releases mentioned above all on the same SD card.
Not really sure what to report or what stage the staging versions failed as it seem to build then try to reboot and then stopped at the normal Zyntian boot screen but did not progress to the normal menu. This is the web config of the successful 2022-11-01-zynthianos-stable-2211.zip build.
Hi @pac_71 !
The automatic build system builds an image every night and publish it in the “test” folder. This images has not been tested, so you can’t be sure they are good ones. Most of times, this “untested” image files works perfectly OK, but sometimes they are broken. The build system detects a number of errors and warnings, but in some cases, detection fails. The only way to be sure an image is good is by testing it in a real zynthian device. In fact they must be tested in several devices before going outside the “test” folder.
None of these images is the file i’ve linked in this thread:
https://os.zynthian.org/test/2023-05-17-zynthianos-staging-2305.zip
so they are not tested and unfortunately, they were broken.
Please, when testing images, stick to the links i send here. If you don’t, don’t blame me when untested images doesn’t work. If you really like to be in the cutting edge, then i would recommend to check the build status of an untested image before downloading. You can do it here:
https://jenkins.zynthian.org/job/ZynthianOS-UPDATE/
All the best!
It would be nice to upload the tested images in https://os.zynthian.org
