i5Js

  • Content Count

    22
  • Joined

  • Last visited

About i5Js

  • Rank
    Member

Recent Profile Visitors

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

  1. Well clearly is not a power issue. I've installed 4.4 kernel and worked root@nanopct4:~# dmesg | grep -i pcie [ 1.958739] phy phy-pcie-phy.5: Looking up phy-supply from device tree [ 1.958752] phy phy-pcie-phy.5: Looking up phy-supply property in node /pcie-phy failed [ 1.961110] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep [ 1.961124] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup [ 1.961156] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0) [ 1.961403] rockchip-pcie f8000000.pcie: Looking up
  2. Could be a power supply issue? jsalas@nanoserver:~$ dmesg | grep -i pci [ 0.008528] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created [ 1.483641] PCI: CLS 0 bytes, default 64 [ 2.709362] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 2.771099] ehci-pci: EHCI PCI platform driver [ 2.804225] ohci-pci: OHCI PCI platform driver [ 3.208966] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 3.734680] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 3.735230] rockchip-pcie: probe
  3. I’m on 5.8.14 and my nvme is not detected.... It was working fine till I updated to that kernel version The logs are uploaded to http://ix.io/2ATb Many thanks....
  4. Good job! Many thanks! Could this also work with the nanopi M4 V2?
  5. Hi guys, I've a nanopim4 V2 running Armbian Focal with Linux 5.7.15-rockchip64, on a Kubernetes k3s cluster, and I realise that time to time, the board crashes (or reboot) but I'm unable to find why. I've checked syslog kernel.log under /var/log.hdd without luck. What else should I check? This is the output of armbianmonitor if it's help. http://ix.io/2vgU Many thanks in advanced. Regards
  6. Yesterday I reinstalled on kernel 5.4.32 and it's working fine, just 24h without any reboot. The fan works fine and the temperature is stable around 50 degrees. Fingers cross!
  7. And what about the fan control? Because I've downgraded to 4.4 because of that.
  8. Yes, I found it as well, in fact I've to add this every time it reboots.
  9. Thanks both for your replies. Armbianmonitor output has been uploaded to http://ix.io/2ndb It's booting from emmc memory
  10. Hello all, I have this board and It's suffering crashes and reboots all day. I think the logs are stored in RAM because I can't never find anything related to this issue. Is there anything I can do to find the cause? Many thanks. Regards.
  11. How can I figure out which is the pin of the fan on my nanopc t4? Because when I run the script I get the following: Traceback (most recent call last): File "test_fan.py", line 36, in <module> fan_rpm() File "test_fan.py", line 8, in fan_rpm with GPIO(70) as rpm_gpio: File "/home/i5Js/.local/lib/python2.7/site-packages/periphery/gpio.py", line 32, in new return SysfsGPIO.__new__(cls, *args) TypeError: __new__() takes exactly 3 arguments (2 given) Thanks.
  12. Ok, it’s working perfect.
  13. It was fixed flashing with FriendlyElec core image and then armbian... I’m going to test now the fan service.
  14. It's strange because this behaviour is after booted from MicroSD and transfer the system with nand-sata util...