I am using this nightly build:
But I don't think that is the problem. As I wrote, I have 4 different builds on my Pi4 dating back to December. All of them worked before. So the problem had to be either with a driver or with a file that is being changed during installation and that is being used by all independent builds.
I remembered that I had a similar problem about 18 months or so ago when my PoleMaster was no longer recognized. At that time that had something to do with a QHY update that changed a .rules file and as a result the PoleMaster was no longer recognized when I started EKOS. I wondered whether something similar could be going on again now.
Before you proceed, take everything with a large grain of salt. I have made multiple changes and did not test them systematically for each change, so I can't be 100% certain what finally fixed the problem.
Search your machine for a folder called rules.d . There should be two places where you should find it. One as a /usr/././.. and one as a /etc/././.. subdirectory. The location is different depending on what machine you installed Kstars on (Pi4 or AMDx64, at least in my case, so it is probably simpler to just search for the folders). In there, you should find several files ending in .rules . Find the ones that have asi in the name. 99-asi.rules or just called asi.rules. There are also rules files for filterwheels (efw.rules) and focusers ( 99-focusers.rules ). I suspected that during one of the recent nightly updates one of the asi.rules files must have changed, preventing my efw from being recognized.
I then asked Hy to check his functioning installation and send me the contents of his asi.rules file. Comparing the two versions I saw that one line in the "new" rules file was missing. I added that back and then placed the modified file back into the rules.d folders.
My EFW was still not recognized after doing that, so I recompiled all the drivers. After that, I was back in business and it has been functioning now again flawlessly last night.
Again, I need to stress that I have not performed this test systematically, so I cannot say for sure which part (or location of the asi.rules file) is the critical one. But you could try it and see if that fixes your problem.
This is the content of the now functioning 99-asi.rules file:
ACTION=="add", ATTR{idVendor}=="03c3", RUN+="/bin/sh -c '/bin/echo 256 >/sys/module/usbcore/parameters/usbfs_memory_mb'"
# All ASI Cameras and filter wheels
SUBSYSTEMS=="usb", ATTR{idVendor}=="03c3", MODE="0666"
The first line was missing on my Pi4 when it was not working.
Let me know if that helps (or even makes sense).
Jo
PS: Also, I used an older version of the efw.rules file and placed it into both of the rules.d folders. I don't know whether that made a difference. There may be a rules file that defines your ZWO-EAF device ID and that may also have been changed. You may have to experiment with that if just replacing the asi.rules file and recompiling the drivers is not sufficient.