Thanks for the reply, but it turns out there was no root password. Sudo passwd root took care of it.

Hmm...not so fast. I just tried to do an update using sudo and got this-

sudo apt-get update && apt-get upgrade
Hit:1 archive.raspberrypi.org/debian buster InRelease
Get:2 raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]      
Hit:4 www.astroberry.io/repo buster InRelease                          
Hit:3 vega.ap-i.net/apt unstable InRelease
Fetched 15.0 kB in 3s (5,002 B/s)
Reading package lists... Done
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?

I am rusty.

Run two separate commands. Mine does not like using the && either.

I did use two commands and it got a lot further/did much more, but it still failed (too many errors).

Unfortunately, it appears my Pi has locked up.

Hard reboot (power cycle) but it doesn't come up. I get a solid red LED, and the green LED flashes 4 times.

I think my installation is fubar. Argh...

Do you have a console for your rpi? It might be stuck with a fsck prompt from a corrupted shutdown (y/n)

Is there a beta/test version of astroberry that needs testing? I searched around but didn't find mention of it..

Hello,


Mine has been doing this same behavior. I use a 7” monitor to view the console, ring 0. Usually, I have to include a keyboard and mouse. I have to supply a password.

I connected to a keyboard and monitor, but it was just a black screen.

I have since installed Astroberry 2.0.3 and it came up fine. Seems a few configuration bugs have been worked out, too, as I didn't have to jump through hoops to get my gps (UART) working, and configuring connection to my wifi was much simpler than previously. 

So, it *seems* like I am in pretty good shape for Kstars 3.5.3 when it comes out. Actually glad this crash happened now rather than later.

The way the HDMI works on the Pi is that if it is already booted up and you then connect a monitor then you just see a blank screen.
I have found it necessary to have the screen connected and powered up, and then turn on the Pi - you should see something on the screen even before it finds the boot image.

I had the tv power up ready to go. The Pi blinked momentarily like it was going to do something, then I kept getting 4 blinks on the green LED.

Fortunately, it was not a big deal to install the latest version.

Four blinks of the green led indicates the system can not find (maybe corrupted) some starting files (.elf)
Few days ago, after an upgrade I got seven blinks when rebooting. This indicates the system can not find the kernel.
i had to burn again the stellarmate image. There are methods to recover the system without losing your files but I found them a bit complicated. In my case, I mounted the sd card on another raspberry and copied the important files before burning the image.

Check this thread for compiling it yoursef: www.indilib.org/forum/general/9748-build...-from-git.html#71737

I am a bit frustrated at the moment. I thought I read where KStars 3.5.2 was part of Astroberry, so I expected it to be there with the latest Astroberry install I did. It was not. Thinking maybe I needed to update/upgrade, I the the sudo apt update and that went fine. I then did sudo apt upgrade, and that pretty much wiped my sdcard back to 4 green blinks and almost nothing on the sdcard. Having to start all over again. 

For now, I'll look on the bright side and say I needed the experience anyway.

I updated my Astroberry (Sudo apt-get update && sudo apt-get upgrade) and I now have KStars 3.5.2
I was hoping for KStars 3.5.3