knro wrote: It's new image.. there are no packages since Ubuntu does not work officially yet on rpi4.
Ubuntu recently introduced official support for Rpi4. Here is the process for building a system based on Ubuntu 19.10:
Please feel free to use any portions of it.
There seems to be an issue with some INDI drivers for 19.10 missing on PPA server.
El Corazon wrote: Got it!
I used the same server image and just built up the system from there by adding Gnome and MATE desktop environment and other components I wanted.
Crashes may be dependent upon the peripherals that are connected. With my Nikon D3300, I would get these random crashes. When I use my ASI1600MC-Pro instead, so far it looks a lot more stable.
There are still a few idiosyncracies, though: For instance, I cannot Polar align if I choose the mount to go towards the East. Then everything crashes at the solver stage. I need to restart and slew to the West ONLY. Then there is no crash and the solve completes fine.
That could also be mount specific, though, have only tested on iOptron SmartEQPro+ so far.
Anyway, why are you trying to use Ubuntu 19, if 18 gives you full RAM and USB functionality?
Just for reference - my equipment is ZWO 174 guider, SBIG ST8300 CCD, OnStep mount.
Never had problems with polar alignment, although I dont use it much given that I use permanent setup most of the time.
I don't like 18 because it is a big hack - Raspbian firmware transplanted into Ubuntu.
El Corazon wrote: The unexplained KStars crashes are a far bigger problem. This is NOT a KStars problem, though, since the same KStars versions work fine on my Zotac mini PC with the same version of Ubuntu MATE, so it must be Pi4 related.
I am running Kstars on Pi4, which is based on 18.04 and I did not have any crashes.
Here is the process I used for building my 18.04 system (see Pi4 section):
starhopper wrote: I had some trouble
1. the complete process stopps because sbig-indi (I need it) cannot be found? I commented it out.
2. chromium-browser installation lags several minutes. I commented it out.
After the installation process a nice pink fox was visible via VNC
It take long time until the built-in wireless adapter was visible in the system.
I did not use this script for real work yet, I only tested the build under the simulator.
Yes, there are some issues with indi drivers in the PPA, although there was no problem with sbig driver at the time when I was building my Pi4.
I guess 19.10 is not fully cooked yet.
I did not notice slowness with wifi, although I mostly connected to it using ethernet. How long does it take for you?
My Pi4 is 2GB version, I guess I was lucky that I did not go with 4GB version.
Here is my older script (see Pi4 section) which I used for building my current production system. Even though this build is very hacky, it is rock solid and I never had problems with it for couple of months:
The script is a little messy because it started with Mate 16.04, then moved to 18.04 and finally to Pi4, so I am not sure all is working there, but it is very simple so it should be easy to troubleshoot.
Feel free to try and let me know if you run into issues.
Pi4 is now officially supported by Ubuntu, although it does not come with UI.
I developed a script which installs all imaging software I use plus KDE by default or mate as on option.
The script and instructions are available here:
Thank you Han!
My 20 minutes image was not a sync image, it was an image from my previous session, which I used for setting the go to target.
I will try additional command and see how it goes.
It works great with 2GB. Try ASTAP - it works very fast.
I run everything on PI and connect to it via VNC.
I think it is more reliable - no chance that network glitch or your client deciding to go to sleep or just crash to interrupt your session.
It used to be a challenge to run everything on Pi due to low memory, but with Pi 4 all is running very smoothly on 2GB version.
With VNC approach, I can start a session from a PC and then monitor it from phone or tablet.
I noticed that if I connect to external guider, while exposure is running, the exposure gets stuck and the countdown timer stops.
I am seeing this with 2 week old build from bleeding PPA.
Not a big deal, as long as you remember about this.
It solves super fast for me too!
Agreed, great work by Jasem and Hans!
I ran into an issue with resolving a Ha image with 20 minutes exposure, which had a lot of stars - ASTAP was not able to solve.
It worked when I ran the solver from command line and added -s 30 parameter. I believe it reduces number of stars to be used for plate solving.
Do you think we should include configuration for -s value in Kstars?
I pulled the latest build from nightly PPA and the issue seems to be fixed.
Thank you for your help!