Search the Community

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.

Hi, I have read the topic about emmc backuping, thank to @martinayootte . Now, how do I restore from backup? New Nano Pi has booted. SD/USB card with backup image is attached. Must I simply use dd form "if" to emmc? Is it correct? Emmc contains image that is being run now, and as far as I know, some files are locked? Does it matter? Brgs, Aleksei Mikutskiy

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.

Has anyone been able to install a remote desktop on the R2S? If so I would be very interested in how that was achieved?

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.

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!

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.

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.

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#