I’d like to disconnect it and reconnect it, but I can’t get my fat fingers in there.
EDIT: Was able to use the included screwdriver to lift and then reseat the connection on the bottom board, and now I’ve got full screen displaying again and no fading.
I just updated my repository with all of the changes just delivered from argon40 (i.e. hdd temp monitoring and fan speed changes based on that).
I also noticed in passing that the desktop icon was not getting installed on 64bit bullseye, this appears to be directly related to a check of /etc/os-release, expecting to see ‘Raspbian’ listed… it is not so modified that,
Also the desktop of the person installing the tools will get the icon added. The code was assuming user pi, and that caused a number of issues.
I had zero testing on RAID… I do not have a RAID setup on the box anymore, and can’t get it on there for a little while as I have the system dedicated to another task (for the moment).
My fan is running at 100% now , doesn’t seem to be recognizing the config files.
EDIT: BTW, It’s not your changes that’s causing it.
I also tried out the updated script from Argon40, and it’s doing it.
There seems to be something not quite right with it, at least for me.
EDIT2: Figured it out.
It was the HDD temperature profile that was causing it to spin constantly.
My HDDs are between 37C and 41C, so that was causing the fan to run all the time.
Okay so there is a bug in the original script in the get_fanspeed function.
The code calls the get_fanspeed function twice, once with the CPU temp, to get the fan speed requirements from that list, and once with the MAX hdd temp.
The maximum of these two calls is then used to set the fan speed in the temp_check function. This is all good.
The issue is that in the get_fanspeed function while processing temperatures, if we are above one of the settings the code will always return 25.
So assume you have argononed-hdd.conf setup like:
35=0
45=50
50=100
When you HDD temp is between 35 and 44.999 the fan speed will be set to 25% not 0. There are two things you can do to prevent this.
Make sure that neither configuration file has a temperature that you want the fan running at 0%
Make a code change.
Since the purpose of the configuration file is to drive the fans, I’m going to fix the code and remove the 25% minimum.
I also found that the code will not reload the settings unless you stop and restart the service. I modified that so now if you pull down the latest, the code inspect the two config files every time it checks the temperature. This occurs once every 30 seconds, UNLESS the new fanspeed is less than the prior fan speed in which case the code will pause 30 seconds to prevent lots of fluctuation.
Still not happy with it as the code will always set the fan speed even if the previous speed was identical (i.e. it is setting the speed every 30 seconds or so…)
There’s a bug in the current release of the script, whereby a fan speed value of 0 effectively translates to a value of 25.
If you remove all the zero-speed entries from both configuration files and restart, it should work fine. There’s no point having them in there, anyway: the default is for the fan to be off below your trigger temperatures (65 for CPU and 50 for HDD, in your current scripts.)
So a HDD temp of 30 would provide a 30% fan speed, IF there was no /etc/argononed-hdd.conf file. Since I have never seen an HDD temp on my system below 30, seems like the fan would be on all the time.
@Uruloki So… question… does /etc/argononed-hdd.conf exist?
I tried uninstalling but when i tried installing the standard argon script, just installed again your script (yes with this code " curl http://download.argon40.com/argoneon.sh | bash " even i reboot my pi)
Now my conf files
# Argon Fan Speed Configuration HDD
#
# Min Temp=Fan Speed
50=33
55=45
60=66
65=100
# Argon Fan Speed Configuration CPU
#
# Min Temp=Fan Speed
55=33
60=66
65=100
Actually my problem is when i install your script everything just normal but if i set temperature cpu and hdd with argon-config command then fan always running, so right now i first deleted script with argon-config command then reboot then installed again and set conf files with nano, right now fan stopped but i dont know, if system reach temperature conf files fan run
Allright - after some fights in unexpected places, I’ve got my Eon up and running now, hosting a raid1 Time Machine capsule for starters.
@NHHiker , your repo seems to be the go-to for getting the Eon’s specials usefully set up, thanks for the work and for having it open on GitHub!
But I’m posting here, so there’s a question… : on Ubuntu 22.04, there’s two problems with getting going:
hddtemp does not exist anymore as a package
raspi-gpio doesn’t exist either
For hddtemp, I’ve found the place where the executable is used - and I’m guessing that e.g. skdump might be an alternative to get hard disk temperatures.
Where exactly is raspi-gpio coming into the picture? I’d try to get a PR going with a 22.04 version, but need to work out what the deal is with that.
@Daniel I have not setup a system with Ubuntu 22.04 (not really a fan of Ubuntu and their kernel patch mechanisms… )
Not sure what the raspi-gpio package has changed to… anyway it looks like the GPIO package is required for talking to the OLED and on/off and fan functionality.
Looks like raspi-gpio was replaced with python3-lgpio
@Daniel - I updated my code to handle Ubuntu 22.04.
Since hddtemp is no longer available as a package from Ubuntu (it is for x86), I have the code download smartmontools. I created a fake hddtemp script so nothing else needs to change.
I plan on doing some more updates:
use smartctl for all platforms
remove all of the non-EON stuff from the scripts
make it easier to add new platforms, based of of the /etc/os-release file.
@NHHiker
I don’t know if you’ve seen my post, but I see that you’ve been update the Git for the install script.
I’m using Ubuntu 21.10 and I have yet to get it to work. I sent a message to support and have researched here for any relevant threads.
I have zero fan control and no OLED. The config script will run if I type argon-config. I checked to see if a argoneon.service is running and it’s not nor does the system know of one.
Any help is greatly appreciated.