gprovost

Members
  • Content count

    41
  • Joined

  • Last visited

1 Follower

About gprovost

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    http://kobol.io

Profile Information

  • Gender
    Male
  • Location
    Singapore

Recent Profile Visitors

427 profile views
  1. gprovost

    Helios4 Support

    @iNTiGOD It seem you resolved your issue ? Based on the content of /etc/network/interfaces, it seems you are running an old build where armbian-config tool was outputting something not quite right for the first 2 lines of eth0 settings. allow-hotplug eth0 no-auto-down eth0 should be replaced by auto eth0 allow-hotplug eth0 Have you upgraded your system ? Because in Debian Stretch network will be handle by NetworkManager.
  2. gprovost

    Helios4 Support

    You mean the board is not working anymore at all ? If yes, then please PM me and let's figure out if we need to process to an exchange. Something is definitely not quite right either with the board or the PSU.
  3. gprovost

    Helios4 Support

    @hatschi1000 Any chance you can try with another HDD model, just for test purpose. Because it is not normal it doesn't even work with one HDD. Starting to feel something could be wrong with your AC/DC power brick. Issue would only arise if transient current on 12V rail goes above 5.8A and on 5V rail goes above 4.5A simultaneously. So even though Hitachi drives are known to be unusually hungry on the 5V rail, I don't think it's possible one HDD would draw more than 4 Amps at spin-up. Just to be sure, you don't have any USB devices connected to the board while doing the test ? Can you double check that the AC/DC power brick is 12V / 8A ? (No reason it isn't, but well we never know)
  4. gprovost

    Helios4 Support

    Hi @hatschi1000, sorry to hear you are facing issue with your setup. From your description it looks like a case of surge current from disk spin-up. This could happen if you use 4x HDD that have very high inrush current at spin-up (e.g old generation of HDD, or some 7200rpm Desktop HDD). This issue can be addressed with spin-up staggering technique by using Power-Up In Standby feature of HDD (PUIS mode). What is strange here is that your setup only has 2x HDD and you said you also observed the issue with only one HDD connected, so the issue could be something else. So here couple of questions to try to narrow down the issue (Let's focus on 'the only one HDD connected' use case) : 1. What is the exact model of HGST HDD you use (please provide model number) 2. Have you tried with both SATA power cables ? just to be sure it couldn't be a cable issue. 3. What do you see on serial console when you power up ? 4. While system is powered up, and nothing is coming up as you described, have you tried to press the reset button (U16) and see if something coming-up on the serial console ? 5. Can you power up the system without the HDD connected (power cable), once OS is up try to connect the HDD is see what happened (Does the system freeze) ?
  5. To all folks, We are taking order for the 2nd batch of Helios4. If you are interested visit our shop. We offer the two following kits for order : Helios4 2GB ECC Full Kit Helios4 2GB ECC Basic Kit Thanks for the support ;-) The Kobol Team
  6. gprovost

    Helios4 Support

    @iNTiGOD Have you try with one of the stock fan that was part of the kit ? To see if it's an issue related to the new fan you bought or it's just system config. Also did you check the existence and content of /etc/udev/rules.d/90-helios4-hwmon.rules ?
  7. gprovost

    Helios4 Support

    @iNTiGOD which build / image version are running ? Maybe you can refer to the following blog post to check if the files on your system show to correct settings.
  8. gprovost

    Helios4 Support

    Let me know once you received and replaced the damage fan ;-)
  9. gprovost

    Helios4 Support

    Yes it's still in the pipe but not the highest priority. It is not so trivial because of some decisions that was made quite a while ago in kernel for other A388 implementations.
  10. gprovost

    Helios4 Support

    It could be a quick temperature rise. Plus since the heat need to dissipate somewhere, if no heatsink, it will transfer to other components which might create other side effects. Hard to say exactly, but I'm certain the root cause here is the lack of heat dissipation. I'm confident everything will be back to normal once you have proper heat transfer. In any case you keep me updated and if something is still not ok then we find a solution ;-)
  11. gprovost

    Helios4 Support

    @nemo19 Ok no need to look any further, you found the issue. There should be a thermal pad between the CPU and the Heatsink as shown below. Without the thermal pad no proper heat transfer can happen, therefore the CPU might have reached above Maximum Junction Temperature (115C) resulting by it to get unstable and crash. I'm really sorry about this missing thermal pad, this should definitively not have happened, I will report / complain to the company that handled the board assembly for us. FYI the thermal pad dimension we are using is 20x20x1mm. Please provide me by private message your complete shipping address. I will send you this missing thermal pad. In the meantime you can try using thermal paste, even though the gap between CPU and Heatsink is a bit too big for thermal paste.
  12. gprovost

    Helios4 Support

    Hi guys, sorry for the lack of follow-up lately, was completely caught up in another venture but now it is over. So the focus will come back 100% on Helios4 support and the second campaign. @JakeK I think the problem you mentioned is something that we have encountered before at rare occasion and it seemed to be linked to the Marvell ethernet driver under Kernel 4.14. Could be a bring up sequence issue that makes the Ethernet PHY not probed properly by the SoC. Will investigate and revert to you. @nemo19 It's true that your CPU temps seems a quite high. Meanwhile the SoC die is designed to operate without issue up to 115 degres. Couple of things you could do to help troubleshoot along with what Igor suggested. Can you check the thermal pad is well positioned between the SoC and the heatsink. For that you will need to unscrew the heatsink. Can you explain why the load is constantly 70% ? Is it because of RAID resync or something else ? Any chance you can keep a console open on the serial until the crash you described occurs again ? Can you share your /var/log/messages and /var/log/syslog history, unless you wipe everything already ?
  13. gprovost

    Helios4 Support

    None of the LED are lighted-up ? Look at LED8 on the board, it indicates if the boards is powered-up. But first, is the LED on the AC/DC power brick is lighted-up ?
  14. gprovost

    Helios4 Support

    @jnko Nice test to prove that active cooling is still needed to ensure HDD lifespan. Technically the SoC (CPU) on its own is designed to run at even higher temperature than 90°C, so you can rely on passive cooling if you run the board alone. As explained, unfortunately the fan type provided (PWM Type A) doesn't stop spinning completely when PWM is set to 0. We will consider another fan type for the next batch. @Nova Soon we will announce our next batch ;-) Stay tune.
  15. gprovost

    Helios4 Support

    @jnko In regards to XOR engine : Check your kernel message you should see the kernel has detected 2 XOR engines. [ 0.737452] mv_xor f1060800.xor: Marvell shared XOR driver [ 0.776401] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr pq ) [ 0.776570] mv_xor f1060900.xor: Marvell shared XOR driver [ 0.816397] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr pq ) In the current mvebu kernel configs, mv_xor driver is part of the kernel, not a module. But I agree there is no obvious way to say if the system offload on the hardware XOR engine. In regards to Wake-on-LAN : This was already asked and answered before You will be able to suspend the system but no interrupt will be able to wake up the system. We will announce once WoL is supported (soon). In regards to FAN always spinning : This is expected, at PWM 0 this fan type (PWM Type A) will still run at minimum rpm... power consumption is negligible