Just change sda1 to mmcblk0p1 (and sda2 to mmcblk0p2 respectively) and you will be fine
This is right. It is related how SSH handles authenticity of a destination host - each system has its unique keys generated at the first boot. If you access these systems by the same hostname you will get a warning from SSH. You can either remove key association as stated in SSH message each time or setup unique names for these systems, so to avoid conflict (same name, different keys).
That's was I suspected. Browser was caching some parts of the user interface. I'm glad it works for you.
By the way... Isn't Atik Air answet to your question related to ATIK Infinity? www.atik-cameras.com/atik-air-software/
Thanks for directions. If you cannot avoid hard shutdown due to random power losses it is the way to go
Similar approach is already enabled for root file system of Astroberry Server (see /boot/cmdline.txt), but it might be good idea to enable it for /boot partition too.
You won't be able to do anything with vfat partition. It is the only one supported by raspberry boot loader. I would rather focus on determining a root case for reboots. Unreliable PSU?
The version will probably refresh after reboot or you need to do dist-upgrade.
I don't know about ATIK Infinity, but INDI drivers use official ATIK libraries so it should be supported. Have you tried it yet?
Today, I have decided to run Astroberry Server Live Sessions. I will be presenting system features during this sessions and stream real astrophotography sessions.
The recording of the first session is already available on YouTube. Stay tuned for next ones.
Domer wrote: I just don't know how to build a new Astroberry image with the v2.9 supplicant. It's odd that the folks who manage Astroberry haven't done this already. Samsung devices are very popular and the Wi-Fi hotspot needs to work with those devices.
Official Raspbian Buster system from Raspberry Foundation (see www.raspberrypi.org/downloads/raspbian/ ) provides wpa_supplicant version 2.7. This means that the issue impacts all Raspberry Pi users who use official system, not just Astroberry users.
Astroberry is built on top of Raspbian Buster so we are impacted as well. The only solution is to manually upgrade version of wpa_supplicant to the latest 2.9.
However version 2.9 is marked unstable/experimental so it is not available in stable repositories yet. It must be compiled from sources located on the official site w1.fi/releases/wpa_supplicant-2.9.tar.gz
This will take some time wpa_supplicant is promoted to stable. As soon as it is you will receive it with regular updates and the issue will be solved for you and all the other users.
In the meantime, can anybody compile and package version 2.9 from the sources?
@patdut - This is well discussed in the forum. See this post
@Tardieu - This is not a bug and it has nothing to do with QHY. These are warnings related to SBIG libraries. You can ignore them
What driver are you using?
This is great idea!
Oh, La Serena! I visited the place last year for Solar Eclipse. Great place and the sky is just unbelievable! Not mentioning Elqui Valley!
Great move from Spain to Chile!
BTW. Isn't it the case that CEM25 can be controlled directly from a PC? Instead via hand controller? Why don't you try it.
Birthdate08. 05. 1974
About meAstronomy geek. Keen on electronics, new technologies, IoT. Cybersecurity professional. Full time CEO. Conference speaker and post-graduate teacher.
Astroberry Server core developer. Member of INDI development team.