Jump to content

Helios64 Upgrade from Debian10/OMV5 to Debian11/OMV6?

greg396

By greg396
in Rockchip

 Share

Recommended Posts

greg396

greg396

Posted
Posted

Dear Forum,

I am using a Helios64 with armbian Debian 10 (Buster) Linux-Kernel 5.15.52 and OMV 5.6.26-1.
If I want to have further Updates from OMV I need to upgrade to Debian 11, because OMV6 isn't compatible to Buster.

Any recomendations how I should upgrade?
The H64-System is on a SDD. Should I try a cli system upgrade or installing everything new with a bullseye image, if this is available (Where?)?

 

Best wishes, Greg

0
Werner

Werner

Posted
Posted

Hi

 

  On 8/15/2022 at 4:51 PM, greg396 said:

if this is available (Where?)?

Expand  

No pre-built image available since it is unmaintained. You can use the build framework to build your own image with Bullseye userspace.

 

 

  On 8/15/2022 at 4:51 PM, greg396 said:

try a cli system upgrade

Expand  

Userspace upgrades are neither tested nor supported. You can try but you are on your own if something breaks. Create proper backups first.

Good luck.

 

 

 

0
n3o

n3o

Posted
Posted (edited)

@Werner "You can try but you are on your own if something breaks" do You mean side software or side hardware? If openmediavault, armbian and all other packages are opensource the only limit can be represented from the driver that interface with kernel ...is right? (Note: I don't know Linux very well, I have only theoretical notion on operating system)

Edited by n3o
0
n3o

n3o

Posted
Posted

so best way is make a backup of image on other microsd with Linux-Kernel 5.15.52 and OMV 5.6.26-1 and update both Linux and OMV... if there are problems then switch to other microSD

0
Daniel Helios64

Daniel Helios64

Posted
Posted

Have upgrade Helios64 from OMV5 to OMV6 2 weeks ago.

 

System runs normal.

Only issue; fans became quite noisy since upgrade, guess maxrpm fancontrol is not working without hdd temp sensors.

 

Some info on config;

root@helios64:~# uname -a
Linux helios64 5.15.52-rockchip64  #22.05.4

 

Upgrade procedure;

- Linux updates

apt-get update && apt-get upgrade && apt-get dist-upgrade && apt-get --purge autoremove

 

- OMV update

omv-update

follow questions

reboot, hope for the best ;-)

0
Daniel Helios64

Daniel Helios64

Posted
Posted

The Helios64 documentation was a little unclear;

with these commands I found a (temp) solution for the RPM;

Get hardware addresses (find fan 6 and 7):

ls -l /sys/class/hwmon/

 

Read pwm setting (255 is max, possibly your hwmon-address is different)
cat /sys/class/hwmon/hwmon5/pwm1
cat /sys/class/hwmon/hwmon6/pwm1

 

Manual change rpm for Helios64 fans (value 60 is safe and quiet);
echo 70 > /sys/class/hwmon/hwmon5/pwm1
echo 70 > /sys/class/hwmon/hwmon6/pwm1

 

0
allen--smithee

allen--smithee

Posted
Posted

Hi,

 

maybe you want to modify some lines,

 

/usr/sbin/fancontrol

  Reveal hidden contents

my value is MAX=80 because when it comes to restart or shutdown I want to hear it

 

/etc/fancontrol

  Reveal hidden contents

my fancontrol setup with special setting with high quality thermal paste (With Gelid Solutions GP-Ultimate my unit is without thermal bottleneck Fanless) and use only SSDs.

MAXPWM is the key to silence but you have to find the max hwmonX/pwm1 value for CPU100%/Thermal PAD/Heatshink solution = temp1_input ≤ 80°C , otherwise you risk reaching the value of temp1_crit under heavy load.

 

Ex: With the original thermal PAD my old MAXPWM=120

0
greg396

greg396

Posted
  • Author
Posted

I just use the Usb-backup plugin.

I tried the upgrade but had some errors which I couldn't solve ending up in installing the latest bullseye image from here https://armbian.hosthatch.com/archive/helios64/archive/ first to SD then to eMMC and then the system to a SSD while booting from eMMC - which works now really good again with having actual OMV6. The only trouble is that I won't get the fan quiet :) Thank you allen--smithee for your modification which doesn't work for me, sorry! I can only manual set it quiet with Daniel Helios64 commands

echo 70 > /sys/class/hwmon/hwmon5/pwm1
echo 70 > /sys/class/hwmon/hwmon6/pwm1

0
allen--smithee

allen--smithee

Posted
Posted

I'm curious 

what is the result of this command

systemctl status fancontrol.service
 

and what does the next command say

systemctl start fancontrol.service

 

if the configuration file /etc/fancontrol contains it a syntax error or wrong variable fancontrol will not run.

also check 

ls -l /sys/class/hwmon | grep fan

ls -l /etc/udev/rules.d/

cat /etc/udev/rules.d/90-helios64-hwmon.rules

ls -l /dev/thermal-cpu/

 

Have you read old threads on the subject?

 

 

0
greg396

greg396

Posted
  • Author
Posted

Dear allen--smithee, thank you for taking you time! Yes, indeed the service won't start automatic after a reboot

 

status fancontrol.service shows these errors:

Error: file /dev/fan-p5/pwm1 doesn't exist
Error: file /dev/thermal-cpu/temp1_input doesn't exist
Error: file /dev/thermal-cpu/temp1_input doesn't exist

 

I could fix it with

sudo ln -s /sys/devices/virtual/thermal/thermal_zone0/hwmon0 /dev/thermal-cpu

and then starting the service manual

but after a reboot it's gone

I don't understand how I can apply it permantent

 

 

fancontrol.service
● fancontrol.service - fan speed regulator
     Loaded: loaded (/lib/systemd/system/fancontrol.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/fancontrol.service.d
             └─pid.conf
     Active: failed (Result: exit-code) since Fri 2022-09-16 17:53:17 UTC; 4s ago
       Docs: man:fancontrol(8)
             man:pwmconfig(8)
    Process: 3011 ExecStartPre=/usr/sbin/fancontrol --check (code=exited, status=0/SUCCESS)
    Process: 3144 ExecStart=/usr/sbin/fancontrol (code=exited, status=1/FAILURE)
   Main PID: 3144 (code=exited, status=1/FAILURE)
        CPU: 1.362s

Sep 16 17:53:17 helios64 fancontrol[3144]:   AVERAGE=1
Sep 16 17:53:17 helios64 fancontrol[3144]: Error: file /dev/fan-p5/pwm1 doesn't exist
Sep 16 17:53:17 helios64 fancontrol[3144]: Error: file /dev/thermal-cpu/temp1_input doesn't exist
Sep 16 17:53:17 helios64 fancontrol[3144]: Error: file /dev/thermal-cpu/temp1_input doesn't exist
Sep 16 17:53:17 helios64 fancontrol[3144]: At least one referenced file is missing. Either some req>
Sep 16 17:53:17 helios64 fancontrol[3144]: modules haven't been loaded, or your configuration file >
Sep 16 17:53:17 helios64 fancontrol[3144]: In the latter case, you should run pwmconfig again.
Sep 16 17:53:17 helios64 systemd[1]: fancontrol.service: Main process exited, code=exited, status=1>
Sep 16 17:53:17 helios64 systemd[1]: fancontrol.service: Failed with result 'exit-code'.
Sep 16 17:53:17 helios64 systemd[1]: fancontrol.service: Consumed 1.362s CPU time.
lines 1-22/22 (END)

 

s -l /sys/class/hwmon | grep fan
lrwxrwxrwx 1 root root 0 Sep 16 17:55 hwmon4 -> ../../devices/platform/p7-fan/hwmon/hwmon4
lrwxrwxrwx 1 root root 0 Sep 16 17:51 hwmon5 -> ../../devices/platform/p6-fan/hwmon/hwmon5

 

ls -l /etc/udev/rules.d/
total 56
-rw-r--r-- 1 root root    70 Nov 19  2020 10-wifi-disable-powermanagement.rules
-rw-r--r-- 1 root root    45 Feb  3  2021 50-mali.rules
-rw-r--r-- 1 root root   138 Feb  3  2021 50-rk3399-vpu.rules
-rw-r--r-- 1 root root  3132 Feb  3  2021 50-usb-realtek-net.rules
-rw-r--r-- 1 root root 20275 Aug 31 20:17 61-openmediavault-dev-disk-by-id.rules
-rw-r--r-- 1 root root    79 Feb  3  2021 70-keep-usb-lan-as-eth1.rules
-rw-r--r-- 1 root root   866 Feb  3  2021 90-helios64-hwmon.rules
-rw-r--r-- 1 root root   424 Feb  3  2021 90-helios64-ups.rules
-rw-r--r-- 1 root root  1348 Jan 20  2022 99-openmediavault-md-raid.rules
-rw-r--r-- 1 root root  1647 Jan 20  2022 99-openmediavault-nonrot.rules

 

 

cat /etc/udev/rules.d/90-helios64-hwmon.rules
# Helios64 persistent hwmon

ACTION=="remove", GOTO="helios64_hwmon_end"

#
KERNELS=="p6-fan", SUBSYSTEMS=="platform", ENV{_HELIOS64_FAN_}="p6", ENV{_IS_HELIOS64_FAN_}="1", ENV{IS_HELIOS64_HWMON}="1"
KERNELS=="p7-fan", SUBSYSTEMS=="platform", ENV{_HELIOS64_FAN_}="p7", ENV{_IS_HELIOS64_FAN_}="1", ENV{IS_HELIOS64_HWMON}="1"
KERNELS=="2-004c", SUBSYSTEMS=="i2c", DRIVERS=="lm75", ENV{IS_HELIOS64_HWMON}="1"

SUBSYSTEM!="hwmon", GOTO="helios64_hwmon_end"

ENV{HWMON_PATH}="/sys%p"
#
ATTR{name}=="cpu", ENV{IS_HELIOS64_HWMON}="1", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu"
#
ENV{IS_HELIOS64_HWMON}=="1", ATTR{name}=="lm75", ENV{HELIOS64_SYMLINK}="/dev/thermal-board"
ENV{_IS_HELIOS64_FAN_}=="1", ENV{HELIOS64_SYMLINK}="/dev/fan-$env{_HELIOS64_FAN_}"

#
ENV{IS_HELIOS64_HWMON}=="1", RUN+="/bin/ln -sf $env{HWMON_PATH} $env{HELIOS64_SYMLINK}"

LABEL="helios64_hwmon_end"


ls -l /dev/thermal-cpu/
ls: cannot access '/dev/thermal-cpu/': No such file or directory

 

/usr/sbin/pwmconfig: There are no fan-capable sensor modules installed

0
allen--smithee

allen--smithee

Posted
Posted

p5-fan and /dev/thermal-cpu doesn't exist, try with these changes

 

copy paste /etc/udev/rules.d/90-helios64-hwmon.rules

  Reveal hidden contents

 

copy paste /etc/fancontrol

  Reveal hidden contents

 

shutdown 0

 

Start

ls -l /dev/thermal-cpu/

systemctl status fancontrol.service

0
greg396

greg396

Posted
  • Author
Posted

Thank you.

You just need to exchange this fix here

https://github.com/useful64/build/commit/b9f17bdffa24cc3309dc20de487aaa19bb5c481d

 

-> ATTR{name}=="cpu|cpu_thermal", ENV{IS_HELIOS64_HWMON}="1", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu" is missing above

 

et voila

ls -l /dev/thermal-cpu/
total 0
device -> ../../thermal_zone0
subsystem -> ../../../../../class/hwmon
temp1_crit
temp1_input
uevent

 

so the working /etc/udev/rules.d/90-helios64-hwmon.rules looks like

 

# Helios64 persistent hwmon

 ACTION=="remove", GOTO="helios64_hwmon_end"

#
KERNELS=="p6-fan", SUBSYSTEMS=="platform", ENV{_HELIOS64_FAN_}="p6", ENV{_IS_HELIOS64_FAN_}="1", EN>
KERNELS=="p7-fan", SUBSYSTEMS=="platform", ENV{_HELIOS64_FAN_}="p7", ENV{_IS_HELIOS64_FAN_}="1", EN>
KERNELS=="2-004c", SUBSYSTEMS=="i2c", DRIVERS=="lm75", ENV{IS_HELIOS64_HWMON}="1"
KERNELS=="thermal_zone0", SUBSYSTEMS=="thermal", ENV{IS_HELIOS64_HWMON}="1"

SUBSYSTEM!="hwmon|thermal", GOTO="helios64_hwmon_end"

ENV{HWMON_PATH}="/sys%p"
#
ATTR{type}=="soc-thermal", ENV{HWMON_PATH}="/sys%p/temp", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu/t>
ATTR{name}=="cpu", ENV{IS_HELIOS64_HWMON}="1", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu"
ATTR{name}=="cpu|cpu_thermal", ENV{IS_HELIOS64_HWMON}="1", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu"
#
ENV{IS_HELIOS64_HWMON}=="1", ATTR{name}=="lm75", ENV{HELIOS64_SYMLINK}="/dev/thermal-board"
ENV{_IS_HELIOS64_FAN_}=="1", ENV{HELIOS64_SYMLINK}="/dev/fan-$env{_HELIOS64_FAN_}"

#
ENV{IS_HELIOS64_HWMON}=="1", RUN+="/bin/ln -sf $env{HWMON_PATH} $env{HELIOS64_SYMLINK}"

LABEL="helios64_hwmon_end"

0
freed00m

freed00m

Posted
Posted
  On 9/17/2022 at 2:01 PM, allen--smithee said:

shutdown are no longer noisy

Expand  

 

I think shutdowns will always be noisy, because the script ends and there is a TRAP signal that turns it to 100% .

 

But not sure if MAXPWN affects the AFCPWM values in that script.

 

Just look at the `/usr/sbin/fancontrol`

 

```

function restorefans()
{
        local status=$1 fcvcount pwmo

        echo 'Aborting, restoring fans...'
        let fcvcount=0
        while (( $fcvcount < ${#AFCPWM[@]} )) # go through all pwm outputs
        do
                pwmo=${AFCPWM[$fcvcount]}
                pwmdisable $pwmo
                let fcvcount=$fcvcount+1
        done
        echo 'Verify fans have returned to full speed'
        rm -f "$PIDFILE"
        exit $status
}

trap 'restorefans 0' SIGQUIT SIGTERM
trap 'restorefans 1' SIGHUP SIGINT

```

0
allen--smithee

allen--smithee

Posted
Posted

 

/usr/sbin/fancontrol

line 44 >> Max=

precisely defines the nominal speed when fancontrol is inactive,

which means, at the ignition of the device before the launching of the processes (including fancontrol) and at the extintion of the device when the processes are interrupted (including fancontrol)

and it can last several minutes when you have installed OMV and some containers.

But yes indeed you hear the fans roar for a second at the start and the end before the unit shuts down completely.

 

I leave MAX=80 because from memory during my previous tests, the fans make an audible noise, which allowed me to verify that my unit restarted or turned off when I sent a command from my phone.

A memory because it's been a while...

 

Screenshot_20220918_174423.jpg

 

 

/usr/sbin/fancontrol

  Reveal hidden contents

 

 

 

  On 9/18/2022 at 12:19 PM, freed00m said:

I think shutdowns will always be noisy, because the script ends and there is a TRAP signal that turns it to 100% .

Expand  

Line 394 >> declare -A PWM_ENABLE_ORIG_STATE

Line 395 >> declare -A PWM_ORIG_STATE

  Reveal hidden contents

>> /usr/sbin/pwmconfig

 

 

 

 

  On 9/18/2022 at 12:19 PM, freed00m said:

But not sure if MAXPWN affects the AFCPWM values in that script.

Expand  

line 46  >> function LoadConfig

line 108 

 

Line 521 >> function UpdateFanSpeeds
Line 609

  Reveal hidden contents

 

1
eClapton

eClapton

Posted
Posted (edited)

Hello @allen--smithee Im surprised by your uptime. I have manually freezed updates to my Helios64 at 21.05.1, because last time I tried the update, the / partition was mounted ro, and had to downgrade.

Is it safe to upgrade to 21.08.2?

My systems reboots frequently:

 

image.png.afd3d692a161dd1b989639fed3cb745a.png

Edited by eClapton
typo
0
allen--smithee

allen--smithee

Posted
Posted

 

I share my personal experience, this one works with me.

 

I use Helios64 on SD Card 32Gb, with this version

https://imola.armbian.com/archive/helios64/archive/Armbian_21.08.2_Helios64_buster_current_5.10.63.img.xz

 

installing omv with this script.

https://github.com/OpenMediaVault-Plugin-Developers/installScript

 

I modified or added a few lines in files but I can't tell you exactly which one and how because I forgot since.

 

I use 3 SSD disks individually managed by OMV + Containers.

no raid, just EXT format

Nothing special, but it is sufficient for my family use.

 

With 45 cents per kilowatt, Helios64 + SSD will cost me a maximum of 40 Euros this year. (Energie cost 2.5x since september)

0
n3o

n3o

Posted
Posted (edited)

if I follow your steps here

isn't necessary made a build such here https://docs.armbian.com/Developer-Guide_Build-Options/ ? 

 

if however I want compile a build , I should just only execute the following command 

 

./compile.sh BOARD=helios64 BRANCH=current KERNEL_ONLY=no RELEASE=buster

 

?

 

the main scope that I'm interested, as well as the updates of omv and plugin, is the support of ZFS filesystem

 

even with previous build, build 2.1.5  ( https://github.com/openzfs/zfs/releases ), I can't install it on my system and I get the following error

modprobe: FATAL: Module zfs not found in directory /lib/modules/5.15.52-rockchip64

 

How can I solve ?

 

@Daniel Helios64 and @greg396 do You get some issue with omv 6 and linux kernel 5.15.52 ?

 

p.s.: if we want continue to support helios64 hardware, what it's needed? the source code of driver of the various peripherals and what other? if there is an issue with omv 6, it should be related only between linux kernel and omv 6, why helios hardware should be involved? 

 

p.s. 2: somebody has tried kernel 5.19.15?

Edited by n3o
0
bunducafe

bunducafe

Posted
Posted

My Helios64 has some hick-ups now end then and it takes a few attempts to get it booted properly. No big big issue, but annoying nontheless.

 

I am wondering who is playing with the community builds? Until now I could not dig deep enough to compile my own build so far but I do suppose that some might do that here and possibly share the output. Or push me in the right direction where I could look and / or indeed build something from the scratch... The hardware setup of the helios64 is untouched therefore I do think that I don't need a kernel >5.15. but within the community builds we are already at 6.0.x and I have that slight concern that this will work well together with OMV for example...  or is this a concern that I should not have at all :)

 

Or do you guys have a preference for a specific / stable linux kernel for the helios64? That's also something I would consider to freeze the kernel completely if one of the builds work as expected without hick-ups.

0
Atticka

Atticka

Posted
Posted

Quick add to the thread, I did the 10->11 and then OMV5->6 upgrade recently and everything went as planned and has been working well since (over a week in now).

0
bunducafe

bunducafe

Posted
Posted

Short shout out: running stable on the latest 5.19.x kernel. But with cpu frequency throttled to 400 - 1600 ondemand governor. Means that it runs slightly below maximum power.

 

Does anyone know if there is a workaround to correct this issue and use it with full cpu power and not creating any kernel panic?

0

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept