Orange Pi One: No ethernet following reboot


Recommended Posts

Ethernet was working fine for me, up until I rebooted the board. The LEDs on the ethernet port blink briefly during boot, but once booted they are off, and the board does not have an IP address. Via serial console I undid the change I made prior to the fateful reboot (adding 'overlays=uart1' to '/boot/armbianEnv.txt') and rebooted again, but to no avail.

 

Having searched for the issue, I also confirmed that my power supply is sufficient; running 'stress -c 2 -m 2', and measuring across pins 2 (5V) and 6 (GND) of the 40-pin header, I get 5.05V.

 

As I don't have a network connection, I did not run 'sudo armbianmonitor -u', but I gathered the following information:

 

Boot info:

 

U-Boot SPL 2018.11-armbian (Feb 08 2019 - 11:25:07 +0100)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2018.11-armbian (Feb 08 2019 - 11:25:07 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi One
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In:    serial
Out:   serial
Err:   serial
Net:   phy interface0 
eth0: ethernet@1c30000
230454 bytes read in 22 ms (10 MiB/s)
starting USB...
USB0:   USB EHCI 1.00 
USB1:   USB OHCI 1.0  
USB2:   USB EHCI 1.00 
USB3:   USB OHCI 1.0  
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...   
Found U-Boot script /boot/boot.scr
3798 bytes read in 12 ms (308.6 KiB/s)
## Executing script at 43100000
U-boot loaded from SD 
Boot script loaded from mmc
219 bytes read in 10 ms (20.5 KiB/s)
4950770 bytes read in 253 ms (18.7 MiB/s)
7323200 bytes read in 367 ms (19 MiB/s)
Found mainline kernel configuration
29097 bytes read in 45 ms (630.9 KiB/s)
502 bytes read in 96 ms (4.9 KiB/s)
Applying kernel provided DT overlay sun8i-h3-uart1.dtbo
4155 bytes read in 91 ms (43.9 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4950706 Bytes = 4.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
EHCI failed to shut down host controller.
   Loading Ramdisk to 49b47000, end 49fffab2 ... OK
   reserving fdt memory region: addr=43000000 size=6d000
   Loading Device Tree to 49ad7000, end 49b46fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Debian GNU/Linux 9 OrangePi-db-4e ttyS0

OrangePi-db-4e login:

 

The result of 'uname -a':

Linux OrangePi-db-4e 4.19.20-sunxi #5.75 SMP Sat Feb 9 19:02:47 CET 2019 armv7l GNU/Linux

 

The result of 'dmesg | grep eth':

 

[    0.000000] psci: probing for conduit method from DT.
[    1.879134] dwmac-sun8i 1c30000.ethernet: PTP uses main clock
[    1.879173] dwmac-sun8i 1c30000.ethernet: No regulator found
[    1.879482] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000)
[    1.879501] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported
[    1.879506] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported
[    1.879512] dwmac-sun8i 1c30000.ethernet: COE Type 2
[    1.879517] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported
[    1.879523] dwmac-sun8i 1c30000.ethernet: Normal descriptors
[    1.879528] dwmac-sun8i 1c30000.ethernet: Chain mode enabled
[    1.880078] dwmac-sun8i 1c30000.ethernet: Found internal PHY node
[    1.880181] dwmac-sun8i 1c30000.ethernet: Switch mux to internal PHY
[    1.880190] dwmac-sun8i 1c30000.ethernet: Powering internal PHY
[    9.498459] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    9.505005] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found
[    9.505022] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available
[    9.505030] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW
[    9.505503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

 

The result of 'cat /etc/network/interfaces':

 

# Network is managed by Network manager
auto lo
iface lo inet loopback

I edited the above file to add 'auto eth0' and rebooted, but the result was the same; brief flashes of the ethernet LEDs, then nothing.

 

Any hints or tips gratefully received. Thanks.

 

EDIT: I booted with a freshly-flashed SD card, with the same result. So I assume this is physical damage, which is unfortunate.

Edited by chris1h1
Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

Yot eth0 link isnt ready :(
Do you use IPv4 or IPv6?

My Orange Pi One with

Welcome to ARMBIAN 5.77 user-built Debian GNU/Linux 9 (stretch) 5.0.1-sunxi
package bsp-kernel[5.77] u-boot[5.77] dtb[5.77] firmware[5.77] config[5.77]

is showing this in dmesg for eth0:

root@opi-one(192.168.6.114):~# dmesg|grep eth0
[    6.545262] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found
[    6.545278] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available
[    6.545288] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW
[    6.547210] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[    6.547255] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

for dhcpv4 in /etc/network/interfaces you not only need auto eth0, but

auto eth0
allow-hotplug eth0
iface eth0 inet dhcp

for dhcpv6
 

auto eth0
allow-hotplug eth0
iface eth0 inet6 dhcp

 

 

If you delete eth0 in /etc/network/interfaces, then you could try to configure eth0-connection via nmtui
Keep in mind that the (v4) IP-adress does need a/24 at the end like  192.168.6.114/24

BUT only for the IP-address of your board - NOT Gateway, DNS

 

 

Link to post
Share on other sites
Guest
This topic is now closed to further replies.