I just received my Raspberry Pi4 yesterday and I've been inspired to duplicate and modify my AstroPi3 setup script to work for Raspbian so I don't have to wait for Wimpress to finish ubuntu mate. I worked some yesterday and some today. It should not be too much longer before I'm done assuming I don't have any serious issues. Maybe a day or two.

Thanks,

Rob

Hi Rob,
I have a full working set up on the rpi4 but it was a long winded job to get to this stage, had issues with creating the hotspot and also with phd2, but all good now, bit will look forward to seeing and maybe trying your script..
What is included in this script...
William

You can take a look at it here: github.com/rlancaste/AstroPi3

My new script for Raspbian is going to be: setupAstroRasbianPi.sh

I'm still working on adapting it. But so far it has: PHD2, INDI, KStars, INDIWebManagerApp, INDI Web Manager, GSC, Conky, samba (file sharing), Real VNC, astrometry, xplanet, and ZRam. It configures a number of settings to be better set up for astrophotography.

It is NOT done yet, but it does work. The biggest thing I still need to work on is Networking. In my ubuntu version of the script, I have it set up for DHCP with ethernet and standard wireless, a direct ethernet connection as a backup with a fixed IP, and if desired, you can click an icon to start an ad-hoc network in the field. But, what I did for ubuntu did NOT work for Raspbian. I need to change all that.

Here is what it looks like now:

Thank you for this. My Flirc case comes soon and my (RMA) Pegasus UPBv2 comes in a day or so and I'm hoping my first all Indi setup will be ready by mid August with the PPBv2 drivers hopefully being in the next update.

If it helps anyone, I built a Mate system based on Ubuntu 18.04 server. To make it bootable, the firmware is replaced from raspbian.
Here is the script (actually it is makefile) , which builds the system:
github.com/avarakin/astropi
Nice thing about it is that it is using official Kstars and other repositories so there is no need to build anything from source.

Alex

I got the wireless up and running with a hotspot with static ip for out in the field, on wlan1 (USB WiFi dongle) WiFi for internet on wlan0 on the internal WiFi ...but that will not work on static ip only dhcp....not sure why..
The networking stuff is very awkward on this raspbian I must say...

Also one more thing to add is that the 4K resolution WILL NOT work over any VNC only full HD max, which was useless to me as have 4K monitor, so had to use XRDP with Remote Desktop on either windows or Remmina Remote Desktop on a Linus laptop.. so worth considering as the 4K is very useful. For many people...

So have you got this fully working with Ubuntu and rpi4 before I spend the time trying it out ..?

I never tried running it with real equipment but Ekos with simulator works.
Internal Wifi adapter, wireless mouse and keyboard do not work but I read that it can be fixed by installing modules from Raspbian.
The setup was done half headless: with ssh over Ethernet + display over HDMI.
I think that this method is the best available right now - it removes the dependency on Ubuntu Mate which was very slow to adopt 18.04.
Also hopefully Ubuntu guys will build a proper image for Pi 4 soon so no hacking with firmware would be required.

Alex

Please forgive my ignorance, but as this is Ubuntu Mate server, does that mean that it does not have the Ubuntu mate desktop gui..?? As I would need that...

The original Ubuntu server does not have Mate desktop but my script installs it, as well as X Windows and LightDM desktop manager.
It also uninstalls some server software which is not needed.
I intentionally did not install office stuff as it is very heavy and not needed for imaging.

When the official image forUbuntu-mate on Raspberry Pi 4 comes out, I will probably go back to using that, since my original script should work just fine for that and I like ubuntu mate better. But I thought it would be good to take this opportunity to make a new script so that those who wish to use Raspbian can have a script that gets them up and running just as well as somebody using ubuntu mate. Plus this gives me a chance to start using and playing with the pi until that time.

Do you really want to use 4K resolution Remote Desktop control over ethernet/wifi to control your Raspberry Pi? I would think that would take more CPU cycles, more RAM, more power, and more traffic over the network. What is gained by using remote control with 4K resolution vs. just HD resolution? Is it just more screen space or something else?