gprovost

Members
  • Content Count

    331
  • Joined

  • Last visited

Reputation Activity

  1. Like
    gprovost got a reaction from flower in Helios64 Support   
    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.
  2. Like
    gprovost reacted to aprayoga in Helios64 Support   
    Could you try edit the /boot/armbianEnv.txt and add idVendor and idProduct of your drive to usbstoragequirks ?
    usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x174c:0x5106:u,0x1e68:0x003a:u reboot the system and see whether your external USB drive can be recognized.
     
  3. Like
    gprovost reacted to aprayoga in Helios64 Support   
    The LED brightness is not adjustable. You would need to use semi transparent plastic/tape to reduce the brightness, or change the resistor on front panel board.
     
    Does FTDI USB serial still connected to your PC? That image should switch USB MUX to RK3399 internal USB and you would see the FTDI disconnected on your PC.
    On Windows, if you ever installed rockusb driver then you would need uninstall it otherwise it will be recognized as rockusb device instead of usb drive.
     
     
    How did you test? After remove the file, shutdown the system and unplug the power supply, then the system would automatically power on without need to press power button when power supply re-plugged.
    Ah i just remember, do you have RTC battery or the UPS battery? the batteries is needed to make auto power on working correctly.
    More info will be described on the wiki.
     
    As mentioned by @flower, those are just symlinks generated by udev rules. The reason is similar like we have done in Helios4, the hwmon order could be changed depend on kernel version or kernel module loading order.
    With this symlink, fancontrol configuration can just refer to /dev/fan-*.
     
    The first boot should not take time more than 5 minutes, unless you were using 64GB/128GB card. As suggested by other, you need to shave the cable so it can connect properly. You definitely need access to serial console for system setup.
     
    You could get supply for your fan from pin 1 or 2 and pin 3 on GPIO header but i'm not sure whether the additional fan would help much.
     
  4. Like
    gprovost got a reaction from djurny in Helios64 Support   
    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  :-/
  5. Like
    gprovost got a reaction from Werner in Helios64 Support   
    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  :-/
  6. Like
    gprovost reacted to TDCroPower in Helios64 Support   
    After several weeks of testing and trying I finally put my Helios64 into production.
    With the 20.08.10 and the possibility to run the firmware over the eMMC I can finally sleep more calmly again.
     
    The front view mounted:

     

     
    The back view connected:

     
    And to prevent my wife from killing me because there is a lighting party going on in the hallway I taped the front LEDs with insulating tape...

     
     
    And for all who have problems with the included USB-C cable at the USB-C port of the Helios64.
    You have to remove the plastic so that the connector looks like this...

     

     
    The black plastic of the USB-C cable must NOT touch the backside of the Helios64, this ensures that the Cable is 100% plugged in.
  7. Like
    gprovost got a reaction from antsu in Helios64 Support   
    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.
  8. Like
    gprovost reacted to flower in Helios64 Support   
    if someone wants to shutdown their unit on powerloss:
     
    create file: /etc/udev/rules.d/15-gpio-charger.rules
    SUBSYSTEM=="power_supply", ENV{POWER_SUPPLY_ONLINE}=="0", RUN+="/usr/sbin/halt"  
    i'd love to know a way to start that unit when power is available again though.
     
    on 4.4 the system crashes on halt. but as it does this after all services are stopped and the disks are synced this is not really a problem.
    on 5.8 the system stops and "system halted" appears on serial console - BUT it is still on and fans are spinning.
  9. Like
    gprovost reacted to pekkal in Helios4 Support   
    @gprovost FYI: I've had zero issues past 6 months after starting umounting MacOS NFS mounts when no longer using them. When I forget to do this (which is often) & Mac goes to sleep a few times there will be tens of NFS daemons running on the Helios/Debian server.  I do believe there is an issue related to NFS between MacOS & Debian.  Issuing 'netstat | grep nfs' every now and then might help to confirm this.
  10. Like
    gprovost got a reaction from sandeepnd in Helios4 Support   
    @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 ?
     
  11. Like
    gprovost reacted to DavidGF in Helios4 - Cryptographic Engines And Security Accelerator (CESA) Benchmarking   
    Not sure whether it's a good idea to bump this thread but just my 2cts on this:
    CESA is quite good for use cases such as LUKS. Obviously you will need to use aes-cbc (use 128 bits for maximum perf).
    In this mode the CPU usage is quite low (you can see two kernel workers doing 10% on each CPU and a ton of interrupts, but other than that works well) which is awesome to keep the load of the CPU which is already limited. In comparison on using pure CPU, in my current setup I get:
     
     - Plain access to disk: 180MB/s
     - LUKS2 + CESA: 140MB/s
     - LUKS2 (no CESA): 52MB/s
     
    I tuned LUKS using sector size= 4096 and keysize=128, as well as using aes-cbc-plain64.
    For me this is quite good already even tho CESA only supports some "relatively old" ciphers.
     
    Hope this helps other people!
  12. Like
    gprovost reacted to PEW in Helios4 Support   
    Here is my guide to upgrade omv4to5. Hopefully this will help out others looking to do the same.
     
    Was able to upgrade omv4 to 5. Here is my posts and the github bash script from the omv site: I downloaded the scripts then changed to executable.
    https://forum.openmediavault.org/index.php?thread/27909-omv-5-0-finally-out/&pageNo=2  
    https://forum.openmediavault.org/index.php?thread/27909-omv-5-0-finally-out/&pageNo=22
    https://github.com/OpenMediaVault-Plugin-Developers/installScript/blob/master/upgrade4to5
    https://forum.openmediavault.org/index.php?thread/33219-upgrade-to-5-x-failure/&pageNo=1
     
    Steps to reproduce:
    1. Remove incompatible plugins
    2. Switch over to dockers that are incompatible
    3. Download the two bash scripts:
    wget https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/upgrade4to5
    wget https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install
    4. chmod +x the upgrade4to5 chmod +x install
    5. Run the upgrade4to5 as root
    6. omv and plugins will fail. as describes here: https://forum.openmediavault.org/index.php?thread/33219-upgrade-to-5-x-failure/&pageNo=1
    7. Remove failed packages not purge since we want config files from omv They should print out.
    8. Reinstall openmediavault only
    9. Reboot
    10. Run this command : apt-get purge openmediavault-omvextrasorg resolvconf
    11. Reboot again
    12. Run the install script as root. this will install omv extras.
    13. apt update
    14. apt dist-upgrade
    15. omv-salt deploy run nginx
    16. omv-salt deploy run phpfpm
    17. But remove or move upsschedule-cmd from usr/bin and bin then run  apt-get install usrmerge
    18. apt install docker
    19. https://forums.docker.com/t/fa…te-nat-chain-docker/78269
    The docker installer uses iptables for nat. Unfortunately Debian uses nftables. You can convert the entries over to nftables or just setup Debian to use the legacy iptables.
    sudo update-alternatives --set iptables /usr/sbin/iptables-legacy
    sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
    dockerd, should start fine after switching to iptables-legacy.
    sudo service docker start
    20. Switch to 5.4 kernel using armbian-config refer to kobol blog: 
    https://blog.kobol.io/2020/03/13/armbian-new-release/
    Hopefully this helps others out.
    Thanks 
     
  13. Like
    gprovost got a reaction from lanefu in Helios4 Support   
    Not sure which country you are but on amazon you can find the following good replacement : https://www.amazon.com/dp/B07NCG1P8X
    You might have to look for the same product ref. on the correct market place according to your country.
     
     
    While for sure our bandwidth is more focus on Helios64, we are still supporting Helios4, and no plan to change that ;-)
    For instance latest Armbian 20.05 Kagu still actively includes Helios4. Ok we will still need to put a post on our blog about that and link the image in our wiki :/
     
     
     
  14. Like
    gprovost got a reaction from Werner in Helios4 Support   
    Not sure which country you are but on amazon you can find the following good replacement : https://www.amazon.com/dp/B07NCG1P8X
    You might have to look for the same product ref. on the correct market place according to your country.
     
     
    While for sure our bandwidth is more focus on Helios64, we are still supporting Helios4, and no plan to change that ;-)
    For instance latest Armbian 20.05 Kagu still actively includes Helios4. Ok we will still need to put a post on our blog about that and link the image in our wiki :/
     
     
     
  15. Like
    gprovost got a reaction from gounthar in Helios64 Annoucement   
    We will post some info this week (on our blog and by newsletter) on production progress and shipping estimate.
     
     
     
    Well we have some track record of donations to Armbian, and actually we are part of the Armbian team as mvebu family maintainer until now, and you can expect us to be very active on the rockchip64/rk3399 family. So even though it's never enough, I think we are doing our share of contribution back ;-)
     
     
  16. Like
    gprovost got a reaction from Werner in Helios64 Annoucement   
    We will post some info this week (on our blog and by newsletter) on production progress and shipping estimate.
     
     
     
    Well we have some track record of donations to Armbian, and actually we are part of the Armbian team as mvebu family maintainer until now, and you can expect us to be very active on the rockchip64/rk3399 family. So even though it's never enough, I think we are doing our share of contribution back ;-)
     
     
  17. Like
    gprovost got a reaction from Werner in Helios4 Support   
    @Declan Yes it's a failing PSU.
     
    Right now it's difficult for us to send spare parts because of lockdown in Singapore.
     
    Plus most probably will be faster and cheaper (if you account shipping fees) to order a substitute model on amazon.
     
    Here is the one we recommend and have been tested : https://www.amazon.com/dp/B07NCG1P8X
     
    I'm not sure what's your country or residence so you might have to look for the same model on the right marketplace country.
     
    Hope it helps.
     
  18. Like
    gprovost reacted to Jeckyll in Helios4 Support   
    Thanks @gprovost for youre reply.
    Ok, i will stick to all time spinning fans.
    Maybe i find some less nosy fans
     
  19. Like
    gprovost reacted to smith69085 in Helios4 Support   
    In case anyone is interested, a Helios 4 is for sale in the UK on eBay - 
    http://rover.ebay.com/rover/1/710-53481-19255-0/1?icep_ff3=2&pub=5575378759&campid=5338273189&customid=&icep_item=264729497930&ipn=psmain&icep_vectorid=229508&kwid=902099&mtid=824&kw=lg&toolid=11111
  20. Like
  21. Like
    gprovost reacted to Igor in Armbian v20.05 (Kagu) Planning Thread   
    Perhaps we need one example how this is planned and others can follow this? I am not sure everyone noticed this and even I was confused how this should be done.
     
    @sfx2000 @gprovost I would like not to deal with more gadgets at this point. We added Jira several months ago and we haven't manage to use much of its powers. IRC is nothing fancy, but its good enough. We have a channel recorder, no need to deal with any subscriptions and/or legal stuff. It works. Consider that many folks are old school or geeky, where IRC is the thing and already a Skype represent a far end of comm tools  

    Anyway, my concerns goes to the meeting content. To come up with an agenda that will help us bring up, put attention to common problems and to spark our comm channel regardless of technology behind this. For the future, if majority decide we need to upgrade to something from this century , I will follow.
  22. Like
    gprovost reacted to FredK in Helios4 Support   
    Release of openmediavault 5 (Usul)
    https://www.openmediavault.org/?p=2685
     
  23. Like
    gprovost reacted to sabirovrinat85 in Helios64 Annoucement   
    WOW it's really wonderful SBC!!!
     
    As ZFS user, I suppose that the best testing configuration would be 5x4Tb hard disks in raidz2 pool, without de-duplication but with compression turned on, no GUI to save memory, 4Tb disks are more efficient in terms of dollar/megabyte than 2Tb models and if there would be slight performance issues one could choose to prefer 5x2Tb config or to deal with some slowiness
  24. Like
    gprovost reacted to Igor in Helios4 Support   
    Architecture limit, max. 16TB for logical volume. In case your hard disks or their setups (raid, lvm) are bigger you only need to split them into more logical volumes. For 2 x 16TB in raid 1 you don't need to do anything.
     
    Current max. raw capacity needs small update to 64TB. 4 x 16TB drive, soon 4 x 20TB.
  25. Like
    gprovost reacted to FredK in Helios4 Support   
    I upgraded my Helios4 from OMV4/Armbian4.14 to OMV5 yesterday. After sorting out some minor glitches the system was operable.
    Today I used armbian-config to switch the kernel to 4.19. Everything seemd o.k. until I tried to inspect my docker containers and I detect a problem with docker-ce which couldn't be started neither re-installed. I had to go back to 4.14. Now I'm rather reluctant to try out one of dev dev-kernels (5.4.x).
     
    Any clue?
     
    Edit:
    as proposed by Koen solved the docker problem.