AradoSKYindi wrote: Hello,

I just updated using

Use: sudo apt-get update && apt-get upgrade.

I then connected everything up and opened KSTARS with EKOS. I started my profile and everything works. I used the USB 2.0 ports. My two RSHTECH 3.0 hubs worked well. Cameras worked. Now, the next clear night is next week.

What version of Kstars have you got after the apt-get upgrade ?

This whole thread is about the latest version not being n the astroberry repository.


Avocette wrote:

xsnrg wrote: @wornish, yes I see it was others having problems with ports and devices after the apt upgrade, not yourself. If the kstars packages had not been updated yet, it would be the OS changes, not the kstars package, that introduced differences. A bit of leapfrog going on between the OS and kstars. Your recompile seems to make everything work well together again, so hopefully when the new packages are released, they will also work well with the latest OS updates.

The USB problems are still present in the very latest OS upgrade I carried out today, and upgrading to KStars 3.5.0 has no significant effect on this. So whereas the fallback of a clean installation of the Astroberry 2.0.2 image ported to an SSD works well, and lists 14 USB devices under lsusb, the latest RPi OS with KStars 3.5.0 doesn't list any of the USB2.0 devices connected to the USB3.0 powered hub, nor via the USB2.0 hub built into the ASI533MC camera.

I just tried mine again running KStars 3.5 all my USB connections are working fine. EKOS connects to all my gear with no errors.

It is very strange that all is well with the earlier version of Kstars. I did a completely fresh install of RPi OS and then the latest Astroberry before doing the compile for Kstars. Its a pain having to redo all the settings but it was worth it.
I would have thought if it was an Astroberry or a Kstars issue this forum would be full of people raising concerns.


xsnrg wrote:

wornish wrote: In the end, I decided to compile from source code. Once I got the dependencies sorted it all compiled well, it took a little time. Now I have the latest bleeding-edge 3.5 release !!
So problem solved.

Congrats on compiling, and glad it works for you. It seems that if compiling it yourself did not show the same problems as you had before, then there are problems with the packages made available in the repo that need to be addressed.

The only issue is that the astroberry repo has not been updated with the latest kstars release which only came out last week. Some of us are eager to try the new features hence taking the step to compile from source.


Well here goes these are the steps that worked for me. Hope this helps but I have to say that you follow them at your own risk.
I am certainly Linux no expert and I am using a RPi4 running the latest version of RPi OS.
All the commands following are typed in a terminal window after the $ prompt. I have shown them in large font

I am not sure if git is installed as standard but make sure you have it by typing

Sudo apt update
Sudo apt install git

To verify enter the command
git --version

Since RPi OS is a version of Debian I followed the steps on the link below for Debian.
If you copy and paste this into your browser it will give more info.

The first thing is to make sure you have all the prerequisites and dependencies.
So open Terminal and type the following command, probably easiest to copy and paste it using the right mouse button. This is all one line it is just wrapping in the viewer.

sudo apt-get -y install build-essential cmake git libeigen3-dev libcfitsio-dev zlib1g-dev libindi-dev extra-cmake-modules libkf5plotting-dev libqt5svg5-dev libkf5xmlgui-dev kio-dev kinit-dev libkf5newstuff-dev kdoctools-dev libkf5notifications-dev qtdeclarative5-dev libkf5crash-dev gettext libnova-dev libgsl-dev libraw-dev libkf5notifyconfig-dev wcslib-dev libqt5websockets5-dev xplanet xplanet-images qt5keychain-dev libsecret-1-dev breeze-icon-theme

You will be asked for your password which in my case was the default

It might ask you to confirm some things as it runs just type Y if prompted.

When it's done you will be returned to the Terminal prompt $

Create and change into a KDE development directory:
mkdir ~/kde && cd ~/kde

Fetch the KStars source code: this site converts links to green characters so make sure that you copy and paste the following line:
git clone

Create and change into a build directory for compilation:
mkdir build && cd build

The next steps will take some time so get a coffee

Run the configure process with cmake:
cmake ../kstars -DCMAKE_INSTALL_PREFIX=/usr

Compile KStars:

Install KStars:

sudo make install

Thats it.

To get updates in future its very easy
cd ~/kde/kstars
Git pull —rebase

Good luck


In the end, I decided to compile from source code. Once I got the dependencies sorted it all compiled well Took a little time. Now I have the latest bleeding-edge 3.5 release !!
So problem solved.


Same here. I thought it was just me.


KStars has just released a new update to 3.4.3. How do I update it on my Raspberry Pi 4 running Astroberry on Raspbian Buster.
The apt-get update and apt-get upgrade commands don't update Kstars.

Can anyone help?


Thanks fpr sharing this


David Thompson replied to the topic 'Mesu Mount 200 Driver Request' in the forum. 1 year ago

No, I think you have misunderstood my post.

I would really like to have an Indi driver on my RPi4. As far as I know, none exists. Just trying to log the request for Sitech to produce one.


David Thompson replied to the topic 'Mesu Mount 200 Driver Request' in the forum. 1 year ago

I am very tempted to get the recently released MesuE200 mount but don't want to have to use a windows machine for the Sitech drivers.
I am a very satisfied INDI user with Kstars on a RaspberryPi4 which works great with my skywatcher AZ-EQ6GT mount.
Having an Indi driver for the MESU would be a big plus in helping me take the plunge.