• Content Count

  • Joined

  • Last visited

About TCB13

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

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

  1. Hello, I've been using a M4V2 since its release mostly as a NAS (disks over UBS 3.0). I also have it booting from a Samsung NVMe with the official NVMe hat. My setup works flawlessly however I was thinking about ways to add more storage with reasonable performance/price so I thought, what if I managed to add a standard PCIe x1 port from the pins on the board and use standard hardware with it. The idea was to add a cheap PCI switch + NVMe adapter (to boot from) and a PCI to SATA controller such as the following: 1) PCI Switch:
  2. You always need and SD card / eMMC to start the boot, then it switches to the system on the NVMe disk. Here the general steps on how to set it up: parted -l parted /dev/nvme0n1 mklabel msdos parted -a opt /dev/nvme0n1 mkpart primary ext4 0% 100% armbian-config # -> system -> install -> boot from (eMMC/SD) run from NVMe. reboot cd /media/mmcboot rm -rf bin etc home lib media mnt opt proc root run sbin selinux srv sys usr var dev tmp Enjoy.
  3. TCB13

    NanoPI M4

    @williamv unfortunately I can't try the new kernel right now. But for for future reference: Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Output is in kBytes/sec random random bkwd record stride kB reclen write rewrite 133470 128882 43201 75881 freread 102400 16 159788 222536 251343 252133 141357 215236 10
  4. TCB13

    NanoPI M4

    hm.. not much better: dd if=/dev/zero of=test bs=100MB count=100 conv=fdatasync 100+0 records in 100+0 records out 10000000000 bytes (10 GB, 9.3 GiB) copied, 31.697 s, 315 MB/s My previous command gives perfectly good results on my desktop.
  5. TCB13

    NanoPI M4

    I was expecting something between 500-700 MB/s from my M4v2.
  6. TCB13

    NanoPI M4

    My results with a NanoPi M4v2 + 8A custom power supply + Samsung NVMe 250 GB EVO 960 PRO: $ dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync 16384+0 records in 16384+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.72603 s, 394 MB/s Kernel 4.4.213-rk3399 Slow isn't it ? I wonder what can be done to improve this.
  7. Maybe the problem is the kernel not the speed?
  8. @nobody @Noboot as we discussed on the other thread the issue seems to only happen in higher CPU frequencies. Now, the question I still have is, what power supplies are you using guys? I'm asking this because the issue might be lack of enough power to run at that speeds.
  9. @Matthias was kernel were you using?
  10. With the 5.x kernel by default the CPU seems to upscale up to 2.02GHz, with the 4.x kernel it only goes up to 1.8Ghz. If I understood you correctly, you think that since my 5.x kernel uses a higher clock it just crashes due to lack of power. That's interesting and would mean that the new kernel isn't broken at all. It would also explain why it reboots without logs. What power supply are you using? and what would you recommend to run at 2.2 without crashes? What do you think about this @piter75?
  11. Yes I will, but only in a few days. I'll report as soon as I have new information.
  12. @piter75 and @NicoD as you guys suggested I decided to try the 4.x image and it works just fine! Look like there are bugs in the 5.x image. Thank you. PS: I tried to downgrade the kernel using armbian-config and my system never booted again had to do a fresh install. I've noticed that the CPU in the 5.x image was running up to 2.02Ghz on the big cores, with the 4.x image seems to be a cap at 1.80Ghz.
  13. Hi, About the Ethernet: as expected I was able to fix it by disabling tcp offload. Now about the hard drive: It's a SATA hard drive connected via a USB 3 ASM1051E SATA bridge. The disk has its own power supply and if I connect it to my old M4 (the original one) I'm able to copy GB of data without issues, however in the M4v2 the board restarts itself. I guess since it works fine on the old M4 it is safe to assume that the issue is on the new board and/or kernel. The only difference here is that the old board is runing a 4.X kernel while the new one is running 5.X.
  14. I've also notice some random reboots / maybe crashes without logs: As you can see it was running fine without any messages at 1:38 am and them it later rebooted by itself at 2:17 pm without logging anything.