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

  • 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

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

  1. I am trying to build an armbian image for a nanopi R1S-H3 this used to be possible in the past. Now when I build and select the extended board list the R1S-H5 is present but not the R1S-H3. Should I build using another H3 board, or is the R1S-H5 close enought o get it to boot.
  2. Hi all, I've just booted my NanoPi M4 V2 after not using it for a year or so and when I log in via ssh I'm told the / usage is at 100% - I've deleted all logs and the usual suspects but to no avail uname gives Linux M4V203 5.10.63-rockchip64 #21.08.2 SMP PREEMPT Wed Sep 8 10:57:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux I'm using a 32gb SD card df -h gives Filesystem Size Used Avail Use% Mounted on udev 1.9G 0 1.9G 0% /dev tmpfs 387M 41M 346M 11% /run /dev/mmcblk1p1 29G 29G 0 100% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup tmpfs 1.9G 4.0K 1.9G 1% /tmp /dev/nvme0n1p1 458G 73M 434G 1% /mnt/Docker /dev/nvme0n1p2 458G 280G 155G 65% /mnt/music /dev/zram0 49M 20M 26M 44% /var/log tmpfs 387M 0 387M 0% /run/user/0 any ideas ?
  3. Armbian Jammy (Minimal CLI) boots/works fine from an SD Card. (Armbian_23.5.2_Nanopi-r1_jammy_current_6.1.30_minimal.img.xz) apt update && apt upgrade -y && apt autoremove apt install armbian-config -y armbian-install I choose option #2 - Boot from eMMC - System on eMMC Accept the warning. I choose option #1 - ext4 The install appears to move along smoothly. I choose the "Power Off" option. Pull the power, remove the SD Card. Reconnect the power. I never see the "heartbeat" on the "System"(red) LED. The NanoPi never boot or obtains an IP address.
  4. I'm a newbie. Got the NanoPi R1 that sports a UART but no Video Output. Now when I want to read the output of the serial console I need a 3-wire cable and a converter, that much I know. But what is the baud rate? Where is this configured on the armbian NanoPiR1 image (on my raspberry Pi I just checked and found the file /boot/cmdline.txt with that settings, in my case it's 115200) Why is the baud rate nowhere documented? On the download page https://www.armbian.com/nanopi-r1/ it is stated that "serial console is enabled on UART1, which is exposed on chasis" , but no hint about which speed to use. There neither is any info about the baud rate on the friendlyelec site where they provide various OS images for download. Plenty of documentation on how to wire the serial cable though. Is there a kind of industry standard that everyone knows and therefore it is not necessary to include it in the how-to guides. Or are we supposed to try every rate from 9600 upward until we get readable output? Thanks. So far I couldn't get my NanoPi to work, it just blinks red, and I haven't seen anything on the console too. It's a brick, possible defective hardware.
  5. Hi, i am beginner in SBC other than Rapsberry Pi and i just got my NanoPi R1 with case. I try power the board without SD card for the first time and i see that friendlyWRT already installed but i would like to use a general OS. Since i can't download the official OS from friendlyelec, i saw that armbian is another way and might be better. I follow all step in quick start guide page, and can't even get my board boot up. Below is the list of OS that i try with SD card: - Armbian_22.11.1_Nanopi-r1_jammy_current_5.15.80_minimal - Armbian_22.11.1_Nanopi-r1_bullseye_current_5.15.80 - Armbian_22.11.1_Nanopi-r1_bullseye_current_5.15.80_minimal - Armbian_22.02.1_Nanopi-r1_bullseye_current_5.15.25 - Armbian_21.08.1_Nanopi-r1_buster_current_5.10.60 - Armbian_21.08.1_Nanopi-r1_bullseye_current_5.10.60 - Armbian_21.05.1_Nanopi-r1_buster_current_5.10.34 - Armbian_21.02.1_Nanopi-r1_buster_current_5.10.12 - Armbian_22.08.1_Nanopi-r1_bullseye_current_5.15.63 - Armbian_22.05.4_Nanopi-r1_bullseye_current_5.15.48 - Armbian_22.02.1_Nanopi-r1_focal_current_5.15.25 In each sd card flash, i always format the sd card using SD Card Formatter. There are different outputs from all image above: No output at all Happen in 5.10.12 Stuck in "starting kernel.." Happen in 5.10.34 , 5.10.48 and 5.10.25 images U-Boot SPL 2021.10-armbian (Feb 27 2022 - 08:49:47 +0000) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2021.10-armbian (Feb 27 2022 - 08:49:47 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi R1 DRAM: 1 GiB MMC: mmc@1c0f000: 0, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: phy interface7 Error: ethernet@1c30000 address not set. No ethernet found. starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found 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 3964 bytes read in 2 ms (1.9 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 237 bytes read in 2 ms (115.2 KiB/s) 11387894 bytes read in 473 ms (23 MiB/s) 8303240 bytes read in 347 ms (22.8 MiB/s) Found mainline kernel configuration 33828 bytes read in 7 ms (4.6 MiB/s) 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost1.dtbo 502 bytes read in 5 ms (97.7 KiB/s) Applying kernel provided DT overlay sun8i-h3-uart1.dtbo 4185 bytes read in 6 ms (680.7 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 Kernel image @ 0x42000000 [ 0x000000 - 0x7eb288 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11387830 Bytes = 10.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 EHCI failed to shut down host controller. Loading Ramdisk to 49523000, end 49fff3b6 ... OK Loading Device Tree to 494b2000, end 49522fff ... OK Starting kernel ... Everything is timeout and open some kind of console It happen in 5.15.80 and 5.10.60 images U-Boot SPL 2022.07-armbian (Nov 30 2022 - 10:45:40 +0000) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (Nov 30 2022 - 10:45:40 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi NEO DRAM: 1 GiB Core: 60 devices, 17 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: phy interface1 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found 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 4021 bytes read in 2 ms (1.9 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 229 bytes read in 2 ms (111.3 KiB/s) 11798171 bytes read in 489 ms (23 MiB/s) 8393496 bytes read in 349 ms (22.9 MiB/s) Found mainline kernel configuration Failed to load '/boot/dtb/allwinner/sun8i-h3-nanopi-r1.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost1.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 502 bytes read in 6 ms (81.1 KiB/s) Applying kernel provided DT overlay sun8i-h3-uart1.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Error applying DT overlays, restoring original DT Failed to load '/boot/dtb/allwinner/sun8i-h3-nanopi-r1.dtb' Kernel image @ 0x42000000 [ 0x000000 - 0x801318 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11798107 Bytes = 11.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image Device 0: unknown device sun8i_emac_eth_start: Timeout missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-81-6c-b0-b3-e0 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm-sunxi sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default sun8i_emac_eth_start: Timeout Config file not found sun8i_emac_eth_start: Timeout sun8i_emac_eth_start: Timeout => I don't know this info matter or not, but the red led on the board is blinking, same pattern when the image output stuck in "starting kernel" and when SD card is not attached. Also, i even flash the SD with dietpi OS, but it has the same output with stuck in "starting kernel". I wait multiple times but nothing happen in after "starting kernel". Any help appreciated! Thank you!
  6. I try to use last images: Armbian_22.11.1_Nanopi-r1_bullseye_current_5.15.80.img.xz Armbian_22.11.1_Nanopi-r1_bullseye_current_5.15.80_minimal.img.xz But in both instances DHCP client couldn`t start. If I use old image: Armbian_22.08.1_Nanopi-r1_bullseye_current_5.15.63.img.xz All work correctly, nanopi get IP from DHCP server and I can connecting to it. What reason?
  7. 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')
  8. 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
  9. 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:
  10. I'm trying to load Armbian on my NanoPi R1, but it doesn't boot. I've been able to boot it successfully with https://www.friendlyarm.com/ official image, and also various (unsupported) DietPi images. I tried Armbian_21.02.3_Nanopi-r1_focal_current_5.10.21.img.xz using Balena Etcher to copy it to the SDCard on a Macbook laptop. Instead of seeing the uboot startup, the terminal remains completely empty. No idea where to start on debugging this. Please help! Thanks!
  11. 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?
  12. 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
  13. 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.
  14. 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
  15. 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!
  16. 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...

Important Information

Terms of Use - Privacy Policy - Guidelines