Is it intended that the WIFI enabled checkbox doesn’t survive a reboot anymore.
And furthermore I found it annoying that wifi is shutdown when the zynthian service is being stopped.
So now I need ethernet connectivity if I debug the system?
No, it’s a issue 
I will solve It asap
2 Likes
I can’t talk to the box to tell it its wrong … 
When zynthian service is stopped, some entity, probably a trojan from Korg or Yamaha, is shutting down the wifi network:
Nov 12 15:19:54 zynthian systemd[1]: Stopping Zynthian User Interface...
Nov 12 15:19:57 zynthian startx[6581]: Zyncoder: Zynaptik CV-IN poll thread created successfully
Nov 12 15:19:57 zynthian startx[6581]: zynseq: Jack samplerate: 44100
Nov 12 15:19:57 zynthian startx[6581]: zynseq: Jack buffer size: 256
Nov 12 15:19:58 zynthian startx[6581]: zynseq exit
Nov 12 15:19:58 zynthian startx[6581]: xinit: connection to X server lost
Nov 12 15:19:58 zynthian startx[6581]: [1B blob data]
Nov 12 15:19:58 zynthian kernel: fb_ili9486 spi0.0: fbtft_backlight_update_status: polarity=1, power=1, fb_blank=0
Nov 12 15:19:58 zynthian startx[6581]: waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
Nov 12 15:20:00 zynthian dhcpcd[822]: wlan0: carrier lost
Nov 12 15:20:00 zynthian dhcpcd[822]: wlan0: deleting address fe80::4888:627:a869:662e
Nov 12 15:20:00 zynthian avahi-daemon[397]: Withdrawing address record for fe80::4888:627:a869:662e on wlan0.
Nov 12 15:20:00 zynthian avahi-daemon[397]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::4888:627:a869:662e.
Nov 12 15:20:00 zynthian avahi-daemon[397]: Interface wlan0.IPv6 no longer relevant for mDNS.
Nov 12 15:20:00 zynthian avahi-daemon[397]: Withdrawing address record for 192.168.43.5 on wlan0.
Nov 12 15:20:00 zynthian avahi-daemon[397]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.43.5.
Nov 12 15:20:00 zynthian avahi-daemon[397]: Interface wlan0.IPv4 no longer relevant for mDNS.
Nov 12 15:20:00 zynthian dhcpcd[822]: wlan0: deleting route to 192.168.43.0/24
Nov 12 15:20:00 zynthian dhcpcd[822]: wlan0: deleting default route via 192.168.43.1
Nov 12 15:20:00 zynthian systemd[1]: zynthian.service: Succeeded.
Nov 12 15:20:00 zynthian systemd[1]: Stopped Zynthian User Interface.
This is happening always you turned on/off the wifi from the UI, but not if the wifi was enabled on startup and you didn’t use the UI for enabling/disabling. Really curious!!
As you can see, wifi is disabled just after X11 ends and before the service is terminated, so it seems to be related with systemd. I analyzed the systemd service files, looking for wrong dependencies, etc. Nothing! ;-(
Any help would be really welcome because i’m totally lost.
Thanks!
maybe there is a new option when we start WIFI over UI, that is telling him to start “unattached” to this service?
And they changed the default behavior recently?
Interesting stuff…
I am also not able to switch my wifi on.
Yes, I did configure the local wifi network and it is there.
Then I go to Wifi/on and I get the error message - connection not possible.
I really don’t need wifi on the zynthian. If I run an update or need the config, I use the LAN cable, but I am curious if you solve this wifi issue.
Who knows… maybe this is related to my audio-dropouts?!
If you mention a trojan… anything is possible.
