Hi,
as a fresh owner of the Helios4 NAS (batch 3) I've prepared a rpm with some bits to make the user experience better. It could be done with ansible playbook too, but I think a rpm is more convenient in this case.
http://fedora.danny.cz/helios/bsp-helios4-1-1.fc31.noarch.rpm http://fedora.danny.cz/helios/bsp-helios4-1-1.fc31.src.rpm
It simply packs - modules-load file to force load lm75 that's not loaded automagically - udev rules for the temperature sensors symlinks from Armbian - fancontrol config file using the symlinks - Requires: lm_sensors for fancontrol, i2c-tools for the OLED display shipped with batch 3
The fancontrol config is set for the single PWM control (j10) that's available in mainline (and Fedora) kernels. The source rpm contains also the Armbian's config with both fans, but this relies on the out-of-tree patch [1], which now requires rebasing.
[1] https://raw.githubusercontent.com/armbian/build/master/patch/kernel/mvebu-ne...
to-do - ship a script controlling the OLED display - rebase the gpio/PWM patch and build some kernel with it
Right now I'm running it with the bottom fan (uncontrolled) fan disconnected and it doesn't seem to be running too hot. But use this method on your own risk.
Comments, contributions, etc are welcome :-)
With regards,
Dan
Hi Dan,
Sorry for the delayed reply here.
as a fresh owner of the Helios4 NAS (batch 3) I've prepared a rpm with some bits to make the user experience better. It could be done with ansible playbook too, but I think a rpm is more convenient in this case.
http://fedora.danny.cz/helios/bsp-helios4-1-1.fc31.noarch.rpm http://fedora.danny.cz/helios/bsp-helios4-1-1.fc31.src.rpm
It simply packs
- modules-load file to force load lm75 that's not loaded automagically
Looks like it's missing a compatible in the driver, or the device tree has the wrong one. I'll take a look at that, should be straight forward to fix.
- udev rules for the temperature sensors symlinks from Armbian
- fancontrol config file using the symlinks
- Requires: lm_sensors for fancontrol, i2c-tools for the OLED display
shipped with batch 3
So I think most of the above things around fan control should be handled with a cooling-map, then it would be handled automatically by the kernel thermal subsystem. You can see an example ine Odroid XU* devices in the upstream and looking at the Helios4 DT I don't think it should be too difficult to add. It would negate all of those bits.
arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi
The fancontrol config is set for the single PWM control (j10) that's available in mainline (and Fedora) kernels. The source rpm contains also the Armbian's config with both fans, but this relies on the out-of-tree patch [1], which now requires rebasing.
The upstream has both fans defined, any idea if anyone is trying to get that patch upstream?
[1] https://raw.githubusercontent.com/armbian/build/master/patch/kernel/mvebu-ne...
to-do
- ship a script controlling the OLED display
Is there details of the model? I suspect it might be a candidate for the tiny drm space along with some DT and userspace tools for stats (there is a project that does that by I can't seem to remember the name).
- rebase the gpio/PWM patch and build some kernel with it
Right now I'm running it with the bottom fan (uncontrolled) fan disconnected and it doesn't seem to be running too hot. But use this method on your own risk.
Comments, contributions, etc are welcome :-)
Comments above, let me know how I can help or if I can review anything for you.
Peter
-
Dan Horák -
Peter Robinson