sudo sh -c 'echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb' solved it for me as well.

Another strong thing is the line:
2021-03-21T18:27:30: [ERROR] Failed to activate cooler.

Nevertheless, cooling and temperature regulation works on my ASI 1600.


EFW filter weel is detected and connected o.k.

I've added back the rule now but it's generic for all USB devices and check if usbfs < 256 then sets it to 256. It's in GIT.

@knro

Jasem, the rule  you´ve added does not work on my system (Tumbleweed):

Looks like cat /sys/module/usbcore/parameters/usbfs_memory_mb has to be set into "back apostrophes" (don´t know theright word in english

This is working for me:

I did not have time to look into this until tonight, as my skies have been rotten and other things are taking some time anyway.

The change included the script, but it was just missing the execution of the `cat` statement.

Seescho, those are called "grave accents" in English, the back single quote. Using grave accents is the older, non-POSIX  way of execution in a shell, so we should probably change that to the $() POSIX way. The grave accents would have the same effect, but
in the future may not be as compatible with new shells.

<code>ACTION=="add", SUBSYSTEM=="usb", RUN+="/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'"</code>

I just put a PR up for the change.

Jim

 

Works, ThankYou!

Edgar

Jim, if you have a chance, please look also into this problem: 

indilib.org/forum/ccds-dslrs/9089-indi-c....html?start=24#69568

The issue with the ZWO-EFW is still ongoing, although I was able to fix that for my own installation.  However, Brian still has no joy getting his ZWO-EAF connected.

These problems arose at the same time as the image buffer issue in middle of last month, so the cause is likely related to the changes that were made at the time.

Merci

Jo

The current git build of indi-asi and libasi crash and dump core on the INDI server, and also cause kstars to crash and dump core on the client at the same time! I'd stay away from it for now. I sent Jasem some information to look at.

Jo, I don't have an EAF, but after reverting to the build of indi-asi from March 19, my ASI1600 MM Pro, ASI290 Mini, and ASI-EFW 8 are all working again.

Jim

No crash with current build and ASI120mc-s. So I changed to ASI1600mm-pro: crash.
I went back in the git history. The first time, the crash comes in, is this commit:
Maybe someone of you can have a closer look into this.
Edgar

Is there any news on this?  I just tried to connect my camera (ASI183MC) locally to the laptop, and trying to take an image crashes the indi driver.  Streaming works on the first try (I can even select sub-fields etc), but a restart (also from within the stream window to change exposure) will crash it....
This is with libindi-1.9.0-92_gbd9110b4.  No issues with the previous one I had installed (libindi-1.9.0-21_gd9a5e309 as of March 11)
 

I compiled from git just an hour before. The problem is not solved: ASI1600mm-pro crash the asi-cam-driver and kstars as well.

I played a bit with this stuff
 
The crash comes in with the new ASI-Cam-SDK 1.17.  "libASICamera2.so.1.17" is a shared library and dynamically loaded. I told my system to load the old SDK instead ( "libASICamera2.so.1.16.3" ). Result: No more crash. All is working well. So going back to SDK 1.16.3 should fix the problem

Edgar

I can't replicate the crash with multiple ZWO cameras here, so what's going on?

Jasem, which cameras did you use?

The little ASI120mm-s gives no crash for me. All is fine.
The big ASI1600mm-pro crash the cam driver and finally kstars.

That´s hat happen on my Linux-PC
Edgar