You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have installed buster OS on my "Raspberry Pi Model B Rev 2 ( I suppose it is "Raspberry Pi 1", BCM2835 with 512 MB RAM) plus I have done "apt install indi-full".
My idea was to be able to wirelessly control a mount plus gather images from ASI camera to my laptop.
Each binary from indi-bin gives me Segmentation fault or Illegal instruction (any software installed from buster repositories works OK).
My suspition is there is something wrong with build system (it is built not built for armhf 32bit system, but is marked as such in the repo)?
Is astroberry (or at least indiserver part) supposed to be running on those old RPIs as stated ("Support for Raspberry Pi 3 and 4, Pi Zero and... probably any other Raspberry Pi version released so far")?
The text was updated successfully, but these errors were encountered:
I would add that astroberry repo does not apparently have indiserver for bullseye raspberry pi OS version (for this architecture?) - I was also trying to install indiserver using this environment. Should it work?
Hi,
I have installed buster OS on my "Raspberry Pi Model B Rev 2 ( I suppose it is "Raspberry Pi 1", BCM2835 with 512 MB RAM) plus I have done "apt install indi-full".
My idea was to be able to wirelessly control a mount plus gather images from ASI camera to my laptop.
Each binary from indi-bin gives me Segmentation fault or Illegal instruction (any software installed from buster repositories works OK).
My suspition is there is something wrong with build system (it is built not built for armhf 32bit system, but is marked as such in the repo)?
Is astroberry (or at least indiserver part) supposed to be running on those old RPIs as stated ("Support for Raspberry Pi 3 and 4, Pi Zero and... probably any other Raspberry Pi version released so far")?
The text was updated successfully, but these errors were encountered: