ok, so depending on how you look at this it's either good news or bad news...

I renamed xorg.conf so I could carry on configuring the device, but out of sheer curiosity I unplugged the HDMI rebooted and tried to connect via VNC and it worked.

I think I potentially know why though, and digging back into the memory banks I seemed to remember from using tightvnc to support racked servers that it launched its own desktop rather than the one seen at the vga port on the kvm in the server room.

From what I read here it seems that the xorg.conf is only needed if using x11vnc as it expects to ride on an open desktop, whereas tigervnc (or indeed any vnc server) will launch its own desktop:


The last post is the relevant one:"You want vncserver, not x11vnc. Vncserver will start a virtual desktop (headless xserver with desktop manager, not virtual machine).Here are some instructions:  www.digitalocean.com/community/tutorials...-vnc-on-ubuntu-18-04 "

Anyhow, all sorted, so now all I need to do is connect it to the scope, learn all of the necessary software, connect it to the relays controlling my roll-off roof,make a weather station to close the roof if it rains as its a remote-ish obsy, learn how to focus the scope and learn about astronomy.

So that's the next 10 years sorted...

Thanks for helping to wake my brain up Wolter, people like you are helping me keep sane in these very odd times.



Hi Wouter,

I have an odroid N2 that I'm sure I had working when I tried this last time, but this time I reboot and I can neither connect via VNC nor do I get a login, just a flashin underscore.

The only difference between this time and last time is that I am not 100% sure sure I was following this instruction, though it is very likely I was using the odroid one, and the N2 was using Ubuntu 18.04.

Any tips to resolvign beyond removing the xorg.conf file I created and buying an HDMI emulator dongle?

I can get in using Ctrl-Alt-F4, so can probably answer questions that can be got to from the cli, but I am very green with Linux so I'd probably need it spelled out if there is anything complex to do - the last time I was usign commands like ls and rm the century started with 19 and I was a lot slimmer...

All the best,



I am assuming some thing has changed in a build somewhere since I last updated, as I now find that KSTARS crashes if I load a profile with my ASI EFW in it.

At first I assumed it was something I had done as I have been finalising the installation of the hardware, but I couldn't think what and so a little trial and error led me to take components out of the profile until I got to the EFW, and as long as it is not in the profile all is well, but as it was working before updating recently, I'm thinking this might be the next point of investigation.

Can anyone offer any assistance or insight?

Here is the offending line form the log:

[2020-01-04T18:15:20.299 UTC INFO ][ org.kde.kstars.indi] - EQMod Mount : "[INFO] Device configuration saved. "
[2020-01-04T18:15:20.394 UTC INFO ][ org.kde.kstars.ekos] - "ASI EFW filter is online."
[2020-01-04T18:15:20.395 UTC WARN ][ default] - QObject::disconnect: Unexpected null parameter

Given I hadn't updated any parameters, I'm a bit foxed, but let me know what else you might need to help diagnose the issue...

Thanks in advance,



Ignore my pessimistic comment Chris, was simply being a grumpy old shite during a bit of a crappy weekend for variety of reasons but I'm now back to my usual optimistic self and hunting down a solution, so would really appreciate your input.

It does seem that Atik only have the 16IC being forces to use non-core USB1 drivers, but may call them in a bit to discuss.

I really want to stick with Linux as it is a much better solution for my needs, and so if I just need to replace the 16IC for a newer guidecam then so be it.

All the best,



It seems the 16 series cameras are supported by Atik, and are in the current Core download, but some further digging leaves me thinking that the 16 series cameras don't have INDI drivers, and as they are old tech I don't see anyone with the skills having the will do take on what sounds like a lot of work.

So that's the end of my Linux adventure unless I want to replace my two cameras, and given there are working Windows options I can't see why I'd do that until I can justify the cost of what is still a new hobby for me.

Unless someone has any other ideas?


Thanks Chris, appreciate the help here, I think this has most people stumped unfortunately, given the silence on this thread...


Ian Sullivan replied to the topic 'AstroPi3 Scripts revised' in the forum. 4 years ago

Not sure if I have a bug here Rob, but could do with a pointer or two if not.

Seems INDI/EKOS can't see my Atik cameras, yet they seem to have drivers in the right place, but then I am only just beginning my Linux Learning...

Posted EKOS output here after searching for asolution on the boards, it contains a link to the initial thread I raised wehen I first got stuck:



This looks very similar to an issue I am experiencing:

2019-10-22T13:47:08 Unable to establish remote device:
+ Atik CCD
Please ensure remote device name corresponds to actual device name.
2019-10-22T13:46:53 INDI services started. Connection to remote INDI server is successful. Waiting for devices...
2019-10-22T13:46:53 Connecting to remote INDI server at on port 7624 ...
2019-10-22T13:46:53 Establishing communication with remote INDI Web Manager...

More details in this thread:


@rlancaste / @knro - Could there be a similarproblem with Atik cameras as I used AstroPi3 to build both this RPi and my Odroid N2 and both have the same issue?

Wish I knew more about Linux...


Worked out verbose logging, seem to have this at the bottom:

"Unable to establish remote device:\n+ Atik CCD\nPlease ensure remote device name corresponds to actual device name."

Any tips?