gprovost

@Magnus Nygren Until hardware encoding engine is fully implemented for rockchip RK3399, it might a bit too much for the processor to handle a full HD transcoding.

@Zageron You could boot in recovery mode in order to expose the Heliso64 eMMC as USB Mass Storage device to a PC connected to Helios64 via the USB-C port. Then on your PC use a tool to clone the exposed USB Storage device. You can use dd for example. dd bs=4M if=/dev/sdb | gzip > image1-`date +%d%m%y`.img.gz Replace /dev/sdb by the path of the exposed USB storage device. But there are many other tools and way to clone, you can find tutorial. The day you need to revert to an old backup you can use again use the recovery mode but this time you burn your backup image to the exposed USB Mass Storage (the eMMC of Helios64).

@SleepWalker You don't want to share your FreeBSD image for others to test also ?

@allen--smithee Based on what you described and your video, the fans type you are using are Type-A while the stock ones are Type-C. Refer to this page to understand the difference : https://wiki.kobol.io/helios64/pwm/#pwm-fan-implementation With Type-A, the fans will always spin, they can't be stopped even at PWM 0.

@aprayoga will help answer in details @retrack question on what is the blocker right now to have WoL working on Heliso64. But in a nutshell is because suspend mode is not supported yet properly. I think we all understood that the question is addressed to us Kobol team, no one was expecting the core Armbian team to follow up on this. So let's move on and not hold any grudge against each other...we are only one to blame to not have answer quickly enough this thread. @Igor Maybe we could delete this exchange above, put that being us.

Hmm good point. Something to keep in view. Issue is already reported by other nextcloud user : https://github.com/nextcloud/richdocuments/issues/1282

We will post soon instruction on our wiki on how to install Nextcloud via docker compose (along side OMV) with reverse proxy (nginx proxy manager). In the meantime find attached the the docker compose files for nextcloud I made. 1/ You will need to adjust the .yml file for the volumes location. 2/ You will need to update db.env to define DB user and password Note: This setup only exposes the port 80 via port host post 9001. It is meant for running behind a reverse proxy which would handle HTTPS. You need to install docker and docker-compose on your machine. Then decompress the attached folder and once inside the folder just do docker-compose up -d nextcloud.tar.gz

We will have some spare stock to sell soon. Yes we ship to China. As for the next batch we will announce our plan soon.

@succo Thanks for the feedback and good to see you found the issue for the fan not spinning which clearly wasn't normal. We didn't design the enclosure for such use case.

Hi, could try to the following tweak and redo the same methods that triggers the crash : Run armbian-config, go to -> System -> CPU And set: Minimum CPU speed = 1200000 Maximum CPU speed = 1200000 CPU governor = performance This will help us understand if instability is still due to DVFS.

Did you dig into the syslog history to see what was the event that resulted in the array to be inactive ? Since you are running at RAID6 with one missing drive, as soon as you will have one drive that drops, the raid will move to inactive state by safety. So maybe look at ATA event.

Yes for the next batch we will finally offer board only purchase option ;-)

@michabbs Thanks for your contribution to our wiki. You PR was merged. https://wiki.kobol.io/helios64/software/zfs/install-zfs/

I'm unable to reproduce the issue. Just tried a fresh install of Armbian Buster 20.11.4 on microSD card then used armbian-config to install boot and system on eMMC (option 2)... and it works as expected. What does the serial console output when you boot the system ? We need to see where your system stops. When did you do the migration SD card to eMMC, before or after installing OMV ?

@NickS Instead of using a physical timer power switch, you can use RTC wake alarm feature ;-) https://wiki.kobol.io/helios64/rtc/#scheduled-power-on-using-rtc

Yes as suggested by @Schroedingers Cat can you try to change cpu governor to performance while reducing a bit the frequency. Run `armbian-config`, go to -> System -> CPU And set: Minimum CPU speed = 1200000 Maximum CPU speed = 1200000 CPU governor = performance Let us how it impacts your setup.

For now we haven't forced the CPU governor to performance, we still hope to find a fix for DVFS to work properly. v20.11.4 doesn't change anything related to DVFS, it is just a rebuild after the realtek r8152 driver was removed by mistake on previous version. BTW you can check you current CPU governor settings with following command : cpufreq-info

@Ammonia Nice job :-) What was the casualties ? Should have told you that better unsolder first the Molex connectors since they easily start to melt when expose to close to heatgun.

Nice tuto :-) This could be easily turned into a page for our wiki : https://github.com/kobol-io/wiki ;-)

@Remus So you mean you still have problem ? Not really clear from your last message. How did you setup the IP address of Helios64 ? Is it DHCP or fixed IP ? Are you using OMV by any chance ? If yes take note that OMV will wipe out any fixed IP configuration after installation.

@crosser Yes you have followed any of the instructions described here : https://wiki.kobol.io/helios64/install/preliminary/ If yes, at which step are you stuck ?

Ideally you have serial console opened with dmesg -w command running in order to catch any exception in case system freeze.

You are correct, the Helios4 PSU is outputting DC 12V / 8A. PIN 1: 12 VDC PIN 2: 12 VDC PIN 3: GND PIN 4: GND And yes between the 4-pin connector and the AC/DC power adapter it's just 2 wire ( +12VDC (red) and GND (black) ). So it should be easy to replace the power block with another while keeping the 4-pin connector as you did ;-)

@DBwpg Do you have some log to share ?

Are you sure you running the latest image ? Can you share the output of your dmesg command.