×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

AstroArch - yet another raspberry distro for astrophotography for ARM64

  • Posts: 232
  • Thank you received: 8
6 months 4 weeks ago #96249
The topic has been locked.
  • Posts: 16
  • Thank you received: 2
Hi. Thank's a lot . I have pasted your system on my card and it works. more needs to be implemented but it seems like a very good option. I will continue testing and look forward to more updates. thank you so much.
6 months 3 weeks ago #96289
The topic has been locked.
  • Posts: 155
  • Thank you received: 107
Hi Manel,

glad you tried and it works. Can you elaborate a bit more on the additional needed things? If you have any ideas or requirements feel free to share them, this may help me focusing on the right things for the new upcoming release (or put them into a queue if they are more complicated :)

Thanks,
Mattia
6 months 3 weeks ago #96299
The topic has been locked.
  • Posts: 16
  • Thank you received: 2
hi. Mattia. it would be helpful if the screen resolution is in the "computer setting" Astroberry style. so you can change at your convenience.
and the icons in EKOS they don't have graphics iside. they are just empty.
6 months 3 weeks ago #96301
The topic has been locked.
  • Posts: 155
  • Thank you received: 107
Thanks Manel,

for the resolution you should be able to use arandr, I believe it is installed, if not a simple sudo pacman -S arandr will do the trick.
For the icons, can you send a screenshot? I believe this may be an issue with the KDE dark breeze them
6 months 3 weeks ago #96302
The topic has been locked.
  • Posts: 16
  • Thank you received: 2
I listened to your advice and now everything works better. thanks
6 months 3 weeks ago #96303
The topic has been locked.
  • Posts: 12
  • Thank you received: 0
Hello,
Yesterday I tried to install AstroArch distro on an RPi4 4GB but I faced an issue.
Boot sequence started as expected but stopped at 'Graphical Interface target reached' step (see figure). I waited several minutes but nothing happened.
I re-flashed the sd-card, tried with another USB cable without succes.
Would you have any ideas on this problem?

Clear skies.
6 months 3 weeks ago #96365
Attachments:
The topic has been locked.
  • Posts: 155
  • Thank you received: 107
Hi deepskyphoto, looks like you connected the pi to a monitor via hdmi? Is that correct?
6 months 3 weeks ago #96366
The topic has been locked.
  • Posts: 12
  • Thank you received: 0
Hello Mattia,
Thank you for your quick reply. Yes the raspberry is connected via the HDMI port, may it be the source of the issue?
6 months 3 weeks ago #96367
The topic has been locked.
  • Posts: 155
  • Thank you received: 107
Hi! No this is not a real "issue", I simply never went to fix the hdmi thing. Astroarch for the time being works only through VNC. What you see through the monitor is the system booting but not entering the graphical state on HD I, it should be functional though. You can try VNC (browse or some VNC client) to confirm it is working
The following user(s) said Thank You: DeepSkyPhoto
6 months 3 weeks ago #96368
The topic has been locked.
  • Posts: 12
  • Thank you received: 0
Thank you very much for your help, AstroArch is up and running ;)
(connected through VNC in Google Chrome)

Clear skies!
6 months 3 weeks ago #96371
The topic has been locked.
  • Posts: 232
  • Thank you received: 8
Mattia: when I plug my USB u-blox7 GPS unit into a USB port on my Pi running Astroarch, Ekos no longer can find my AVX mount:.
2023-10-14T00:55:46: [ERROR] Failed to communicate with the mount, check the logs for details. 
2023-10-14T00:55:46: [ERROR] Serial read error: Read overflow 
2023-10-14T00:55:45: [ERROR] Serial read error: Read overflow 
2023-10-14T00:55:44: [INFO] Trying connecting to /dev/serial/by-id/usb-u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver-if00 @ 9600 ... 
2023-10-14T00:55:43: [WARNING] Port /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0 is already used by another driver or process. 
2023-10-14T00:55:40: [INFO] Trying connecting to /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0 @ 9600 ... 
2023-10-14T00:55:39: [ERROR] Failed to communicate with the mount, check the logs for details. 
2023-10-14T00:55:39: [ERROR] Serial read error: Read overflow 
2023-10-14T00:55:38: [ERROR] Serial read error: Read overflow 
2023-10-14T00:55:37: [INFO] Trying connecting to /dev/serial/by-id/usb-u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver-if00 @ 9600 ... 
2023-10-14T00:55:35: [WARNING] Communication with /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0 @ 9600 failed. Starting Auto Search... 
2023-10-14T00:55:35: [WARNING] Port /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0 is already used by another driver or process.

If I unplug the u-blox and restart the Pi, then I don't have this issue. What could be going on here?
6 months 3 weeks ago #96440
The topic has been locked.
Moderators: Mattia
Time to create page: 1.312 seconds