• Content Count

  • Joined

  • Last visited

1 Follower

About gprovost

  • Rank
    Elite member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

4445 profile views
  1. @Harvey I just updated sys-oled repo to fix the issue since the code wasn't aligned with latest luma.core changes. Pull the git repo and reinstall (sudo ./ Let me know if it works.
  2. Honestly hard to say since capacitor failure is something not to be unexpected on such appliance PSU (you can check for other NAS brand, it's quite common). However clearly these occurrences experiences by some users are premature capacitor failure. For instance on our side we have yet to experience these capacitors failure, even though we have some setup that have been running non stop for more than 2 years now. As mentioned previous we are changing PSU supplier for Helios64. Supplier which gives us more control on the capacitor brand and model. We will be using Rubycon capacitor.
  3. @Janne Yes that is a correct pinout. But it's quite expensive. Maybe check on amazon first for Synology power adapter replacement since we use the same exact 4-pin pinout and connector.
  4. @Janne Actually pretty straight forward. If you cut the DC side of power adapter cable you will see inside there are only 2 wire. One black and one red. Red : +12Vdc Black : GND So you can easily repurposed the 4-Pin Mini Din cable with a ATX PSU (P4 connector) or any AC/DC 12V Adapter (need 8A output at least).
  5. @NickS Thanks for sharing your experience and actions regarding a dying PSU. Just to mention again here, for Helios64 we have changed completely supplier for the PSU to a very reputed one. This way we won't anymore experience these premature dying PSU.
  6. @DavidGF Actually something I forgot to ask before but maybe you already check. Can you confirm that there is thermal pad between the SoM and the heatsink. You will have to unscrew the heatsink for that. We had one case last time of an unit missing the thermal pad and it resulted in frequent system hang. Sorry to hear you disappointed by the device and that we haven't figure the issue yet. Unfortunately we are unable to reproduce your issue. Yes it's running kernel 5.4 We will still need to put a post on our blog about that and link the new image in our wiki :/ But you can find them directly on Armbian download section.
  7. Not sure which country you are but on amazon you can find the following good replacement : 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 :/
  8. 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 ;-)
  9. @DavidGF Honestly right now I have idea what could be the issue you report. If things persist and everything point out to hardware issue then we could arrange a board exchange. We can discuss that in PM. Heatsink screw holes are M2.5 Marvell Armada 388 SoC is designed to run at high ambient temperature as you can see in the table below from the hardware datasheet (FYI Helios4 uses Commercial variant). The temperature of this SoC (Tj) is expected to be higher than the average SoC. So to see it around 70-80C when system loaded is quite normal. I live in very humid and hot country, daily ambient average of 30C and 70% humidity, my personal Helios4 in idle is showing CPU : 55-60 C and HDD (4x WD Red) : 35-38C I agree with you that controlling the 2x FAN based on SoC temperature wasn't the smartest approach. We should have instead used hddtemp + fancontrol to control the temperature. Here a pointer on how to do it. I would use at least the HDD that is located on top of the SoC as the main source of temperature to control the case fan.
  10. @DavidGF That's effectively a strange occurrence to see this Ethernet link issue together with SATA link issue together. Yeah I'm not sure about the DC supply issue, because a little voltage drop on 12V shouldn't impact the Ethernet that is on the 3.3V rail. I don't have an idea right now, but looks more like an hardware issue. Most probably unrelated but by any chance you have SPI enabled in your /boot/armbianEnv.txt ?
  11. @DavidGF You 100% sure it's not wiring related ? Could you change cable and maybe also swap ports on your router/switch. Because in your trace there are 2 occurrences where the PHY only negotiated link at 100Mbps. [82281.490395] mvneta f1070000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [82545.668087] mvneta f1070000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
  12. @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 : 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.
  13. Could you do the measure with 2x HDD connected to one of the Molex header ? Also please provide the output link generated by armbianmonitor -u
  14. @Koen The Helios4 has effectively a battery powered RTC, however until now it wasn't used in Armbian because the builds are using fakehw-clock, a generic solution for most SBC that don't have RTC at all. Anyhow it's something we have addressed recently to be part of Armbian 20.05 release : However the change/tweak won't get applied on already installed system. So you here how to make your Helios4 use the RTC clock : 1. Delete fake-hwclock package apt-get purge fake-hwclock 2. Edit /lib/udev/hwclock-set and comment following lines at the beginning of the file if [ -e /run/systemd/system ] ; then exit 0 fi That's all. HOW TO TEST : 1. boot you system with network 2. let the system sync time over ntp 3. check that both system time and rtc time are updated $> timedatectl status Local time: Thu 2020-05-07 14:46:48 +08 Universal time: Thu 2020-05-07 06:46:48 UTC RTC time: Thu 2020-05-07 06:46:48 [...] 4. poweroff system and disconnect PSU 5. wait 10 min 6. remove network cable 7. start system without network (you don't want chrony to sync the time) 8. check system is still at current time $> timedatectl status Local time: Thu 2020-05-07 14:58:30 +08 Universal time: Thu 2020-05-07 06:58:30 UTC RTC time: Thu 2020-05-07 06:58:30