I did a apt update & upgrade on my NanoPi Neo2 NAS and it updated to nightly 5.37

but at the beginning of the boot-log it tells me:

Net:   No ethernet found.

 

I didnt get an eth0 interface from the mainboard ethernet-port (only lo)
 

[    1.633544] dwmac-sun8i 1c30000.ethernet: PTP uses main clock
[    1.798411] dwmac-sun8i 1c30000.ethernet: PTP uses main clock
[    1.798556] dwmac-sun8i 1c30000.ethernet: Will use external PHY
[    1.904820] dwmac-sun8i 1c30000.ethernet: Chain mode enabled
[    1.904832] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported
[    1.904842] dwmac-sun8i 1c30000.ethernet: Normal descriptors
[    1.904853] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported
[    1.904863] dwmac-sun8i 1c30000.ethernet: COE Type 2
[    1.904873] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported
[    1.905433] dwmac-sun8i 1c30000.ethernet: Cannot register the MDIO bus
[    1.905452] dwmac-sun8i 1c30000.ethernet: stmmac_dvr_probe: MDIO bus (id: 0) registration failed

 

Now I can access the Neo2 only via TTL-serial-debug console

 

Lucky me - I have a USB-Ethernet Adapter which I can use:

[  787.473350] MOSCHIP usb-ethernet driver 3-1:1.0 eth0: register 'MOSCHIP usb-ethernet driver' at usb-1c1b000.usb-1, MOSCHIP 7830/7832/7730 usb-NET adapter, 00:12:34:55:56:2b
[  787.473508] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
[  787.503850] MOSCHIP usb-ethernet driver 3-1:1.0 enx00123455562b: renamed from eth0

so here the armbianmontor -u :

root@nanopineo23:~# armbianmonitor -u
System diagnosis information will now be uploaded to http://sprunge.us/JQdE

 

PS: The NanoPi NAS with only a "normal" Neo has found his Network after update to 5.37

root@nanopi-neo:~# dmesg|grep -i 1c30000
[    4.313641] dwmac-sun8i 1c30000.ethernet: PTP uses main clock
[    4.313714] dwmac-sun8i 1c30000.ethernet: No regulator found
[    4.313819] dwmac-sun8i 1c30000.ethernet: Will use internal PHY
[    4.313937] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000)
[    4.314111] dwmac-sun8i 1c30000.ethernet: Chain mode enabled
[    4.314123] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported
[    4.314134] dwmac-sun8i 1c30000.ethernet: Normal descriptors
[    4.314145] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported
[    4.314156] dwmac-sun8i 1c30000.ethernet: COE Type 2
[    4.314167] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported
[   19.124960] dwmac-sun8i 1c30000.ethernet eth0: device MAC address 16:1c:0c:e4:e5:76
[   19.128797] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available
[   19.128816] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW
[   22.249109] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx

 

ARMBIAN 5.37.171208 nightly Debian GNU/Linux 9 (stretch)

Linux nanopineo23 4.14.4-sunxi64 #11 SMP Thu Dec 7 11:55:12 CET 2017 aarch64 GNU/Linux

Neo2_Bootlog_537.txt

I guess enabling nightlies was perhaps too fast (I need to test repository management) but at least a problems were found. Since you have a temporal network, roll back to previous nightly version ... and don't update kernel until this is fixed.

7 minutes ago, Igor said:

I guess enabling nightlies was perhaps too fast (I need to test repository management) but at least a problems were found. Since you have a temporal network, roll back to previous nightly version ... and don't update kernel until this is fixed.

How to roll back? Re-Install?
The kernel can be freezed in armbian-config - right?

20 minutes ago, guidol said:

How to roll back? Re-Install?

 

Install packages from here: https://beta.armbian.com/pool/main/l/linux-4.13.14-sunxi64/ you can leave headers out if you don't need them. Or via apt-get.

 

Hmm. We could implement this to armbian-config, to make rollback simpler. Yes, freeze in armbian-config or manually.

2 hours ago, Igor said:

 

Install packages from here: https://beta.armbian.com/pool/main/l/linux-4.13.14-sunxi64/ you can leave headers out if you don't need them.

@Igor

Thanks for the information!
I did:
 

Rollback:
mkdir /home/guido/rollback
cd /home/guido/rollback
wget https://beta.armbian.com/pool/main/l/linux-4.13.14-sunxi64/linux-dtb-next-sunxi64_5.34.171121_arm64.deb
wget https://beta.armbian.com/pool/main/l/linux-4.13.14-sunxi64/linux-headers-next-sunxi64_5.34.171121_arm64.deb
wget https://beta.armbian.com/pool/main/l/linux-4.13.14-sunxi64/linux-image-next-sunxi64_5.34.171121_arm64.deb
dpkg --force-all -i ./linux-dtb-next-sunxi64_5.34.171121_arm64.deb
dpkg --force-all -i ./linux-headers-next-sunxi64_5.34.171121_arm64.deb
dpkg --force-all -i ./linux-image-next-sunxi64_5.34.171121_arm64.deb

reboot

armbian-config ==> system ==> freeze

after that removed the usb-ethernet (because it was configured as the same IP) and rebootet again.

(If I didnt need the headers - which I installed via dpkg.... could I use the armbian-config funtion to deinstall the headers?)

Now my Neo2 NAS is accessable via SSH again - but I wonder after downgrading I do get the newer welcome Message out of  /etc/armbian-release - which hasnt been downgraded?:

Welcome to ARMBIAN 5.37.171208 nightly Debian GNU/Linux 9 (stretch) 4.13.14-sunxi64

I also did see that with the working 5.34 the u-boot doenst show the network:
 

U-Boot 2017.11-armbian (Dec 07 2017 - 12:01:53 +0100) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO 2
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.

As attachment you could see that the u-boot of my Orange Pi R1 could see the network card

 

[EDIT because of the Linux-Headers]

I did try to use armbian-config for removing/uninstallting the headers - and armbian-config offered it also to uninstall/remove it - but after I selected it it does try to INSTALL something. Then goes one screen back and did now again to remove/uninstall it
 

But with dpkg I also could complete install the headers:
 

root@nanopineo23:/home/guido/rollback# dpkg --purge --force-all linux-headers-next-sunxi64
(Reading database ... 65039 files and directories currently installed.)
Removing linux-headers-next-sunxi64 (5.34.171121) ...
dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/selinux/mdp' not empty so not removed
dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/selinux/genheaders' not empty so not removed
dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/mod' not empty so not removed
dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/kconfig' not empty so not removed
dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/dtc' not empty so not removed
dpkg: warning: while removing linux-headers-next-sunxi64, directory '/usr/src/linux-headers-4.13.14-sunxi64/scripts/basic' not empty so not removed

 

 

On 9-12-2017 at 7:37 PM, Igor said:

 

Install packages from here: https://beta.armbian.com/pool/main/l/linux-4.13.14-sunxi64/ you can leave headers out if you don't need them. Or via apt-get.

 

Hmm. We could implement this to armbian-config, to make rollback simpler. Yes, freeze in armbian-config or manually.

Hi Igor,

How does this work? How can we make sure the build process uses these packages?

 

PS: thanks for all your work!

 

EDIT: I've reset the Armbian repo to commit 5f4c4c77b28b4d15fd0165809ccfaed7af5c73e5 (right before the update to 4.14) and created a file named  `.ignore_changes`. After that the network worked again even though it's not recognised on boot.

Looks like nanopi neo plus2 is almost there, great work! I also stumbled on this Ethernet issue with the next kernel, in the  Armbian_5.37_Nanopineoplus2_Debian_stretch_next_4.14.5.img I build yesterday with the Armbian build script. I need custom kernel to get some more Industrial I/O features like standalone triggers enabled, so the older 4.13.14 packages are unfortunately not enough. I guess I have to use wifi until there is a fix. If there is anything I can do to help (e.g. testing an initial fix), please let me know.

 

I also noticed some other minor issues in the image, otherwise it seems to be working fine:

- kernel headers are not installed in the image (but may not be needed by all)

- the /boot/overlay-user folder does not exist

- had to run ldconfig a few times to get my libs in /usr/local/lib working