• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Helios4 Support
2 2

9 posts in this topic

Recommended Posts

Main thread for general questions related to Helios4 setup and usage.

 

Note : Before asking a question please insure the information is not already available on HELIOS4 Wiki or addressed in a previous post in this forum.

 

 

helios4.jpg.189fec2640d21e4339455aa8e7b63c36.jpg

 

Latest Build :

 

Debian 9 Stretch (Kernel 4.14.12)

Helios4_Debian_Stretch_4.14.12.img.xz
Build date : 06/01/2018
Size : 242 MB

MD5SUM: a97fef50ecb1c14a6013695f3b2a51b6

 

Debian 8 Jessie (Kernel 4.4.110)

Helios4_Debian_Jessie_4.4.110.img.xz
Build date : 06/01/2018
Size : 210 MB

MD5SUM: a97fef50ecb1c14a6013695f3b2a51b6

 

Debian 8 Jessie (Kernel 4.4.110) with OMV 3.0.96

Helios4_Debian_Jessie_4.4.110-OMV_3.0.96.img.xz
Build date : 06/01/2018
Size : 272 MB

MD5SUM : 250fa48a6fbb92eef31152d0d6783077

 

Known Issues :

All Kernels :

  • During SATA heavy load, accessing SPI NOR Flash will generate ATA errors. Temporary fix : Disable SPI NOR flash.
  • SDcard High Speed timing have compatibility issue with some brands. Temporary fix : Disable UHS option/support.

 

Legacy Kernel (4.4) :

  • PWM-FAN driver not working. Temporary fix : Use GPIO-FAN driver, only 2 speeds supported (low or full speed).

 

Mainline Kernel (4.14) :

  • DVFS doesn't use correct CPU freq range (666 - 1332Mhz instead of 800-1600MHz).

 

 

 

Edited by gprovost
update software release info

Share this post


Link to post
Share on other sites

@zador.blood.stained Merging 4.4.y kernels from Marvell seems a bit problematic and wasteful. Shall we implement this workaround to the mvebu.conf:

https://github.com/armbian/build/blob/master/config/sources/mvebu.conf#L16

    if [[ $BOARD == helios4 ]]; then
        KERNELSOURCE='https://github.com/helios-4/linux-marvell'
        KERNELBRANCH='branch:linux-marvell-4.4'
        KERNELDIR='linux-helios-4'
        LINUXFAMILY=helios4
    fi

Mainline target remains mvebu-next. Any better idea?

 

P1010585.JPGP1010609.JPG

Share this post


Link to post
Share on other sites
2 minutes ago, Igor said:

Any better idea?

Why do we have to use a separate kernel tree in the first place? If there are no critical features in the helios4 fork we should stay with the current 4.4.y branch and try to cherry-pick the helios4 DT and other small improvements.

According to the commit log the only problematic change may be the PWM support which wasn't even working the last time it was mentioned.

Share this post


Link to post
Share on other sites

@Igor @zador.blood.stained

 

Even though we have our own 4.4 marvell kernel repo, as agreed with Zador before, to add Helios4 support in Armbian framework we are integrating our additions/modifications via patches to armbian mvebu-default, this way all mvebu board build against the same kernel repo (which uses moonman repo).  We have new stuff to be merged soon for mvebu-default, can be found here.

 

For the mvebu-next (mainline), we are almost done also, can found the work here.

 

Later today or tomorrow, we will rise a pull request from our armbian/build repo to update both mvebu-default and mvebu-next. Hopefully from this point you will start to build Helios4 image and make them available on your website. For the time being I will still build and maintain on our own builds as found here. Once you are making build available, then our wiki will point to your download page for baseline Jessie and Stretch build... we will then only build and maintain OMV images.

 

@Igor Nice pic ;-) You will realize the casing is not really perfect for single disk, it needs at least 2 disks to properly hold together. You should rather put your disk in one of the middle slots.

Share this post


Link to post
Share on other sites

I had troubles with images above - sometimes network was not recognized ... so I tried to put together mvebu-next with 4.14.12 ... I only used DT from legacy, no other patches. The network works, CPU scaling works, SATA works, ... Fans. One is spinning fast and one slow. I didn't even try to resolve this PWM thingy.

 

Download page: https://www.armbian.com/helios4/
Boot logs: http://ix.io/DIO

 

Yes, I quickly find out that you need at least two drives so I added one at the bottom and case become stable. Eventually, I ended up in "engineering mode" :D

25660939328_5f80bf2574_o.jpg

Share this post


Link to post
Share on other sites

Hi All,

 

As announced in our blog Debian 9 Stretch release is now available which provide the best hardware support of Helios4. For now you can find the latest build release on our wiki, link also available above in the this thread banner.

Share this post


Link to post
Share on other sites

Running OpenMediaVault image on Helios4

Supplied fans connected to fan headers continue to spin after shutdown or in standby mode.

 

Share this post


Link to post
Share on other sites

OpenMediaVault image comes with SABNZBD plug-in.

I have used SABNZBD for years on several different OS's - installs have usually been issue free.

However I cannot get this implementation to access any storage share.

 

Config folder options are restricted to the base folder - which with Helios4 - is the microSD card - a bit useless really for 

a NAS. Has anyone worked out how to move SABNZBD's incomplete & complete folders to a storage share on one of the HDDs?

Share this post


Link to post
Share on other sites
3 hours ago, NickS said:

Running OpenMediaVault image on Helios4

Supplied fans connected to fan headers continue to spin after shutdown or in standby mode.

 

 

I think this is expected. At PWM 0, this fan type will still run at minimum rpm.

Note : standby mode is not yet fully supported. Plus there is no yet proper way to wake up, this will come later with Wakeup-On-Lan support.

 

3 hours ago, NickS said:

OpenMediaVault image comes with SABNZBD plug-in.

I have used SABNZBD for years on several different OS's - installs have usually been issue free.

However I cannot get this implementation to access any storage share.

 

Config folder options are restricted to the base folder - which with Helios4 - is the microSD card - a bit useless really for 

a NAS. Has anyone worked out how to move SABNZBD's incomplete & complete folders to a storage share on one of the HDDs?

 

FYI This is the kind of question that should be rather asked on openmediavault forum.

OMV3 mounts file system under /srv folder. So in sabnzd config folder you can chose/find your share folders by browsing under /srv/<mount-point-name>/<your-share-folders>.

Important : Don't forget under OMV / Share Folder / ACL to give read/write permission to sabnzbd user for the share folders you wanna use.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

2 2

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.