Search the Community
Showing results for tags 'nanopineo3'.
-
Last night my Neo3 seems to have died. As I checked it earlier today the heartbeat was gone and the SoC (with glued heat sink on) was hot. After power cycle it refuses to boot again. Wrote the same known to work image I used yesterday to boot it on a fresh sd and got this from serial which was the same as the other sd: DDR version 1.16 20190528 ID:0x805 N In DDR4 333MHz Bus Width=32 Col=10 Bank=4 Bank Group=2 Row=15 CS=1 Die Bus-Width=16 Size=1024MB ddrconfig:14 OUT Boot1 Release Time: May 13 2019 17:34:36, version: 2.50 ChipType = 0x11, 248 mmc2:cmd1,20 emmc reinit mmc2:cmd1,20 emmc reinit mmc2:cmd1,20 SdmmcInit=2 1 mmc0:cmd5,20 That's it. No further output. I assume the board is toast.
-
Title says it all: The Images offers by the site https://www.armbian.com/nanopineo3/ simply doesn't work on a NanoPi Neo3. I don't have a Serial-Connector to find out what's going on during the Boot-Process. I connected a Router on the Lan-Interface, and the Router never get a DHCP-Request from the Neo3. Tried multiple times, SD-Card is fine (tested). If I use an Image from a totally different Project (for Example "DietPi" which also offers a Neo3-Image), it works like a charm. Router gets DHCP-Request, I can connect using SSH (and so on), everything works. My Neo3 is working fine, Power-Supply is also good (it's made for Raspberry Pi and offers 5.1V and 3A...) -
Hi Armbians I have a problem with one of my NanoPi Neo 3 boards and dropped RX packages on eth0. From multiple Neo 3`s I have running, this is the only one having this issue. But its also the only one with 1GB of RAM. All other boards have 2GB of RAM. But this should not matter I think. Output ifconfig: eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet XXXXXXXXXX netmask 255.XXXXXXX broadcast XXXXXXXXXX ether XXXXXXXXXXX txqueuelen 20000 (Ethernet) RX packets 140166777 bytes 110091299296 (102.5 GiB) RX errors 0 dropped 3686 overruns 0 frame 0 TX packets 127249076 bytes 110451144546 (102.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 39 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 20000 (Lokale Schleife) RX packets 96 bytes 7103 (6.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 96 bytes 7103 (6.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Output "ethtool -S eth0": Any secure way to fix this issue?
-
I have a nanopi neo3 rk3328. I would like to modify the i2s(1) at start. I tried to modify /boot/dtb/rockchip/rk3328-nanopi-neo3-rev02.dtb but nothing change. Which is the right dtb file its load at start? Thank you.
-
I got the following error message when I try to install firmware-misc-nonfree_20190114-2_all.deb from the upstream debian repository. ... Get:1 http://deb.debian.org/debian buster/non-free arm64 firmware-misc-nonfree all 20190114-2 [3,338 kB] Fetched 3,338 kB in 1s (4,022 kB/s) Selecting previously unselected package firmware-misc-nonfree. (Reading database ... 77206 files and directories currently installed.) Preparing to unpack .../firmware-misc-nonfree_20190114-2_all.deb ... Unpacking firmware-misc-nonfree (20190114-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-misc-nonfree_20190114-2_all.deb (--unpack): trying to overwrite '/lib/firmware/dvb-fe-xc5000-1.6.114.fw', which is also in package armbian-firmware 21.02.2 d ... So it seems, there is the same firmware package in different packages...but idea, because armbian-firmware 21.02.2 miss the mt7* firmware, which is required to use the wifi expansion module of the nanopi neo3. So, I think the pakcage mantainer should resolve this issue. -
Hi I try ro install and use Armbian on my NanoPi NEO 3. But when I do a first boot, I stuck at Generate Locale step. How can I fix it? Thank you very much. .
-
hi, I am running newest armbian for NEO3. I've noticed that when I issue poweroff command armbian shuts down correctly, but the CPU (with heatsink) remains hot. I left my board for 2 days in poweroff state and it remained 'warm' all the time. Is there something that can be done to put CPU to sleep before shutting down system (or some low power state) ?
-
I'm trying to make boot a NanoPi Neo3 from SSD connected through USB. - I installed armbian Buster 5.8.6 downloaded from armbian.com - Next, I tried with and without apt update - connected an external SSD through the USB port and and a USB 3.0->SATA box - Executed nand-sata-install and selected the option to boot from external SSD - The system prepared the SSD, copied filesystem, modified boot (and I verified that in armbianExt.txt it set the UUID of the external disk) - rebooted ... And nothing I've observed that the system not always detects the external SSD. I must unplug and plug it to be recognized (as /dev/sda btw). Perhaps this is part of the problem. Does anyone have any idea on what happens and how can I solve it?
-
/usr/bin/brcm_patchram_plus/rk3399 hogs 100% CPU until rk3399-bluetooth.service is stopped and disabled. The NanoPi Neo3 does not have bluetooth.
