Jump to content

Search the Community

Showing results for tags 'nanopi-r1'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

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 9 results

  1. Hi, Nanopi R1 - Kernel and Armbian version: 4.19.62-sunxi #5.92 I have the following problem: If I put the ethernet cable on the interface, and then turn on the nano pi, the interface receives a valid ip. But the problem is, if I start nanopi without the cable connected, and I connect after system boot, the interface does not receive ip configuration. Configs and logs: /etc/network/interfaces: source /etc/network/interfaces.d/* auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet static address 10.100.3.1 netmask 255.255.255.0 gateway 10.100.3.1 auto lo iface lo inet loopback up command iptables-restore < /scripts/iptables /scripts/iptables *nat :PREROUTING ACCEPT [120:10027] :INPUT ACCEPT [11:1747] :OUTPUT ACCEPT [24:1848] :POSTROUTING ACCEPT [4:304] -A POSTROUTING -o eth0 -j MASQUERADE COMMIT journalctl -b 0 -u NetworkManager | grep eth0 Mar 25 01:38:29 2-0211 NetworkManager[556]: <info> [1648183109.1115] keyfile: add connection /run/NetworkManager/system-connections/eth0.nmconnection (91ae80f1-5092-4e36-8f48-72f86df06873,"eth0") Mar 25 01:38:29 2-0211 NetworkManager[556]: <info> [1648183109.1178] device (eth0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') Mar 25 01:38:29 2-0211 NetworkManager[556]: <info> [1648183109.1247] device (eth0): Activation: starting connection 'eth0' (91ae80f1-5092-4e36-8f48-72f86df06873) Mar 25 01:38:29 2-0211 NetworkManager[556]: <info> [1648183109.1258] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Mar 25 01:38:29 2-0211 NetworkManager[556]: <info> [1648183109.1287] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Mar 25 01:38:29 2-0211 NetworkManager[556]: <info> [1648183109.1309] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Mar 25 01:38:29 2-0211 NetworkManager[556]: <info> [1648183109.1328] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Mar 25 01:38:29 2-0211 NetworkManager[556]: <info> [1648183109.1372] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Mar 25 01:38:29 2-0211 NetworkManager[556]: <info> [1648183109.1388] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Mar 25 01:38:29 2-0211 NetworkManager[556]: <info> [1648183109.1538] device (eth0): Activation: successful, device activated. Mar 25 01:38:37 2-0211 NetworkManager[556]: <info> [1648183117.8873] device (eth0): carrier: link connected Mar 25 01:39:56 2-0211 NetworkManager[556]: <info> [1648183196.5941] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'external') Mar 25 01:39:56 2-0211 NetworkManager[556]: <info> [1648183196.7318] device (eth0): carrier: link connected Mar 25 01:39:56 2-0211 NetworkManager[556]: <info> [1648183196.7333] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'external')
  2. Creating a wireless access point through armbian-config fails in the new 22.02 release for the popular TP-Link TL-WN725N USB Wifi Dongle. I am raising it here because it worked previously on 21.08. I have tracked it down to be related to a driver change. Release version 22.02 uses the r8188eu and in fact this is one of the drivers the Hotspot configuration actually warns you about. Could this commit be related? In order to overcome this I have downloaded the official TP Link driver sources. but failed to compile them because headers are missing (even after using armbian-config to install headers). I have also followed the official documentation to learn about how to build a wireless driver but the make scripts step fails. On a positive note, bluetooth never worked on the nanopi-r1 model but does now work with the new 22.02 release even though the website still states "Bluetooth is not yet enabled." which is patently untrue
  3. Hi, We've built a network experimentation system using NanoPi R1 modules, but when load testing the system with iperf3, we are seeing the on-board RTL8152 interface enter a state where it does not seem to be responding until the board is power cycled. The system consists of 32 NanoPi modules connected in a torus, with the 1Gig interface connected to its neighbour's 100Mbit interface. An additional USB Ethernet dongle functions as a control interface. The modules are powered from a Ubiquiti PoE switch, using this type of isolated PoE splitter. Eyeballing the switch UI, power consumption per node seems to hover between 2.3W-3.5W, depending on load. We're using the latest Ubuntu-based image, with kernel 5.4.28. Under light loads, the system works fine, but when performing load tests, we're seeing the RTL8152 entering some kind of lock-up state. As can be seen from the system logs, first the netdev watchdog triggers, then the kernel tries to reset the USB device, finally reporting that it is unable to enumerate the device. After encountering this problem, if the node is rebooted, the USB device can still not be enumerated, and will remain unresponsive until it is powercycled. The external USB Ethernet dongle stays working through all of this, so it seems that the USB host controller and subsystem works OK. We haven't seen any issues with the 1Gig interface. Searching the net, I have found reports with similar backtraces, but they seem to be either several years old, or related to the RTL8153 chip, which shares the same driver. In either case, none of them seem to offer any answers as to what's going on, or if there is any fix. Has anyone else seen this? Any ideas if it's a driver or hardware issue? Relevant bit from the kernel log: Full diagnostic dump:
  4. I've been using the Armbian R1 image (Armbian_20.02.1_Nanopi-r1_buster_current_5.4.20.7z) on the NanoPi R1S with good success. In particular, the USB host port worked perfectly, with no changes required. I thought it was probably about time to upgrade to a newer kernel, so I downloaded Armbian_21.02.1_Nanopi-r1_focal_current_5.10.12.img, flashed it to an SD card, and booted. However, plugging in an external USB device results in absolutely zero shoing up in `dmesg -w`. I tried a USB-UART (STM32-based ACM), USB3 hub, USB 3 Mass Storage (Kingston 16GB), and a Playstation 3 Eye, without any entries in dmesg. To do some debugging, I also downloaded Armbian_21.02.1_Nanopi-r1_buster_current_5.10.12.img, and did the same testing, with the same result. I have verified that there is power on the Vcc, as the camera's microphone light lights up. I should mention that the built-in Realtek 8153 Ethernet port IS recognised: root@nanopi-r1:~# lsusb Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@nanopi-r1:~# Any suggestions as to what I can do to figure out why this USB port is not working?
  5. Hi, I am trying to boot image Armbian_20.02.1_Nanopi-r1_buster_current_5.4.20.img, without success ... First, i am using following line to create SD ... ansible@solo:/mnt/backup$ sudo dd if=./Armbian_20.02.1_Nanopi-r1_buster_current_5.4.20.img of=/dev/mmcblk0 bs=1M status=progress ;sudo sync After connected my tty on internal pins on PCB, it is possible to connect to this tty and look at the first u-boot log ... Welcome to minicom 2.7.1 OPTIONS: I18n Compiled on May 6 2018, 08:02:47. Port /dev/tty-target-srv-nanopir1-170-position-1.2.4.1, 20:34:41 Press CTRL-A Z for help on special keys U-Boot SPL 2019.10-armbian (Feb 17 2020 - 06:18:08 +0100) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2019.10-armbian (Feb 17 2020 - 06:18:08 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi R1 DRAM: 1 GiB MMC: mmc@1c0f000: 0, mmc@1c11000: 1 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Net: phy interface7 Error: ethernet@1c30000 address not set. eth-1: ethernet@1c30000 Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3789 bytes read in 3 ms (1.2 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 236 bytes read in 3 ms (76.2 KiB/s) 7342788 bytes read in 557 ms (12.6 MiB/s) 7744344 bytes read in 587 ms (12.6 MiB/s) Found mainline kernel configuration 29509 bytes read in 10 ms (2.8 MiB/s) 504 bytes read in 7 ms (70.3 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo 504 bytes read in 7 ms (70.3 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost1.dtbo 502 bytes read in 7 ms (69.3 KiB/s) Applying kernel provided DT overlay sun8i-h3-uart1.dtbo 4155 bytes read in 7 ms (579.1 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 7342724 Bytes = 7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 498ff000, end 49fffa84 ... OK Loading Device Tree to 4988f000, end 498fefff ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. But not possible to have the login (!). As a result, after umounting SD and modifying code in in /boot/armbianEnv.txt (verbosity=7), then following booting is always the same... Regards
  6. I have two NanoPi R1s, both with Armbian Buster. I want to use both as wireless access points, however the wifi seems to be problematic. It always works at first, but not anymore after updating, changing the config and rebooting. My hostapd config is the following: # # armbian hostapd configuration example # # nl80211 mode # ssid=[myssid, contains some numbers] interface=wlan0 hw_mode=g channel=6 [11 on the other one] #bridge=br0 driver=nl80211 logger_syslog=0 logger_syslog_level=0 wmm_enabled=1 wpa=2 preamble=1 wpa_psk=[random thing armbian-config generated] wpa_passphrase=[secret] wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP rsn_pairwise=CCMP wpa_strict_rekey=1 wpa_disable_eapol_key_retries=1 ieee80211w=2 auth_algs=1 macaddr_acl=0 noscan=1 ## IEEE 802.11n ieee80211n=1 ht_capab=[DSSS_CK-40][HT20+] country_code=DE ieee80211d=1 ## IEEE 802.11n ### IEEE 802.11a #hw_mode=a ### IEEE 802.11a ### IEEE 802.11ac #ieee80211ac=1 #vht_capab=[MAX-MPDU-11454][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][MAX-A-MPDU-LEN-EXP3] #vht_oper_chwidth=1 #vht_oper_centr_freq_seg0_idx=42 ### IEEE 802.11ac # controlling enabled ctrl_interface=/var/run/hostapd ctrl_interface_group=0 Systemd says hostapd is loaded, active and exited. The wifi is not detectable by any of my devices. If I try to start hostapd manually via hostapd /etc/resolv.conf , it says Configuration file: /etc/hostapd.conf wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE wlan0: Could not connect to kernel driver Using interface wlan0 with hwaddr 18:93:7f:73:4a:ec and ssid "[SSID from config file]" random: Only 18/20 bytes of strong random data available from /dev/random random: Not enough entropy pool available for secure operations WPA: Not enough entropy in random pool for secure operations - update keys later when the first station connects wlan0: Could not connect to kernel driver Interface initialization failed wlan0: interface state COUNTRY_UPDATE->DISABLED wlan0: AP-DISABLED wlan0: Unable to setup interface. wlan0: interface state DISABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING hostapd_free_hapd_data: Interface wlan0 wasn't started nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Not sure whether this is a bug or an error on my side. It used to work with OpenWrt, however the problem there is the only images for it are provided by FriendlyArm (there are no official images by the OpenWrt team), and that image is still on version 18.01, which doesn't get any security updates anymore. EDIT: I maybe also should have mentioned the WiFi and hotspot options disappear in `armbian-config`. `ip addr` or `ip link` still show the wlan0 interface however. Maybe a recent update broke the driver or so? Still not sure whether I should move this to H3 bug reports. EDIT 2: I now tried to connect to a different WiFi with `wpa_supplicant`. Works with both `wext` and `nl80211` drivers (the former returns some `IOCTL` errors, but isn't used by hostapd anyway, and it still seems to work nevertheless). So the issue is probably more related to hostapd than to the driver. EDIT 3: `iw list` said it only supported CMAC-128 ciphers, so I removed any config that would use 256 bit ciphers. Also various sources suggested this was an old bug, and I needed to run `nmcli radio wifi off` and `rfkill unblock wlan` before starting hostapd, however that didn't change anything.
  7. Hi, I am running Debian buster 10.1 with following kernel on nanopir1 (1Gb of RAM) Linux srv-nanopir1-170 5.3.9-sunxi #5.99.191113 SMP Wed Nov 13 08:12:49 CET 2019 armv7l GNU/Linux I have all services up on local LAN Ethernet port, but not possible for me to setup WAN Ethernet port . Packages installed are .... The boot sequence is ... My current network configuration in udev is .... As a result, r8152 kernel module is correctly installed After connected one RJ45 to external DHCP server (running) , it is not possible to setup interface According hardware documentation, it seems that WAN port is based on on RTL8211E (§ 3.1) http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1 As a result, perhaps this bug is due to the fact there is no rtl8211e drivers Where is the firmware and the drivers ? Thanks in advance for your help tty-from-srv-nanopir1-170-2019-11-14-15h-39min.ok.txt
  8. Hi! Just saw a new board from FriendlyARM - NanoPi R1 (https://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=248). It based on Allwinner H3, has dual Ethernet port, wi-fi and Bluetooth, USB, and onboard eMMC. Memory options are 512MB or 1GB. It comes in a case, just add power supply. Looks quite fun SBC for IoT and for micro router. I was unable to find Armbian images for this board. Could you please comment if is it possible to use images for other Allwinner H3 boards? Do you have any plans to support this board? Thank you in advance for your comments!
  9. I am having problems with the NanoPi R1. I loaded the latest Armbian for R1 on flash. All works good. I went to armbian-config to load into eMMC. The last step of the process had weird text on the dialog, I clicked "OK" anyway, and the process seemed to be working. But after removing uSD card and rebooting, the board does not work. The red led stays on solid. Did anyone successfully burn the image from uSD to eMMC using the tool in armbian-config?
×
×
  • Create New...