Updated the code for bookworm… I am having a hard time creating a microSD at the moment (all of mine are failing…) so I tested on a non-EON. Script downloaded everything, and it appears functional.
Please retry and let me know if something is not working,
This still does not sync RTC time at all. Why it’s SO HARD to just have this feature working on this case ? Like i activate i2c, enable it, sync timezone. All : still not working.
Can we just have a SIMPLE way to activate a feature at a thing we buy ? Please ?
Um… @tripop I don’t work for Argon… Frankly I have zero need for the RTC functionality past time setting, and with a battery that works just fine for me.
Well. Just do “timedatectl” to show it not sync, and not working. I follow the steps.
It seem i fixed it by doing a modification of a systemd (thing that i found here on a old thread) but now it doesn’t work AGAIN (for… no reason ?) and the script don’t want to update RTC because
sudo argon-config does this :
Traceback (most recent call last):
File "/etc/argon/argoneond.py", line 961, in <module>
print("RTC Time:", getRTCdatetime())
File "/etc/argon/argoneond.py", line 481, in getRTCdatetime
bus.write_byte(ADDR_RTC,2)
OSError: [Errno 16] Device or resource busy
Without sudo it does
Traceback (most recent call last):
File "/etc/argon/argoneond.py", line 17, in <module>
bus=smbus.SMBus(1)
PermissionError: [Errno 13] Permission denied
Also i have to do this to finally make RTC chip working : EON RTC Working? - #3 by SJMarty (kind of baffled by the fact this thing is not mentioned anywhere ? It like… the thing you have to do to make RTC work, so hello argon doc ? argon support ?. Don’t understand, really…)
Means that there is no access for that operation to succeed… this could be a number of issue (incorrectly configured system, system that has things locked down more, etc).
Not knowing the operating system you are using, makes it impossible to help…
sudo argon-config
--------------------------
Argon Configuration Tool
Version 2203003
--------------------------
Choose Option:
1. Configure IR
2. Configure RTC and/or Schedule
3. Uninstall
0. Exit
Enter Number (0-3):2
----------------------------
Argon RTC Configuration Tool
----------------------------
RTC Time: 2024-01-24 16:47:35
Choose from the list:
1. Update RTC Time
2. Configure Startup/Shutdown Schedules
0. Exit
Enter Number (0-2):1
Matching RTC Time to System Time...
RTC Time: 2024-01-24 16:47:40
----------------------------
Argon RTC Configuration Tool
----------------------------
RTC Time: 2024-01-24 16:47:40
Choose from the list:
1. Update RTC Time
2. Configure Startup/Shutdown Schedules
0. Exit
Enter Number (0-2):0
It really comes down to… what do you want to have working? What exact feature? The Real time clock? The RTC and the ability to automatically shutdown at a specific time, and restart at a specific time?
When you modify the config file to include:
dtoverlay=i2c-rtc,pcf8563
That prevents the python scripts from accessing the RTC… I’m not sure why. (yet).
MY recommendation would be to try and contact Argon… and be nice…
I did a little research because I was interested in knowing the cause. The overlay activates the kernel driver/module for communication with the RTC (0x51 ?). This is blocking access from other scripts to the same I2C address. I think, If you use
i2cdetect -y 1
you should get “UU” for this device as the confirmation. The user has to decide for himself what he wants to use: argoneon script OR direct kernel support. It is not possible to do both at the same time.
EDIT
By the way, there seems to be some progress in the scripts from Argon since the begin of the year. The only difference between argon1.sh and argoneon.sh is, if the EON / fanhat support is enabled by default.
Ah… .I am responding months later, lol. Sorry I didn’t see the question. Luckily, I have recently re-done my NAS devices at home, including my EON. I have installed Bookworm and OMV7. I used the script from the official location, was that the one that was updated? It seems to be working, but I haven’t tried all the config that I did last time. Fan gets pretty loud again, I’ll have to remember what I did and readust the curve.
I had no problem during the install. If the latest script is not at the official argon location, can you remind me where it is again? I’ve learned a bit since I started this whole process. I have my USB NVME adapter (housing the OS), passing through SMART details now, which is an improvement. I have moved to running MergerFS and SnapRAID for my NAS, exposed as a Samba share. I’m not going to run the same containers as I was running last time (Pi was slightly underpowered for those), so I have to come up with something to run. My 8GB or RAM is mostly underutilized at the moment.