nightseas Posted December 13, 2017 Share Posted December 13, 2017 I had a NanoPi NEO2 working well with ARMBIAN 5.34.171121. After apt-get upgrade, ARMBIAN has been changed to ARMBIAN 5.37.171208 with below firmware update: Get:1 http://beta.armbian.com xenial/main arm64 linux-dtb-next-sunxi64 arm64 5.37.171208 [25.0 kB] Get:2 http://beta.armbian.com xenial/main arm64 linux-image-next-sunxi64 arm64 5.37.171208 [14.7 MB] Get:3 http://beta.armbian.com xenial/main arm64 linux-u-boot-nanopineo2-next arm64 5.37.171208 [222 kB] Get:4 http://beta.armbian.com xenial/main arm64 linux-xenial-root-next-nanopineo2 arm64 5.37.171208 [318 kB] Then the Ethernet port is no longer working. Kernel message shows MDIO register failure: root@NEO2-ST0:~# dmesg | grep -i eth [ 0.000000] psci: probing for conduit method from DT. [ 1.661750] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 1.838435] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 1.838566] dwmac-sun8i 1c30000.ethernet: Will use external PHY [ 1.944368] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 1.944381] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 1.944391] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 1.944401] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 1.944412] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 1.944422] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 1.944984] dwmac-sun8i 1c30000.ethernet: Cannot register the MDIO bus [ 1.945003] dwmac-sun8i 1c30000.ethernet: stmmac_dvr_probe: MDIO bus (id: 0) registration failed Any hack do I need on device tree or driver to make it work again? BTW: Is there any way to select specific version of ARMBIAN to build? 5.36 for example. Even if I checkout the specific release tag the build scripts will always switch to master and build the latest version. Thanks & BR, Xiaohai Li Link to comment Share on other sites More sharing options...
guidol Posted December 13, 2017 Share Posted December 13, 2017 1 hour ago, nightseas said: I had a NanoPi NEO2 working well with ARMBIAN 5.34.171121. Then the Ethernet port is no longer working. Any hack do I need on device tree or driver to make it work again? Yes - as I alreday did - you have to rollback to the old version and wait for the next version where hopefully the bug is fixed. After the rollback you should freeze the kernel in armbian-config to avoid the ethernet problem while the fix isnt ready. See my thread for this problem: PS: The NanoPi Neo2 has a H5-CPU and you did ask in the part for H2/H3-CPUs The normal NanoPi Neo has a H3-CPU Link to comment Share on other sites More sharing options...
Igor Posted December 18, 2017 Share Posted December 18, 2017 Should be fixed after this commit: https://github.com/armbian/build/commit/10816a3c68c5041ce8c2d9f49db0696b9fec83a4. A beta repository has also been updated. Link to comment Share on other sites More sharing options...
guidol Posted December 18, 2017 Share Posted December 18, 2017 58 minutes ago, Igor said: Should be fixed after this commit: https://github.com/armbian/build/commit/10816a3c68c5041ce8c2d9f49db0696b9fec83a4. A beta repository has also been updated. Iam using ARMBIAN 5.34.171121 nightly Debian GNU/Linux 9 (stretch) 4.13.14-sunx Linux nanopineo23 4.13.14-sunxi64 #246 SMP Mon Nov 20 01:58:09 CET 2017 aarch64 Is this commit active, that I can unfreeze my kernel in armbian-config and do a apt update & upgrade to get a actual system and the ethernet port would remain useable? Link to comment Share on other sites More sharing options...
Igor Posted December 18, 2017 Share Posted December 18, 2017 32 minutes ago, guidol said: Is this commit active Yes, it is. Link to comment Share on other sites More sharing options...
guidol Posted December 18, 2017 Share Posted December 18, 2017 32 minutes ago, Igor said: Yes, it is. Thanks - did work ARMBIAN 5.37.171218 nightly Debian GNU/Linux 9 (stretch) 4.14.7-sunxi64 Linux nanopineo23 4.14.7-sunxi64 #38 SMP Mon Dec 18 00:49:34 CET 2017 aarch64 GNU/Linux u-boot does show (like on the old working kernel): Net: No ethernet found. but ethernet does work: [ 8.463845] RTL8211E Gigabit Ethernet 0.2:07: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=0.2:07, irq=POLL) [ 12.544959] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 12.545009] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Link to comment Share on other sites More sharing options...
Igor Posted December 18, 2017 Share Posted December 18, 2017 Just now, guidol said: u-boot does show (like on the old working kernel): Net: No ethernet found. That is normal. AFAIK no network support within u-boot for now or not enabled. Good! Link to comment Share on other sites More sharing options...
nightseas Posted December 19, 2017 Author Share Posted December 19, 2017 18 hours ago, Igor said: That is normal. AFAIK no network support within u-boot for now or not enabled. Good! Really great work! Is there any way to select specific version of ARMBIAN to build? 5.36 for example. I could checkout the specific release tag, but the build scripts would always switch to master and build the latest version. Thanks & BR. Link to comment Share on other sites More sharing options...
Igor Posted December 19, 2017 Share Posted December 19, 2017 1 hour ago, nightseas said: Is there any way to select specific version of ARMBIAN to build? 5.36 for example. It's possible but not really recommended. https://github.com/armbian/build/releases Link to comment Share on other sites More sharing options...
minusdelta Posted December 22, 2017 Share Posted December 22, 2017 On 12/18/2017 at 11:44 AM, Igor said: Yes, it is. Not all boards are created equal: OPi+2E Ubnt Xenial Next nightly -> 5.37.171221 = no ethernet; back to 5.34.171121 = OK. Link to comment Share on other sites More sharing options...
guidol Posted December 22, 2017 Share Posted December 22, 2017 45 minutes ago, minusdelta said: Not all boards are created equal: OPi+2E Ubnt Xenial Next nightly -> 5.37.171221 = no ethernet; back to 5.34.171121 = OK. Igor did the same for the Orange Pi Zero Plus (H5) as for the NanoPi Neo2 - maybe he isnt aware of the problem on the Orange Pi Plus 2E? Link to comment Share on other sites More sharing options...
Igor Posted December 22, 2017 Share Posted December 22, 2017 17 minutes ago, guidol said: maybe he isnt aware of the problem on the Orange Pi Plus 2E? fixed. 2 Link to comment Share on other sites More sharing options...
minusdelta Posted December 27, 2017 Share Posted December 27, 2017 Many Thanks! Link to comment Share on other sites More sharing options...
Recommended Posts