Jump to content

TDCroPower

Members
 View Profile  See their activity

  • Posts

    99

  • Joined

  • Last visited

 Content Type 

Posts posted by TDCroPower

    Helios64 - Armbian 23.08 Bookworm issues (solved)

    in Rockchip

    Posted

    my bookworm installation is now over 1 year ago, has there been any further optimization in that time that should be adopted?
    Which setup combination is currently the most stable?
      

    Armbian 23.08.0-trunk Bookworm with Linux 6.6.8-edge-rockchip64
user@helios64:~# uname -a
Linux helios64 6.6.8-edge-rockchip64 #1 SMP PREEMPT Wed Dec 20 16:02:07 UTC 2023 aarch64 GNU/Linux


    I have been successfully connecting my Helios64 to a 2.5G Unifi switch for some time now and recently noticed that it kept interrupting the transfer when transferring files via 1G client.

    I then deactivated the scatter/gather offloading option, but did not yet adjust the /etc/rc.local as described here...

     

     

    0

    Helios64 - Armbian 23.08 Bookworm issues (solved)

    in Rockchip

    Posted

    now that OMV is finally installable on the Bookworm image from @ebin-dev (hopefully a proper fix will come from the OMV devs soon) I would like to share the changes you have made to the system for the Helios64.

     

    Here are my optimizations...

     

    CPU Frequency:

    Since only 2 of the 6 cores of the Helios64 can reach the max of "1800000", the general max setting must unfortunately be set to a value below which all 6 cores can reach. 

        CPU 1:
      Microarchitecture: Cortex-A53
      Max Frequency:     1.416 GHz
      Cores:             4 cores
      Features:          NEON,SHA1,SHA2,AES,CRC32
    CPU 2:
      Microarchitecture: Cortex-A72
      Max Frequency:     1.800 GHz
      Cores:             2 cores
      Features:          NEON,SHA1,SHA2,AES,CRC32


    Theoretically, all 6 cores can handle a max of "1416000", but unfortunately there have also been frequent problems with this, so a value of max "1200000" is recommended for a stable system. 

    root@helios64:~# cat /etc/default/cpufrequtils
ENABLE="true"
GOVERNOR="ondemand"
MAX_SPEED="1200000"
MIN_SPEED="408000"

     

    root bashrc

    In order to be able to use the bashrc with the root user, the following .profile file must be created in the /root directory with the following content...  

    root@helios64:~# cat .profile
if [ "$BASH" ]; then
  if [ -f ~/.bashrc ]; then
    . ~/.bashrc
  fi
fi

mesg n || true

     

    Docker Fix

    to fix the problem the line with ledtrig-netdev must be commented out so that containers can be started... 

    root@helios64:~# cat /etc/modules-load.d/modules.conf
lm75
#ledtrig-netdev

     

    Fancontrol:

    Here I have the following optimizations of the Fancontrol settings from a user from here... 

    root@helios64:~# cat /etc/fancontrol
# Helios64 PWM Fan Control Configuration
# Temp source : /dev/thermal-cpu
INTERVAL=10
FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input
MINTEMP=/dev/fan-p6/pwm1=45 /dev/fan-p7/pwm1=45
MAXTEMP=/dev/fan-p6/pwm1=110 /dev/fan-p7/pwm1=110
MINSTART=/dev/fan-p6/pwm1=25 /dev/fan-p7/pwm1=25
MINSTOP=/dev/fan-p6/pwm1=20 /dev/fan-p7/pwm1=20
#MINPWM=20
MINPWM=/dev/fan-p6/pwm1=20 /dev/fan-p7/pwm1=20
MAXPWM=/dev/fan-p6/pwm1=120 /dev/fan-p7/pwm1=120

    after the change restart the fancontrol.service with... 

    root@helios64:~# systemctl restart fancontrol.service

     

    LED State:

    If the flashing of the blue status LEDs of the Helios64 bothers you, you can simply stop the service, then it's quiet... 

    root@helios64:~# systemctl stop armbian-led-state.service

    Alternatively, you can also just stop the status LED from flashing heartbeat by changing the value from heartbeat to none... 

    root@helios64:~# cat /etc/armbian-leds.conf
[/sys/class/leds/helios64::status]
trigger=none
brightness=0
invert=0

     

     

    Do you have other optimizations for the system or other values like me?
    Please share them here 😉

    0

    Helios64 - Armbian Bookworm -> OMV 7 RC1 install problems (SOLVED)

    in Rockchip

    Posted

    @Trillien could be due to the commands after the installation... 

    line 345-347
  omv-confdbadm populate 2>&1 | tee -a ${logfile}
  omv-salt deploy run hosts 2>&1 | tee -a ${logfile}
fi

    also explains why your "workaround" probably works, since the part is skipped if OMV has already been installed... 

    line 295-297, end with fi on line 347
# install openmediavault if not installed already
omvInstall=$(dpkg -l | awk '$2 == "openmediavault" { print $1 }')
if [[ ! "${omvInstall}" == "ii" ]]; then

     

    ... the DEV ryecoaaron from the script is currently looking at the script fortunately and will hopefully fix the problem in the next version.

     

    Do you use Docker?
    For me, Helios crashes when I try to start a container, even with the hello-world test image from Docker... 

    docker run hello-world

     

    0

    Helios64 - Armbian Bookworm -> OMV 7 RC1 install problems (SOLVED)

    in Rockchip

    Posted · Edited by TDCroPower

    @Trillien your command to clean up the install doesn't work... 

    root@helios64:~# dpkg-reconfigure -a
Unknown option: a
Usage: dpkg-reconfigure [options] packages
  -u,  --unseen-only		Show only not yet seen questions.
       --default-priority	Use default priority instead of low.
       --force			Force reconfiguration of broken packages.
       --no-reload		Do not reload templates. (Use with caution.)
  -f,  --frontend		Specify debconf frontend to use.
  -p,  --priority		Specify minimum priority question to show.
       --terse			Enable terse mode.

     

    edit:

    The following command worked and then the script ran through without any problems... finally I have OMV 7 on the eMMC (boot) + SSD installation! 

    dpkg-reconfigure openmediavault

     

    or do you perhaps mean the following command, which has at least the -a option... 

    dpkg --configure -a

     

    0

    Helios64 - Armbian Bookworm -> OMV 7 RC1 install problems (SOLVED)

    in Rockchip

    Posted · Edited by TDCroPower

    @Trillien I have monitored the installation with the following command to see when the frequency is changed and then when it crashes.
    Command to monitor the cpufrequtil file... 

    while [ 1 ]; do sleep 1; clear; tail /etc/default/cpufrequtils; done

     

    at this point the cpufrequtils file is changed to the 0 values... 

    /usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead
  ) = locale.getdefaultlocale()
/usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead
  ) = locale.getdefaultlocale()
/usr/lib/python3/dist-packages/salt/utils/pycrypto.py:26: DeprecationWarning: 'crypt' is deprecated and slated for removal in Python 3.13
  import crypt
/usr/lib/python3/dist-packages/salt/modules/linux_shadow.py:21: DeprecationWarning: 'spwd' is deprecated and slated for removal in Python 3.13
  import spwd
Deploying service configurations ... <<<<< here !!!
Processing system modifications ... <<<<< or here !!!

     

    and at this point the cpufrequtils file is changed back to its own values... 

                                    - modules.omv_conf
                                - modules.omv_utils

              Summary for helios64
              ------------
              Succeeded: 4 (changed=4)
              Failed:    0
              ------------
              Total states run:     4
              Total run time:   3.700 s

Summary for helios64
------------
Succeeded: 6 (changed=5)
Failed:    0
------------
Total states run:     6
Total run time:  22.648 s

     

    and exactly then the helios64 crashes/reboots directly.

    I'll take a look at the script that is executed at this point and see if it can be deactivated.

     

    edit:

    ok the installation of omv changes the cpufrequtils file at this point of the script... 

    line 337 - 343...  
  _log "Installing openmediavault..."
  aptFlags="--yes --auto-remove --show-upgraded --allow-downgrades --allow-change-held-packages --no-install-recommends"
  apt-get ${aptFlags} install openmediavault 2>&1 | tee -a ${logfile}
  if [ ${PIPESTATUS[0]} -gt 0 ]; then
    _log "failed to install openmediavault package."
    exit 2
  fi

    ... I'll go to the OMV forum and ask why this is done and whether it is really necessary, because changing the cpufrequtils without reboot kills the Helios!

     

    Here my OMV forum post:

    https://forum.openmediavault.org/index.php?thread/52156-omv-7-install-on-helios64-fails/

    0

    Helios64 - Armbian 23.08 Bookworm issues (solved)

    in Rockchip

    Posted

    I had a little time to test again today and had an idea.
    I simply install OMV on the eMMC + eMMC combination and then transfer it to the SSD.
    The installation worked without any problems but unfortunately armbian-config does not offer the transfer from eMMC + eMMC to eMMC + SSD.
    So I also discarded this idea and tried to install everything on my microSD and then switch to eMMC + SSD.

    Well... the installation fails here too!

     

    The only combination to install OMV cleanly is on eMMC + eMMC, everything else fails and then has the known strange cpufrequtils entries.

     

    @ebin-dev do you have any ideas as to what is causing the problem and how I can fix it?
    I'm slowly running out of good ideas 🥲

    0

    Helios64 - Armbian 23.08 Bookworm issues (solved)

    in Rockchip

    Posted · Edited by TDCroPower

    I think I found something in the install script of omv that may be causing the problems.
    The script changes the CPU min/max frequency and the governor, which is known to be fatal with a Helios64!

     

    Spoiler 
    [...]
confCmd="omv-salt deploy run"
cpuFreqDef="/etc/default/cpufrequtils"
crda="/etc/default/crda"
[...]
if [ ${armbian} -eq 1 ]; then
  systemctl unmask systemd-networkd.service 2>&1 | tee -a ${logfile}
  # save off cpuFreq settings before installing the openmediavault
  if [ -f "${cpuFreqDef}" ]; then
    . ${cpuFreqDef}
    gov="${GOVERNOR}"
    minspd="${MIN_SPEED}"
    maxspd="${MAX_SPEED}"
  fi
fi
[...]
# governor and speed variables
if [ ${armbian} -eq 1 ]; then
  if [ -n "${defaultGov}" ]; then
    GOVERNOR="${defaultGov,,}"
  elif [ -n "${gov}" ]; then
    GOVERNOR="${gov}"
  fi
  if [ -n "${minspd}" ]; then
    MIN_SPEED="${minspd}"
  fi
  if [ -n "${maxspd}" ]; then
    MAX_SPEED="${maxspd}"
  fi
elif [ -f "${cpuFreqDef}" ]; then
  . ${cpuFreqDef}
else
  if [ -z "${DEFAULT_GOV}" ]; then
    defaultGov="ondemand"
  fi
  GOVERNOR=${defaultGov,,}
  MIN_SPEED="0"
  MAX_SPEED="0"
fi
[...]
# update config files
${confCmd} nginx phpfpm samba flashmemory ssh chrony timezone monit rrdcached collectd cpufrequtils apt watchdog 2>&1 | tee -a ${logfile}
[...]
if [ ! "${GOVERNOR,,}" = "schedutil" ]; then
  _log "Add a cron job to make NAS processes more snappy and silence rsyslog"
  cat << EOF > /etc/rsyslog.d/omv-armbian.conf
:msg, contains, "omv-ionice" ~
:msg, contains, "action " ~
:msg, contains, "netsnmp_assert" ~
:msg, contains, "Failed to initiate sched scan" ~
EOF

     

     

    the omv install script can be found under...

    https://raw.githubusercontent.com/OpenMediaVault-Plugin-Developers/installScript/master/install

     

    edit:

    ok it's totally crazy, now the omv installation went through without any problems.
    However, I am surprised that I saw the following cpufrequtils during the failed installation...
    GOVERNOR="schedutil"
    MAX_SPEED="0"
    MIN_SPEED="0"

     

    so now I'll test it again with eMMC + SSD, hope it runs smoothly this time!

     

    edit2:

    the same again, in the middle of the installation of omv the helios64 restarts and has the following cpufrequtils content...

    root@helios64:~# cat /etc/default/cpufrequtils
    ENABLE="true"
    GOVERNOR="schedutil"
    MAX_SPEED="0"
    MIN_SPEED="0"

     

    Why does it only work with eMMC + eMMC but not with eMMC + SSD?

    I just don't see what the cause is.
    The sbc-bench script ran before without any problems and the check with... 

    for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done

    ... was without any problems.

    0

    Helios64 - Armbian 23.08 Bookworm issues (solved)

    in Rockchip

    Posted

    Can I actually remove the 6.1.36 files?
    Since it links to the 6.6.8-edge, the old ones are unused, right?

      

    root@helios64:~# ll /
total 60
lrwxrwxrwx   1 root root     7 Jun 18  2023 bin -> usr/bin
drwxr-xr-x   4 root root  4096 Mar 24 12:41 boot
drwxr-xr-x  21 root root  4760 Mar 24 12:41 dev
drwxr-xr-x  99 root root  4096 Mar 24 12:41 etc
drwxr-xr-x   6 root root  4096 Mar 20 12:01 home
lrwxrwxrwx   1 root root    37 Feb 22 10:35 initrd.img -> boot/initrd.img-6.6.8-edge-rockchip64
lrwxrwxrwx   1 root root    33 Jun 30  2023 initrd.img.old -> boot/initrd.img-6.1.36-rockchip64
lrwxrwxrwx   1 root root     7 Jun 18  2023 lib -> usr/lib
drwx------   2 root root 16384 Jun 30  2023 lost+found
drwxr-xr-x   2 root root  4096 Jun 18  2023 media
drwxr-xr-x   9 root root  4096 Mar 23 20:19 mnt
drwxr-xr-x   3 root root  4096 Mar 20 12:09 opt
dr-xr-xr-x 293 root root     0 Mar 24 12:41 proc
drwx------   6 root root  4096 Mar 23 20:13 root
drwxr-xr-x  30 root root   880 Mar 24 12:47 run
lrwxrwxrwx   1 root root     8 Jun 18  2023 sbin -> usr/sbin
drwxrwxr-x   2 root root  4096 Jun 30  2023 selinux
drwxr-xr-x   4 root root  4096 Mar 20 12:15 srv
dr-xr-xr-x  13 root root     0 Mar 24 12:41 sys
lrwxrwxrwx   1 root root    42 Mar 24 12:41 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0
drwxrwxrwt  10 root root   200 Mar 24 12:42 tmp
drwxr-xr-x  11 root root  4096 Jun 18  2023 usr
drwxr-xr-x  13 root root  4096 Feb 22 09:51 var
lrwxrwxrwx   1 root root    34 Feb 22 10:35 vmlinuz -> boot/vmlinuz-6.6.8-edge-rockchip64
lrwxrwxrwx   1 root root    30 Jun 30  2023 vmlinuz.old -> boot/vmlinuz-6.1.36-rockchip64

root@helios64:~# ll /boot/
total 167948
-rw-r--r-- 1 emby emby      166 Mar 24 12:41 armbianEnv.txt
-rw-r--r-- 1 root root     1536 Jun 30  2023 armbian_first_run.txt.template
-rw-r--r-- 1 root root    38518 Jun 30  2023 boot.bmp
-rw-r--r-- 1 emby emby     3180 Jun 12  2023 boot.cmd
-rw-rw-r-- 1 root root     3252 Jun 30  2023 boot.scr
-rw-r--r-- 1 root root   238799 Jun 28  2023 config-6.1.36-rockchip64
-rw-r--r-- 1 root root   258775 Dec 20 18:58 config-6.6.8-edge-rockchip64
lrwxrwxrwx 1 root root       25 Feb 22 10:33 dtb -> dtb-6.6.8-edge-rockchip64
drwxr-xr-x 3 root root     4096 Jun 30  2023 dtb-6.1.36-rockchip64
drwxr-xr-x 3 root root     4096 Feb 22 10:33 dtb-6.6.8-edge-rockchip64
lrwxrwxrwx 1 root root       29 Feb 22 10:39 Image -> vmlinuz-6.6.8-edge-rockchip64
-rw-r--r-- 1 root root 22339789 Jun 30  2023 initrd.img-6.1.36-rockchip64
-rw-r--r-- 1 root root 27251745 Feb 22 10:39 initrd.img-6.6.8-edge-rockchip64
-rw-r--r-- 1 root root  4801937 Jun 28  2023 System.map-6.1.36-rockchip64
-rw-r--r-- 1 root root  5251808 Dec 20 18:58 System.map-6.6.8-edge-rockchip64
lrwxrwxrwx 1 root root       29 Feb 22 10:39 uInitrd -> uInitrd-6.6.8-edge-rockchip64
-rw-r--r-- 1 root root 22339853 Jun 30  2023 uInitrd-6.1.36-rockchip64
-rw-r--r-- 1 root root 27251809 Feb 22 10:39 uInitrd-6.6.8-edge-rockchip64
-rw-r--r-- 1 root root 29331968 Jun 28  2023 vmlinuz-6.1.36-rockchip64
-rw-r--r-- 1 root root 32815616 Dec 20 18:58 vmlinuz-6.6.8-edge-rockchip64

     

    0

    Helios64 - Armbian 23.08 Bookworm issues (solved)

    in Rockchip

    Posted

    @ebin-dev I got it to work with the armbian tools, but before it wanted to shut down the system at the last query, I ran the dd commands again.

    Unfortunately the transfer did not work with your script, the rsync command ran in a continuous loop.
    Now it worked with the tests after booting via eMMC and SSD.

     

    Strangely enough, however, I am now again having considerable problems with the installation of OMV and subsequent operation.
    The system simply freezes and restarts during some runs.
    I didn't have this with the other Helios64 device.

    I'll test installing everything via microSD to see if the same unstable symptoms can be observed.

    0

    Helios64 - Armbian 23.08 Bookworm issues (solved)

    in Rockchip

    Posted · Edited by TDCroPower

    @ebin-dev thanks for the script, i will try it.

    But you have 3 different UUID in the script...

    first one 7268e76f-3e1b-4e01-a6be-123456789012 ... 

    mount  --uuid 7268e76f-3e1b-4e01-a6be-123456789012 /mnt/emmc

    the second b790c4d7-5709-4000-91ac-123456789012 and the third 7268e76f-3e1b-4e01-a6be-987654321098 ... 

    sed -e 's/UUID=b790c4d7-5709-4000-91ac-123456789012/UUID=7268e76f-3e1b-4e01-a6be-987654321098/g' -i /mnt/emmc/etc/fstab

     

    the mount one is the "to device" or it is an another?

    here are my uuid's... 

    root@helios64:~# blkid
/dev/sdd: UUID="29f2832b-d95d-3e76-0375-3b2b0f0xxxxx" UUID_SUB="e187038d-7022-19b6-ac81-2f7dd80b2dae" LABEL="helios64:0" TYPE="linux_raid_member"
/dev/md127: LABEL="nas" UUID="b5c52051-e75f-408c-a7af-4a5d0daxxxxx" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdb: UUID="29f2832b-d95d-3e76-0375-3b2b0fxxxxx" UUID_SUB="914413d8-94a7-a983-6c96-7ae639f85ad2" LABEL="helios64:0" TYPE="linux_raid_member"
/dev/mmcblk0p1: LABEL="armbi_root" UUID="b790c4d7-5709-4000-91ac-099eeefxxxxx" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="188abe42-01"
/dev/sdc: UUID="29f2832b-d95d-3e76-0375-3b2b0fxxxxx" UUID_SUB="dbef45c4-9262-371c-fa47-b5efccc1b384" LABEL="helios64:0" TYPE="linux_raid_member"
/dev/mmcblk1p1: UUID="e4d8315e-aeb2-4e95-becf-88aaed8xxxxx" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f11f8806-01"
/dev/sda1: UUID="902f758f-240c-4f5a-b802-5ab5d35xxxxx" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0182fc84-01"
/dev/zram1: LABEL="log2ram" UUID="299a178d-7269-46e4-988c-f691813xxxxx" BLOCK_SIZE="4096" TYPE="ext4"
/dev/zram0: UUID="cab32334-75a4-4fda-b539-b17a55dxxxxx" TYPE="swap"

     

    0

    Helios64 - Armbian 23.08 Bookworm issues (solved)

    in Rockchip

    Posted

    @ebin-dev I tried to transfer my installation to my productive helios64 installation today, but unfortunately I still get... 

    Segmentation fault
free(): invalid pointer

    ... but here i am using a m.2 ssd on sata1 for the filesystem
    What should the "dd" commands look like in this setup?

    Here is the output of the volumes ... 

    root@helios64:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.8G  8.3M  1.8G   1% /dev
tmpfs           380M  6.0M  374M   2% /run
/dev/sda1       117G  3.1G  108G   3% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/mmcblk0p1   15G  182M   14G   2% /media/mmcboot
tmpfs           1.9G     0  1.9G   0% /tmp
/dev/zram1       47M  556K   43M   2% /var/log
tmpfs           380M     0  380M   0% /run/user/0

root@helios64:~# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda            8:0    0 119.2G  0 disk
└─sda1         8:1    0 119.2G  0 part  /var/log.hdd
                                        /
sdb            8:16   0   3.6T  0 disk
└─md127        9:127  0   7.3T  0 raid5
sdc            8:32   0   3.6T  0 disk
└─md127        9:127  0   7.3T  0 raid5
sdd            8:48   0   3.6T  0 disk
└─md127        9:127  0   7.3T  0 raid5
mmcblk0      179:0    0  14.6G  0 disk
└─mmcblk0p1  179:1    0  14.4G  0 part  /boot
                                        /media/mmcboot
mmcblk0boot0 179:32   0     4M  1 disk
mmcblk0boot1 179:64   0     4M  1 disk
zram0        252:0    0   1.9G  0 disk  [SWAP]
zram1        252:1    0    50M  0 disk  /var/log
zram2        252:2    0     0B  0 disk

     

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept