• Content Count

  • Joined

  • Last visited

Everything posted by Nobby42

  1. I have no crash since 5 days. Welcome to Armbian 20.08.3 Buster with Linux 5.8.10-rockchip64 No end-user support: built from trunk System load: 20% Up time: 5 days 1:18 Memory usage: 34% of 3.71G Zram usage: 6% of 1.86G IP: CPU temp: 48°C Usage of /: 17% of 458G storage/: 6% of 916G storage temp: Always°C $ cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=600000 MAX_SPEED=1800000 GOVERNOR=performance
  2. Hello, I found a problem with the CPU GOVERNOR. ENABLE=true MIN_SPEED=600000 #MAX_SPEED=2016000 MAX_SPEED=1800000 # performance i firefox preferences i 6 # GOVERNOR=conservative # GOVERNOR=ondemand GOVERNOR=performance When I set the GOVERNOR set to "performance" it looks like that the NANOPI run stable. In MODE "ondemand" and "conservative" the PI crashes after a few hours. I do not have enough experience to play with the GOVERNOR parameters to get a stable setting in USER mode.
  3. Now I have get the next crash processes (see the log). Kernel 5.4.13 CPU 1,42/1,8Ghz governor is set to "conservative" What I doing. I open the webgui from a nextcloud (docker) installation. log_crash-20200191.txt
  4. Since I set the CPU frequency to 1.4/1.8Ghz I have no problems. Look at this topic
  5. It was the same with me, too. CPU message on the console and nothing works. I use the 5.4.8 kernel. Currently I use a power supply with 5.3V/4A on pin4/6 But I'm not entirely satisfied with that either. I am currently preparing a rack mounting of the NanoPi and will then use this power supply. That's stable at 5A.
  6. Hi, I have had formative experience with the NanoPI M4v2.. First, you need a real power supply. The Rasbberry 4 power supply for example breaks down when using a NMVe and a SSD, at high load, to below 5V (approx. 4.8V - 4.7V). 2. the CPU frequency. I think the 1.5/2Ghz is too much. I have had several crashes. For example the NanoPi crashes when transferring large amounts of data, sometimes processes (kworker, sshd, ...) just crashed and sometimes the NanoPi just stopped. Since I use the frequency to 1.4/1.8Ghz and a similar power supply, it looks like the NanoPI runs stable with NMVe
  7. Hi, when I used rsync to copy several GB of data from the NMV3 to a USB SSD, the SSHD crashed. [96500.101926] ------------[ cut here ]------------ [96500.102376] kernel BUG at arch/arm64/kernel/traps.c:405! [96500.102858] Internal error: Oops - BUG: 0 [#2] PREEMPT SMP [96500.103343] Modules linked in: sg uas hci_uart bluetooth cpufreq_userspace zstd zram dw_hdmi_i2s_audio rockchip_rga v4l2_mem2mem videobuf2_dma_sg panfrost fusb302 tcpm videobuf2_memops gpu_sched typec videobuf2_v4l2 videobuf2_common videodev mc brcmfmac brcmutil cfg80211 rfkill rockchipdrm analo
  8. Hi, I have no experience with GitHub, but I'll look into it. It may take a while.
  9. Yes ;-) Thanks for your support.
  10. Hi piter75, I think I found the problem. The UAS. After I add the USB-ID for my adapter in the armbianEnv.txt the SSD was black list für the UAS and the board booting with the rootfs on the SSD. [ 56.463044] hub 8-1:1.0: USB hub found [ 56.463741] hub 8-1:1.0: 4 ports detected [ 57.026120] usb 8-1.2: new SuperSpeed Gen 1 USB device number 3 using xhci-hcd [ 57.047008] usb 8-1.2: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 [ 57.04777
  11. Hi piter75, thanks for your support. I ran some tests yesterday. During the last test I made a mistake and forgot to remove the SD card and the Pi boots with all memory media. After booting I saw that the ROOTFS is on the device /dev/sda1. Why? It looks like it booted from a mix of SD and EMMC and rootfs on sda1 lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda └─sda1 ext4 b1a869c6-23b1-4254-b604-6c8e9abe4440 215.3G
  12. Happy new year. UUID looks good. Here they are from the last test. lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda └─sda1 ext4 5a664488-9c46-46a8-92a8-73127b19c54b 215.3G 1% /media/ssd mmcblk2 └─mmcblk2p1 ext4 ddceb71a-f588-4aea-bdb0-2fc352dfef3d 13.3G 1% /media/mmc mmcblk2boot0
  13. The NanoPi don't boot from emmc with roots on SSD with the 5.4.6 kernel. I have attached the boot log. After the Pi found the ssd they do nothing. I have tested variuos SSD. Booting from only SD or only EMMC works fine. nanopi_log201911231_1.txt
  14. I also use the NanoPi as a server. Could it possibly be due to the CPU frequency? The 5.4.6 kernel use 1,5/2Ghz and the 4.4.192 kernel 1,4/1,8Ghz. I'll test it tomorrow.
  15. @piter75 Thanks. Now the ethernet workes and I can test the legacy kernel. With the 5.4.6 kernel I have a lot of problems. Sometimes the Pi crashes. I cannot verify the reason. I boot the Pi from emmc and rootfs on a SSD. Looks like a problem with the USB SSD adapter but I am not shure. I use USB adapters with JM567 and ASM1153 chipset.
  16. Hi, I work without WiFi. Regards Norbert
  17. Hi, I have testet the image with the 5.4.2 kernel. No problems. Can anyone reproduce the problem with the 4.4.192 kernel? Kind regards Norbert
  18. Hi, I have a problem with my NanoPi M4V2 (with Raspberry Pi 4 power supply) and the new Armbian release 19.11.3 (Buster). I can boot the image from SD, eMMC. But when I connect any USB storage (USB-Stick or SSD with USB to SATA) then I have packet lost on the Ethernet connection. Any idea where the problem is? On the interface I can't see problems. eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.xx.36 netmask broadcast inet6 fd58:xxxx:xxxx:1::1006 prefixlen 64 scopeid 0x0<global>