PeterDB

@Vetteman maybe you figured it out by now, but if /dev/serial/ cannot be found, then it's because the device is not recognized. I had the same issue. Try to connect it to a USB2 port and see if it works, mine did.

If you need any help testing your "more functional version" sign me up

I'm waiting for mine, but honestly this "hacky version" is still better than trying to get Dynamix Auto Fan to work with various chipsets and fans, and on top of it Dynamix Auto Fan will only control one PWM fan, so you need a splitter. I gave up on getting my chipset working with Dynamix Auto Fan and after reading a lot settled on either OpenFan or Aqua Computer OCTO Fan. After 4 days of battling with Dynamix Auto Fan and Aqua Computer OCTO Fan or running scripts, I gave up. I'm sticking with OpenFan (and I don't even have it yet, but I know and can see that it will work better!)

Thanks! I ordered a print of them and they look great. Sadly I ordered two sets be accident, so if anyone is interested I have a spare.

@SasaKaranovic this actually looks really good. While i understand the unraid service is there, wouldn't it be possible to integrate the service into the docker? At least that the openfan docker has the ability to view temps and build scripts from within it, as this kinda feels like the last part to make this a truly great piece of hardware... And honestly you are only a few steps away from having something which is extremely good.

it looks like you are doing everything right, but I'm at my limit to answer why 1. it's not picking up the configuration file and 2. why the temps are so low. Unfortunately, I'm at the limit of where I can help, and you might/will need to seek help from other Linux forums/communities, as there must have been others with the same issue (unless you reallly have that low temps in your system because you are extreme cooling or live in the arctic circle with that computer) FYI: I've also myself thrown in the towel getting the fan controls to work for myself. The maintainer of the this driver also helped with the one I'm battling with, and he even writes himself that Gigabyte motherboards have fans speeds you can measure, but not change.

looks like everything is downloaded Now for good measure before you reboot or if you already have, run sensors-detect and let it write the config file, then reboot. If you already rebooted, do the same. FYI: I'm having similar issues as you with a new build (reusing old hardware) using a Gigabyte B560m motherboard and the IT87 drivers. Turns out it's also now well supported for all motherboards. I'm honestly myself a few steps away from ordering a dedicated fan controllers that works. What I'm looking at is https://github.com/aleksamagicka/aquacomputer_d5next-hwmon specificallly the Octo model and then using the Aquacomputer Unraid plugin to make it work. This is the "joy" of running any Linux OS, you need to fiddle/have fun/suffer (pick one)

looks like it downloaded the file. now run the ls and cat commands to validate everything is there.

Okay, so it never go downloaded either. Open a Terminal Type and run cd /etc/sensors.d/ Type and run rm Z690_Extreme.conf Type ls to check that only the file sensors.conf is there Type and run wget https://github.com/petersulyok/asrock_z690_extreme/raw/refs/heads/main/Z690_Extreme.conf Type ls to check that only the file sensors.conf and Z690_Extreme.conf are there and grab a screenshot too After type cat Z690_Extreme.conf and grab a screenshot again. IF you see both files and if the cat command shows something like below, you should be okay and you can reboot, and test again.

when you open the Terminal type and run cd /etc/sensors.d/, then type and run ls and grab me a screenshot of what you see, because now it kinda sounds like you never even downloaded the file.

You need to change to the folder first using the previous command cd /etc/sensors.d/

Yeah, then I think you need to maybe contact the GitHub maintainer, as a new/fixed conf file would be needed. Only last thing I can think of is maybe rights on the file. You could copy the rights from the existing sensors file to the GitHub file using chmod --reference=sensors.conf Z690_Extreme.conf

Did you try to do it without running sensors detect?

First had time to check this now. However, looking through the https://github.com/petersulyok/asrock_z690_extreme/blob/main/Z690_Extreme.conf and the names you get from sensors command, it looks like the configuration file didn't get loaded because the command I gave didn't download the file, but the html page. So what you need to do now is the following: Open a Terminal Type and run cd /etc/sensors.d/ Type and run rm Z690_Extreme.conf Type ls to check that only the file sensors.conf is there Type and run wget https://github.com/petersulyok/asrock_z690_extreme/raw/refs/heads/main/Z690_Extreme.conf Reboot Open a Terminal again and run sensors and check if the names of the sensors have updated, as they the temps should also be showing correctly.

First some questions: - Which CPU do you have? - Can you run sensors and post here? - Can you grab a screenshot again from the System Temp settings page with all the options in the drop-down menu?

Just reboot What do you mean by spiking? Did you try to run top in a terminal to see what processes are causing it

Actually you saw the driver name now and that means it did load and its working. Now you need to start to configure Dynamix. Downside with this is that a motherboard and cards have a lot of temp sensors so it takes time and fiddling to get it just right. In short: you did get it working!

What happens if you open a terminal and just write sensors does it show anything? Afterwards can you run sensors-detect and run through it and then reboot?

try /etc/init.d/lm_sensors start or /etc/init.d/lm_sensors restart, or just reboot the system

Going by my experience no, but going by the maintainer (the guy who wrote the driver) there are risks. But then again he still wrote the driver and still recommends people to use it, with the warning that there are risks. Again, i run an Unfair build that's under heavy daily use, and I've never had any issues since I wrote the original post. Then again my hardware isn't the same as yours. No matter what you do, if the system is unstable you can just reboot and choose the standard Unraid boot option which doesn't include the lax option.

I too went through the same as you, but a tip for testing is just get a second usb stick with unraid on it. Unplug all your disks and boot on the new unraid stick, and do your testing on it. If you have a lot of disks seated close together there are real world needs for this to work, such as better cooling control for the disks. Without it my system would run hot.

Yeah plus the additional step before you reboot. However, before you do, try first to check the plugin setting for Dynamix to make sure it really isn't working.

I did a bit more reading and it would seem you could get this to work, but my instructions would need to be tweaked. Specifically before you reboot, you need to do the following: Open the Terminal in Unraid Type cd /etc/sensors.d to navigate to the right folder Type wget https://github.com/petersulyok/asrock_z690_extreme/blob/main/Z690_Extreme.conf to download the configuration file from https://github.com/petersulyok/asrock_z690_extreme Type systemctl restart lm_sensors.service to restart lm_sensors to load the configuration file. Now you can reboot and you should be able to get full control in Dynamix.

Looking at https://github.com/petersulyok/asrock_z690_extreme i dont think this workaround will work.

No, there will never be any updates that truly fixes this. Bios' have moved away from this flawed architecture rather than solving it. For me the Dynamix and the workaround is the only way to get proper fan and heat control, as I run a build with 18 disks seated close together. Plus, I work in the same office as the build, so when there's no heavy disk read/writes I'd like not to be spinning like crazy.