allen--smithee

Members
  • Posts

    34
  • Joined

  • Last visited

Recent Profile Visitors

864 profile views

allen--smithee's Achievements

  1. Hi @Fabrizio I had already read about a case similar to yours in which the user @Zykr had fixed his problem. @aprayoga can you advise him?
  2. Hello, your helios64 has 3 options to run the bootloader (SPI, Emmc and SD) without a proper bootloader the motherboard will light up some tension LEDs... Your helios64 is at this moment only a 5w toaster, because no instructions for the support of modules and hardware nodes are executed at startup. we can assume that if the jumpers were missing, that maybe your friend was using a homemade boot code on the SPI (not armbian) or failed to put the jumpers back after a manipulation and the SPI was empty, the board was powered up and that's all. Nevertheless, you are now in control of your Helios64 with Bootloader on SD card slot.
  3. Hello and Welcome, in diagnostic Mode, 0. remove all hard drives SD/PCI/Sata, check the position of all jumpers on the motherboard, and the connections inside the case. 1. remove the metal backplate and plug your USB C cable directly into the helios64 motherboard if you get a putty access in COM it is stupidly a known problem. 2. take a valid Armbian image, install it with the Win32DiskImager program on a SanDisk SD card, put it in helios64, plug Helios64 in ETH0 on your network, turn it on and wait for it to flashled System, run a network diagnostic, get the ip of the nas and run SSH on it. 3. Call your friend and ask him what the hell happened with the Helios64.
  4. @bunducafe I think people want to recover the market value to get another market product (Black friday/Christmas/New gen) or/also else be completely overwhelmed by the dt notion. https://forum.armbian.com/subscriptions/ it's a good start 5€ per month = 60€ per year, over the lifetime of the equipment estimated at several years. 300€ = 5years. The financing of the support therefore depends on the quality of the product. If my Kobol Product dies and no other Board support by Armbian Community interests me, my Armbian participation will end. For me the two are linked. @Amix73 I find your intervention very chivalrous, and I thank you for supporting the Armbian project which supports this great Board (with its known flaws) produced by Kobol.
  5. Hi, I was thinking of something else...(I thought you were taking the Board probe values as a reference value but which is not the case) But I highly recommend MAXTEMP = / dev / fan-p6 / pwm1 = 85 / dev / fan-p7 / pwm1 = 85 and MAXPWD=140 with the original thermal pad. Personally my helios has a powerful thermal pad, this allows it to be fanless (which is not the case because I always have a MAXPWM = 50 for ventilation in my helios64 with SSD), but the original thermal pad is of very poor quality (it insulates more than it dissipates). If you have high enough usage I would recommend changing the thermal pad or having the more severe fan control variables for safety or only not to use your helios64 without safety net (without thermal control it is hardware suicide with original thermal pad). Thank BipBip1981
  6. Hello, we all have a different use or experience of our Helios64, the support you requested is finished since Kobol unplugged. in my use this version of uboot allows me from usb-c to access the EMMC memory of Helios64 from a computer. as explain here https://wiki.kobol.io/helios64/install/emmc/#step-1-download-u-boot-only-image-and-an-helios64-image-build Kobol does not mention any use to access M.2 Sata from this image and i doubt this image can do it, unfortunately I have not have M.2 to do try this. Could you describe your use so that those who have a similar use can better help you and those who discover can follow in your footsteps.
  7. not same https://www.thingiverse.com/thing:4671804 for 2,5 https://www.thingiverse.com/thing:4647559 I have solved the problem differently.
  8. same here, the user experience is excellent this Nas is a real little bomb. Kobol and the armbian community have done a great job. Armbian_21.08.2_Helios64_buster_current_5.10.63.img I don't use Softy, only curl yunohost to start, no update | upgrate compulsive I only use Two 32 Gb SD cards, step by step after every major modification or installation that works, I create a backup of the image with Win32DiskImager, it allows me to go back if I have a problem. 16gb SD Card is more than enough and the images take up less space. the Emmc/Sata should only be used when your image is mature and you have nothing more important to edit, only take advantage of your Nas. Enjoy
  9. 5v - 12v At your peril ! https://wiki.kobol.io/helios64/sata/#j8-pinout 12v Maybe you can possibly bridged the input power to J16 https://wiki.kobol.io/helios64/hardware/#connector-interface-list 3v - 5v but not 2.5a https://wiki.kobol.io/helios64/ gpio /# pinout Helios64 is not intended for this. the best would be to make a space size of your power cable on back cover of the case and plug it into a power source provided for this purpose.
  10. not surprised, and very mature decision of the team. Thank Kobol Team for your hard work, your fruit continues to feed our needs here. let us know if you decide to plant again.
  11. @tionebrr Source : https://www.rockchip.fr/RK3399 datasheet V1.8.pdf 1.2.1 Microprocessor  Dual-core ARM Cortex-A72 MPCore processor and Quad-core ARM Cortex-A53MPCore processor, both are high-performance, low-power and cached application processor  Two CPU clusters.Big cluster with dual-coreCortex-A72 is optimized for high-performance and little cluster with quad-core Cortex-A53 is optimized for low power. <... >  PD_A72_B0: 1st Cortex-A72 + Neon + FPU + L1 I/D cache of big cluster  PD_A72_B1: 2nd Cortex-A72+ Neon + FPU + L1 I/D cache of big cluster <... >  PD_A53_L0: 1st Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster  PD_A53_L1: 2nd Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster  PD_A53_L2: 3rd Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster  PD_A53_L3: 4th Cortex-A53 + Neon + FPU + L1 I/D Cache of little cluster <...> 3.2 Recommended Operating Conditions The below table describes the recommended operating condition for every clock domain. Table 3-2 Recommended operating conditions Parameters Symbol Min Typ Max Units Supply voltage for Cortex A72 CPU BIGCPU_VDD 0.80 0.90 1.25 V Supply voltage for Cortex A53 CPU LITCPU_VDD 0.80 0.90 1.20 V Max frequency of Cortex A72 CPU 1.8 GHz Max frequency of Cortex A53 CPU 1.4 GHz
  12. thank you for your feedback. don't bet an winning horses, but on a solution to a specific problem. every one of my problems were software...!! I don't minimize yours!
  13. @SalamandarYou cannot do anything without compromising the integrity of the motherboard as it is a hardware limitation and it is announced in the product description (remember 900mA/port USB-A) so there are no surprises here. Its true that it will be very practical (although not necessarily vital) to have a USB-C DAS 3A on the front of the device (Pine User, Hub, HDD, ..) for next gen. Sometimes I am using my USB-C 11in1 Hub with USB-C to USB-A adapter on the front port of the unit and my Hub is powered by the power charge input with my power supply of smartphone 5A.(Native function at the same time : Eth 1G, SD, USB3x3 / USB2x2; not fonctional : Jack3.5mm, VGA and Hdmi).
  14. Line 44 MAX = 255 You will probably want to change this value to your own. nevertheless, I will not advise you not to go below 120, for the obvious reasons cited by @Heisath . If it's still too noisy. you can safely reduce this value (> 35) after modifying the thermal Pad between the board and the heat sink.
  15. Hi @freed00m I think you would like to read /usr/sbin/fancontrol.