Same issue. Only commands I ran before were the usual sudo apt update ; sudo apt upgrade. Additionally, the script yields no output when ran directly: /usr/bin/python3 /etc/argon/argoneond.py
nor /usr/bin/python3 /etc/argon/argoneond.py SERVICE
If I’m not mistaken then rebooting the system with these services enabled freezes the entire indefinitely, at least that’s what happened to me. So after the second failed attempt at installing the Argon script, this time I’m trying
They are systemd service modules if you look at the configuration in those modules whether they block bootup or not is dependent on the service type argument. I believe they are type simple which doesn’t block other scripts from running. Regardless I didn’t have any issues with restarting.
[quote=“coro1404, post:3, topic:748”]the process seems stuck in either i2c or gpio:
[/quote]
I haven’t troubleshooted this any further TBH, but that is my suspicion as well. I have a hunch from reading the myriad of complaints about the oled screen(and some of the python code the service daemons run) that there is something wrong with the i2c connection which it seems is setup over gpio.
Curiously I sent a support email right after starting this thread and have received no response other then the canned automated one(so 2 weeks ago). Pretty annoying to me considering the main thing I’m currently using this thing for is just documenting how to set it up so I can write a howto thread for new users. Help me help you and all that.
the Ubuntu tweaks of the script is seemingly chosen instead the Raspbian/Pi OS ones.
Additionally the same grep command is used in /etc/argon/argoneon-rtcconfig.sh and in /etc/argon/argonone-ir which should concern @staff if the problem description is correct.
Yes, this is what I looked into doing. Though both files mentioned; argoneon-rtcconfig.sh and argonone-ir are auxiliary in function and the Raspbian detection is at the point of installation only used for selecting which packages to install (and to create some desktop shortcut in /home/pi. So I don’t quite see how it would help as I’ve manually installed all required packages anyway. (Again, hesitant to reboot with services installed)
I can actually get the OLED and fan control to work by running /usr/bin/python3 /etc/argon/argononed.py SERVICE manually. However sudo systemctl start argononed.service freezes as usual.
Interesting… that worked for me to(fan is going bonkers, but that’s probably a config thing). Proves it’s a software issue not a hw one as far as I am concerned.
If I run argononed.service in console one and let it hang, then check it’s status in console two it says “Active: inactive (dead)”.
But if I then “check ps -aux | grep argon” in a third console not only does it show the systemctl command still running, but it shows it running twice (once with sudo and once without and both running as root).
Journalctl logs don’t show anything
Either the script starts, fails silently, and systemctl locks up or
systemctl locks up and never even calls the command for some reason.
I also tried tweaking the systemd configuration in a variety of ways and reloading to no avail.
Sorry, I’m a Chinese, and my English is not very good. I also bought argon eon in my country. I like it very much, but I also encountered this problem. When executing the script, I got stuck, hit a breakpoint, and found that I was also stuck in the service of starting argononed. If you have any way, can you tell me?
So here is a ‘hacking’ solution which solves the wrong ID issue and the multiuser issue described above in one line: curl https://download.argon40.com/argonfanhat.sh | sed -E 's/"\$ID" *= *"raspbian"/\0 ] || [ "$ID" = "debian"/g;' | sed -E 's/echo "(After|WantedBy)=multi-user\.target"/# \0/g;' | bash
Hi, I am having exactly the same problem. Did you ever fix it? I tried to do : curl https://download.argon40.com/argoneon.sh | sed -E ‘s/“$ID” *= *“raspbian”/\0 ] || [ “$ID” = “debian”/g;’ | sed -E ‘s/echo “(After|WantedBy)=multi-user.target”/# \0/g;’ | bash
as in similar fashion mentioned by buegelbeatz.
But it did not work. I am a raspi 4 running a nextcloudpi image.