[Reboot not working properly with OMV]

@mortomanos looks like something wrong with the eMMC. It works intermittently.

on your first log, there are several error like this

[    3.351947] mmc1: mmc_select_hs200 failed, error -110
[    3.352420] mmc1: error -110 whilst initialising MMC card

 

On your second log, it failed for several times but finally it initialized

[    3.577160] mmc1: mmc_select_hs200 failed, error -110
[    3.577624] mmc1: error -110 whilst initialising MMC card
[    3.577761] of_cfs_init
[    3.578449] of_cfs_init: OK
[    3.631765] usb 3-1: New USB device found, idVendor=2109, idProduct=2815, bcdDevice= 7.04
[    3.632503] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.633140] usb 3-1: Product: USB2.0 Hub
[    3.633594] usb 3-1: Manufacturer: VIA Labs, Inc.
[    3.685522] hub 3-1:1.0: USB hub found
[    3.686115] hub 3-1:1.0: 4 ports detected
[    3.739853] mmc1: Command Queue Engine enabled
[    3.740269] mmc1: new HS200 MMC card at address 0001
[    3.741441] mmcblk1: mmc1:0001 AJTD4R 14.6 GiB
[    3.742111] mmcblk1boot0: mmc1:0001 AJTD4R partition 1 4.00 MiB
[    3.742891] mmcblk1boot1: mmc1:0001 AJTD4R partition 2 4.00 MiB
[    3.743579] mmcblk1rpmb: mmc1:0001 AJTD4R partition 3 4.00 MiB, chardev (243:0)
[    3.745394]  mmcblk1: p1

 

Could you check whether you have P10 jumper enabled?

[Recovery: (too) short delay between UMS and Maskrom modes]

As we have mentioned on the wiki, you can watch the System LED as visual cue. When it blink once, release the button.

There are roughly 2 second delay to release the button.

https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-rockchip64-mainline/general-support-recovery-button.patch#L131-L137

 

Another visual cue you can check is through serial console.

U-Boot 2020.07-armbian (Nov 23 2020 - 16:22:15 +0100)

SoC: Rockchip rk3399
Reset cause: POR
DRAM:  3.9 GiB
PMIC:  RK808
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
using mmc0 device for download mode
rockchip_dnl_mode = ums mode

as soon as you see rockchip_dnl_mode = ums mode, release the button.

[Helios 4 doesn't switch on anymore]

You can check the PSU by measuring the output voltage.

 

You can check the motherboard by following instruction on the older support thread. You can also find our recommendation for replacement PSU

 

 

[Issues to install PHP for NextCloud, Armbian-Config and SSH timed out]

Do you have OMV installed? Last time (long time ago) I tried to install both, it left my system broken due to dependencies conflict.

 

24 minutes ago, GeckoX said:

2. Also, when I enter Armbian-Config, it seems unstable and crash. The menu doesn't display. 

Is this after you installed Nextcloud?

 

25 minutes ago, GeckoX said:

3. Other issue, I cannot access my NAS through SSH. It returns "operation timed out"

Are you able to access Helios4 through serial console? Does the network interface connected and got IP?

[system crash Armbian 20.11.4 / 5.9.14-rockchip64]

No, that is not an issue.

Please provide complete serial console log.

 

Is this the first time setup?
Did you upgraded from previous version?
Where did you install the Armbian, eMMC or micro SD card?

 

[Unable to connect helios64 to router]

Providing logs with 

armbianmonitor -U

 helps with troubleshooting and significantly raises chances that issue gets addressed.

copy paste the log here

 

 

12 hours ago, Remus said:

I can connect to helios via putty

Did you mean via USB-C serial console?

Which network interface you use? on Armbian 20.11.3, the driver for eth1 (2.5Gb Ethernet) accidentally removed.

Have you tried the 1G ethernet?

 

[system crash Armbian 20.11.4 / 5.9.14-rockchip64]

@jlaurencin it's just a warning, not a problem.

https://www.denx.de/wiki/view/DULG/WarningBadCRCUsingDefaultEnvironment

[Can't access OMV after first install]

@Niglix How did you install the OMV? using armbian-config?

The installation process took roughtly half an hour. You can use serial console to access your Helios64 if for some reason the network down.

 

You would also see screen like this in serial console after OMV installed

Spoiler

Starting kernel ...



openmediavault 5.5.17-3 (Usul) helios64 ttyS2
Copyright (C) 2009-2020 by Volker Theile. All rights reserved.

To manage the system visit the openmediavault web control panel:

eth0: 192.168.0.124
eth0: 2002:c0a8:10a:1:6662:66ff:fed0:17c
eth0: fe80::6662:66ff:fed0:17c

By default the web control panel administrator account has the
username 'admin' and password 'openmediavault'.
It is recommended that you change the password for this account
within the web control panel or using the 'omv-firstaid' CLI
command.

For more information regarding this appliance, please visit the
web site: https://www.openmediavault.org

helios64 login: 

 

 

[How to use a Buzzer on Helios64 P4 header]

The buzzer pin on Helios64 is designed for active buzzer. The one on your photo is passive buzzer.

Passive buzzer requires the system to generate tone while the active one, system just need to supply power (on/off switch). The buzzer itself that generate the tone.

 

you can buy the passive buzzer at electronic component store, the one that sell Arduino etc.

[Unable to boot Helios64 after update to 5.9.14-rockchip64]

@obynio since you have a Linux system, could you modified the /boot/armbianEnv.txt ?

add following lines
 

console=serial
earlycon=on
extraargs=ignore_loglevel

 

you could modify the file on the sdcard if you are going to test with sd card.

or you could also modify the file on eMMC by mounting it in ums mode.

 

[eth1 (2.5) vanished: Upgrade to 20.11.3 / 5.9.14-rockchip64]

Apparently @Igor removed the driver in this commit.

The driver in mainline kernel, only support RTL8152/R8153

 

Spoiler

module not loaded

root@helios64:~# lsmod | grep r8152
root@helios64:~#

 

modinfo, return built in kernel module

root@helios64:~# modinfo r8152
filename:       /lib/modules/5.9.14-rockchip64/kernel/drivers/net/usb/r8152.ko
version:        v1.11.11
license:        GPL
description:    Realtek RTL8152/RTL8153 Based USB Ethernet Adapters
author:         Realtek linux nic maintainers <nic_swsd@realtek.com>
firmware:       rtl_nic/rtl8153b-2.fw
firmware:       rtl_nic/rtl8153a-4.fw
firmware:       rtl_nic/rtl8153a-3.fw
firmware:       rtl_nic/rtl8153a-2.fw
srcversion:     48B8817DA3B8BFDCEB9CE7C
alias:          usb:v2357p0601d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v2357p0601d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0955p09FFd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0955p09FFd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v13B1p0041d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v13B1p0041d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFpA387d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFpA387d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp7214d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp7214d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp720Cd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp720Cd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp7205d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp7205d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp3082d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp3082d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp3069d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp3069d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp3062d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp3062d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp304Fd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp304Fd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v04E8pA101d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v04E8pA101d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v045Ep0927d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v045Ep0927d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v045Ep07C6d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v045Ep07C6d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v045Ep07ABd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v045Ep07ABd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8153d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8153d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8152d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8152d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8050d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8050d*dc*dsc*dp*icFFisc*ip*in*
depends:
intree:         Y
name:           r8152
vermagic:       5.9.14-rockchip64 SMP preempt mod_unload aarch64
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        6C:BA:7A:89:0A:75:61:DC:2D:05:7A:61:7C:E3:6E:B9:F0:2A:D8:94
sig_hashalgo:   sha1
signature:      AC:70:32:E7:D9:5B:7B:56:07:D9:9D:07:D8:4F:BB:A9:14:10:F3:23:
                62:B0:07:66:F6:A5:51:34:86:D7:8C:C5:D7:57:A0:3D:1E:B4:B1:13:
                F1:69:14:72:B1:15:93:9E:69:6A:84:02:EE:ED:8B:3D:A9:3D:34:5D:
                32:38:3F:A0:51:A7:8F:B1:13:DD:42:4A:F3:08:8C:E5:C1:53:18:D8:
                CC:3F:E2:A7:0B:C3:41:A2:EC:4A:61:5A:A9:CC:26:47:A8:09:EA:8D:
                03:01:D4:0F:90:5A:4C:87:DA:15:3C:65:11:9D:15:61:58:54:C1:68:
                44:39:10:18:47:8D:A4:C2:68:6F:2B:D9:08:29:2B:60:C4:CC:36:6A:
                89:1A:EE:17:56:E9:E5:D6:7B:A3:F4:0A:79:B5:F3:36:64:46:E9:A8:
                F4:93:11:BA:34:E6:73:AA:C1:03:1C:4F:17:2C:D6:9B:C4:C1:8E:73:
                95:2F:41:C5:E8:3A:EA:B2:22:57:02:C0:CD:F4:DE:D1:B2:0E:C4:41:
                40:6B:76:44:21:6A:E3:A5:AC:9D:EF:D8:EA:17:EE:D5:36:7C:E7:56:
                3A:36:67:DB:A3:C7:C0:DD:98:B5:8F:68:4A:3B:4F:2E:8A:08:E1:22:
                64:D0:D0:4D:DA:AE:04:9B:1E:5D:FC:CE:25:94:6B:0A:9E:57:29:2C:
                CD:33:F9:20:25:63:9A:A9:FA:80:7C:38:BF:68:DC:40:49:A2:50:D2:
                D1:08:94:9A:B8:F3:2D:C3:27:CF:E3:91:C8:22:38:63:B0:1B:E4:C5:
                37:F3:5A:84:79:C0:3D:04:53:09:98:9E:6B:E4:31:F4:C8:BA:55:28:
                95:F2:91:EC:1B:BE:B5:3A:17:DD:43:C3:9E:01:51:CA:10:E5:60:1F:
                76:E7:71:D2:D9:98:15:A8:DE:01:41:DA:E9:A2:D7:92:FB:8B:EB:84:
                26:25:B0:D8:A0:F9:82:81:32:BB:B1:C0:67:52:05:34:48:C8:05:28:
                F7:1B:0B:07:A0:24:BE:76:25:27:4D:CA:57:52:F2:AD:D2:02:53:0F:
                0F:2C:E2:BE:98:BC:A1:8B:F3:F8:23:2B:A4:27:C1:E5:3E:C8:7F:4B:
                CC:4D:CB:20:96:2F:BF:8D:FD:36:57:E8:18:C9:B8:49:5B:D8:58:7B:
                7E:1F:1F:2C:D0:CF:5F:41:EE:EB:B8:D0:82:D0:AC:0A:DB:7A:50:39:
                14:5D:E3:E3:C0:02:C7:F6:F1:C9:DF:C0:27:F7:C1:7D:82:27:24:5E:
                A7:4B:D8:8F:53:2E:5D:60:47:EF:9C:9B:71:81:B1:E5:39:CF:DA:AE:
                54:25:54:C6:3D:29:6B:2F:DA:73:84:B8
parm:           ledsel:Override default LED configuration (int)

 

 

[lan only showing orange light not connecting to network]

@Cpz, Orange light up if the link speed 1G (and 2.5G on eth1) and green if the link speed is 10/100M. either led will blink/flashing when there is network activity.

As already suggested by @m11k, you should get log from serial console.

 

[USB C to display]

@0utc45t, try legacy image. if it still not working, make sure your cable has converter chip inside.

There are at least 2 standards regarding display signal in USB Type-C. one is DisplayPort Alternate Mode, which is the one supported on Helios64 (RK3399) and the other one is HDMI Alt mode.

If you have cable that use HDMI Alt mode, it won't work on Helios64.

 

@RussianNeuroMancer,

yes. on legacy, HDMI+Hub combo working fine. The problem with mainline driver, it does not support OTG. You have to define the port as "host" or "peripheral" in device tree.

That PR comment, before i knew https://github.com/armbian/build/pull/2299

HDMI+hub combo working fine in LK5.9 if you also enable rockchip-dwc3-0-host overlay.

[Ethernet 1Gbps often disconnects on Legacy kernel]

there are several other packages than 'linux-current-image' to switch. You could use armbian-config > System > Other to switch to current.

That being said, we are still recommend to do fresh install using CURRENT image rather than switch from LEGACY.

[Reboot not working properly with OMV]

@mortomanos do you have other Linux system ? edit the boot/armbianEnv.txt and add

extraargs=ignore_loglevel

 

[Ethernet 1Gbps often disconnects on Legacy kernel]

I don't recall if i ever have issue with 1G ethernet.
Was it idle?

 

 

regarding USB-C support, what do you want to do? Currently the only issue with USB C support in LK 5.9 is switching role "on the fly".

 

[XOR on Helios 4]

yes, mv_xor loaded late. i think after async_tx loaded.

mdadm RAID5 use the xor engine

[Reboot not working properly with OMV]

@mortomanos Did you manage to see the problem in serial console?

[2.5G Ethernet crash (r8152)]

@FloBaoti you can get 2.14 source from https://github.com/wget/realtek-r8152-linux

and compile using docker similar like in this thread

[SSD Unexpected_Power_Loss / POR_Recovery_Count on Reboot]

 

On 11/30/2020 at 8:01 PM, ShadowDance said:

Edit: Side-question, is it actually necessary to power cycle the drives during reboot? Or could they be left running? Might that require changes to u-boot perhaps?

Maybe it is not necessary and rely on SATA soft reset. U-Boot definitely needs to be modified to differentiate reboot and power on.

 

 

 

[ft230x and fan spins]

That is strange. First it won't stop after shutdown, then now it won't run at all.

 

On 11/30/2020 at 7:39 AM, Lago said:

i tried the following and bot fans are are stopped and neither turn on.

when it stopped? after running sudo systemctl stop fancontrol ? or since power on?

[USB-C DAS (Is it or is it NOT supported?)]

@Z06Frank you can create the file at your home (~) folder,  the armbian-add-overlay will do the rest

[Only HDD 1 & 2 power up]

yes, TDM3421 is implemented as high-side switch.

According to your measurement, indeed, the MOSFET seems faulty

[Armbian 20.11 on Helios64.... Feedback?]

@Zageron run

echo ledtrig-netdev | sudo tee -a /etc/modules

add the modules into auto load list.

 

apparently /etc/modules is not modified during upgrade.

[Armbian 20.11 on Helios64.... Feedback?]

Yes, you can upgrade to 20.11.