gprovost

Members
  • Content count

    28
  • Joined

  • Last visited

About gprovost

  • Rank
    Member

Contact Methods

  • Website URL
    http://kobol.io

Profile Information

  • Gender
    Male
  • Location
    Singapore

Recent Profile Visitors

342 profile views
  1. 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.
  2. 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
  3. Helios4 Support

    @NickS I just created this patch for fancontrol that fixes 2 issues : - fix 'too many arguments' error messages - set pwm to minimum speed when fancontrol exit https://github.com/helios-4/build/blob/helios4/packages/bsp/helios4/fancontrol.patch @Last_phil Good that you managed to setup Plex server. You pinpoint one the reason I never liked Plex, the need to still transcode stuff while the player device can natively support the codec. Many people asked the question about Plex on Helios4, I said clearly it will run but don't expect it to have the guts to transcode everything. @tbendiksen Good suggestion, you can rise a Pull Request directly on Armbian official repo as Igor suggested you.
  4. Helios4 Support

    @igor.bernstein We will add WoL support a bit later because it requires more investigation from our side since there are currently a patch in the kernel preventing suspend to ram. Here an old discussion that refer to it : https://patchwork.kernel.org/patch/5793931/ Related to what repo / source we (Kobol Team) work on and use to build our images, even though it was clarify by Igor and Zador, we will add one of those days some clarification and guide in our wiki on how to build an image with Armbian framework. In any case, beside the OMV images, ou wiki will soon just link to the Armbian download page for the baseline images. I know our Wiki is still lacking a lot of details and info but bear in mind that we are a bit short handed and under water with the fulfillment follow-up.
  5. Helios4 Support

    @Igor Thanks a lot @pedro67 Check our latest blog post on how to update/patch existing system : https://blog.kobol.io/2018/02/05/sw-fw-update/ @soydemadrid You correctly pinpointed the issue, if you have 2 identical MAC address on same network you will see the exact issue you are observing. You will need to change the predefined MAC address in one of your Helios4. Here the steps : 1. Launch armbian-config from console / shell 2. Go in following menu System > Bootenv 3. Add the following line eth1addr=00:50:43:84:25:2f 4. Save, Exit and Reboot Note : Because of udev rules your interface might be rename as eth1 after you change MAC address. Delete file /etc/udev/rules.d/70-persistent-net.rules and reboot. @wsian I don't have time now to write as I was planning some wiki page about how to use a I2C OLED screen. You will have to dig by yourself first. There is this driver that supports many OLED screen (including SH1106) https://github.com/hallard/ArduiPi_OLED
  6. Helios4 Support

    @pedro67 @Igor Pull Request has been created : https://github.com/armbian/build/pull/885 Waiting it get merged and that Igor publishes the kernel debian packages on apt.armbian.com Once it's done I will post a blog post tomorrow morning with the instructions on how to upgrade from an existing install. Meanwhile I'm building on my side the different sdcard images that I will publish tomorrow morning on our wiki.
  7. Helios4 Support

    You right I didn't realized you upgraded your kernel to the latest provided by Armbian dpkg repo which unfortunately is missing PWM and LM75 options because of a incomplete merge on Armbian side. Our intention was to fix this issue along the improvement of udev rules and PWM support in LK4.4, I didn't foresee that people will be updating their kernel via dpkg and end up in your situation Will post something here once new kernel version is available. Some manual editing will be require in /etc/fancontrol and udev rules.
  8. Helios4 Support

    Go to /sys/class/hwmon Look inside each hwmon[1-5] folders to find the two folder that contain a file named pwm1. Let's say folder hwmon4 and hwmon5 contains the filename pwm1, then to setup the speed do the following command : $> echo 100 > /sys/class/hwmon/hwmon4/pwm1 $> echo 100 > /sys/class/hwmon/hwmon5/pwm1 PWM range is 1 - 255, so you can have fun trying different speed.
  9. Helios4 Support

    @pedro67 The issue is not really related to kernel, but rather in which order the kernel detects the difference hwmon type device, and sometimes the order unfortunately change. We are working on this issue, it will be fix in our next build release tomorrow. We are adding udev rules to hardcode the path of the hwmon devices.
  10. Helios4 Support

    @bigheart Is the serial issue you described happens all the time after over night running ? The helios4 board has an onboard FTDI USB-to-UART bridge (FT230X), this way you don't need to have a RS232 port on your computer or to buy a USB-to-Serial converter. The FT230X is actually power supplied by the USB port of your computer that you connect to the Heliso4 micro-USB console port, so even if the Helios4 board is not powered-on the FTDI USB-to-UART bridge will still come to live and should be detected by your computer. Assuming your computer is a Linux machine, as soon as you connect the Helios4 console port you should see the following in your kernel messages $> dmesg -w [...] [684438.411938] usb 1-2: new full-speed USB device number 18 using xhci_hcd [684438.547622] usb 1-2: New USB device found, idVendor=0403, idProduct=6015 [684438.547631] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [684438.547636] usb 1-2: Product: FT230X Basic UART [684438.547639] usb 1-2: Manufacturer: FTDI [684438.547643] usb 1-2: SerialNumber: DN00KDNN [684438.551627] ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected [684438.551703] usb 1-2: Detected FT-X [684438.552290] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 If you unplug you should see the following USB disconnect message [684398.900050] usb 1-1: USB disconnect, device number 17 [684398.900432] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [684398.900463] ftdi_sio 1-1:1.0: device disconnected So when the serial issue you described happens again, you should try to unplug / plug the console port and see if you see the above messages appearing in you kernel messages. If the expected kernel messages appear but you still can't access the shell console of the Linux running on your Helios4, then the issue is somewhere else than the onboard FTDI USB-to-UART bridge (unless a very unlikely issue with the Dual-Buffer IC between the FTDI chip ans the SoM) . In this case you should post the full dmesg ouput of your Helios4 when the issue appear (use https://pastebin.com/ to share the output to us).
  11. Helios4 Support

    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. 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.
  12. Helios4 Support

    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.
  13. Helios4 Support

    @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.
  14. Helios4 Support

    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. Latest Build : Build by Armbian Team : Check : https://dl.armbian.com/helios4/ Build by Kobol Team : Debian 9 Stretch (Kernel 4.14.20) Helios4_Debian_Stretch_4.14.20.img.xz Build date : 17/02/2018 Size : 229 MB MD5SUM: fc98aac0c0f1617061bd6f5112896838 Debian 8 Jessie (Kernel 4.4.112) Helios4_Debian_Jessie_4.4.112.img.xz Build date : 05/02/2018 Size : 202 MB MD5SUM: dd6f5ea6e9ac80e4f379d619b71ef1e8 Debian 8 Jessie (Kernel 4.14.20) with OMV 3.0.97 Helios4_Debian_Jessie_4.14.20-OMV_3.0.97.img.xz Build date : 17/02/2018 Size : 259 MB MD5SUM : 963af770df27c351a84622bcfc90617a 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. Mainline Kernel (4.14) : DVFS doesn't show correct CPU freq range (666 - 1332Mhz instead of 800-1600MHz).
  15. gprovost