Skip to content

FAN control OMV Auyfan 0.10.12: gitlab-ci-linux-build-184, Kernel 5.6

Linux
  • Hey,

    I will do it in english, hope it is okay. Thanks, for very informative forum.

    My question is, is it possible to control the FAN in the newest OMV Auyfan 0.10.12: gitlab-ci-linux-build-184, Kernel 5.6?
    The install was very easy no problems at all, the only problem is i did try some different commands to reach the fan, but was not able to get it going. Do somebody know how? Thanks.

    Best Regards.
    Soeren

  • Hi Soeren,

    I have this succesfully running.

    Kind Regards
    Martin

  • @mabs sagte in FAN control OMV Auyfan 0.10.12: gitlab-ci-linux-build-184, Kernel 5.6:

    Hi Soeren,

    I have this succesfully running.

    Kind Regards
    Martin

    Thanks, i will try the fan tool again. I'm almost sure i did try without luck, have you edited something in the fan tool conf..?

  • Hi,

    I only played with two parameters.

    I have two rockpro64 boards, currently one has a small fan and the other one has a large fan.

    Therefore I changed PROFILE_NR accordingly.

    Also I have ALWAYS_ON on true on the one with the large fan, but don't see a difference. The fan goes on and off still, maybe I misinterpreted the parameter.

    Also I just noticed now that the CTL settings of the version on github changed slightly, but I think this only improved the detection depending of the kernel settings.

    M

  • @mabs

    With the new OMV kernel 5.6 image from Auyfan, i can't get the FAN to spin - If the fan spins it runs really slow, no sound from the fan.

    With the FAN tool the master installation "failed" and with the release installation it did report "active"..
    I have installed a 92mm FAN inside the NAS case, it runs on Armbian with kernel 5.4.32

    I will open op the case later today to be sure. Thanks.

  • Hi,

    Now i did find the fan, here it goes "nano /sys/devices/platform/pwm-fan/hwmon/hwmon3/pwm1" it is at "0" can be controlled to "255"

    Best Regards.

  • Yes that is basically the way ATS is doing the changing as well I think, as those /sys entries are in the _CTL variables.

    good that you got it working, or are you only half way?

    M

  • @mabs

    The tool works on all image under 5.4 or so for me. But yes i am at the finish line, just wanted the fan to be always on. Just wanted to share, if someone will run in the same problems. Thanks.

  • Helpful Thread!

    But, ATS don't work for me on kernel 5.6 with ayufan release. Only this command works.

    nano /sys/devices/platform/pwm-fan/hwmon/hwmon3/pwm1
    

    Thanks @soerenderfor for the hint.

  • Ok, problem in ATS is this?

    -- FAN Control[ String ]
    	PWM_CTL		= {
    			"/sys/class/hwmon/hwmon0/pwm1",
    			"/sys/devices/platform/pwm-fan/hwmon/hwmon0/pwm1",
    			"/sys/devices/platform/pwm-fan/hwmon/hwmon1/pwm1"
    	},
    
  • @FrankM - did you try fix the ATS tool, if yes. Will it Work?

    Best Regards.

  • Hi,

    since I'm currently change my rockpro64 setup I came across this.

    With the kernel from ayufan you need to set PWM_CTL to

    /sys/devices/platform/pwm-fan/hwmon/hwmon3/pwm1
    

    for my self compiled one I need

    /sys/devices/platform/pwm-fan/hwmon/hwmon0/pwm1
    

    But I got it only working with one entry for PWM_CTL e.g.

    PWM_CTL		= "/sys/devices/platform/pwm-fan/hwmon/hwmon0/pwm1",
    

    after that you need to start ats again

    sudo systemctl stop ats
    sudo systemctl start ats
    

    initially the fan should start immediately for a short period of time.

    In case it is even a different one on your kernel you can find the right one using this command.

    sudo find /sys -name pwm1 | grep hwmon
    

    So far I'm not sure which kernel parameter or modul changes this.

    Martin

  • Raspberry Pi5 - Netzteil

    RaspberryPi
    1
    0 Stimmen
    1 Beiträge
    143 Aufrufe
    Niemand hat geantwortet
  • 0 Stimmen
    1 Beiträge
    255 Aufrufe
    Niemand hat geantwortet
  • FrOSCon 18 - Bericht

    Linux
    2
    0 Stimmen
    2 Beiträge
    118 Aufrufe
    FrankMF

    Und man soll ja auch was mitnehmen....

    Screenshot_20230809_194620.png

    Das ist Semaphore, installiert in einer VM auf meinem Proxmox.

  • NanoPi R4S - Armbian

    NanoPi R4S
    2
    0 Stimmen
    2 Beiträge
    306 Aufrufe
    FrankMF

    Müsste seit gestern so weit sein 🙂

    b20f93d2-1719-40c5-afb8-6b4edafa6793-image.png

  • Kopia - HTTP/S Server

    Verschoben Kopia
    3
    0 Stimmen
    3 Beiträge
    1k Aufrufe
    FrankMF

    Ich hatte ein paar Probleme, die ich mir teilweise nicht erklären kann 🤔

    Ich möchte den Kopia Server gerne über systemd steuern.

    SystemD [Unit] Description=Kopia Server After=syslog.target After=network.target [Service] Type=simple User=kopia Group=kopia ExecStart=/usr/bin/kopia server --tls-cert-file /home/kopia-server/fullchain.pem --tls-key-file /home/kopia-server/privkey.pem --htpasswd-file /home/kopia-server/.htpasswd --address <IPv4>:51515 Restart=always RestartSec=5 [Install] WantedBy=multi-user.target

    Danach

    systemctl daemon-reload systemctl start kopia-server

    Mit

    systemctl status kopia-server

    kann man sich den Status anzeigen lassen.

    Client Rechner

    Auf dem Client, der das Backup zum Server schicken soll, machen wir dann folgendes.

    USER@HOSTNAME:~$ kopia repo connect server --url=https://<DOMAIN>:51515 --override-username=USER --override-hostname=HOSTNAME Enter password to open repository: Connected to repository API Server. NOTICE: Kopia will check for updates on GitHub every 7 days, starting 24 hours after first use. To disable this behavior, set environment variable KOPIA_CHECK_FOR_UPDATES=false Alternatively you can remove the file "/home/frank/.config/kopia/repository.config.update-info.json".

    Danach steht die Verbindung und wir können Backups hochschieben.

    kopia snapshot create $HOME

    Damit wird das Homeverzeichnis gesichert. Das initiale Backup, hat 30 Minuten gebraucht.

    created snapshot with root kb9e50ff5xxxxxxxxxx265d40a5d0861 and ID cda5c0ffxxxxxxxxxxxxxxa4cb4a367b in 30m28s

    Ein späteres Backup, sieht so aus.

    USER@HOSTNAME:~$ kopia snapshot create $HOME Snapshotting USER@HOSTNAME:/home/frank ... * 0 hashing, 51 hashed (324.8 MB), 8524 cached (6.6 GB), 0 uploaded (0 B), 0 errors 100.0% Created snapshot with root kc20a4xxxxxxxxxxxx745c6c7b37c and ID d7a96eaxxxxxxxxxxx0961018eacffa in 3m12s

    Nach 3 Minuten durch. Zu diesem Zeitpunkt hat sich aber auch nicht wirklich was geändert!

    Fazit

    Das Tool macht immer noch einen sehr guten Eindruck. Die Geschwindigkeit ist sehr gut. Die Anleitung ist leider unzureichend. Da gibt es so viele Möglichkeiten, da braucht es sehr lange, bis man da mal durchsteigt. Zum Glück, ist das was man normalerweise braucht, recht überschaubar. Bis zum produktiven Einsatz braucht das aber bei mir noch eine Menge mehr Tests.

    Was ich noch testen möchte

    Verzeichnis mounten Backup testweise wieder herstellen (zumindestens teilweise)

    Der Test läuft mit Standard Einstellungen, also z.B. ohne Kompression. Das sollte man dann auch mal testen..

    Bitte achtet auf gleiche Versionen auf dem Clienten, wie auf dem Server. Ich meine da ein paar Probleme festgestellt zu haben...

  • Debian Minimal von Mr.Fixit2001

    Linux
    4
    0 Stimmen
    4 Beiträge
    429 Aufrufe
    FrankMF

    Release 190531 - Updated Debian Minimal Release

    Kernel Updated to 4.4.180 Additional Kernel Fixes U-Boot patched to fix weird issue where only some EMMC modules will not boot
  • Mainline Kernel 4.18.0-rc3

    Linux
    1
    0 Stimmen
    1 Beiträge
    946 Aufrufe
    Niemand hat geantwortet
  • Mainline Kernel 4.20.x

    Verschoben Images
    26
    0 Stimmen
    26 Beiträge
    4k Aufrufe
    FrankMF

    4.20.0-1090-ayufan released

    Änderungen -> https://gitlab.com/ayufan-repos/rock64/linux-mainline-kernel/commits/master