NanoPi A64 ethernet driver

[jimsy]

The following Ubuntu images had a working ethernet driver:

Code: Select all

nanopi-a64_friendlycore-xenial_3.10.65_20180207.img

In the following from https://github.com/avafinger, the ethernet did not work:

Code: Select all

nanopi-a64-server-8GB-kernel-4.4.img
nanopi-a64-gsm-support-8GB.img

The following with FreeBSD version 12 worked without the ethernet driver:
https://github.com/freebsd/crochet

It looked like the Realtek driver was slightly different but the information was missing. Should the ethernet driver work in these Ubuntu versions? What are the differenses in this Realtek ethernet chipset and the drivers?

Using Apple keyboard, is there still some power issue? The keyboard is a USB-hub consuming more power. Previous attempts to connect to the upmost USB-connector resulted the board to reboot over and over again. Does this have anything to do with the ethernet driver?

Jimsy

[guidol]

you could try some "unofficial" self-build armbian (like a pine64 fork) where eth0 & wlan0 does work:
https://forum.armbian.com/topic/9308-ex ... anopi-a64/

(you need a small .dtb/.dts-tweak for getting the upper usb-port working)

armbianmonitor -u
System diagnosis information will now be uploaded to http://ix.io/1Uq5

Code: Select all

login as: root
root@192.168.6.116's password:
 _   _ ____  _         _    __   _  _
| \ | |  _ \(_)       / \  / /_ | || |
|  \| | |_) | |_____ / _ \| '_ \| || |_
| |\  |  __/| |_____/ ___ \ (_) |__   _|
|_| \_|_|   |_|    /_/   \_\___/   |_|

Welcome to Debian Buster with Armbian Linux 5.3.0-rc6-sunxi64
package bsp-kernel[5.96] u-boot[5.96] dtb[5.96] firmware[5.96] config[5.96]

System load:   0.67 0.24 0.09   Up time:       1 min
Memory usage:  9 % of 989MB     IP:            192.168.6.116
CPU temp:      40°C
Usage of /:    10% of 15G

[ General system configuration (beta): armbian-config ]

Last login: Fri Sep  6 14:27:04 2019 from 192.168.6.17

root@npi-a64(192.168.6.116):~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.6.116  netmask 255.255.255.0  broadcast 192.168.6.255
        ether 02:ba:e4:72:fa:2b  txqueuelen 1000  (Ethernet)
        RX packets 104  bytes 11397 (11.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 83  bytes 12465 (12.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 26

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 34:c3:d2:13:f2:05  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[jimsy]

Thanks for the answear. Sorry I'm late to post.

The ethernet driver is MII interface and it should work with the existing drivers according to the available information. Maby it is not found. There are some packets sent and received through this "eth0" according to 'ifconfig' but the interface won't connect. How do I pass the flattened device tree to the kernel when it starts? This maby could fix the problem. There is a NanoPI A64 FDT -file (or dts before it is compiled in to dtb). Where do I put this? If in uBoot, what is the easiest way to access the console?

This camera already compiled in image starts with H5 uBoot graphical image and I'm assuming it lacks the correct device-tree -file since the ethernet connector works with the official image. I don't know. The ethernet connector just won't work. Whats the catch?

In FreeBSD this is a kernel option described in 'man fdt' -page. It is compiled in the kernel. The uBoot needs the FDT-file in the boot process. There is a Pine64 (A64) support and EFI is recommended.

Jimsy

p.s.
It would be nice to get the kernel .config -file to not to start experimenting with the new device and the kernel config. Where could I copy one?