Jump to content

Search the Community

Showing results for tags 'nanopiduo'.

  • 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

Categories

  • Official giveaways
  • Community giveaways

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

  1. Image Armbian_23.5.2_Nanopiduo2_bookworm_current_6.1.30.img uname -a Linux nanopiduo2 6.1.30-sunxi #1 SMP Wed May 24 16:32:53 UTC 2023 armv7l GNU/Linux It turns out the dtb has some missing pieces: ethernet@1c30000 { compatible = "allwinner,sun8i-h3-emac"; syscon = <0x1e>; reg = <0x1c30000 0x10000>; interrupts = <0x00 0x52 0x04>; interrupt-names = "macirq"; resets = <0x03 0x0c>; reset-names = "stmmaceth"; clocks = <0x03 0x1b>; clock-names = "stmmaceth"; status = "okay"; phy-handle = <0x69>; // differs from NEO phy-mode = "mii"; allwinner,leds-active-low; after adding phy-handle, phy-mode and allwinner.. wired ethernet works. Of course NetworkManager config /etc/network interfaces must be configured properly. In my case # Network is managed by Network manager auto lo iface lo inet loopback # network interface not managed by Network Manager allow-hotplug eth0 iface eth0 inet static address 192.168.179.222 netmask 255.255.255.0 gateway 192.168.179.1 dns-nameservers 192.168.179.1 Possibly the leds* are not required. Maybe these can be tweaked for other IO's then 🙂 btw. would be nice to thave a separate Nanopi duo2 section here. T.
  2. Just tried Armbian 23.5 Bookworm, cli & minimal. Both report the same in the console. Board works just fine with official img from www.friendlyelec.com Here is the terminal output.
  3. Hello, I am using a NanoPi Duo2 with Armbian 22.11 and Kernel 5,15,80. This device uses an AP6216 wireless interface, which I have noticed are pretty common on sunxi based boards. I ran some bandwidth tests and had pretty poor results: [ ID] Interval Transfer Bandwidth [ 3] 0.0000-1.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 1.0000-2.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 2.0000-3.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 3.0000-4.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 4.0000-5.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 5.0000-6.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 6.0000-7.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 7.0000-8.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 8.0000-9.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 9.0000-10.0000 sec 129 KBytes 1.05 Mbits/sec Not sure if the issue was the driver, hardware, or otherwise I connected a USB wifi dongle and disabled the AP6216. I've tested with the same results again: [ ID] Interval Transfer Bandwidth [ 3] 0.0000-1.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 1.0000-2.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 2.0000-3.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 3.0000-4.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 4.0000-5.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 5.0000-6.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 6.0000-7.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 7.0000-8.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 8.0000-9.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 9.0000-10.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 0.0000-10.0191 sec 1.25 MBytes 1.05 Mbits/sec It's my suspicion that the issue is now elsewhere - but where? I have no idea. Thanks for any ideas.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines