pierre

Hello, Same problem for me: impossible to install update: the following packages have unmet dependencies: armbian-bsp-cli-helios64 So what can we do to fix this bug ? Thank you. Pierre

Hello, well deserved break. (In comparison, the helios4 is not that great. The plastic breaks easily and the disposition of the elements is not practical) A great job. Have a good break!!

Oups sorry. Stupid am I ! The SATA connector has been mounted upside down !! It works wonderfully now ! Sorry.

Hello, we have a strange thing here. Since ... (I don't remember), the tray number 2 is not working. We tried with 3 different disks but each of them, when inserted in tray n2, aren't start. Why ? And how to fix that ? Thank you. PS: other trays (n1, n3, n4, n5) are ok.

So strange, but after these specials characters, I have access to root login. So it is ok for now...

Hi, nobody have these characters problem...? And it isn't ok that after a shutdown the system won't boot up. I imagine I'm not the only one... Regard.

Ok, so I reinstalled on the eMMC card. Apparently it is ok, but impossible to made something with the terminal. When rebooting still same problem with characters... Maybe a language, local problem ? See screenshot (with CRTL-C in the middle)

So I tried to reinstall with the eMMC method and with the classic SDcard method. Still the same, no reaction. Oh yes, when I tried to reset (with the SDcard method), here is the logs: see the screenshot

Hello, here is the logs when I just boot. U-Boot 2020.07-armbian (Dec 15 2020 - 08:45:45 +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 Net: eth0: ethernet@fe300000 scanning bus for devices... 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 8 ms (388.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 166 bytes read in 6 ms (26.4 KiB/s) 15755753 bytes read in 673 ms (22.3 MiB/s) 28582400 bytes read in 1213 ms (22.5 MiB/s) 81913 bytes read in 19 ms (4.1 MiB/s) ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15755689 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 f4fe0000, end f5ee69a9 ... OK Loading Device Tree to 00000000f4f63000, end 00000000f4fdffff ... OK Starting kernel ... And with the "recover" tool U-Boot 2020.07-armbian (Dec 15 2020 - 08:45:45 +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 rockchip_dnl_mode = maskrom mode FATAL: read zero bytes from port term_exitfunc: reset failed for dev UNKNOWN: Input/output error So, nothing really working... Thank you. Regard.

Hello, so we use Kobol 64 with OMV since 4 months, and no problem at all. Just yesterday, want to change Ethernet cable, correctly shutdown the Helios64 NAS, and impossible to start it again. Just have the right system light, but left LED no blinking, no information in the USBC terminal. For the "recovery", press the recovery button, and then press the power button, and the LED System don't light up. What can we do, format the system, and reinstall OMV with all parameters... Not really serious, ins't it ? Thank you for any help. Regard.

Hello, yes I use the last image of ARMbian > Armbian_21.02.1_Helios4_buster_current_5.10.12.img.xz And I tried with another SD card and now there are 2 lights (LED8 + LED1 (blinking)) + the light of the network interface. I have access to root with Picocom. Apparently it was the SD card, which is corrupted, but never have an error message when I format it (long format). Thank you for help. Regard.

Hello, I tried to use again my Helios4, but when we put the power on, only the LED8 light up. This Helios4 was working great a few month ago (before we receive the Helios64 :-) So we removed all sata cables (and fan, and power cables for hard drives) to made new tests. But still the same...:-( And the processor is hot. So, if someone have a idea to fix it. Thank you. Regard.