NSA310S can't connect to network/no network interface

[chiarpavel]

Hi,

I bought this cheap ZyXEL NAS and a 1TB WD HDD about half a year ago to turn into an always-running linux box, to learn and test stuff with, but I've been having some trouble. I've been using an USB-Serial converter to see what's going on.
I tried using both ARMv5 Kirkwood releases and I haven't managed to get a network connection with either of them. I linked to pastebins of the output from the screen command (what I did was boot+check network+dmesg+poweroff) hereand here.

1. ArchLinuxARM-armv5te-latest.tar.gz (the instructions for the NSA320 link to this one)

After booting, I can see eth0 is up, but it doesn't get an IP and seems to have no connection to the router, even though the cable is plugged in.
I tried to get an IP with dhcpcd but I get this:
$this->bbcode_second_pass_code('', '[root@alarm ~]# dhcpcd eth0
DUID 00:01:00:01:1c:1b:83:0a:5c:f4:ab:e3:e4:06
eth0: IAID ab:e3:e4:06
eth0: soliciting a DHCP lease
eth0: soliciting an IPv6 router
eth0: no IPv6 Routers available
timed out
dhcpcd exited')

I also also tried setting a static IP but that didn't work either.

2. ArchLinuxARM-kirkwood-latest.tar.gz (the instructions for NSA325 link to this one)

There are a couple of lines in the boot messages that don't look right:
$this->bbcode_second_pass_code('', '[ 26.298300] rtc-pcf8563 0-0051: chip found, driver version 0.4.3
[ 26.352255] libphy: PHY orion-mdio-mii:00 not found
[ 26.357148] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 26.389346] rtc-pcf8563 0-0051: pcf8563_write_block_data: err=-6 addr=0e, data=03
[ 26.461160] rtc-pcf8563 0-0051: pcf8563_probe: write error
[ 26.509362] rtc-pcf8563: probe of 0-0051 failed with error -5')

After booting, I can't find any network interfaces (other than lo) with ifconfig -a.
My guess is that the driver's not right for this device's network card.

There's also the problem of running poweroff with either releases. The drive spins down, but the devices stays on and I can see that there's a kernel panic right after "Activating power off GPIO pin..."
Does anyone have any recommendations on what I could try next? Or ideas on what could be going wrong?

[WarheadsSE]

Yup, there is something different about this hardware. However, its hard to say what without a lot more detail on the spec, pinmux, etc.

[bodhi]

@WarheadsSE,

Perhaps the NSA310S uses the Marvell Alaska 88e1510 like the NSA320S does?

Edit: google turned up that somebody said: Alaska 88E1318 (don't know if it's accurate).

-bodhi

[chiarpavel]

Can I help find this info?

Here's a picture of the PCB. I can get a better one once I get home.

EDIT: found this (Ctrl+F 88F6702) for the CPU; I'll check to see if the transceiver is visible on the PCB.

$this->bbcode_second_pass_code('', '
KIRKWOOD™ Series Embedded Processors

Part Numbers 88F6702
CPU Base Architecture ARM®v5TE Single Core
I/O Support PCIe (x1), 2 x GbE, 1 x USB2.0, 2 x SATA, 2 x UART, 8 bit Device bus
Frequency 1GHz
Number of Issues Single-Issue
Cache L1: 16KB-I, 16KB-D; L2: 256KB unified
DDR Controller 16-bit DD R2-400
Package Size 24mm x 24mm
Package Type 216-LQFP
Ball Pitch 0.4mm
I-Temp
Evaluation Board DB-88F6702-A1
Software u-boot, Linux, vxWorks and others')

[WarheadsSE]

The concern here is the Ethernet PHY might be different, and obviously the pin mux is slightly different, hence the issue with the powercycle.

[bodhi]

Most definitely, here is the NSA320S DTS looks like for the Alaska 88e1510. And different pin mux from the NSA320.

$this->bbcode_second_pass_code('', '&mdio {
status = "okay";
ethphy0: ethernet-phy@1 {
compatible = "marvell,88e1510";
reg = <1>;
marvell,reg-init = <0x1 0x16 0x0 0x3>,
<0x1 0x10 0x0 0x1017>,
<0x1 0x11 0x0 0x4408>,
<0x1 0x16 0x0 0x0>,
<0x1 0x4 0x0 0x1e1>,
<0x1 0x9 0x0 0x300>,
<0x1 0x10 0x0 0x3860>,
<0x1 0x0 0x0 0x9140>;
};
};
')

[chiarpavel]

Here's a better resolution photo of the PCB. The transceiver is an Alaska 88E1318 according to the markings.
$this->bbcode_second_pass_code('', '88E1318-NNB2
PPK9800 22JW
1323 A0P
TW')

[WarheadsSE]

@bodhi, IDK what we have that DTS in our tree.

@chairpavel what is the installed kernel package?

[chiarpavel]

I'm not sure what you mean by "installed kernel package", but I've been switching back and forth between ArchLinuxARM-armv5te-latest.tar.gz and ArchLinuxARM-kirkwood-latest.tar.gz. Both have a uImage file in /boot

[WarheadsSE]

pacman -Qs linux