djurny

  • Content Count

    40
  • Joined

  • Last visited

About djurny

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Taiwan

Recent Profile Visitors

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

  1. Hi @SR-G, FYI I have been running Linux kobol0 5.9.13-rockchip64 #trunk.16 SMP PREEMPT Tue Dec 8 21:23:17 CET 2020 aarch64 GNU/Linux for some days now. Still up. Perhaps you can give this one a try? Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster /etc/default/cpufrequtils: ENABLE=true MIN_SPEED=408000 MAX_SPEED=1200000 GOVERNOR=powersave (The box runs idles with 'powersave' and will be set to 'performance' when performing tasks.) I do not know which non-dev kernel version this is? I assume it's
  2. Hi, I would also be interested in finding out what it would take to host a local repository mirror. Over the past few weeks I did try to rsync the repo to local storage, but I'm not sure if that will affect anything on the 'other' side. Had to break off the rsync as it appeared to sync extremely slow. Groetjes,
  3. Hi @tikey, Did you make sure the SSD is making proper contact to the backplane connector? I also have some issues with the utmost left disk slot, when I remove/replace a disk in that slot, I have to open up the box and make sure that the connectors are tight and snug. If that does not help, you can try to insert the disk in another slot to rule out any connector or power rail issues. When box is open, make sure to also press down on the connectors in the main board, to make sure this is not related to loose cables or such. Just FYI, I run a CT120BX500SSD1 in my box, although not the
  4. Hi @3735943886, When logging in on any of "my" Armbian devices, it will also (start and) attach to GNU screen session. I sometimes observe this behavior as well (mostly in aptitude and not armbian-config), but have not been able to pinpoint when this starts or what causes this. Have you tried to detach from GNU screen and retry? If it shows and behaves correctly outside of GNU screen, you can start digging in the environment settings first by 'env'. Perhaps also show the current active LOCALEs and write down the terminal encoding configured for your ssh client/terminal, as fo
  5. Hi @snakekick, USB HDD for snapraid parity, sounds like my setup! You can check with vm_block_dump what is waking up your device: echo 1 | sudo tee /proc/sys/vm/block_dump Above will enable logging of block device accesses into syslog. If you want to see it happen without flooding your /var/log/syslog: sudo service rsyslog stop while true ; do dmesg -cT ; done sudo service rsyslog start See: Documentation for /proc/sys/vm/* and How to conserve battery power using laptop-mode. You should also check if you have enabled SMART offline auto
  6. Hi, Not sure if I can help here, but willing to help. Can you put the SDcard into another Linux system and list the contents of the /boot folder? Also, please share the contents of the /boot/armbianEnv.txt. Looks like the same thing I had once, after a downgrade of kernel, the DTB files were renamed or not present for unknown reasons. Groetjes
  7. Hi, Can you connect the USB-C cable, connect to the serial console (1.500.000 baud and no HW/SW flow control) and post the output after a reboot/powercycle? What's on the serial console should point to what is going wrong. Did you by any change update the system and continue without rebooting? I had something similar happen on one of the nanopi R2S boxes, where the update was not successful, resulting in an incomplete /boot folder. Groetjes,
  8. Hi, Short update. After looking at the most recent kernel freezes I experienced on 5.9.13-rockchip64 #trunk.16 and reading through a thread meant for Helios4, I decided to stop using cpufreq governor conservative. Switched to either 'powersave' or 'performance' depending on workload, but not to have the frequency changed on-the-fly. Box has been running smooth since last power cycle. As system is nice and stable now, will do some more maintenance before upgrading to latest advised configuration. Groetjes, See last Oops, mentioning something about trying
  9. Hi, Also here kernel Oops after some load: [82182.500900] Unable to handle kernel paging request at virtual address ffff800011b14000 [..] [82182.505753] Internal error: Oops: 96000007 [#1] PREEMPT SMP [..] [82182.526948] Call trace: [82182.527414] x1 : ffff800011532db0 x0 : 00000000ffffffea [82182.527921] gic_handle_irq+0x124/0x158 [82182.528384] Call trace: [82182.528883] el1_irq+0xb8/0x180 [82182.529350] __handle_domain_irq+0xc4/0x108 [82182.529593] arch_cpu_idle+0x14/0x20 [82182.530058] Code: f822683a a94153f3 a9425bf5 a94363f7 (a9446bf9) [82182.530425] do_idle+0x210/0x260 [
  10. Hi all, Something to share for those who use the USB-C serial console from another Linux host. Install and use 'tio' to connect to the serial console instead of minicom. This supports both 1500k baud and also can be easily used inside GNU screen (minicom gets a meta key conflict per default; CTRL-A is default meta key for both GNU screen and minicom). Minicom resulted in regular errors posted in syslog by the ftdi_sio kernel module. Did not run any strace to find out what syscall is causing it, but in short, tio appears to not treat the tty as a modem: no errors are popping up in syslog.
  11. Hi, A short update, unfortunately kernel has crashed again, but after a couple of days. So there is improvement :-) No serial console output, as the usb-serial connection on my Pi stopped responding (will open another thread on this, not really Helios64 related though). Will restart some loading and try a different usb-serial setup, hopefully both will not crash (that often) anymore. Groetjes,
  12. Hi, I've also experienced almost hourly instabilities when running some load on my Helios64 box. Tried several kernels, each with their own Oops/BUG pattern. See below for an overview: It's not exhaustive; in the end I did the following and the box is now running some load (snapraid scrub on ~12TiB of data) without any issue: Enabled daily built kernel, now running Linux kobol0 5.9.11-rockchip64 #trunk.2 SMP PREEMPT Sun Nov 29 00:29:16 CET 2020 aarch64 GNU/Linux. Why: Every kernel had their own pattern, either do_undefinstr or XHCI hangup or page fault. Ass
  13. Hi @gprovost, Looks like I had 'tlp' installed, presumably during some messing about with getting things like powertop installed. Thanks for the trigger: Removed tlp and LEDs are back to normal! Groetjes,
  14. Hi, It's only the "HDD x Activity LEDs" that are cycling. The other LEDs are not showing this cycling. The cycling speed appears to increase with CPU frequency, just like how the "System Activity LED" (heartbeat trigger) frequency will increase when CPU frequency increases. I made a video of the effect, but have some trouble uploading it (>20MiB). here: https://streamable.com/v8wa36, Note I do not have any trouble with this effect, just wondering if this is by design and how I can customize it :-) Groetjes,
  15. Hi @gprovost, replies have crossed. Yes, all the HDD status LEDs are cycling simultaneously. For the HDD with activity, it's still blinking with activity. I cannot make out if the actitivy LED itself is also cycling, my eyes are a bit too old for that. Groetjes,