gprovost

No this is not related to tx offloading. For now we still don't know why tx offloading needs to be disabled on LK5.8, while on LK4.4 it works without issue.

We will do an announcement soon but we realized we made a design mistake on the Helios64 2.5GbE port (LAN2 | eth1) which makes it not perform well in 1000Mb/s mode, however no impact in 2500baseT mode. Regarding your iperf test, seems a bit funny. You sure your routing table is correct for traffic to go really to the expected interface since you are on the same subnet. Can you do the same tests, but for each test disconnect the cable of the interface you are not testing.... or at least use different subnet. Also can you check interface speed with ethtool (ethtool eth0 and ethtool eth1).

It might be that one side of front panel (the side with red LEDs) touch a bit the metal opening shorting the LED therefore lighting them up. Could you trip to loosen a bit the 2x screws holding the front panel, then push a bit back the PCB, then tighten again the screw. Otherwise putting a piece of tape on the PCB side that touch the metal opening, to isolate the LED, could help. For next batch we will have to increase more the gap because mass production doesn't seem to meet exactly our tolerance requirement :-/

1/ in IDLE around 40C. But beyond that it's hard to define an "expected" temperature too many factors in place. I guess we could give the temperature numbers for each use cases listed in our power consumption table : https://wiki.kobol.io/helios64/hardware/#power-consumption 2/ Thermal pad. 3/ Heatsink is in contact will all key ICs, PMIC and inductors (The "center" square is the SoC) 4/ You can experiment, but i really don't think it would benefit much.

Could you contact us to support@kobol.io and see how we can help you from there in case there is a need to return the board.

That's strange that one of the fan never spin up, the same fancontrol configuration applies to both fans, so they should both spin at the same time and same speed. Maybe something wrong with the fan. You can manual set speed as follow : echo 100 > /dev/fan-p6/pwm1 echo 100 > /dev/fan-p7/pwm1 PWM accepts value from 0 to 255. You will have to stop fancontrol service otherwise it will constantly override you pwm values. systemctl stop fancontrol.service

Cool simple trick ;-) Our goal is to have a service doing that in order to trigger the halt (or suspend) after a configurable amount of time when main power loss. Yes we have provisioned for it in our design, there is a gpio that you can toggle to enable auto power-on. However this GPIO isn't exposed yet in our DT file, we will put that in our immediate TODO list.

Hmmm... I think what you are referring to is completely normal. The 2 halves are 2 pieces of extruded aluminum that just slides into each other. What keep them secured, aligned and flushed is the internal metal sheet structure (what we call the Internal Backplane on our assembly manual). When the 2 halves are not secured to the Internal Backplane then, they can freely slides. Completely normal.

Right now we are working on stability, not really the time to talk about overclocking.

In the meantime you can use ethtool -K eth1 tx off This will disable checksum offloading which is what cause problem on LK5.8 with RTL8156 usb-to-lan brige (on LK4.4 there is not such problem and you will get sustained 2.35 Gbit/s). When checksum offloading is disable performance will be degraded to around 1.5 Gbit/s.

@antsu Maybe you want to create a dedicated thread "ZFS on Helios64" since it's a big topic on its own ? It will useful for later and this will avoid too many cross discussion here.

Could you please send us an email to support@kobol.io with some pictures in order to check what's wrong with your enclosure unit.

I think you need to read again carefully our wiki page on jumper to understand the boot order system, if you have nothing on SPI Flash (which should be the case) then you don't need to set jumper 11 to boot on eMMC. The jumpers (P10 and P11) are used to skip boot device by disabling the device. The Soc will always look for bootcode as follow : 1. SPI Flash (unless it's disable by P11) 2. eMMC Flash (unless it's disable by P10) 3. micro-SD Card The issue with eMMC is that U-Boot wasn't supporting the UHS mode therefore unable to access the rootfs on eMMC, it's being fixed by @aprayoga. He's also preparing some wiki instruction around eMMC. I see you asked many questions on many pages of our wiki around this topic... So a bit of patience ;-) otherwise all those questions might be more confusing than anything for other users. ;-) .

Humm if you still get 0V on 12V molex but you are sure that the PSU is ok, then it could the 0-ohm resistors R106 or R107 that are dead, maybe due to a power surge. Can you do a continuity test with your multi-meter on those 2 resistor (highlighted in yellow below) ? If you confirm R106 and R107 doesn't let juice go through then you can bypass them by doing 2x dirty solder bridges as shown with the 2 red lines below.

Hi All, just to announce that this week we will publish new images that fixes instability issue and also fix eMMC install ;-)

This main thread has been locked. Thanks to the Armbian team, we now have our own Kobol club (kinda sub forum) dedicated to our products (Helios64 & Helios4). So now you are encourage to create individual threads for new issue, discuss feature, share setup, etc... This will help to improve overall readability. Note : Before asking a question please insure the information is not already available on Helios64 Wiki or addressed in a previous post in this forum. Latest Build : Check : https://dl.armbian.com/helios64/ Archived Build : Check : https://archive.armbian.com/helios64/archive/ Known Issues : Work-in-Progress images, not all board features are supported yet. Find software support status on our wiki or our here on the forum

@soydemadrid By any chance you have a voltmeter ? Could you measure DC voltage on molex power connector shown on photo below? Expected measured value, on 5V rail: 4.90 V - 5.20 V on 12V rail: 11.90 V - 12.5 V If 12V is outside that range, that means the power supply is faulty.

@PEW Honestly you should do a fresh install, we don't recommend upgrade from OMV4 to OMV5, it was too much of a big transition between the 2 version to result in a proper upgrade, without even taking in consideration OS upgrade (Stretch to Buster).

@PEW Don't forget to reboot after disabling the watchdog.

Were there new microSD cards ? which model ? How long before it starts to show this issue ?

@PEW Can you check if watchdog service is running (systemctl status watchdog.service), if yes then you could also disable it to remove and see if you still experience reboot.

@fri.K That's very interesting info and not the first time NFS has been pointed as a possible root cause : Have you tried some different NFS block sizes (wsize and rsize) settings on your client side ? or maybe reduce the number of NFS daemon ? Because most probably under NFS load with default settings the system reach a unresponsive state and the hw watchdog kicks in and reset the system. Check if watchdog service is running (systemctl status watchdog.service), if yes then you could also disable it to remove it from the equation during your troubleshooting.

@sandeepnd Hard to find a replacement in India. I will contact you by PM to find another solution.

@sandeepnd Most probably it's again a dying PSU not providing enough voltage for the HDD to spin-up, it you read this thread you will see that it has been a recurrent problem. We provided instruction in the past posts to check the voltage on the Molex connector. Which country are you located ? Can provide you a link of a good replacement. Yes you can plug your HDD on any other machine that run Linux, you might need to install mdadm package if not present already : https://wiki.kobol.io/helios4/mdadm/#import-an-existing-raid-array @bramirez Good to see you fixed it. Out of curiosity when you say update, you mean upgrade from what version to what version ?

Go on amazon and look for TAIFU or KFD 12V 8,33A. https://www.amazon.de/dp/B07Q72NBQK https://www.amazon.de/dp/B07P9PR5VB Ok keep us updated.