×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

RaspberryPi 4 my version of full install indi/kstars

  • Posts: 2876
  • Thank you received: 809
I just got my Raspberry Pi4 this week. I was inspired by your success to go back and modify my script to work on the Raspberry Pi 4 in Raspbian instead of just ubuntu. I worked on that for a few hours yesterday and today. I've just about got it. There are a few more issues with networking, but mostly everything else is working pretty well now. I'll post again when its done. By the way, with zram turned on, this thing basically has nearly 8 GB of Ram!
The following user(s) said Thank You: Clive Garner
4 years 7 months ago #41565

Please Log in or Create an account to join the conversation.

  • Posts: 28
  • Thank you received: 1
If you need someone for testing, let me know. I’ve been manually doing what your script does for a few days because I was trying out a few things.
4 years 7 months ago #41577

Please Log in or Create an account to join the conversation.

  • Posts: 1208
  • Thank you received: 559
Some quick Pi questions:

1) zram: Do you mean to do step #2 in this: peppe8o.com/2019/03/4-tricks-to-improve-...nd-power-consuption/
do you still recommend that? Any other OS optimizations?

2) Not very git-experienced. When one does a git clone/pull, as in the above or your (@rlancaste) scripts, and then compile to make the binaries, does one wind up with the "bleeding edge" of the repository or the latest release? If it's the head of the tree, how would one get the latest (stable as possible) release?

3) I seem to recall reading that one can do better than running from sdcards, e.g. some inexpensive SSD (not sure how ssd and flash cards differ, honestly). Is that the case? Anything anyone recommends? One thing I really like about SD cards is that I can clone the entire system and, in case of failure/corruption/mistakes I can revert to a known working state. Downside, though, is you want to limit to 32Gb SD cards, since cloning/writing 64Gb is painful, at least the way I do it. Also, with all the source compiled, I'm only left with 10Gb working space on the system.

4) My system, basically the OP's script with mods to make it work for me, on a RPi4b 2Gb is working nicely. One issue though is heat. Believe it or not, I once saw temperature of > 100C! Once it starts throttling (at 80C), the thing slows significantly. I've gone running the Pi "naked" (nothing around the raw board, dangling from an ethernet cable attached to my telescope) until the flirc case I ordered comes in. Any heat control suggestions anyone?

Hy
4 years 7 months ago #41703

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
You can give my script a try now. I have most of the issues all worked out. There are still just a couple of things that I want to refine, but nothing that should stop you

1. ZRam is awesome. It does cost a little in cpu cycles, but it doesn't hurt the sd card, and it effectively adds RAM. I made a lot of modifications to my script for the new raspbian version, one of them is installing ZRAM differently for the Pi. On the Ubuntu version, it is an installable package, but for Raspbian it is a downloaded and installed script.

2. The way I currently do the INDI and KStars build, it uses the absolute bleeding edge KStars and INDI. It doesn't have to be done that way. You could download the source of the latest release instead and build that. That could be an option I add to my script in the future.

3. I've been using SD cards for my PIs since 2016. I haven't had any issues or corruptions yet. And I've used them quite a lot. But you can probably do something else

4. I don't have a case yet. I've not been happy with what I have seen so far. Right now my Pi4 is used for experimentation. I currently am using my Raspberry Pi 3b's and 3b+ for imaging. So far I haven't seen it get above 80 degrees. I have some small heat sinks on the components to dissipate heat though.
4 years 7 months ago #41720

Please Log in or Create an account to join the conversation.

  • Posts: 1067
  • Thank you received: 140

I have this case with built in fan and heatsink on my rpi4, £9.99 from amazon

4 years 7 months ago #41735
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
Yep I have seen those cases on amazon. They are transparent, which is a huge issue at a star party with the led lights. Also how is the dew proofing?

smile.amazon.com/gp/aw/d/B071YPZFZ4

I have these cases for all the sbcs I use in the field. I have two for raspberry pi 3bs, one for a 3b+, and another for a rock64. They are very rugged, look great, are opaque, and protect the pi somewhat from dew. But no version for 4b yet.
4 years 7 months ago #41736

Please Log in or Create an account to join the conversation.

  • Posts: 28
  • Thank you received: 1

Thanks for all that work, this has really helped me a lot. I even ran the script on a non-RPi and it worked pretty well. Just two quick comments:
  • There is a zram-tools package for Raspbian, not sure if you are aware of that. Using that the zram setup might look pretty similar to what you are doing on Ubuntu.
  • You could probably checkout to a particular tag when cloning the git repositories. Perhaps that's something that could be specified via command line or environment variables?
4 years 7 months ago #41746

Please Log in or Create an account to join the conversation.

  • Posts: 1067
  • Thank you received: 140
Yes, I have those cases too for my 3b+ and 3b and also tried one on my rpi4 too....but it runs too hot on a metal case so went for the acrylic one instead, and now runs about 45 degrees all the time...
Easy to adapt for the rpi4
4 years 7 months ago #41748
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
I'm going to try that! I have a couple of heat sinks on mine that might help. And I have a case that I already slightly modified for the rock64, but the rock64 has some issues that I never resolved so I don't use it. So it wouldn't hurt to try!
4 years 7 months ago #41753

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
A script for a "non-pi" is included in there too. it is called setupUbuntuSBC (renamed from 64 bit, because it doesn't have to be 64 bit)

But I have been working hard on the Raspian and Ubuntu Mate PI scripts, so the Ubuntu SBC probably still needs some updating to include all the revisions I have made this week in the others.
4 years 7 months ago #41754

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
Yes, you can checkout a specific commit when cloning the git repositories, but progress on INDI and KStars is so rapid, that it would quickly get out of date if I don't update it very very very regularly.
4 years 7 months ago #41755

Please Log in or Create an account to join the conversation.

  • Posts: 1208
  • Thank you received: 559
Do you know the specific git command to do this?
I'm not too familiar with Git, and kstars development, but I did a little googling and came up with the following:

> git clone github.com/indilib/indi.git
> cd indi
> git tag
v1.3
v1.3.1
v1.4.0
v1.4.1
v1.5.0
v1.6.0
v1.6.1
v1.6.2
v1.7.0
v1.7.1
v1.7.2
v1.7.4
v1.7.5
v1.7.6
v1.7.7
v1.7.8
v1.7.9
v1.8.0

I assume tag v1.8.0 is the tag for indi 1.8.0

Then, I assume this is how to get the released indi source:

cd indi
git checkout v1.8.0
// then go ahead and compile indi in this directory

However, for kstars, things seem more complicated:

// Get kstars
git clone git://anongit.kde.org/kstars
cd kstars
// Find all the tags
git tag
...
v16.12.3
v17.03.80
v17.03.90
v17.04.0
v17.04.1
v17.04.2
v17.04.3
v17.07.80
v17.07.90
v17.08.0
v17.08.1
v17.08.2
v17.08.3
...
v4.9.0
v4.9.1
v4.9.2
v4.9.3
v4.9.4
v4.9.5
v4.9.80
v4.9.90
v4.9.95
v4.9.97
v4.9.98

It doesn't look like any of these are the current tags, if they still use tags. e.g.

> git log --tags --simplify-by-decoration --pretty="format:%ai %d"
2018-08-15 21:09:17 +0300 (tag: v2.9.8)
2018-07-25 21:38:14 +0300 (tag: v2.9.7)
2018-04-23 00:20:55 +0300 (tag: v2.9.5)
2018-04-08 10:06:21 +0300 (tag: v2.9.4)
2018-02-26 17:27:08 +0300 (tag: v2.9.3)
2018-01-28 09:57:47 +0300 (tag: v2.9.2)
2018-01-10 08:45:17 +0300 (tag: v2.9.1)
2018-01-09 16:22:27 +0300 (tag: v2.9.0)
2017-12-16 00:51:54 +0300 (tag: v2.8.9)
2017-11-19 15:33:38 +0300 (tag: v2.8.8, origin/2.8)
...

there is nothing for 2019.
Any ideas how to get kstars release source via git?

I guess the alternative is to use
download.kde.org/stable/kstars/kstars-3.3.3.tar.xz.mirrorlist
or some other release from download.kde.org/stable/kstars/
and skip git altogether.

Is that the recommended approach?
Hy
4 years 7 months ago #41763

Please Log in or Create an account to join the conversation.

Time to create page: 0.689 seconds