barnumbirr

Hello, I wasn't clear enough indeed: I'm selling my Helios64 and am gauging interest on here before I put ut up for sale on /r/homelabsales and the likes. Drop me a DM and we'll talk

Sold on Reddit. Hello, looking at selling my Helios64. Mostly looking at getting a price check (what's the device still worth) and gauging interest. Device is in pristine condition, standard fans were swapped for Noctua NF-A8. (standard fans will be included) I'd prefer to keep this EU only as shipping is going to be a pain.

Haven't tried it myself. There is an Ubuntu Hirsute based image running kernel 5.13.x available for download if you want to give it a spin.

Stable kernel for the Helios64 (rockchip64) is kernel 5.10, edge is kernel 5.13.

Finally managed to catch something. Had to reset the device after this: [150372.308197] Unable to handle kernel paging request at virtual address ffff0001f77bd7bf [150372.308900] Mem abort info: [150372.309153] ESR = 0x96000005 [150372.309431] EC = 0x25: DABT (current EL), IL = 32 bits [150372.309903] SET = 0, FnV = 0 [150372.310178] EA = 0, S1PTW = 0 [150372.310461] Data abort info: [150372.310720] ISV = 0, ISS = 0x00000005 [150372.311063] CM = 0, WnR = 0 [150372.311333] swapper pgtable: 4k pages, 48-bit VAs, pgdp=000000000366b000 [150372.311925] [ffff0001f77bd7bf] pgd=00000000f7ff9003, p4d=00000000f7ff9003, pud=0000000000000000 [150372.312697] Internal error: Oops: 96000005 [#1] PREEMPT SMP [150372.313192] Modules linked in: softdog governor_performance cfg80211 rfkill r8152 snd_soc_hdmi_codec snd_soc_rockchip_i2s snd_soc_core snd_pcm_dmaengine snd_pcm rockchip_rga hantro_vpu(C) leds_pwm rockchip_vdec(C) snd_timer fusb302 videobuf2_dma_sg videobuf2_vmalloc tcpm snd gpio_charger v4l2_h264 panfrost videobuf2_dma_contig typec v4l2_mem2mem rockchipdrm soundcore videobuf2_memops videobuf2_v4l2 videobuf2_common gpu_sched dw_mipi_dsi videodev dw_hdmi mc analogix_dp drm_kms_helper cec sg rc_core drm drm_panel_orientation_quirks cpufreq_dt gpio_beeper ledtrig_netdev lm75 dm_mod sunrpc ip_tables x_tables autofs4 raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx realtek md_mod dwmac_rk stmmac_platform stmmac pcs_xpcs adc_keys pwm_fan [150372.319348] CPU: 5 PID: 2769 Comm: rtorrent main Tainted: G C 5.10.60-rockchip64 #21.08.1 [150372.320178] Hardware name: Helios64 (DT) [150372.320531] pstate: 20000085 (nzCv daIf -PAN -UAO -TCO BTYPE=--) [150372.321074] pc : __mod_zone_page_state+0x50/0x108 [150372.321494] lr : __mod_zone_page_state+0x3c/0x108 [150372.321914] sp : ffff8000167db4f0 [150372.322212] x29: ffff8000167db4f0 x28: 0000000000000001 [150372.322687] x27: 0000000000000020 x26: ffff0000f77d9100 [150372.323160] x25: 0000000000000001 x24: ffff0000f77d9e00 [150372.323634] x23: 00000000ffff8000 x22: ffff8001115757bf Now that the Kobol team has pulled the plug, I doubt these issues will ever get fixed.

Seems risky to me to upgrade now: Bullseye support is coming but might take a few months. I'll stick with Buster for now as I already have enough stability issues.

I might have missed something but it looks to me like voltage tweaks are no longer required according to gprovost's comment from March 10th.

Wut?

I've had a secondary device connected to my Helios64 over serial for the last couple of months. Unfortunately, even at verbosity 7 it dies so suddenly that the output doesn't actually provide any valuable information: Starting kernel ... [ 2.721938] cacheinfo: Unable to detect cache hierarchy for CPU 0 [ 2.881028] vcc3v3_sys_s0: failed to get the current voltage: -EPROBE_DEFER [ 2.900490] dw_wdt ff848000.watchdog: No valid TOPs array specified [ 3.012992] dwmmc_rockchip fe320000.mmc: All phases bad! [ 3.013479] mmc1: tuning execution failed: -5 [ 3.013881] mmc1: error -5 whilst initialising SD card [ 3.135010] dwmmc_rockchip fe320000.mmc: All phases bad! [ 3.135502] mmc1: tuning execution failed: -5 [ 12.521811] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed [ 15.212309] dw-apb-uart ff1a0000.serial: forbid DMA for kernel console [ 17.035708] lm75 2-004c: supply vs not found, using dummy regulator [ 18.572536] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW [ 18.817621] OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22 [ 18.833386] OF: graph: no port node found in /syscon@ff770000/usb2-phy@e450/otg-port [ 19.262970] [drm] unsupported AFBC format[3231564e] [ 19.366283] rockchip_vdec: module is from the staging directory, the quality is unknown, you have been warned. [ 19.410603] r8152 4-1.4:1.0 (unnamed net_device) (uninitialized): netif_napi_add() called with weight 256 [ 19.421732] hantro_vpu: module is from the staging directory, the quality is unknown, you have been warned. [ 24.903650] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 helios64 login: DDR Version 1.24 20191016 In soft reset SRX channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 This is what my uptime looks like over the last 90 days. Again, none of the reboots were triggered by me. Reboots wouldn't be such a pain the backside on their own if 90% of them didn't retrigger a mdadm RAID resync...

Strange that the website doesn't display properly for you. You might have a rogue extension installed. Here's a screenshot of installation step number 7, which is the step that takes care of fans.

Helios64 assembly instructions have you mount the fans as to pull fresh air trough the front grill: https://wiki.kobol.io/helios64/kit/#step-7-install-back-panel

Had the issue happen semi-regularly to my Helios as well. Same "gibberish" saved to ArmbianEnv.txt as in your example. Haven't been able to figure out where the issue comes from unfortunately.

Good shout, my Helios64 is unfortunately in a location where I can't easily plug in another computer to get serial access. Might try to dig out an old RPi...

This is what my uptime looks like. OMV5, plex and r/rutorrent with 5 12TB WDC disks (LVM). None of these reboots were triggered by me... Wish I could find were the problem lies, can't read the logs for debugging as the reboot is so abrupt that nothing gets written to disk.

Nicely done. Corruption of the armbianEnv.txt file is one of the remaining nagging issues on the Helios64. I suspect it is linked to the system instability but I've not been able to pinpoint the exact issue so far.

Can you try to boot from the SD card again, mount the eMMC and edit the /boot/armbianEnv.txt to increase verbosity (defaults to 1 which means less verbose, maximum value is 7). Please then post the logs.

I've already asked the question on Twitter but I'll ask here as Twitter might not be everyone's cup of tea:

Try and restart your Helios64 while connected to it via serial, you should then see the boot logs. If you need to increase verbosity of said logs, edit your armbianEnv.txt to contain the following: armbianEnv.txt Report back with the logs. Hope this helps.

Try kernel 5.10.16, that seems to fix most of the stability issues for me compared to 5.10.12.

My system is on a microSD card as armbian-config never managed to configure the eMMC correctly (never took the time to debug the issue unfortunately). My system did crash at some point while I was at work today but no logs have a trace of the crash. System just froze, solid blue 'System' LED. I'll probably downgrade to an earlier kernel...

SOLVED!!! Of course this was due to armbianEnv.txt being corrupt. Restoring the file from backups allows the device to boot cleanly again.

Just applied the latest update to my Helios64, here is what apt reported: The following packages will be upgraded: armbian-config armbian-firmware base-files device-tree-compiler file iproute2 libcairo2 libgnutls30 libgnutls30:armhf libmagic-mgc libmagic1 libnss-myhostname libpam-systemd libsystemd0 libudev1 linux-buster-root-current-helios64 linux-dtb-current-rockchip64 linux-image-current-rockchip64 linux-u-boot-helios64-current systemd systemd-sysv udev unzip This went just fine until it tried to setup systemd, the Helios then lost all network connection: Tried rebooting, no luck. Can't get a serial console up and running as it won't go past 'Starting kernel...' The blue 'System' LED is on but doesn't blink. What can I do to help debug/fix this?

No, don't need to perform fix if you're only ever going to use the 1Gbps interface AFAIK.

I've been running into the same issue for about a week or two, haven't had the time to dig into it though. armbian-config says the "Boot from eMMC - System on eMMC" step went fine but device won't boot after that. Haven't hooked a serial cable to it to see where it fails.

From the wiki: Source: https://wiki.kobol.io/helios64/sata/#sata-controller-diagram