Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. They are the same as before as far as I know, "netdev" is selected: $ cat /sys/class/leds/helios64\:blue\:net/trigger none usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport disk-activity disk-read disk-write ide-disk mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 activity default-on panic mmc1 mmc2 rc-feedback [netdev] tcpm-source-psy-4-0022-online gpio-charger-online rfkill-any rfkill-none stmmac-0:00:link stmmac-0:00:1Gbps stmmac-0:00:100Mbps stmmac-0:00:10Mbps
  2. Yes, you are right. Didn't notice that. I also see an odd flash here and there but doesn't seem to be related to the network activity at all.
  3. Hi everyone! Just to let you all know that I have updated today my Helios64 to Armbian 21.08.3 Bullseye and the "LAN" front panel led now works again. :-) Great!
  4. Hi! I just noticed this post. I confim My Helios64 front panel "LAN" led doesn't get lit as well with Armbian 21.08.2 Bullseye. Testing the LED it works as described above.
  5. Hi everyone! Thank you for all the updates on this. I have now fully upgraded my Helios64 with a ZFS pool from Armbian 21.08.2 Buster to Armbian 21.08.2 Bullseye (full Debian and Armbian repos). All good, no issues. As currently I'm just using the emmc to boot with system installed on sata1, the emmc speed impact is negligble in my case - but hopefully this will be sorted in the near future.
  6. Thanks for confirming. There is also an Armbian bullseye repository available. Would that work? Update: I guess yes from the linked post "Armbian (Debian Bulleye) - supported or not?" above.
  7. This one is interesting, I would like to upgrade as well! I have a stable Helios64 Armbian 21.05.8 Buster with ZFS from buster-backports and no OMV so I would expect to work well as well. So I guess for the update to Bullseye you have just replaced "buster" for "bullseye" on the several source.list files and then APT updated and full-upgraded right? Or you did only Debian repository packages? I didn't know that there was an Armbian "bullseye" repository already. Is it being updated and developed from "buster" already? Or still on a limbo early stages not ready to use state?
  8. Really sad news, very sorry to hear that for them as a team and company and for ourselves the users of course. The Helios64 is one of the best NAS solutions out there for the budget and the specs and with great potential. I was also counting on getting a Helio64 next revision with the expected improvements and the expected support from the Kobol team... Well hopefully better days will come for all.
  9. Hi! I'm not sure what you mean by "air should go inside"... If you follow the pictures carefully (and you observe the fans blades orientation) you'll notice that fans are mounted in such a way that they pull air outside through the case back panel. Which is what you should expect typically anyway. Fresh air comes inside through the front grill, flows through disks and the Helios64 SBC board and then is pulled out by the fans. But yes, I agree that ideally and to avoid any possible misinterpretation some arrows/text should be included to indicate the proper airflow direction.
  10. Hi @Igor! Thank you for taking the time to reply to me and for your detailed explanation. I certainly appreciate it and yours and the remaing Armbian team good work on this project as well. Thank you! In my case I do prefer and use Debian Sid + KDE Plasma on my x86 workstations. But I do understand where you are coming from. Personal preference apart I was also under the expectation, as the name "Armbian" suggests to imply by the "...bian" part, that it would be Debian base focused firstly - therefore developed from it - and then Ubuntu secondly and that it would keep it as close to default Debian base while changing whatever necessary to boot and work on the arm hardware. I'm also not so sure on those possible "Ubuntu improvements over Debian" - but again that's my personal preference. Anyway keep up the good work, great job so far and hopefully it will get even better in the future.
  11. I would rather have Debian based, Ubuntu brings me back bad memories so I stopped using anything Ubuntu quite sometime ago. By the way, I understand that Armbian is developed on Ubuntu first, is that right? As there is an "unstable" Ubuntu Hirsute based image available but none of Debian Bullseye or Sid. I wonder why?
  12. Hi, all! I also confirm this issue on my Helios64 with a fresh install of the latest Armbian Buster v21.05.4 and default settings. It seems to be a persistent and global issue still. Reported by the OP more than one year now. I'm sorry to ask but why isn't the Armbian team doing anything about it? Solution as detailed above is to disable the APT lists compression entirely. It would be probably best to have this taken care of in the next Armbian releases/updates, compression should probably be optional and not the default. Workaround steps: 1. Remove the file "/etc/apt/apt.conf.d/02-armbian-compress-indexes" or edit it to comment out all settings resulting as following: //Acquire::GzipIndexes "true"; //Acquire::CompressionTypes::Order:: "gz"; //APT::Compressor::gzip::Cost "10"; 2. Remove the existing compressed APT lists: # rm /var/lib/apt/lists/* 3. Update APT indexes to recreate the new uncompressed index files: # apt update
  13. Thanks! Yes, I believe that's the case. I guess something got corrupted on my install. Booted SD card Armbian fine. Tried everything, copy all files at the /boot directory, filesystem check, chrooted and updated and fully upgraded. In the end I gave up and reinstalled everything from scratch. Let's see how if it's stable on the long run... I'm getting a bit worried with all reports I read here regarding instability, hangs, crashes, boot corruptions, custom cpu voltage and frequency modifications. I need it to work reliably as a NAS and apps server. Hopefully all of you will get yours storted as well.
  14. Hi! Not sure if it's related to the original post but my Kobol Helios64 seems to have just stopped responding following a reboot. Already tried to power down and power up and the issue persists. Hardware starts, disks are initialised and responds to ping. But no longer can be accessed via SSH or the OpenMediaVault web admin page. My Helios64 is updated with latest Armbian Buster 5.10.x and latest OpenMediaVault 5.x. Armbian + OMV installed to internal eMMC. Docker apps installed to M.2 SATA Port1. Other 4 HDDs with a ZFS setup on SATA ports 2 to 5 for data storage. A few minutes prior to doing the reboot I noticed some kernel errors on a SSH connected shell to my Helios64 the syslog errors (posted on the shell). They kept appearing randomly and separated for a few minutes apart as the following: Message from syslogd@helios64 at Jul 16 18:47:05 ... kernel:[111630.816643] Internal error: Oops: 96000004 [#8] PREEMPT SMP Message from syslogd@helios64 at Jul 16 18:47:05 ... kernel:[111630.843686] Code: 14000011 f9400273 b40001f3 d1002274 (b9402280) Then rebooted from the OMV web admin page and it stopped responding from there. Pings ok but dead SSH connection is refused and OMV dead web admin page. Any idea of what's this about and how to sort this?
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines