Jump to content

Search the Community

Showing results for tags 'nanopi-r2s'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Product Groups

  • Misc
  • Support

Categories

  • Armbian
  • Armbian releases

Categories

  • Volunteering opportunities

Calendars

  • Community Calendar

Categories

  • Members

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 12 results

  1. I first made a self-built image for nanopi-r2s and everything is fine. But another self-built image of Nanopi-R2S seems refuse to boot after enabling these configurations: `DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT`, then `DEBUG_INFO_BTF` and `MODULE_ALLOW_BTF_MISMATCH` But the LED on RJ45 blinks, and I can ping the IP that I get from my router DHCP, but SSH connection refused. So I guess it may have booted, but refuse SSH connection. I have no TTL serial connections yet, I'll check it and post the logs here some time later. Can anybody help? How can I enable ssh with? Is it possible to enable it at build stage? Thanks.
  2. Has anyone been able to install a remote desktop on the R2S? If so I would be very interested in how that was achieved?
  3. Hi, I just start using armbain after login I saw this error date: invalid date '</body>\r' per attach image. What cause this error ? I have look into motd configuration this error not coming from there. Another monitor package that was installed is rpimonitor. It's look like a some kind of script that run after login.
  4. Hi, I've installed minimal cli version and it restarts when connected to PC via on-board USB-C connector. Board hangs after: [ OK ] Reached target Hardware activated USB gadget. Host computer does: [ 4881.959467] usb 1-5: new high-speed USB device number 47 using xhci_hcd [ 4882.140301] usb 1-5: New USB device found, idVendor=0525, idProduct=a4a6, bcdDevice= 5.15 [ 4882.140315] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4882.140322] usb 1-5: Product: Gadget Serial v2.4 [ 4882.140327] usb 1-5: Manufacturer: Linux 5.15.80-rockchip64 with ff580000.usb [ 4883.572730] usb 1-5: USB disconnect, device number 47 [ 4884.079492] usb 1-5: new high-speed USB device number 48 using xhci_hcd [ 4884.229424] usb 1-5: device descriptor read/64, error -71 [ 4884.499520] usb 1-5: device descriptor read/64, error -71 [ 4884.769501] usb 1-5: new high-speed USB device number 49 using xhci_hcd [ 4884.919510] usb 1-5: device descriptor read/64, error -71 [ 4885.189426] usb 1-5: device descriptor read/64, error -71 [ 4885.309571] usb usb1-port5: attempt power cycle [ 4885.779457] usb 1-5: new high-speed USB device number 50 using xhci_hcd [ 4885.779556] usb 1-5: Device not responding to setup address. [ 4885.999459] usb 1-5: Device not responding to setup address. [ 4886.219537] usb 1-5: device not accepting address 50, error -71 [ 4886.369509] usb 1-5: new high-speed USB device number 51 using xhci_hcd [ 4886.369639] usb 1-5: Device not responding to setup address. [ 4886.589578] usb 1-5: Device not responding to setup address. [ 4886.809467] usb 1-5: device not accepting address 51, error -71 [ 4886.809571] usb usb1-port5: unable to enumerate USB device On regular CLI version it seems to work for now. Or in fact it stops working after initial setup!
  5. Hello everyone, I'm running the image from NanoPi R2S on a NanoPi R2C Plus (that has 8 GB eMMC). Is well working, but I would like to install the OS on the eMMC. Is it possible? Thanks.
  6. Hi, Have the r2s for some time and it worked well in the beginning. But then it started to freeze randomly. The logs do not have any error in it. Initially I thought it could be the interface drive problem, changed the interface and still freezes. When the r2s is frozen, serial port won't respond. Keeping serial connection and restarting the r2s, boot messages show normally. When I keep the serial connected, r2s do not freeze (tried for more than a week). Found this other post, not sure if this is the same problem as it does boot, but seems related. mUSB serial connection rarely works. Have to boot some times until it works. Although I am an experienced linux user, I am not experienced with armbian, mUSB connection and related kernel modules, etc. Does anyone has suggestions on how to troubleshoot/fix this issue? It has been really frustrating. I want to build some services in it but if it does not stays on, it will bring more trouble than solution.
  7. Actuaylly, I have a two problem. First is, If I print large outputs, It's out was unpredictable. $PS1 randomly added ...snip... ], "locs": [ "ALX", "SOP", "PNX", "NYC" ], "jbound": "0.010000", "tbound": "0.05" } ] } 20220908.04:53:56 root@openskyr2s:~# , <<<<<<--------------------- really randomly appeared my $PS1 in output / Even I use less/more, it sometimes happens. "val1": 4, "val2": 0, "subkey1": [ "blah" ], "filters": [ ...snip... Second is, Prints large outputs(jq , cat) to default console few times, I completely can not execute 'htop' or 'mesg'. If I change $TERM linux to xterm-256color, 'htop' works again. But still 'mesg' commands hung. Above two issue was not resolved apt update/upgrade. - dmesg was clean - stty ixon/ixoff, add delays - seterial low_latency What I tried above, it does not helped output stability. Here is my stty conf 20220908.05:14:06 root@openskyr2s:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=nanopi-r2s BOARD_NAME="Nanopi R2S" BOARDFAMILY=rockchip64 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=13f5fba13 VERSION=22.05.3 LINUXFAMILY=rockchip64 ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image BRANCH=current 20220908.05:14:15 root@openskyr2s:~# uname -a Linux openskyr2s 5.15.52-rockchip64 #22.05.4 SMP PREEMPT Mon Jul 4 09:40:29 CEST 2022 aarch64 GNU/Linux 20220908.05:14:20 root@openskyr2s:~# stty -a speed 1500000 baud; rows 57; columns 227; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; discard = <undef>; min = 1; time = 0; -parenb -parodd -cmspar cs8 hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -ixon -ixoff -iuclc -ixany -imaxbel iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon -iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke -flusho -extproc 20220908.05:14:22 root@openskyr2s:~# Any suggestions, solutions are welcome.
  8. I'm not sure this is right place to submit libgnutls30 armbian package issues. If anyone libgnutls30 to 3.6.7.4-deb10u9, you may have trouble to connect some SSL destinations. I revert it back to 10u7, then problem was gone. 20220817.05:18:10 root@armbianr2s:~/lkm# echo -e "GET / HTTP/1.1\n\n\n" | openssl s_client -connect web.telegram.org:443 -tlsextdebug CONNECTED(00000003) ^C 20220817.05:18:47 root@armbianr2s:~/lkm# #SSL_CONNECTION_PROBLEM_SOME_SITES_AFTER_UPGRADE_libgnutls30_THEN_REBOOT; 20220817.05:19:03 root@armbianr2s:~/lkm# #PROBLEM_ALSO_HAPPENED_WHILE_tcptraceroute_THEREFORE_I_WAS_REALLY_CONFUSED_AND_WASTED_TIME. BECAUSE, tcptrace and python NOTE TO ME Connection Timeout(I_WAS_MISTAKEN_PROBLEM_BETWEEN_NETWORK_PATH_OR_DESTINATION_SERVICE_BLOCKS_MY_IP) 20220817.05:19:45 root@armbianr2s:~/lkm# #BUT,THIS CONNECTION PROBLEM HAPPENDED BY libgnutls30!!! 20220817.05:54:50 root@armbianr2s:~/lkm# apt-get -s install libgnutls30=3.6.7-4+deb10u7 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: gnutls-bin The following packages will be DOWNGRADED: libgnutls30 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Inst libgnutls30 [3.6.7-4+deb10u9] (3.6.7-4+deb10u7 Debian:10.12/oldstable [arm64]) Conf libgnutls30 (3.6.7-4+deb10u7 Debian:10.12/oldstable [arm64]) 20220817.05:55:11 root@armbianr2s:~/lkm# echo -e "GET / HTTP/1.1\n\n\n" | openssl s_client -connect web.telegram.org:443 -tlsextdebug CONNECTED(00000003) TLS server extension "supported versions" (id=43), len=2 0000 - 03 04 .. TLS server extension "key share" (id=51), len=36 0000 - 00 1d 00 20 cc c3 07 cd-ca 4c 1a ae db 51 b9 e3 ... .....L...Q.. 0010 - 86 02 18 3e fa b5 b7 bd-0d f2 27 20 fb e8 c9 a5 ...>......' .... 0020 - 16 45 ff 08 .E.. TLS server extension "server name" (id=0), len=0 depth=2 C = US, ST = Arizona, L = Scottsdale, O = "GoDaddy.com, Inc.", CN = Go Daddy Root Certificate Authority - G2 verify return:1 depth=1 C = US, ST = Arizona, L = Scottsdale, O = "GoDaddy.com, Inc.", OU = http://certs.godaddy.com/repository/, CN = Go Daddy Secure Certificate Authority - G2 verify return:1 depth=0 OU = Domain Control Validated, CN = *.web.telegram.org verify return:1 --- Certificate chain 0 s:OU = Domain Control Validated, CN = *.web.telegram.org i:C = US, ST = Arizona, L = Scottsdale, O = "GoDaddy.com, Inc.", OU = http://certs.godaddy.com/repository/, CN = Go Daddy Secure Certificate Authority - G2 1 s:C = US, ST = Arizona, L = Scottsdale, O = "GoDaddy.com, Inc.", OU = http://certs.godaddy.com/repository/, CN = Go Daddy Secure Certificate Authority - G2 i:C = US, ST = Arizona, L = Scottsdale, O = "GoDaddy.com, Inc.", CN = Go Daddy Root Certificate Authority - G2 2 s:C = US, ST = Arizona, L = Scottsdale, O = "GoDaddy.com, Inc.", CN = Go Daddy Root Certificate Authority - G2 i:C = US, O = "The Go Daddy Group, Inc.", OU = Go Daddy Class 2 Certification Authority 3 s:C = US, O = "The Go Daddy Group, Inc.", OU = Go Daddy Class 2 Certification Authority i:C = US, O = "The Go Daddy Group, Inc.", OU = Go Daddy Class 2 Certification Authority --- Server certificate -----BEGIN CERTIFICATE----- MIIGvDCCBaSgAwIBAgIJAJjKNDH6CCbXMA0GCSqGSIb3DQEBCwUAMIG0MQswCQYD ..SNIP.. ..SNIP.. ..SNIP.. xFtIy/Z3OffAcOWV/l+xh7s/8E/cqSNLOvnDPCgCW1s98JWw7xwL+EwGYxS4N2pY -----END CERTIFICATE----- subject=OU = Domain Control Validated, CN = *.web.telegram.org issuer=C = US, ST = Arizona, L = Scottsdale, O = "GoDaddy.com, Inc.", OU = http://certs.godaddy.com/repository/, CN = Go Daddy Secure Certificate Authority - G2 --- No client certificate CA names sent Peer signing digest: SHA256 Peer signature type: RSA-PSS Server Temp Key: X25519, 253 bits --- SSL handshake has read 5720 bytes and written 388 bytes Verification: OK --- New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 Server public key is 2048 bit Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) --- DONE 20220817.05:55:28 root@armbianr2s:~/lkm#
  9. 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 36.86.63.182 device.localdomain has address 36.86.63.182 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: 1.1.1.1 1.0.0.1 2606:4700:4700::1111 2606:4700:4700::1001 # Google: 8.8.8.8 8.8.4.4 2001:4860:4860::8888 2001:4860:4860::8844 # Quad9: 9.9.9.9 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
  10. @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.
  11. I have a strange problem with my R2S. I grabbed latest buster and focal images, burned them using Balena Etcher onto a pair of 32GB SanDisk Extreme Cards and neither is booting. Serial console shows that boot process gives up waiting for root file system and drops me into initramfs shell. Looking into /dev, I see no mmcblk0 device (or any other block device apart from loops). If I now eject and re-insert the card, the device shows up. If I do it during boot process, while the board is still waiting for rootfs, boot process continues correctly. Reboots are fine, but if I unplug the board for longer than a second it's back to initramfs for me. Serial log:
  12. 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?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines