• Content Count

  • Joined

  • Last visited

About RockBian

  • Rank

Recent Profile Visitors

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

  1. I'm not sure, but maybe this will give more info:
  2. @tommitytom: My system is solid too. Running kernel 5.10.21-rockchip64 on Buster. No ZFS, no raid, no OMV. Booting from an m2 sata disk. Since I got the box in november it has only rebooted for kernel updates.
  3. The problem is not that it's slow, but it doesn't work at all. Or did you mean speed up the solution?
  4. Today I updated and upgraded my system, and after a reboot 'apt list' did no longer work. It shows 'Listing... done', and then uses 100% CPU on a single core, without producing anything. According to strace it's looping on reading a file: openat(AT_FDCWD, "/var/lib/apt/lists/deb.debian.org_debian_dists_buster_main_binary-arm64_Packages.lz4", O_RDONLY) = 28 read(28, "\4\"M\30@@\300\206z\0\0\370\377\31Package: 0ad-data\n"..., 65536) = 65536 read(28, "ta$E\17p\2+\377\21c376d3f140540d9424753d"..., 65536) = 65536 read(28, "a5180e3e2d3f503ddcb5dd7b93\201\2\2\275\0\17"..., 65536) = 65536 read(28,
  5. $ cat /etc/apt/sources.list deb buster main contrib non-free #deb-src buster main contrib non-free deb buster-updates main contrib non-free #deb-src buster-updates main contrib non-free deb buster-backports main contrib non-free #deb-src buster-backports main contrib non-free deb buster/updates main contrib non-free #deb-src buster/updates main contrib non-free $
  6. What is a normal CPU temperature on idle? Mine is never lower than 40°C, at an ambient temperature of 19°C, which makes me wonder how much electricity it draws. Is it possible that the GPU is actively doing nothing, or something like that? If so, can it be switched off? The NAS has been placed vertically, with the CPU on bottom. The disk in slot 5 is 22°C.
  7. The boot.scr script is damaged. You can try to recreate it. Boot from sd once again, mount the emmc filesystem and recreate mkdir /tmp/mmc mount /dev/mmc/mmcblk1p1 /tmp/mmc chroot /tmp/mmc mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
  8. As far as I can see it booted from sd, or at least the root file system is an 64GB sd card. To boot from emmc you have to remove the sd card. OK, thanks.
  9. So far I have found that the I2C bus generates ~20k interrupts sec: root@helios64:/proc# cat interrupts && sleep 10 && cat interrupts <snip> 43: 4107025 0 0 0 0 0 GICv3 88 Level ff3d0000.i2c <snip> 43: 4311805 0 0 0 0 0 GICv3 88 Level ff3d0000.i2c but I don't know what exactly that means. A simple i2cdetect on that bus generates 351 interrupts. So it's not bits. Yes I did. I wrote abou
  10. On my system (kernel 5.8.17) a thread kworker/fusb302_wq was running, permanently eating 18% of one core, and causing the load average to be always at least 1.0. The module fusb30x could not be unloaded, rmmod just hung, although it's use count was zero. After blacklisting the module and rebooting the problem was solved. Now is the question: what did I disable? Some googling gave me this document: So it has only to do with the USB-C port? The serial connection is still working fine.