Search the Community

hello guys, i recently observed a weird behavior with my nanopi R4s(jammy os). when the power goes OFF then ON in like 5 seconds duration then the nanopi does not boot up at all! i need to remove the adapter for like 15 seconds so it would be able to boot again! is this normal?

Hello everyone, I have a problem with my NanoPi R4S. The WAN (eth0) port does not work well when it is configured to work on 1Gbps/Full. When this setting is active there is about 15% packet loss, which is quite annoying. In my tests I have already been able to identify that if I configure the port to work at 100Mbps/Full everything works normally. So I found the forum-post below, that explain that some u-Boot version wasn't setting the correct clock configuration for the netwok device at boot time, but now I have installed the linux-u-boot-nanopi-r4s-edge 22.08.6 and linux-image-edge-rockchip64 22.08.8 but the problem still there. I've read millions of forums for the solution, and so far I haven't made much progress. Would anyone be able to help me? in dmesg it looks like: [ 1.853954] rk_gmac-dwmac fe300000.ethernet: IRQ eth_wake_irq not found [ 1.853967] rk_gmac-dwmac fe300000.ethernet: IRQ eth_lpi not found [ 1.854071] rk_gmac-dwmac fe300000.ethernet: PTP uses main clock [ 1.854234] rk_gmac-dwmac fe300000.ethernet: clock input or output? (input). [ 1.854244] rk_gmac-dwmac fe300000.ethernet: TX delay(0x28). [ 1.854253] rk_gmac-dwmac fe300000.ethernet: RX delay(0x11). [ 1.854267] rk_gmac-dwmac fe300000.ethernet: integrated PHY? (no). [ 1.854320] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed [ 1.854326] rk_gmac-dwmac fe300000.ethernet: clock input from PHY [ 1.859341] rk_gmac-dwmac fe300000.ethernet: init for RGMII [ 1.860175] rk_gmac-dwmac fe300000.ethernet: User ID: 0x10, Synopsys ID: 0x35 [ 1.860191] rk_gmac-dwmac fe300000.ethernet: DWMAC1000 [ 1.860199] rk_gmac-dwmac fe300000.ethernet: DMA HW capability register supported [ 1.860206] rk_gmac-dwmac fe300000.ethernet: RX Checksum Offload Engine supported [ 1.860212] rk_gmac-dwmac fe300000.ethernet: COE Type 2 [ 1.860218] rk_gmac-dwmac fe300000.ethernet: TX Checksum insertion supported [ 1.860224] rk_gmac-dwmac fe300000.ethernet: Wake-Up On Lan supported [ 1.860283] rk_gmac-dwmac fe300000.ethernet: Normal descriptors [ 1.860291] rk_gmac-dwmac fe300000.ethernet: Ring mode enabled [ 1.860297] rk_gmac-dwmac fe300000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 11.139092] rk_gmac-dwmac fe300000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 11.178717] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:01] driver [RTL8211E Gigabit Ethernet] (irq=75) [ 11.189571] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found [ 11.189610] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW [ 11.190145] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode [ 14.868809] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx I was thinking that the line below was the problem, but I'm confused now: armbianmonitor -u: https://paste.armbian.com/joperiqoso

I'd like some help please. The ethernet device naming seems inconsistent. Sometimes one interface comes up as eth0 and sometimes as eth1, and sometimes not at all. The enp1s0 interface seems to reliably come up, but not with the right config (sometimes it uses the config for enp1s0 and sometimes for eth0). I am trying to assign status IP addresses (on different networks) to each interface, but because of the unreliable bringup of the network interfaces, I can't get a config that starts up correctly and consistency on reboots or cold boots. As a test I ran the friendly-core-lite-focal from FriendlyCore and it does not have this issue. Is there something I need to do on Arabian to get the network interface bringup to work? I have static IP configs in /etc/network/interfaces.d called eth0, eth1 (these are the same, call it network A, because the 2nd network seems to sometimes come up as eth0) , and enp1s0 (configured for my second network, call it network I'd greatly appreciate any help in making the network bring up consistent.

Hello, After NanoPi R4S reboot, ethernet interface `enp1s0` disappeared. I tried soft reboot for several times but failed. If I shutdown the board and power plug out/in again, then `enp1s0` appears. I tested it several times and 100% same results. Any idea please? wg* is for vpn. please ignore them.

Dear Members, I want to play around with docker on my NanoPI R4S, and while doing that I don't want to kill my micro SD card. For this reason I connected a USB SSD, formatted it with ext4 and mounted it onto /data. Now, I want /var to use /data/var as a bind mount, in order to lessen the burden on the SD card the system is running on. What is the right way to achieve this with Armbian? Thanks! Janos

Hello everyone, due to a project I'm working with the Friendly Elec Nanopi R4S board for which I've to use the i2c bus to read data from a sensor. Unfortunately I've not been able to access it, since the system does not recognize it. I tried with different configurations using the /boot/armbianEnv.txt file with no results, however the i2c ports are enabled. To rule out functionality problems in the sensor, I connected it to other boards (e.g. nanopi Neo3 using Armbian) without problems. Do you have any idea what could be the cause of this problem? Thanks!

Hi, Armbian users. I wonder is it safe to run `do-release-upgrade` to upgrade my Armbian + Ubuntu system from `20.04` to `22.04`? ``` New release '22.04.1 LTS' available. Run 'do-release-upgrade' to upgrade to it. ```

Hello all, First of all, thanks for the Armbian project, love it so far, but had a slight problem with a kernel upgrade. To be honest, I forgot how I installed Armbian since it was a while ago, but I've been using this for a year or so. I saw that unattended-upgrades installed a new kernel and I should reboot for this change. I was a bit apprehensive, but went ahead and rebooted. The NanoPI R4S didn't come back up. I attached a serial console to debug. The console showed that the initramfs was read successfully from the SD card, but then tried to mount to root filesystem by UUID and failed (it kept saying it tried to run /boot/local-block and eventually giving up and complaing that it couldn't find the root filesystem with UUID=...). I checked if the device was present in /dev, I only saw /dev/mmcblk1, but no "p1". After a lot of debugging and trying, I noticed that if I took the SD card out, then put it back in, dmesg would show that it found the partition and only then it showed both /dev/mmcblk1 as well as /dev/mmcblk1p1. At that moment, if I exit the initramfs, it boots the system as normal. After some trial and error, I noticed this happens with the linux-image-current-rockchip64=22.02.1 image. I can boot without problems with the linux-image-current-rockchip64=21.08.2 image, so I downgraded to that version of the package and put it on hold for now. I now have a working system with the linux-image at the 21.08.2 version, even though I upgraded the other packages (like linux-u-boot-nanopi-r4s-current to) their 22.x versions! I looked around for a solution to this problem (or even understand it), but couldn't find something, so I decided to file this bug report. I did see someone mention changing the dtb (/boot/dtb/rockchip/rk3399-nanopi-r4s.dtb? /usr/lib/linux-image-current-rockchip64/rockchip/rk3399-nanopi-r4s.dtb? I don't know which one ends up in the initramfs) which I tried, but ultimately this did not fix my problem. Now whenever I install the new kernel and I need to reboot, I know I can take out the SD-card a couple of seconds after booting, then put it back it to let the OS detect the partition. It's not ideal, but better than having to open up the case and attach a serial console. Is this a known problem? Are there known solutions for this? I'm afraid this problem might persist with newer versions of the kernel and I do not want to be stuck at this version and not get security updates.

https://wiki.friendlyarm.com/wiki/index.php/NanoPi_R4S I am really excited about this board. https://www.cnx-software.com/2020/11/12/nanopi-r4s-headless-rk3399-sbc-features-up-to-4gb-ram-dual-gigabit-ethernet-usb-3-0-ports/ The first comments below this blogpost are also not so bad besides the fact that USB-C is power-in only.

Hi all! I just received a NanoPi R4S, and I got a 128GB microSDXC for it. I loaded the rk3399-sd-friendlywrt-21.02-20220721 image onto it using win32diskimager. I put the SD card in, plugged in a USB-C, and let it setup for a few minutes. When it seemed ready, I plugged my laptop into the LAN port and went to its page. I logged in, all looked good. After setting a password, I tried changing some of the LAN and WAN settings, and the page stopped loading. I waited, but nothing happened. As as how I couldn't give a proper shutdown command, I disconnected the power and plugged back in. The NanoPi then booted, but the Sys light kept blinking green twice, paused, then blinked twice again. It just kept doing this. I then unplugged, took out the SD card, formatted the card, then reloaded the image. I out the SD card back into the NanoPi, but it does the Sys blinking cycle I described. I then got a 16gb microSDHC card, loaded the image, then put the card into the NanoPi. Sadly, it still only gives the same blinking Sys light cycle. It's been going 10 minutes now, well beyond the 2–3 minutes the documentation states for setup. I plugged into the LAN port just to see if it's working but just blinking, and no, it's not doing anything. I don't have the WiFi dongle plugged in. Any advice on how to get past this Sys blinking cycle and have LAN/FriendlyWRT work again?

I have a board(nanopi r4s with rk3399 and 4g ram) and I want to run a minecraft server on it. (with adoptopenjdk arm64) After flashing the SD image I have the following problems: I can't find the IP address of my board through the IP finding tool. (unable to ssh to my system) # This happened on many OSes, including Debian OS in my VM $ ls ./ . .. java (many other files) $ ./java bash: ./java: No such file or directory Something must went wrong... How to plug the network cable? There are 2 ETH ports on the board. The first one has a "WAN" on it. Another one has a "LAN" on it. (scroll down) |= | WAN internet ---------WAN- router -|= LAN ======= ?? ======== Nanopi r4s |= | LAN

Hello, I’m running nanopi r4s with armbian 22.02.1 bullseye. After finishing edit /etc/network/interfaces via armbian-config, there was an error while restarting services. Fail to stop network-manager.service: Unit network-manager.service not loaded. However, for bullseye, network-manager.service might be no longer available.

The second USB port of NanoPI R4s is not working -- the logs were created with a USB disk inserted in port 2. # lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M If I remove and swap the USB devices: # lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M Other users are reporting the same problem, including that it works with FriendlyCore and FriendlyWRT. I can test if needed to confirm the port is not dead.

Checked latest armbian buster and focal. In both disks, connected to second USB (not the middle one) not recognized (nor fdisk -l, nor dmesg). In friendlywrt both USB ports work as expected. Hirsute 10.4.21 also fine.

I have a problem with remote desktop operation on R4S. It installs according to the RDP guide and unfortunately does not work properly, after installing vncserver I also have information about - Cannot find a running X server. Everything works fine on neo3, only here I have a problem. Log VNC xstartup terminated Sending TERM signal to Xvnc... X connection to :1 broken (explicit kill or server shutdown). FreeFontPath: FPE "/usr/share/vnc/fonts/" refcount is 2, should be 1; fixing. <13> 2021-03-16T17:40:30.716Z nanopi-r4s Xvnc[5435]: ServerManager: Server stopped Link Status R4S Please Help 1) Armbian_21.02.3_Nanopi-r4s_focal_current_5.10.21.img.xz 2) armbian-config (Install full firmware) 3) armbian-config (Install Desktop...) 4) armbian-config (Install RDP) When trying to connect from the client side after entering the login and password, the window closes. Xorg.0.log xrdp-sesman.log I observed the problem is R4S: Firmware:Armbian_21.02.3_Nanopi-r4s_focal_current_5.10.21.img.xz - is not correct Firmware: Armbian_21.02.3_Nanopi-r4s_buster_current_5.10.21.img.xz - it is good Neo 3 Armbian_20.11.6_Nanopineo3_focal_current_5.9.14_minimal.img.xz - it is good Armbian_21.02.1_Nanopineo3_focal_current_5.10.12_minimal.img.xz - is not correct What has changed, how to properly start the desktop and RDP.