Search the Community
Showing results for tags 'nanopi-r2s'.
I have set up a server on a nanopi-r2s running Armbian version 5.15.25-rockchip64. It all works fine apart from one thing: while other devices can successfully use BIND on the server, the server itself cannot find the local BIND. If I type in this command host device.localdomain 127.0.0.1 it returns the following: device.localdomain has address 192.168.0.20 192.168.0.20 is the correct address for device.localdomain from the local BIND. If I omit the 127.0.0.1 from the command, it does not find the correct address.: device.localdomain has address 126.96.36.199 device.localdomain has address 188.8.131.52 Host device.localdomain not found: 3(NXDOMAIN) The problem seems to be that resolvconf is not adding 127.0.0.1 to resolv.conf. Here is resolv.conf: # Generated by NetworkManager nameserver 2001:4489:500:102::2 nameserver 2001:4489:506:102::2 nameserver 2001:4488:0:1::76 if, just for test purposes, I manually edit /run/resolvconf/resolv.conf to add 127.0.0.1, the host command works without 127.0.0.1. Clearly, the problem is that resolvconf isn't adding the localhost address to resolv.conf. I have tried several different ways to add 127.0.0.1 to resolv.conf. This includes: editing /etc/systemd/resolved.conf to add DNS=127.0.0.1 editing /etc/default/named to add RESOLVCONF=yes editing /etc/network/interfaces to add dns-nameservers=127.0.0.1 None of these methods makes any difference to what appears in resolv.conf. Here are the files: [Resolve] # Some examples of DNS servers which may be used for DNS= and FallbackDNS=: # Cloudflare: 184.108.40.206 220.127.116.11 2606:4700:4700::1111 2606:4700:4700::1001 # Google: 18.104.22.168 22.214.171.124 2001:4860:4860::8888 2001:4860:4860::8844 # Quad9: 126.96.36.199 2620:fe::fe DNS= "127.0.0.1" #FallbackDNS= #Domains= The example I found showed the ip address in quotes, as above: I tried without the quotes as well, and that didn't work either. # # run resolvconf? RESOLVCONF=yes # startup options for the server OPTIONS="-u bind" # armbian-config created source /etc/network/interfaces.d/* # Local loopback auto lo iface lo inet loopback dns-nameservers 127.0.0.1 # Interface eth0 auto eth0 allow-hotplug eth0 iface eth0 inet static address 192.168.100.10 netmask 255.255.255.0 gateway 192.168.100.1 # Interface lan0 auto lan0 allow-hotplug lan0 iface lan0 inet static address 192.168.0.15 netmask 255.255.255.0
@Contributor/Maintainer AR-1172 - fix complete 08 May 2022 There is was a bug in the 5.15, 5.16 and 5.17 kernel r8152 driver that affected RTL8153b Gigabit USB Ethernet (LAN0) on the Orange Pi R1plus LTS and other boards. The bug only presents on high load and I can trigger it reliably with bidirectional high load on Orange Pi R1plus LTS. The bug kills the RX interface and it requires power down to reset. I assume that it also affects the Orange Pi R1plus, and there are reports of it affecting NanoPi R2S. I would assume that other boards could be impacted. My proposed fix is to revert the driver back to the version used in 5.10 kernel (and to disable TX offload by default). This driver works reasonably well if TX offload is disabled (but with TX offload enabled, another bug is triggered on load). The reason for this post is to alert other board maintainers and to inquire if you are okay with this proposal. The driver from kernel-5.10 (v2.15.0 (2021/04/15)) can be used with 5.15 and 5.16 with minor tweaks. Edit: While researching options for disabling TX ofload, I found a thread on the forums for Helios that talked about xhci trb quirk in rockchip64-current. I followed it to this commit, https://github.com/armbian/build/commit/8eece74eb581367625e6ebcc12ee5c6f4f44617c The quirk is currently funcional for dwc3 xhci usb on rockchip64 and activated for rk3399. It appears that the quirk may not have been applied to rk3328 in the past, so I tried including it in rk3328.dtsi, and it worked very well with the mainline driver on 5.15, 5.16 and 5.17. This means that it is not necessary to revert the driver to the one in 5.10. I have modified AR-1172 and submitted a PR. PR has been merged and fix will be in the new release.
Hi, I have one FriendlyARM NanoPi R2S. It should have 1G DDR4 memory. Everything works fine with latest Armbian 20.02.08 except only 512M memory shows up. Both Buster and Bionic have the same issue: Armbian_20.02.8_Nanopi-r2s_buster_current_5.4.28 Armbian_20.02.8_Nanopi-r2s_bionic_current_5.4.28 I tried FriendlyARM official FriendlyCore. I can see all 1G memory, /proc/meminfo on FriendlyCore is as follows: MemTotal: 971052 kB MemFree: 842880 kB MemAvailable: 844352 kB Buffers: 8012 kB Cached: 48272 kB SwapCached: 0 kB Active: 45904 kB Inactive: 31580 kB Active(anon): 21408 kB Inactive(anon): 4768 kB Active(file): 24496 kB Inactive(file): 26812 kB Unevictable: 4 kB Mlocked: 0 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 1392 kB Writeback: 0 kB AnonPages: 21116 kB Mapped: 24300 kB Shmem: 4976 kB KReclaimable: 19212 kB Slab: 36376 kB SReclaimable: 19212 kB SUnreclaim: 17164 kB KernelStack: 1824 kB PageTables: 780 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 485524 kB Committed_AS: 114152 kB VmallocTotal: 262930368 kB VmallocUsed: 2664 kB VmallocChunk: 0 kB Percpu: 656 kB AnonHugePages: 0 kB ShmemHugePages: 0 kB ShmemPmdMapped: 0 kB FileHugePages: 0 kB FilePmdMapped: 0 kB CmaTotal: 16384 kB CmaFree: 15344 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB Hugetlb: 0 kB I don't have UART to USB at home, so i get these information through ssh. How can i use the other half of the memory?