19 19

About This Club

Dedicated section for talk & support for the Helios4 and Helios64 open source NAS. Lead and moderated by the Kobol Team.
  1. What's new in this club
  2. check that eMMC boot/armbianEnv.txt contains: verbosity=1 bootlogo=false overlay_prefix=rockchip rootdev=UUID=a79a14c0-3cf4-4fb9-a6c6-838571351371 rootfstype=ext4 overlays=dwc3-0-host usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u Note rootdev=UUID= will be different. You can check your by running sudo blkid from the sdcard os. I believe yours is fine so you could also: fsck /dev/mmcblk2p1 when booting from sdcard (booting kernel that has the emmc fix only ! your log shows 5.10.63 armbian 22.08.2 so your are fine. But double check before fscking). Fscking will tell you if the filesystem is fine (readable/mountable by for one u-boot itself to start the kernel). My mmcblk2p1 boot/armbianEnv.txt content was wrong as I ran fsck when my emmc was unstable (this was a bad idea). Thus u-boot was unable to start the system. Restoring armbianENv.txt fixed my boot. The red is fine it is color for deb file type. just a note. The steps were to download from : root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-dtb-current-rockchip64_21.05.4_arm64.deb root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-headers-current-rockchip64_21.05.4_arm64.deb root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-image-current-rockchip64_21.05.4_arm64.deb not 5.10.63 ... but 5.10.63 will be fine too per ie 21.08.2 has the emmc fix.
  3. Hi folks, I am wondering if somebody with a mac enviroment has a decent / performant samba connectivity? After I upgraded to Big Sur I have severe issues with the samba protocol when accessing my shares on the helios running openmediavault. I know that Apple had made some changes with samba but there might be some users that dug a little bit deeper and could give me a hint. I did try it with different settings in the extra options over the past weeks but with no luck so far. Sidenote: Also NFS is terribly slow and laggy. I am back with AFP connection now that does the job perfectly and fast.
  4. ended up re-installing and all good, but i'd like to know what caused it, looks to be GPT sig wrong
  5. You can check the trigger settings on the led. Something along 'cat /sys/class/leds/helios64:blue:net/trigger'
  6. Last night I shutdown my Helios 64 (sudo shutdown now) but when i went to boot it this morning, after startup it looks to be hung, all blue lights solidly on. It's set to run from the micro SD card, so wondering if i hit a R/W limit on that. Serial log below, it doesn't progress beyond "starting kernel" I can mount the MicroSD on my ubuntu box and read the file structure DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 928MHZ channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 928 MHz, current 856MHz OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 254 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=60906MB FwPartOffset=2000 , 0 StorageInit ok = 76288 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xe5b60 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.10-armbian (Mar 08 2021 - 14:54:58 +0000) 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 Net: eth0: ethernet@fe300000 scanning bus for devices... starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe380000 for devices... 1 USB Device(s) found scanning bus dwc3 for devices... cannot reset port 4!? 4 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 5 ms (622.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 166 bytes read in 5 ms (32.2 KiB/s) 15755777 bytes read in 674 ms (22.3 MiB/s) 28582400 bytes read in 1212 ms (22.5 MiB/s) 81913 bytes read in 13 ms (6 MiB/s) Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr' Moving Image from 0x2080000 to 0x2200000, end=3de0000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15755713 Bytes = 15 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f4fe9000, end f5eef9c1 ... OK Loading Device Tree to 00000000f4f6c000, end 00000000f4fe8fff ... OK Starting kernel ...
  7. Yes, you are right. Didn't notice that. I also see an odd flash here and there but doesn't seem to be related to the network activity at all.
  8. Hi @prahal, thank you for helping me ! So, I have remove the jumper cap and the MicroSD card, but the boot from eMMC doesn’t work. This is what I have when I try to start from eMMC : ... and the kernel never start. (The System activity LED of the Front Panel is blue still. It’s not blinking.) When I boot from the MicroSD card (with the command « run bootcmd_mmc1 »), it’s working. When I boot from the MicroSD card, at the step 5 of the @TDCroPower’s message (https://forum.armbian.com/topic/18855-upgrading-to-bullseye-troubleshooting-armbian-21081/?do=findComment&comment=128305 ), I see this (I don’t know if it’s normal, especialy what is in red) : ( Maybe I have made a mistake because when I have do the step 6 of @TDCroPower’s message, I only « wget » 3 packages of this link : http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.63-rockchip64/ : linux-dtb-current-rockchip64_21.08.2_arm64.deb , linux-headers-current-rockchip64_21.08.2_arm64.deb and linux-image-current-rockchip64_21.08.2_arm64.deb. I didn’t « wget » the 3 packages « 21.05.9 ». (But, when i have try the downgrading with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image on my MicroSD, i have « wget » all the three packages of http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.35-rockchip64/ . But it was not working neither....) )
  9. Hi fri.K, it definitively looks like a driver issue (something goes wrong in rtl8152_post_reset)... I will try to debug further based on your information. I'm also wondering if there's an issue with power consumption when using both NIC (attached the image of my fix for 1Gbps)... cable size (AWG) and length could be an issue? Will try to test also an external USB-RTL8152 dongle to see if the same driver works.
  10. Hi jotapesse, yes same for me ... but on closer inspection ... the flashing of the LAN activity light no longer seems to be tied to real network activity! 1/ It flashes a lot less than it used to do. 2/ If I download a large movie file from the Helios64 to my PC I occasionally see a brief flash, but not the sustained activity that I'd expect from a download that takes several minutes. 3/ Inspecting my network router, I can see constant low level activity on the Helios64 ip address (I only have one ethernet cable attached to the Helios64) but don't see any flashing LED. So in conclusion ... its still not working properly!
  11. Nearly at 300€ already, getting too pricey for me, sorry guys :/
  12. If you boot from sdcard while your previous system was on eMMC the ssh identification is different. If you want to connect to the sd card rescue system: ssh -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no -o "PasswordAuthentication yes" root@helios64 I mean if your system is on eMMC and you boot from a sd card rescue system you have to tell ssh to ignore the host (and force password auth because the sd card system will not have public kay auth set up). about the failure at step 10 ... you should remove the sd card before boot (and your jumper mod) to boot from eMMC and all should be fine. Mind the process you followed did not tell to set the jumper 10 because it tells to switch boot media via u-boot prompt a command "run bootcmd_mmc1" for sd and "run bootcmd_mmc0" for eMMC. Doing both jumper 10 and u-boot bootcmd_mmc1 is undefined. Simply do one or the other not both. Cheers
  13. Hi everyone! Just to let you all know that I have updated today my Helios64 to Armbian 21.08.3 Bullseye and the "LAN" front panel led now works again. :-) Great!
  14. Hello everyone, I am currently trying to repair my Helios64. I exposed my problem in this topic : A member ( @IcerJo ) said that this problem could be related to this topic. So I read the posts of this topic looking for a solution. I removed the hard drives from my NAS (to avoid a false manipulation) and I opened it (to be able to force the boot from the microSD with the jumper cab P10). Then I followed the instructions of the @TDCroPower message (here : Unfortunately, it didn't work. My NAS refuses to boot from the eMMC (fail at step 10 of the @TDCroPower message). Note that I tried 2 times these instructions: first with the Armbian_21.08.2_Helios64_buster_current_5.10.63 image. Then with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image. My current version is: Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64 and my NAS can only boot from the MicroSD card. Moreover, I can only communicate with it through the usb−usb-c cable, via picocom. SSH doesn’t work (I have an error message " WARNING: remote host identification has changed! "...). Concerning the boot from the eMMC, I understood that it was maybe necessary to refresh the bootloader on eMMC. I didn’t understand very well the procedure to follow to make such thing. I went to armbian-config > System > Install > 5 - Install/Update the bootloader on SD/eMMC, then I rebooted... but nothing. Here is what picocom returns when I try to boot from the eMMC: I'm a little bit lost. I don't understand much about it. Does anyone have a clue for me? Whether the NAS runs on eMMC or MicroSD doesn't really matter to me. I just want to be able to get a working NAS and recover the data from my hard drives (previously configured with OpenMediaVault). Thank you very much, everyone.
  15. Thank you, @IcerJo. I will try this today or tomorrow ! Two questions, please : 1/ Can I do this without fear for my data (I have 2 RAID1 encrypted with LUKS encryption plugin from OpenMediaVault) ; 2) Can I do this not with a previous Helios64 image (like the Linux 5.10.43-rockchip64) but with a more recent (like the 5.10.63 or the 5.10.64) ? I’m not sure but it’s seem that @alchemist have do this here :
  16. Problem looks very similar like on Odroid N2 SBC with the same SoC RK3399 [ 3.946307] kernel: meson8b-dwmac ff3f0000.ethernet: IRQ eth_wake_irq not found [ 3.947735] kernel: meson8b-dwmac ff3f0000.ethernet: IRQ eth_lpi not found [ 3.959955] kernel: meson8b-dwmac ff3f0000.ethernet: PTP uses main clock [ 3.960322] kernel: meson8b-dwmac ff3f0000.ethernet: no reset control found [ 3.987067] kernel: meson8b-dwmac ff3f0000.ethernet: User ID: 0x11, Synopsys ID: 0x37 [ 3.988569] kernel: meson8b-dwmac ff3f0000.ethernet: DWMAC1000 [ 3.993813] kernel: meson8b-dwmac ff3f0000.ethernet: DMA HW capability register supported [ 4.008458] kernel: meson8b-dwmac ff3f0000.ethernet: RX Checksum Offload Engine supported [ 4.017824] kernel: meson8b-dwmac ff3f0000.ethernet: COE Type 2 [ 4.038408] kernel: meson8b-dwmac ff3f0000.ethernet: TX Checksum insertion supported [ 4.045460] kernel: meson8b-dwmac ff3f0000.ethernet: Wake-Up On Lan supported [ 4.056526] kernel: meson8b-dwmac ff3f0000.ethernet: Normal descriptors [ 4.070716] kernel: meson8b-dwmac ff3f0000.ethernet: Ring mode enabled [ 4.076492] kernel: meson8b-dwmac ff3f0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 4.076496] kernel: meson8b-dwmac ff3f0000.ethernet: device MAC address 00:11:22:33:44:FF [ 97.207023] kernel: meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] (irq=42) [ 97.209362] kernel: meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found [ 97.209373] kernel: meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW [ 97.209582] kernel: meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode [ 100.670345] kernel: meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 100.677458] kernel: meson8b-dwmac ff3f0000.ethernet eth0: Link is Down [ 100.819033] kernel: meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] (irq=42) [ 100.861699] kernel: meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found [ 100.861714] kernel: meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW [ 100.861727] kernel: meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode If I manually try to activate a bit different USB card on Helios64 I got this: # nmcli conn up Team0 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/8) root@helios64:~# [179508.201299] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP [179508.201798] Modules linked in: macvlan veth nf_conntrack_netlink xfrm_user xfrm_algo br_netfilter bridge aufs team_mode_loadbalance team governor_performance rfkill cdc_ether usbnet xt_conntrack nft_counter nft_chain_nat xt_nat xt_tcpudp zram xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat nf_tables nfnetlink r8152 snd_soc_hdmi_codec ftdi_sio usbserial snd_soc_rockchip_i2s snd_soc_core gpio_charger rockchip_vdec(C) snd_pcm_dmaengine hantro_vpu(C) rockchipdrm snd_pcm leds_pwm pwm_fan dw_mipi_dsi snd_timer panfrost rockchip_rga v4l2_h264 dw_hdmi snd videobuf2_dma_contig analogix_dp soundcore videobuf2_dma_sg gpu_sched v4l2_mem2mem fusb302 drm_kms_helper videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 tcpm videobuf2_common cec videodev rc_core typec mc drm sg drm_panel_orientation_quirks gpio_beeper cpufreq_dt nfsd auth_rpcgss nfs_acl lockd grace ledtrig_netdev lm75 sunrpc ip_tables x_tables autofs4 raid10 raid1 raid0 multipath linear raid456 [179508.201952] async_raid6_recov async_memcpy async_pq async_xor async_tx md_mod uas realtek dwmac_rk stmmac_platform stmmac pcs_xpcs adc_keys [179508.210617] CPU: 4 PID: 1029 Comm: kworker/4:42 Tainted: G C 5.10.63-rockchip64 #21.08.2 [179508.211445] Hardware name: Helios64 (DT) [179508.211809] Workqueue: usb_hub_wq hub_event [179508.212187] pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--) [179508.212732] pc : rtl8152_post_reset+0x1d4/0x1e0 [r8152] [179508.213201] lr : rtl8152_post_reset+0x3c/0x1e0 [r8152] [179508.213658] sp : ffff80001958bbd0 [179508.213959] x29: ffff80001958bbd0 x28: ffff00000754f800 [179508.214435] x27: 0000000000000010 x26: 0000000000000000 [179508.214911] x25: ffff000007610b20 x24: 00000000ffffffed [179508.215387] x23: 0000000000000000 x22: ffff000007885000 [179508.215863] x21: ffff000007464800 x20: ffff8000118b9948 [179508.216339] x19: ffff000007885980 x18: ffff8000118dee10 [179508.216815] x17: 0000000000000000 x16: 0000000000000000 [179508.217291] x15: 0000000000000428 x14: ffff80001958b790 [179508.217765] x13: 00000000ffffffea x12: ffff80001194ee48 [179508.218241] x11: 0000000000000003 x10: ffff800011936e08 [179508.218716] x9 : ffff800011936e60 x8 : 0000000000017fe8 [179508.219192] x7 : c0000000ffffefff x6 : 0000000000000001 [179508.219668] x5 : 0000000000000001 x4 : 0000000000000000 [179508.220144] x3 : 0000000000000001 x2 : b9eafe8d9839b500 [179508.220619] x1 : 0000000000000000 x0 : 0000000000000010 [179508.221096] Call trace: [179508.221324] rtl8152_post_reset+0x1d4/0x1e0 [r8152] [179508.221761] usb_reset_device+0x128/0x258 [179508.222122] hub_event+0xe94/0x1618 [179508.222439] process_one_work+0x1ec/0x4d0 [179508.222801] worker_thread+0x48/0x478 [179508.223133] kthread+0x140/0x150 [179508.223428] ret_from_fork+0x10/0x34 [179508.223752] Code: d2800100 910042a3 14009623 17ffffdc (d4210000) [179508.224297] ---[ end trace 087e94c7a84ef6dd ]--- [179508.224711] note: kworker/4:42[1029] exited with preempt_count 1 [179508.225383] ------------[ cut here ]------------ [179508.225812] WARNING: CPU: 4 PID: 0 at kernel/rcu/tree.c:624 rcu_eqs_enter.isra.63+0x138/0x140 [179508.226564] Modules linked in: macvlan veth nf_conntrack_netlink xfrm_user xfrm_algo br_netfilter bridge aufs team_mode_loadbalance team governor_performance rfkill cdc_ether usbnet xt_conntrack nft_counter nft_chain_nat xt_nat xt_tcpudp zram xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat nf_tables nfnetlink r8152 snd_soc_hdmi_codec ftdi_sio usbserial snd_soc_rockchip_i2s snd_soc_core gpio_charger rockchip_vdec(C) snd_pcm_dmaengine hantro_vpu(C) rockchipdrm snd_pcm leds_pwm pwm_fan dw_mipi_dsi snd_timer panfrost rockchip_rga v4l2_h264 dw_hdmi snd videobuf2_dma_contig analogix_dp soundcore videobuf2_dma_sg gpu_sched v4l2_mem2mem fusb302 drm_kms_helper videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 tcpm videobuf2_common cec videodev rc_core typec mc drm sg drm_panel_orientation_quirks gpio_beeper cpufreq_dt nfsd auth_rpcgss nfs_acl lockd grace ledtrig_netdev lm75 sunrpc ip_tables x_tables autofs4 raid10 raid1 raid0 multipath linear raid456 [179508.226715] async_raid6_recov async_memcpy async_pq async_xor async_tx md_mod uas realtek dwmac_rk stmmac_platform stmmac pcs_xpcs adc_keys [179508.235375] CPU: 4 PID: 0 Comm: swapper/4 Tainted: G D C 5.10.63-rockchip64 #21.08.2 [179508.236156] Hardware name: Helios64 (DT) [179508.236511] pstate: 20000085 (nzCv daIf -PAN -UAO -TCO BTYPE=--) [179508.237046] pc : rcu_eqs_enter.isra.63+0x138/0x140 [179508.237474] lr : rcu_eqs_enter.isra.63+0x1c/0x140 [179508.237894] sp : ffff800011cebf10 [179508.238194] x29: ffff800011cebf10 x28: 0000000000000000 [179508.238671] x27: 0000000000000000 x26: ffff000000710e80 [179508.239147] x25: 0000000000000000 x24: ffff800011307b40 [179508.239623] x23: ffff80001157e978 x22: ffff8000118b9948 [179508.240097] x21: ffff8000118ba2e8 x20: ffff8000118b99c8 [179508.240573] x19: ffff800011580a40 x18: 0000000000000004 [179508.241049] x17: 0000000000000001 x16: 0000000000000019 [179508.241524] x15: ffff8000118da498 x14: 000000000000015a [179508.242000] x13: 0000000000000000 x12: 0000000000000001 [179508.242476] x11: 0000000000000040 x10: ffff8000118d9c98 [179508.242952] x9 : ffff8000118d9c90 x8 : ffff000000800028 [179508.243428] x7 : 0000000000000000 x6 : 000003eb30cab0ae [179508.243904] x5 : 00ffffffffffffff x4 : ffff8000e6226000 [179508.244380] x3 : 0000000000000001 x2 : 4000000000000000 [179508.244854] x1 : 4000000000000002 x0 : ffff0000f77a6a40 [179508.245330] Call trace: [179508.245556] rcu_eqs_enter.isra.63+0x138/0x140 [179508.245956] rcu_idle_enter+0x10/0x20 [179508.246286] default_idle_call+0x40/0x1bc [179508.246646] do_idle+0x204/0x278 [179508.246939] cpu_startup_entry+0x24/0x60 [179508.247295] secondary_start_kernel+0x168/0x178 [179508.247700] ---[ end trace 087e94c7a84ef6de ]---
  17. H, I'm also facing issues teaming and bonding both NICs in Helios64. Similar configuration works on Helios4 (second NIC added vie USB 3.0 port). Once 1Gb link sets the speed it crashes and can't be set up: $ dmesg [ 3097.357372] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 3097.357423] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 3097.372171] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down [ 3097.379293] bond0: (slave eth0): Error: Device is in use and cannot be enslaved [ 3097.412528] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL) [ 3097.625230] rk_gmac-dwmac fe300000.ethernet: Failed to reset the dma [ 3097.625246] rk_gmac-dwmac fe300000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed [ 3097.625257] rk_gmac-dwmac fe300000.ethernet eth0: stmmac_open: Hw setup failed [ 3097.676541] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL) [ 3097.885517] rk_gmac-dwmac fe300000.ethernet: Failed to reset the dma [ 3097.885538] rk_gmac-dwmac fe300000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed [ 3097.885554] rk_gmac-dwmac fe300000.ethernet eth0: stmmac_open: Hw setup failed [ 3097.944560] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL) [ 3098.156236] rk_gmac-dwmac fe300000.ethernet: Failed to reset the dma [ 3098.156253] rk_gmac-dwmac fe300000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed [ 3098.156264] rk_gmac-dwmac fe300000.ethernet eth0: stmmac_open: Hw setup failed [ 3098.204543] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL) [ 3098.410564] rk_gmac-dwmac fe300000.ethernet: Failed to reset the dma [ 3098.410581] rk_gmac-dwmac fe300000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed [ 3098.410592] rk_gmac-dwmac fe300000.ethernet eth0: stmmac_open: Hw setup failed [ 3098.556619] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL) [ 3098.768443] rk_gmac-dwmac fe300000.ethernet: Failed to reset the dma [ 3098.768459] rk_gmac-dwmac fe300000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed [ 3098.768465] rk_gmac-dwmac fe300000.ethernet eth0: stmmac_open: Hw setup failed Looking at https://wiki.kobol.io/helios64/ethernet $ ethtool -i eth0 driver: st_gmac version: Jan_2016 firmware-version: expansion-rom-version: bus-info: supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no $ lshw *-network:0 description: Ethernet interface physical id: 7 logical name: eth0 serial: 64:62:FF:FF:FF:FF capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=st_gmac driverversion=Jan_2016 link=no multicast=yes port=twisted pair $ ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Cannot get wake-on-lan settings: Operation not permitted Current message level: 0x0000003f (63) drv probe link timer ifdown ifup Link detected: no $ uname -a Linux nas 5.10.63-rockchip64 #21.08.2 SMP PREEMPT Wed Sep 8 10:57:23 UTC 2021 aarch64 GNU/Linux Is it a kernel bug? If yes, how to debug it further?
  18. Since I got my Helios64 : I had an hadrware problem (voltage on some disk drop too low : it ended : replace MB) But I had many panic/ freeze since first days. I was never able to pass 10 days without problems until I read this topic : Last month I decided to set freq policy as read here : root@helios64:~# cat /sys/devices/system/cpu/cpufreq/policy*/scaling_max_freq 1416000 1416000 root@helios64:~# cat /sys/devices/system/cpu/cpufreq/policy*/scaling_min_freq 1416000 1416000 root@helios64:~# cat /sys/devices/system/cpu/cpufreq/policy*/cpuinfo_cur_freq 1416000 1416000 And I have a much more stable system root@helios64:~# uptime 18:35:42 up 30 days, 1:34, 1 user, load average: 0.01, 0.03, 0.00 root@helios64:~# uname -a Linux helios64 5.10.60-rockchip64 #21.08.1 SMP PREEMPT Wed Aug 25 18:56:55 UTC 2021 aarch64 GNU/Linux root@helios64:~# cat /etc/issue Armbian 21.08.1 Buster \l
  19. Same here, the instability of my Helios64 combined with Armbian not having a test-suite for it (and thus breaking it at any point) lead me to splurge on hardware that cost 4x as much. A NAS should be out of sight and out of mind, not a constant source of worry.
  20. I made an upgrade buster -> bullseye yesterday on Pine64 . It just works . Upgrade needed only if you need some updated software from Bullseye . As for me trigger was mpd (my Pine64 board used mostly as audio player / receiver ) . Sent from my M2007J20CG using Tapatalk
  21. Afaik the problem is that there simply isn't enough power. I (and my friend) just have given up and bought ryzen
  22. Hi, I can confirm having the same problems with CPU freezes. Initially I fixed the problem by setting min CPU frequency = max CPU frequency = 1.4Ghz. This configuration ran very solid. A few days ago I reinstalled my system (due to a different problem) and left the CPU settings on default. I'm now running Kernel 5.10.63-rockchip64. Yesterday I noticed that the system was unresponsive again. Actually the red fault LED was blinking, which I cannot remember that it did before. Unlike documented it was set to trigger on (kernel) panic. Now I set the max CPU frequency to 1.4Ghz, leaving the min CPU frequency at 400Mhz (performance mode). Lets see how this goes... Meanwhile, I'm wondering if anyone heard of an actual fix. Could it actually be a problem with my hardware or is it purely software? And if it is - why are there so little complaints? I mean this system is designed to run 24/7, isn't it? I don't want to complain about Helios64, I'm just trying to understand if there is anything I'm missing out to get around this problem. Many Thanks, Julius
  23. Thank you @Igor, my apologies and thank you for all you and the team do. I plan to donate to Armbian when some of my remodeling projects are done. and That would be swell @Heisath, I did see in the FAQ's that we may not be "supported" Officially but we are in a Community type of support, so if you were able to acquire and run Edge/Nightly that would definitely help out in the long run
  24. Added to watchlist. If it stays cheap enough, I'll buy it. Can't guarantee you "Supported" flag, but I will have it running edge and notice problems
  25. HW is one thing. The biggest part: https://docs.armbian.com/User-Guide_FAQ/#development-time https://docs.armbian.com/User-Guide_FAQ/#support-time This helps a lot more to create value: https://forum.armbian.com/forum/54-help-wanted/ then donating hardware we can usually get for free.
  26. I wonder if someone could buy it and donate it to Armbian for testing so that we could be Supported again? If anyone does buy and donate I will donate to them
  27.