Very similar setup to me with VNC, PegasusAstro etc. I save onto a USB3 stick that’s connected directly to the Pi4.

I don’t think I’ve seen any comments from Jasem and others from the most recent crash dumps though.

Read More...

Sorry to hear that.

A week or so I posted three more crash dumps that I had so I am hoping this helps with troubleshooting for the next version of EKOS.

These new camera’s are starting to see wider adoption now so I hope the awesome crew maintaining EKOS can finally nail this down.

Read More...

One of the first clear nights for an hour or two and I got to do some more testing with v3.5.2. Bad news and good news here.

I managed to get it stable for a short 30min session with the 2600mc by leaving the new adaptive setting "enabled" but had to disable WCS and debaying in the FITS viewer configuration. It ran through 15 x 2min subs until I got clouded out so this looks like at least folks will be able to image with these settings applied, so that's a small win.

Below are a number of Kstars crash dump logs from the debugger so am hoping this helps get to the bottom of the problem.


Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0xb439d428 in QThreadStorageData::get() const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#0 0xb439d428 in QThreadStorageData::get() const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#1 0xb49190c8 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".




Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0xb439d428 in QThreadStorageData::get() const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#0 0xb439d428 in QThreadStorageData::get() const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#1 0xb49190c8 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".



Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0xb439d428 in QThreadStorageData::get() const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#0 0xb439d428 in QThreadStorageData::get() const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#1 0xb49190c8 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".

Read More...

For this specific issue I need to be able test this with guiding, mount control etc etc. I don't have an issue taking multiple subs like for calibration subs (darks, flats, bias) as this is only occurring during imaging runs for some reason.

I have upgraded my Pi4 onto the beta channel yesterday so if/when I get some good weather I'll be able to test it.

Read More...