i5Js
-
Posts
63 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by i5Js
-
-
On 2/16/2021 at 12:23 AM, LiX said:
Hi, it's 5.10.12-rockchip64 #21.02.1, and seems my situation has been improved since I increased bootdelay in armbianEnv.txt from 3 to 10, I got 0/2 fail rate in the past 2 days.
Can you share your armbianEnv.txt? I've just checked mine and it has not that setting.
-
Thanks all for the messages, I've tried with another one, 6.5V, and it's the same, it was rebooted 3.5hours ago. I don't know if it could be a kernel problem, I'm using also a M4V1 with SATA hat, and kernel 5 and works flawless (Up time: 27 days 1:15), so I think it is related to the PSU/cable...
My main problem here is I'm not good with electric stuff, meters etc, I have an standard meter, but I don't know even how to use it
Sorry for asking @NicoD with the usb meter, should be plug and see?
if so, I think even I could make it.
I'm going to look for a good usb cable...
Thanks.
-
The cable made something different, since the board was up almost 1.5 days, but it was rebooted again.
@Werner I'm very noob, can you explain how can I power it up from GPIO? or which other PSU could work? I read in the internet some guys are using Raspberry's Pi 4 PSU, but reading the specs, are lower than the official from friendelec.
Many thanks.
-
Thanks both, I’ll start replacing the cable.
-
21 minutes ago, Igor said:
5V powering via USB-C is on the edge (especially for hungry hw) if it comes via official or unofficial power adapter / cable.mmm perhaps the cable is the problem... how could I check it? Also I'm using a an adapter to fit from Asia to Europe
Anyway, is there any other alternatives you can recommend me?
-
8 minutes ago, Igor said:
Unstable / insufficient powering would be 1st guess.Interesting, because I'm using the official power adapter from friendelec
-
-
Hello all,
I have this board running in a k3s kubernetes cluster, and almost everyday, different time, the board reboots. Please, could you help me to figure out which is the problem? The armbianmonitor output is bellow:
Many Thanks,
-
On 2/12/2021 at 11:23 PM, pkfox said:
What SSD are you using? I've been using Samsung 970 EVO for a couple of years without any issues
Which kernel are you using? Because my board is rebooting unexpectedly almos every day...
-
I’ve updated the kernel to 5.10.12, and it’s failing and suffering randomly reboots all the time.
I’ve uploaded the armbianmonitor output to http://ix.it/2OOZ I can’t see which is the problem of theses reboots on the logs.
-
Mine is working, but the 5.10-RC7 kernel... Thanks to your message my nvme is still working, I was going to upgrade the kernel.
-
Well. with dev kernel I'm suffering kp... I don't know honestly If it's because the nvme hat or it has a hardware issue.
-
I've installed a dev kernel (Linux 5.10.0-rc7-rockchip64)... with 5.9 I've suffered a few kernel panics in a short period of time.
-
I’ve tried with the kernel 5.10.0-RC7, and It’s detected again.... I would like to know which are the differences with the stable kernel :)
-
Sorry to bump this topic again, I'm trying to use kernel 5 in my nanopc-t4, but is still not detecting the nvme. How can I apply that patch?
Thanks.
-
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 vpcie3v3-supply from device tree [ 1.961416] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property in node /pcie@f8000000 failed [ 1.961433] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found [ 1.961443] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree [ 1.961531] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed [ 1.961546] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found [ 1.961556] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree [ 1.961567] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed [ 1.961581] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found [ 1.961591] rockchip-pcie f8000000.pcie: no bus-scan-delay-ms in device tree, default 0 ms [ 1.961601] rockchip-pcie f8000000.pcie: missing "memory-region" property [ 1.961617] PCI host bridge /pcie@f8000000 ranges: [ 2.106173] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00 [ 2.113740] pcieport 0000:00:00.0: enabling device (0000 -> 0002) [ 2.114038] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt [ 2.114051] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt [ 2.114067] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded [ 2.114204] aer 0000:00:00.0:pcie02: service driver aer loadedroot@nanopct4:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1 179:0 0 14.6G 0 disk └─mmcblk1p1 179:1 0 14.4G 0 part mmcblk1boot0 179:32 0 4M 1 disk mmcblk1boot1 179:64 0 4M 1 disk mmcblk1rpmb 179:96 0 4M 0 disk mmcblk0 179:128 0 7.5G 0 disk └─mmcblk0p1 179:129 0 7.3G 0 part / zram0 252:0 0 50M 0 disk /var/log zram1 252:1 0 1G 0 disk [SWAP] zram2 252:2 0 1G 0 disk /tmp nvme0n1 259:0 0 931.5G 0 disk ├─nvme0n1p1 259:1 0 450G 0 part ├─nvme0n1p2 259:2 0 400G 0 part └─nvme0n1p3 259:3 0 81.5G 0 part -
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 of f8000000.pcie failed with error -110
-
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....
-
Good job! Many thanks! Could this also work with the nanopi M4 V2?
-
13 hours ago, Tido said:
Read the log via UART with another SBC, this way you can catch the last lines before it reboots.
Or you change the settings so that Armbian writes everylog right away to the SDcard
Thanks for your reply, I'll try to write the logs to SD
-
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
-
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!
-
And what about the fan control? Because I've downgraded to 4.4 because of that.
-
31 minutes ago, Werner said:
Just found via google. You can disable this "spam" with echo 2 >/proc/sys/abi/cp15_barrier
About your actual issue, sorry no idea
Yes, I found it as well, in fact I've to add this every time it reboots.
Randoms reboot NanoPi M4V2
in Rockchip
Posted
The new cable arrived. It supports up to 4A so fingers cross.