Jump to content

Search the Community

Showing results for tags 'nanopineo4'.

  • 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 13 results

  1. Hello, I am working with "Armbian_21.08.1_Nanopineo4_focal_current_5.10.60" on a nanopi Neo4. During the initial boot, the (HDMI) monitor shortly displayed some text (went to fast to read) and then went blank and the monitor turned off. However, output came through the serial debug port (USB2) and I was able to complete the initial setup. Now, I can now connect with SSH, but it would be nice to be able to work directly. How can I redirect the output to the HDMI monitor? Cheers, John
  2. I've found a problem with Armbian on the NanoPi Neo 4 with USB 3.0. I have a RAID6 via four USB 3.0 external hard disks (I know, not optimum but it's been working fine for years off an older ARM box using USB 2.0). While the RAID works fine on the USB 2.0 port (established this was true afterward), when connected to the USB 3.0 port, the USB 3.0 hub I'm using disconnects after only a few seconds, disconnecting all the drives (of course). I initially used an unpowered USB 3.0 hub (I forget the manufacturer; I can check). I figured at first, this might be a power issue (even though the external drives are all self-powered). I found a 10-port powered Cable Matters USB 3.0 hub in my basement, and deployed it today, thinking that would solve my issues But it doesn't. Not a thing changes; the same problem recurs. I moved the hub's USB cable to the USB 2.0 port on the NanoPi and that cures the issue. So my RAID is slow, but it works. (And it's faster than it was on my old box, so it's good enough for now.) I'm not sure if this is a known issue, but thought I would report it.
  3. But only when the connection is initiated by the remote host. iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from nanopcT4, port 51356 [ 5] local nanopiNeo4 port 5201 connected to nanopcT4 port 51358 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 2.34 MBytes 19.7 Mbits/sec 108 1.41 KBytes [ 5] 1.00-2.00 sec 2.05 MBytes 17.2 Mbits/sec 100 2.83 KBytes [ 5] 2.00-3.00 sec 4.68 MBytes 39.3 Mbits/sec 220 5.66 KBytes [ 5] 3.00-4.00 sec 199 KBytes 1.63 Mbits/sec 24 1.41 KBytes [ 5] 4.00-5.00 sec 3.25 MBytes 27.3 Mbits/sec 179 15.6 KBytes [ 5] 5.00-6.00 sec 4.53 MBytes 38.0 Mbits/sec 217 1.41 KBytes [ 5] 6.00-7.00 sec 1.10 MBytes 9.19 Mbits/sec 56 4.24 KBytes [ 5] 7.00-8.00 sec 860 KBytes 7.04 Mbits/sec 38 2.83 KBytes [ 5] 8.00-9.00 sec 5.75 MBytes 48.3 Mbits/sec 291 1.41 KBytes [ 5] 9.00-10.00 sec 4.00 MBytes 33.6 Mbits/sec 209 1.41 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 28.7 MBytes 24.1 Mbits/sec 1442 sender ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- iperf3 -c nanopcT4 -R Connecting to host nanopcT4, port 5201 Reverse mode, remote host nanopcT4 is sending [ 5] local nanopiNeo4 port 55042 connected to nanopcT4 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 108 MBytes 905 Mbits/sec [ 5] 1.00-2.00 sec 112 MBytes 942 Mbits/sec [ 5] 2.00-3.00 sec 112 MBytes 942 Mbits/sec [ 5] 3.00-4.00 sec 112 MBytes 942 Mbits/sec [ 5] 4.00-5.00 sec 112 MBytes 942 Mbits/sec [ 5] 5.00-6.00 sec 112 MBytes 942 Mbits/sec [ 5] 6.00-7.00 sec 112 MBytes 942 Mbits/sec [ 5] 7.00-8.00 sec 112 MBytes 942 Mbits/sec [ 5] 8.00-9.00 sec 112 MBytes 942 Mbits/sec [ 5] 9.00-10.00 sec 112 MBytes 941 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.09 GBytes 940 Mbits/sec 0 sender [ 5] 0.00-10.00 sec 1.09 GBytes 938 Mbits/sec receiver There was also some less significant packet loss and slower performance running Bionic. and asymmetric as well, but in the opposite direction - when neo4 is initiating connection: iperf3 -c nanopcT4 -R Connecting to host nanopcT4, port 5201 Reverse mode, remote host nanopcT4 is sending [ 4] local nanopiNeo4 port 60366 connected to nanopcT4 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 73.5 MBytes 617 Mbits/sec [ 4] 1.00-2.00 sec 78.2 MBytes 656 Mbits/sec [ 4] 2.00-3.00 sec 78.2 MBytes 656 Mbits/sec [ 4] 3.00-4.00 sec 78.4 MBytes 658 Mbits/sec [ 4] 4.00-5.00 sec 77.7 MBytes 652 Mbits/sec [ 4] 5.00-6.00 sec 77.6 MBytes 651 Mbits/sec [ 4] 6.00-7.00 sec 77.8 MBytes 653 Mbits/sec [ 4] 7.00-8.00 sec 77.7 MBytes 652 Mbits/sec [ 4] 8.00-9.00 sec 76.8 MBytes 644 Mbits/sec [ 4] 9.00-10.00 sec 79.1 MBytes 663 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 778 MBytes 653 Mbits/sec 152 sender [ 4] 0.00-10.00 sec 775 MBytes 650 Mbits/sec receiver iperf Done. iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from nanopcT4, port 51336 [ 5] local nanopiNeo4 port 5201 connected to nanopcT4 port 51338 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 5] 0.00-1.00 sec 106 MBytes 889 Mbits/sec 0 404 KBytes [ 5] 1.00-2.00 sec 113 MBytes 946 Mbits/sec 0 404 KBytes [ 5] 2.00-3.00 sec 112 MBytes 936 Mbits/sec 0 404 KBytes [ 5] 3.00-4.00 sec 113 MBytes 947 Mbits/sec 0 445 KBytes [ 5] 4.00-5.00 sec 112 MBytes 943 Mbits/sec 1 328 KBytes [ 5] 5.00-6.00 sec 112 MBytes 940 Mbits/sec 0 369 KBytes [ 5] 6.00-7.00 sec 112 MBytes 939 Mbits/sec 0 392 KBytes [ 5] 7.00-8.00 sec 112 MBytes 942 Mbits/sec 0 428 KBytes [ 5] 8.00-9.00 sec 113 MBytes 945 Mbits/sec 0 428 KBytes [ 5] 9.00-10.00 sec 112 MBytes 941 Mbits/sec 0 443 KBytes [ 5] 10.00-10.02 sec 2.86 MBytes 1.06 Gbits/sec 0 443 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 5] 0.00-10.02 sec 1.09 GBytes 937 Mbits/sec 1 sender [ 5] 0.00-10.02 sec 0.00 Bytes 0.00 bits/sec receiver
  4. I saw the official document of NEO4 that FriendlyDesktop had full hardware acceleration support, including video decoder, opengl, built-in Chromium browser, etc. So does this ARMBIAN NEO4 have the same complete hardware acceleration support?
  5. I saw there was a download of Buster minimal with 5.3 kernel on the nanopi neo4 page. But it just disappeared. So what happened to it? Is it still a nightly build (I see the Buster desktop with 5.3 kernel is supported)? Where can I download it now? Will it be available for downloading again? Thanks in advance.
  6. Hi I am trying to get my neo4 to boot vmlinuz-5.3.0-rc4-rk3399 I am getting lots of; mmc1: card never left busy state mmc1: error -110 whilst initializing SD card Boots fine with legacy kernel, is there something I can do?
  7. I have a FriendlyElec 1080P HDR camera(MACM400). It only works on some FriendlyElec Release with 4.4 kernel. So how could this camera work on Armbian with Mainline kernel?
  8. I used both buster and ubuntu images (Armbian_5.91_Nanopineo4_Debian_buster_default_4.4.179_desktop.img and Armbian_5.90_Nanopineo4_Ubuntu_bionic_default_4.4.179_desktop.img), both have no wifi, only show "device not ready". So I extracted firmware from official friendly desktop image and unzip to /lib/firmware/rkwifi/ and wifi works. I'm a newbie and hope this could be fixed properly soon. For those new to linux like me, download the attachment, extract everything to /lib/firmware/rkwifi/, reboot and wifi should be there. ap6212.zip
  9. I just bought a FriendlyElec NanoPi Neo4 having had loads of experience with Armbian on Allwinner (OrangePi) boards. My preferred method for getting boards "up and running" is simply to connect a serial terminal to the debug port and power on. I tried this with several Armbian Buster images and found that I couldn't log in as root on any of them. Checking the SD card on my laptop, the debug port (ttyFIQ0) was missing from /etc/securetty. Editing /etc/securetty and adding ttyFIQ0 on a new line at the bottom of the file and all is well and I now have Buster up and running on the Neo4 :-) root@nanopineo4:/etc# diff securetty~ securetty 413a414,415 > > ttyFIQ0 root@nanopineo4:/etc# Can I suggest that this be added into the build? Thanks! George
  10. Hi, I have deployed a NanoPi Neo 4 and for the most part, I'm happy with it, but am having a peculiar problem. I am using the manufacturer-supplied serial console cable and USB adapter (via screen /dev/ttyUSBx 115200). Once the machine is properly booted, if I hit enter, I get a serial console as normal. However, I get garbage from u-boot (and presumably from the kernel boot messages). It looks just as if I have a speed mismatch. I have tried many other speeds (1500000, 230400, 57600, 38400, 19200, 9600) and none of these seem to work. What am I doing wrong? Or is the state of the box right now that u-boot sends garbage through the serial port? I'm having a bit a problem with the box (it may be power-related) and being able to see the console would be a huge help. Thanks! Jim
  11. mindee

    NanoPi NEO4

    Not the final version. Update(8/24/2018): It's time to deal with NEO4, this picture is not the final version. NEO4 will have PCIe x2 and eMMC connector too, and a MIPI-CSI. But the dual-layer USB connector will share USB 3.0 & USB 2.0, Type-C take another USB 3.0.
  12. Armbian_5.69_Nanopineo4_Ubuntu_bionic_default_4.4.167_desktop.7z Image seems all ok except for WIFI which is not working.
  13. Nanopi Neo4 armbian5.65 Mac address is no fixed。 Every times setup my Neo4 the MAC address is diffenence。 Who can help me. forgive my pool English. Thanks
×
×
  • Create New...