16 16

About This Club

Dedicated section for talk & support for the Helios4 and Helios64 open source NAS. Lead and moderated by the Kobol Team.
  1. What's new in this club
  2. I have armbian focal installed in mmc, kernel 5.10.16-rockchip64. After `reboot` command, boot never completes (no heatbeat LED, no network access), though boot process seem to go quite far: [ 10.832087] rk_gmac-dwmac fe300000.ethernet: TX Checksum insertion supported [ 10.832732] rk_gmac-dwmac fe300000.ethernet: Wake-Up On Lan supported [ 10.833507] rk_gmac-dwmac fe300000.ethernet: Normal descriptors [ 10.834059] rk_gmac-dwmac fe300000.ethernet: Ring mode enabled [ 10.834594] rk_gmac-dwmac fe300000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 10.843920] rockchip
  3. We fix bugs every day, while you are not in a position to put any pressure on that efforts. That's the point! Being extremely supportive or being extremely hostile changes nothing in term of support from end users side. It never reached over 1% of the total costs. It's about your attitude towards community developed software. If I am polite and supportive to "you", questions (on my time and expense) never stops. It seems you never looked from the giving side? This will make all problems go away? So you do support non
  4. For anyone visiting from Twitter and wondering what the fuss is about, you can find the split thread here.
  5. This is public forum, just not regulated by Armbian staff. This is still not one to one professional technical support session. You paid for the device or some support with vendor which relationship is not my business, but support efforts in general are almost entirely covered by this large grey zone. I don't want anything from you if you expect anything from me - we operate on your donations, which are free willing act. If one don't give or help with anything (for what you already got) it's a moral problem one have to live with. If you want support, request is denied and reasons represen
  6. @Gareth Halfacree If you would be interested in FreeBSD, @SleepWalker was experimenting with it some time ago. Maybe still is.
  7. The key upgrade for me would be moving away from Armbian to a professional distribution like mainstream Ubuntu or Debian.
  8. No, I was not: I was asking the vendor of the network attached storage device I paid for if there was a convenient way of upgrading its bootloader. Your input was neither requested nor desired. Perhaps this is a language barrier thing, so allow me to be clear: you are being extremely hostile. When people post on this specific sub-forum, it's with the expectation they're engaging in a professional discourse with the people who support the device they paid for - i.e. Kobol. They are not attacking you personally, nor the Armbian project: they, like I, simply want to get the
  9. I explained you how is support with community supported open source software. Like Armbian, Debian or many other community projects in general. 99.9% of the software you use has nothing to do with "commercial support" you might have with your HW vendor. It's their choice and expense what level of support they will provide for you. You were complaining about the software we have created and we maintain. That's why I have reproduced some stuff especially for you. Even you have noticed it before, it seems you don't get it. Your relationship remains intolerant and you are trying to pu
  10. @gprovost Thanks, I really appreciate it. The commands ran without error, though I won't truly know if it's worked until the next reboot!
  11. Ok here the dirty way to update it in your specific case where eMMC is at /dev/mmcblk1 We will work on nand-sata-install to support the use case of rootfs on HDD/SSD and bootloader on eMMC.
  12. @Igor I've seen you post the same copy-and-paste message to others, and I remain as unimpressed now as the first time I saw it. I'm not asking you, nor Armbian, for support, here: I'm asking Kobol, to whom I have paid money for a commercial product with support, to assist me. If you want to help me, feel free; if not, kindly leave Kobol and its appointed representatives to the task. I'll be honest: if I'd know about your user-hostile attitude before pre-ordering the Helios64, I wouldn't have ordered it at all - I'd have bought something that ran plain-Jane Ubuntu instead. It's cert
  13. @Gareth Halfacree Can you provide the output of the 2 following commands. lsblk and cat /proc/mounts
  14. Unfortunately, that doesn't work either - and may provide a hint as to why there's no option to install from armbian-config. If I run nand-sata-install, I get a message reading "This tool must be run from SD-card!" - which, of course, it's not, it's being run from the SATA SSD. Is there a way to update the bootloader without taking the system down, booting from an SD card, updating the bootloader, removing the SD card, and rebooting back into the installed operating system again? Because that's a bit of a slog, especially if the bootloader's going to need regular updates...
  15. Humm that's funny. You can call directly the sub app that is in charge of installing / updating bootloader. $> nand-sata-install You should use option 5.
  16. My Helios64 has been booting from an M.2 drive since I got it, and while I've been doing regular apt-upgrades I've been ignoring the bootloader. This post suggests that could be a problem, so I figured I'd upgrade the bootloader through armbian-config. Trouble is, I can't. I can load armbian-config without error, but when I go into System there's no Install option any more. All I have are Freeze, Nightly, Lowlevel, Bootenv, CPU, Avahi, Hardware, Other, SSH, Firmware, ZSH, Default. Is there another way to ensure the bootloader is up-to-date?
  17. @allen--smithee Thx for the mod tip, I'll do it when I move and have more time. For the time being I will writte myself a systemd service that apply patch (uncomment the script's traps) and when need for quite termintion, I will comment out the lines to have quite halt).
  18. 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 (> 60) after modifying the thermal Pad between the board and the heat sink.
  19. OK, so mounting the microSD on my computer, cd boot/dtb/rockchip and running sudo ln -s rk3399-kobol-helios64.dtb rk3399-helios64.dtb allowed me to boot the NAS again I run sudo apt update && sudo apt upgrade regularly, but wasn't aware I needed to run the armbian-config thing to update the bootloader. Thanks for the help!
  20. I assume the original thinking of the authors of fancontrol was, that when the programm crashes/unexpectedly get closed, it does not leave the fans at a low speed and possibly endanger the system. The fancontrol does not differentiate between shutdown and exit / kill. And from a system perspective it is much better to have annoying loud fans (but a cool and healthy system) than slowly burning away components while no sound is heard I guess that also answers your second question, if you comment those lines away, the fans wont auto speed up if fancontrol crashes or
  21. @kabo is this new fresh sd card image? I assume it is not, looking on u-boot build date that is quite old. Did you recently update & upgrade the Armbian? You can try my instruction on following thread:
  22. @gprovost - Thx that indeed acomplish what I want. Question, what purpose does it serve? Making loud halting seems like a unwanted behavior. Also what side effects can I expect? the script is at /usr/sbin/fancontrol .
  23. Dear H64-Friends, I've got the Armbian Debian installed with Linux Kernel 5.10 and Open Media Vault (OMV). I just use the basic functions for backing up files, nothing extraordinary. I am wondering what's the best strategy to update the Helios64 system concerning stability and getting no errors for backing up files (automatic USB-Backups). Keep it always up to date if there's an update available in OMV? Or just wait some weeks?
  24. @gprovost on the first boot I was able to set the root password, then rebooted and it crashed with LK 4.4. Here is the dump