Jasper Seidel

Interesting, the main CPU does seem to be identical, but perhaps they had to update the Wifi chip. I'll build an image with the latest firmware later tonight.

@dvandijk Can you try this new version? https://github.com/jawsper/motioneyeos/releases/tag/20220119-dev I updated rpi-firmware (not sure if needed) and rpi-wifi-firmware (this may fix your issue).

(I'm not near my Pi so this image is not tested by me)

I had this same issue, I solved it by uninstalling and installing `sslpsk`.

While digging around I found the method `call_with_unix_fd_list_sync`, which seems to be the right function for this job. Documentation: http://lazka.github.io/pgi-docs/#Gio-2.0/classes/DBusConnection.html#Gio.DBusConnection.call_with_unix_fd_list_sync Example usage: https://git.centos.org/blob/rpms!gnome-tweak-tool/aaa06e94d4f5ac34090c5b33a91b8ab2dfdcd74f/SOURCES!0001-Add-a-tweak-to-ignore-systemd-s-default-lid-switch-a.patch#L98 I've made a nasty hack to test...

I did some more checks, and it appears it doesn't matter if you call `call_sync` or `call_with_unix_fd_list_sync`, since they both call `g_dbus_connection_call_sync_internal` anyway. (https://git.gnome.org/browse/glib/tree/gio/gdbusconnection.c?h=2.50.0#n6162 vs https://git.gnome.org/browse/glib/tree/gio/gdbusconnection.c?h=2.50.0#n6281) The question now is...

Isn't it the same to use `1

Hi @MStcz, can you check if there's a file called `bcm2710-rpi-zero-2.dtb` in your boot partition? (the same as where you put the `wpa_supplicant.conf`)

Hmm that matches the one I have. Have you tried running the official Raspberry Pi OS on this specific Pi, to rule out a hardware issue?

Ah that is very interesting! Seems there could be a new chip revision, possibly requires another rpi-firmware update.