There seems to be an issue with your latest OS 1.4 Jasem. When starting up, it stops stating there's an error: Driver 'sdhost-bcm2835' is already registered, aborting…
Then you can only enter commands at the built in BusyBox Shell command prompt: (initramfs)

Keld,

Are you sure? I just checked and it's fine. The sdhost-bcm2835 message can be safely ignored. Maybe try to check the SD card and burn the image again? Did you verify the md5sums?

I'm 99,8% sure, it starts up, shows the four raspberries plus driver error, then the Stellarmate galaxy then it stops with the error message only leaving me with an option to type help at the BusyBox command prompt.
I've burnt the image twice, same result.
The MD5Sum does not match, mine says bd8e0112c0586c69e210540844f44227, you have listed 572a6efa3586d1236b5f2c86516d92c8 on Stellarmate.com (have you updated it with the new MD5sum?).
I noticed that the SD card has three partitions, boot partition (199MB), primary (5,32GB) and not allocated (8,98GB), that's different from the latest versions where all available space is allocated.

this md5sum for the .xz file correct? I just updated them, sha256 is 692ad689b0b0869a13481dcd47fdb585094cea188e023b594dc5f5704ec46b4b

I just updated to the 2nd ? version of 1.4 and as before it automatically provided a stellarmate wi-fi hotspot, which let me add my local wi-fi SSID. I had no command line startup issues, but I wasn't watching via HDMI and a keyboard/mouse, rather I just connected via Screen Sharing. The DNS entry in the network control panel was empty, and I was able to add a new one which worked. However, after a reboot, the DNS list is empty again, so I had to renter the DNS again.

EDIT: I added a DNS entry to my wi-fi Network Connection entry for my router's wi-fi and this solved the connectivity, and is persistent.

It was actually the md5sum for the *.img file, the md5sum for my downloaded .xz file is identical to the one you've specified, a55816718d49bf272f6836b3211be4a5.

This is what I get when I do <strong>fdisk -l</strong>:

That's so strange Jasem, I have always used Win32DiskImager for burning SD Cards, never had any issues.
I tried Etcher (you link to it) and i Works, the SD card now has two partitions as usual, one 199MB boot partition and one 14,24GB primary partition.
Why it Works, I have no idea but something must go wrong burning 1.4.0 to the SD card using Win32DiskImager.

Edit: It's still a problem, just put the SD card back in the RPi, same problem Again. I noticed the green LED was lit way longer when Stellarmate started as it should, now it just blinks a couple of times.

2nd. Edit: I can see BusyBox is a Tool used to handle Wireless access points, any idea how I can close the BusyBox Shell command prompt?

Alright, thanks for the heads up. Internet access is OK now?

I too have had the issue recently where WinDisc imager would only create one partion and so would not work, yet I have used it loads of times before, I now have to use etcher... not sure on the reason thought..

Hello,
Is there a way to transfer INDI/Ekos configs/settings from an older Stellarmate to a fresh install?
Save
/home/stellarmate/.indi and
/home/stellarmate/.local/share/kstars
and transfer to the new install?
Will that work?
Thanks!

Use StellarMate Tools application on the desktop to do backup/restore.

You can also save the directories you indicated above and restore them on the new machine. These are the most important ones.