Paul FreemanThanks in advance.I have successfully installed the daily Debian installer (14 July 2014 version, kernel 3.14.1) from http://d-i.debian.org/daily-images/armel/daily/kirkwood/network-console/qnap/ts-41x/ on my QNAP TS-420.At a hardware level, with the ethernet cable connected, the eth0 port link led is on and the activity led is flashing occasionally. So it seems like the hardware knows there is a link connection that is up.
Problem - When the device is rebooted to commence the installer process I cannot connect to it via the network.
I have assembled a serial console cable and after attaching a terminal session to the TS-420, I can see the device is booting OK and the installer is started however the installer cannot find an active network port so it sets the eth0 port settings to its default setting of 192.168.1.100.
When I check the interface status from a shell, it shows NO-CARRIER. Packet dumps, using tcpdump, of eth0 and eth1 from a directly connected computer do not reveal any traffic from either port. Ping requests to port eth0 at 192.168.1.100 are not answered ie. no arp or icmp replies.
Searching through /var/log/syslog and dmesg reveals the kernel is finding the Marvell ethernet chipset and loading the relevant modules, including mv643xx_eth, but it cannot find a port that is up.
I came across a post on this list back in February 2014 (https://lists.debian.org/debian-arm/2014/02/msg00037.html) which bears some similarity but it was on an Openrd-RD board and not the QNAP kirwkood. There appears to have been no follow up on the posting.
I have attached the syslog, dmesg and lsmod output to this email in case it helps.Does anyone have any suggestions as to what might be wrong and how to proceed with debugging this further?