Stephen,

I don't recall if you posted your network test while in u-boot?

Power up, interrupt u-boot countdown and

ping IP_address_of_your_router

Please post this snipet of the serial console log. And describe the network LEDs behavior before/during/after this test.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Ah, I remember now, it is a different Network chip, unlike other Zyxel boxes.

So, there is no network during u-boot booting.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/07/2017 05:20PM by bodhi.

Hi bodhi,
I believe you are correct. u-boot loads a driver for MV88E1318:

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700)
ZyXEL NSA310 1-Bay Power Media Server 


SoC:   Kirkwood 88F6281_A1
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0

whereas the nsa310 has a realtek 8618 family chipset. I tried ping from u-boot but no response:

NSA310> ping 192.168.1.128
Using egiga0 device

ARP Retry count exceeded; starting again
ping failed; host 192.168.1.128 is not alive

Question regarding the front LEDS: To get the LEDS working during boot up, can they be turned on by code in the DTS script? Or do we need something in initrd?

Yeah, it is expected. I knew this was misconfigured, we've discussed this a while ago :) With too many plugs, I don't recall right away the idiosyncracy of each. This cannot be solved, atm.

In the next kernel release, the LED will be green right after the kernel booted. This is set in the DTS.

If you use the right DTB, then all LEDS are available in /sys/class/leds. And controlled in /etc/rc.local. No need to mess with initrd.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 11/09/2017 09:52PM by bodhi.