gprovost

Members
  • Content Count

    298
  • Joined

  • Last visited


Reputation Activity

  1. 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!
  2. 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 
     
  3. 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 :/
     
     
     
  4. 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 :/
     
     
     
  5. 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 ;-)
     
     
  6. 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 ;-)
     
     
  7. 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.
     
  8. 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
     
  9. 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
  10. Like
  11. 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.
  12. Like
    gprovost reacted to FredK in Helios4 Support   
    Release of openmediavault 5 (Usul)
    https://www.openmediavault.org/?p=2685
     
  13. 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
  14. 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.
  15. 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.
  16. Like
    gprovost got a reaction from gounthar in Helios64 Annoucement   
    Yes exactly this model, we are actually waiting for sample of this upcoming NPU device.
  17. Like
    gprovost reacted to Heisath in Helios4 Support   
    Hi Xavier,
     
    Kernel 5.5 is currently not supported by us. Our current kernel 4.19 has complete hardware support, dev kernel (5.4; which you need to compile yourself with https://github.com/armbian/build) should also have working PWM. 

    If you need to use Kernel 5.5 you are on your own, you can try to use the patches from 5.4 (https://github.com/armbian/build) to get PWM working...
     
    Cheers,
    count-doku
  18. Like
    gprovost got a reaction from TRS-80 in Helios64 Annoucement   
    Effectively I should have blurred the domain info, I made the assumption it was one of those domains from anonymizer email portal
     
     
    Yup happy to that and move on And be sure we appreciate to you seem to very interested by our board.
     
     
    Maybe @aprayoga can bring a bit of clarification here about the the chance that the work that has been done U-boot mainline could translate into not having to use RKBIN preloader one day.
     
     
    Yeah the main reason we added the M.2 SSD slot was to give more option in term of enclosure design for people having specific use case to address. The other reason is that the M.2 Slot has also USB 2.0 interface and can be used to installed NPU extension board.
  19. Like
    gprovost reacted to tekrantz in Helios4 Support   
    Hi,
    my helios4 was not running when I cam in this morning.  When I cycle power all I get is :
     
     
    BootROM - 1.73
    Booting from MMC
    Card did not respond to voltage select!
    Error initializing MMC - FFFFFFEF
    Trying Uart

    and nothing else.  I tried leaving it powered off for an hour and tried again and I get the same thing.
     
    Any suggestions?
     
    Thanks,
     
    Tim Krantz
     
     
    UPDATE!
    I finally got the idea to eject and re-insert the micro-sd card and now all is well.
     
    Have I mentioned how much I love this little machine?
     
  20. Like
    gprovost got a reaction from TRS-80 in Helios64 Annoucement   
    @TRS-80 Effectively all your messages ended up in SPAM, most probably because your first message contained a link :-/ FYI this is the result of Disqus SPAM engine not our actions... and it's not like I'm checking the SPAM box every 5 mins. I just approved all of them except the one where you start claiming we are censoring messages. Maybe next time before jumping to conclusion better to get in touch by other channel (like here) and ask what's happening. I mean honestly what would have been our interest in censoring your message on free software ? Our track record on Helios4 shows that we have always been super transparent. Plus your question is more towards Rockchip than us, since they are the one who so far are keeping their SoC pre-loader close source... there is clearly nothing hide. Anyone the pre-loader issue is something that will improve soon.
     

     
    TRS-80 EDIT: I believe you if you say so. But I removed picture showing partial personal info (email address) in your spam management console as I am very privacy conscious person.
     
  21. Like
    gprovost reacted to lanefu in Armbian 20.02 (Chiru) Release Thread   
    I took a first pass at making a Google Sheet to track testing.
     
    https://bit.ly/2TGaeZN
     
    I'd love some feedback.  Feel free to modify.
  22. Like
    gprovost got a reaction from Heisath in Armbian 20.02 (Chiru) Release Thread   
    Adding @aprayoga
  23. Like
    gprovost got a reaction from lanefu in Armbian 20.02 (Chiru) Release Thread   
    Adding @aprayoga
  24. Like
    gprovost got a reaction from bartvz in Helios64 Annoucement   
    At later stage we will introduce a variant using SDRAM with on-die ECC feature. We are still waiting the 8Gb version to hit the market.
  25. Like
    gprovost reacted to aprayoga in Helios4 Support   
    Between middle-to end of November 2019, Armbian change the version and branch naming.
    Version from something like 5.91 become something like 19.11.x, if i'm not mistaken Year.Month, like Ubuntu versioning.
    Then the branch name,
    DEFAULT become LEGACY NEXT become CURRENT To upgrade to new version, use armbian-config.
    sudo apt-get update sudo apt-get -y upgrade sudo armbian-config
     
    Select System > Other, to switch to other kernel

     
    Confirm the action

     
    And after some process, you will be presented by list of kernels

     
    Select linux-image-current-mvebu. The system will install the new kernel and automatically reboot.
    Confirm the kernel installed correctly and Armbian changed to new branch CURRENT by executing,
    uname -a grep "BRANCH" /etc/armbian-release