Debian on NSA310S?

@Johnny,

Here it is! give it a shot. Note that the DTB is properly named kirkwood-nsa310s.dtb. Extract this DTB from the archive and put it in /boot/dts, regenerate your uImage with this file.

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

bohdi,

tried the new dtb, same thing. At reboot (once booted from stock) ethernet works but if i shutdown -h now, ethernet died.

[   21.944185] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/5c:f4:ab:df:07:2b
Sending on   LPF/eth0/5c:f4:ab:df:07:2b
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.

Johnny,

Perhaps you should create a brand new rootfs on USB and use the new DTB on that for testing.

If that still did not help. Try the ping test again in a different way:

- At serial console, interrupt u-boot
- Press Power button once
- Then do the ping.

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

@Johnny,

The next test:

- Use the new USB rootfs. And make sure nothing else is attached, all other peripherals, HDD,... all should be removed.
- Cold start
- shutdown -h now

- Boot and login with serial console. In Debian:

echo 26 > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio26/direction
echo 1 > /sys/class/gpio/gpio26/value

See if the ethernet PHY is up and link is established in dmesg.

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



Edited 1 time(s). Last edit at 07/11/2015 04:37AM by bodhi.

bohdi,

1st test - had no ping response
2nd test:

root@debian:~# echo 26 > /sys/class/gpio/export
-bash: echo: write error: Device or resource busy
root@debian:~# echo "out" > /sys/class/gpio/gpio26/direction
-bash: /sys/class/gpio/gpio26/direction: No such file or directory
root@debian:~# echo 1 > /sys/class/gpio/gpio26/value
-bash: /sys/class/gpio/gpio26/value: No such file or directory

have no such files/directories:

root@debian:/sys/class/gpio# ls
.  ..  export  gpiochip0  gpiochip32  unexport

Edited 5 time(s). Last edit at 07/11/2015 07:14AM by JohnnyUSA.

there is a mistake.
I have a NSA310s, JohnnyUSA has a NSA320s
we shoudn't mix that up


Marvell® Alaska® 88E1318 <- this is the one on the NSA310s
I'll check the NSA320s when arriving

pengu Wrote:
-------------------------------------------------------
> there is a mistake.
> I have a NSA310s, JohnnyUSA has a NSA320s
> we shoudn't mix that up
>
>
> Marvell® Alaska® 88E1318 <- this is the one on
> the NSA310s
> I'll check the NSA320s when arriving

I have NSA310s, not 320s :)

sorry so you have the same lan chip as I have
(no problems here)
So if there where troubles ahead with the NSA320s I'll open another topic.
Another NSA310s isn't on the way yet ;-(



Edited 1 time(s). Last edit at 07/11/2015 10:26AM by pengu.

Johnny,

As pengu stated again that it's working in his/her box. I guess I ran out of ideas for you to try :)

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

bodhi Wrote:
-------------------------------------------------------
> Johnny,
>
> As pengu stated again that it's working in his/her
> box. I guess I ran out of ideas for you to try :)


Yeah, it's hard to troubleshoot when you're not here. Thanks anyway, gonna struggle myself and hoping for success :)

Hi,

@JohnnyUSA: you are not alone! ;)
I have the same problem: link is not comming up.

What I have:

- ZyXel NSA-310S
- Root: Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi
- Kernel: linux-4.1.0-kirkwood-tld-1-bodhi
- uImage generated with kirkwood-nsa320s.dtb
- Box is connected to a HP ProCurve 1800 manageable switch

My findings:

Connecting power (not switched on):
GREEN LED on network connector is on/blinking, switch says: Link Up, 10HDX

Switching on, booting Debian:
Debian booting, long delay at DHCPDISCOVER, then booting finishes.
GREEN LED on network connector still on/blinking, switch still says: Link Up, 10HDX
Network not working.

Rebooting ("$ reboot"), booting ZyXel-OS:
During boot GREEN LED goes off, AMBER LED starts blinking, switch says: Link Up, 1000FDX
Network working.

Rebooting ("$ reboot"), booting Debian:
AMBER LED is still on/blinking, switch still says: Link Up, 1000FDX
Network working.

Powering off ("$ poweroff"):
After power off: AMBER LED is still on/blinking, switch now says: Link Up, 100FDX

Cold boot into Debian (by pressing power-switch):
Debian booting, long delay at DHCPDISCOVER, then booting finishes.
AMBER LED is still on/blinking, switch still says: Link Up, 100FDX
Network not working.

Rebooting ("$ reboot"), booting ZyXel-OS:
During boot switch status changes to: Link Up, 1000FDX
Network working.

Some infos from ZyXel OS:

/ # dmesg | grep egiga0
egiga0: started
ADDRCONF(NETDEV_UP): egiga0: link is not ready
egiga0: link up, full duplex, speed 100 Mbps
ADDRCONF(NETDEV_CHANGE): egiga0: link becomes ready
egiga0: link down
egiga0: link up, full duplex, speed 1 Gbps
egiga0: no IPv6 routers present

/ # ethtool -i egiga0
driver: mv_eth
version: KW_LSP_5.1.3_patch30
firmware-version: N/A
bus-info: Mbus

.. and from Debian (network working):

root@debian:~# dmesg | grep eth0
[    1.916695] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 5c:f4:ab:2f:fe:28
[   15.925793] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   18.907311] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   18.917172] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

root@debian:~# ethtool -i eth0
driver: mv643xx_eth
version: 1.4
firmware-version: N/A
bus-info: platform
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

.. and from Debian (network not working, GREEN LED is on/blinking, switch says: Link Up, 10HDX):

root@debian:~# dmesg | grep eth0
[    1.994500] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 5c:f4:ab:2f:fe:28
[   15.614167] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

root@debian:~# ethtool -i eth0
driver: mv643xx_eth
version: 1.4
firmware-version: N/A
bus-info: platform
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

So - looks to me, that the Ethernet chip is not correctly initialized by Debian...

EDIT: had a closer look at the LAN chip - same markings as Pengus image here



Edited 1 time(s). Last edit at 07/14/2015 09:53AM by superelchi.

"Happy" that i'm not alone, at least i can stop trying to figure out what's wrong with my setting.. :)

..was about to go crazy and even buying a new router.

@JohnnyUSA: as we say in Germany: "Geteiltes Leid ist halbes Leid" (a trouble shared is a trouble halved). :)

Made one more test:

Changed speed of switch-port from "Auto detect" to "Fixed 1000FDX".
Result after Debian coldboot: switch says "Link down".
Changed port back to "Auto detect": switch says "Link up, 10HDX". :(
So eth0 comes up with 10 MBits halfduplex after coldboot and stays like this in Debian.

superelchi,

Thanks superelchi! it's a really good test you did :)

Could you try the new 310S DTB that I've posted above for Johnny and run the same test? the 325 and the 310S have the same LAN chip. I've changed the 310S DTS to use the same definition from the 325.

I've attached the 310S DTS in this post also.

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



Edited 1 time(s). Last edit at 07/14/2015 02:22PM by bodhi.

@Bodhi: Nope. Tested with kirkwood-nsa310s.dtb.

Coldboot to Debian:
GREEN LED on/blinking, Link Up, 10HDX - no network.

Reboot to ZyXel OS:
GREEN LED goes off during boot, AMBER LED on/blinking, Link Up, 1000FDX - network working.

Rebbot to Debian:
AMBER LED on/blinking, Link Up, 1000FDX - network working.

Powering off:
After power off: AMBER LED on/blinking, Link Up, 100FDX .

Cold boot to Debian (by pressing power-switch):
AMBER LED on/blinking, Link Up, 100FDX - no network.

So - no change at all. Same as with kirkwood-nsa320s.dtb.

Some more infos:

From zyXel OS (network working)

/ # ethtool egiga0
Settings for egiga0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Link detected: yes

From Debian (network not working)

root@debian:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP AUI BNC MII FIBRE ]
        Supported link modes:   Not reported
        Supported pause frame use: No
        Supports auto-negotiation: No
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: 10Mb/s
        Duplex: Half
        Port: MII
        PHYAD: 1
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Link detected: no

From Debian (network working):

root@debian:~# ethtool eth0
Settings for eth[   41.932913] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
0:
        Supported p[   41.939201] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
orts: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: g
        Link detected: yes

What I see here is that ZyXel reports "Transceiver: internal", Debian reports "Transceiver: external". Don't know if this matters...

And another one: Wake On LAN works always - after coldboot, reboot and poweroff. Does not matter if network is working or not.

superelchi,

Haven't tested the WoL myself yet since i was discouraged about COLD BOOT no link on Debian. It's good news that WoL is working regardless.

Just hope for a miracle and i'd be a super happy user of NSA310S.

@bodhi, you're the one responsible when comes to miracles. I can smell it :))

superelchi,

> And another one: Wake On LAN works always - after
> coldboot, reboot and poweroff. Does not matter if
> network is working or not.

This is a good one! it means no problem with router (it does know where the box is, based on MAC address). Now it should be stock u-boot where it occurs....

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

Here is another version for the DTB. Please extract and recreate uImage with it. Cross fingers and reboot :).

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

I can confirm also on my box. WoL works on "shutdown -h now" from Debian.

LE: Testing the new DTB in a sec.



Edited 2 time(s). Last edit at 07/15/2015 06:02AM by JohnnyUSA.

With the new DTB:

root@debian:~# ifconfig -a
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@debian:~# dmesg | grep eth
[    0.171061] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    1.902662] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4

eth0: bye bye!

With new DTB no eth0. Here is the serial console log:

[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Cannot find device "eth0"
Bind socket to interface: No such device

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug.  These pages explain the proper
process and the information we find helpful for debugging..

exiting.
Failed to bring up eth0.
done.

ifconfig log:

root@debian:~# ifconfig -a
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:101 errors:0 dropped:0 overruns:0 frame:0
          TX packets:101 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:13216 (12.9 KiB)  TX bytes:13216 (12.9 KiB)

dmesg:

root@debian:~# dmesg | grep eth
[    0.171058] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    2.072710] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4

Edited 3 time(s). Last edit at 07/15/2015 06:23AM by JohnnyUSA.

superelchi Wrote:
-------------------------------------------------------
> With the new DTB:
>
>

> root@debian:~# ifconfig -a
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:65536 
> Metric:1
>           RX packets:0 errors:0 dropped:0
> overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0
> overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
> root@debian:~# dmesg | grep eth
> [    0.171061] [Firmware Info]:
> /ocp@f1000000/ethernet-controller@72000/ethernet0-
> port@0: local-mac-address is not set
> [    1.902662] mv643xx_eth: MV-643xx 10/100/1000
> ethernet driver version 1.4
>

>
> eth0: bye bye!

Argh! so the previous version, which was based on the NSA325, was the correct ethernet device (This version was based on the Netgear ReadyNAS).

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

I got an interesting message today when trying to coldboot with previous version of NSA310S DTB, this happened with the NSA320S DTB also.

I wonder is there a way to fix it?

[   93.360886] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/5c:f4:ab:df:07:2b
Sending on   LPF/eth0/5c:f4:ab:df:07:2b
Sending on   Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
Unable to set up timer: unexpected error

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug.  These pages explain the proper
process and the information we find helpful for debugging..

exiting.
Failed to bring up eth0.
done.

Maybe this can help further investigating our problem.



Edited 1 time(s). Last edit at 07/15/2015 07:21AM by JohnnyUSA.

Can not confirm this message.

This is what I get on coldboot (320S DTB)

[   21.764163] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/5c:f4:ab:2f:fe:28
Sending on   LPF/eth0/5c:f4:ab:2f:fe:28
Sending on   Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
Trying recorded lease 192.168.27.148
PING 192.168.27.200 (192.168.27.200) 56(84) bytes of data.

--- 192.168.27.200 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

bound: renewal in 25770 seconds.
done.

@superelchi, could be my date/time modifications to blame for that error of mine.

JohnnyUSA Wrote:
-------------------------------------------------------
> @superelchi, could be my date/time modifications
> to blame for that error of mine.

That's why I've suggested to use static IP only, so to eliminate any other misleading errors!

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

bodhi Wrote:
-------------------------------------------------------
> That's why I've suggested to use static IP only,
> so to eliminate any other misleading errors!

You are absolutely right. One less thing to worry about.
Changed to static IP - same as before. No link.
That's what I expected because I can see in the WebIF of my switch that the link is not correctly initialized (still 10HDX after coldboot).

Would it be of any use if I try to get the Linux GPL sources for the NSA-310S from ZyXel? Or is the ethernet driver/init closed source?

superelchi,

> Would it be of any use if I try to get the Linux
> GPL sources for the NSA-310S from ZyXel? Or is the
> ethernet driver/init closed source?

Yes, absolutely, if you can get it. If I have the GPL source, I could try to get new u-boot working, too.

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

Okay, send an request for the GPL sources to ZyXel

GPL-OSS Software Notice
Thank you  for sending a message to ZyXEL; this is an automated response to acknowledge that we received your email.
Your message will be forwarded to the appropriate department and should be answered within the next 2 business days. 
Due to some email spam blockers, please be sure to check your junk or spam email settings. 
If for some reason you do not receive a response within 2 business days, please feel free to email to support@zyxel.com.tw.
Thank you
ZyXEL Communications Corp.

Lets see what happens...

I had a closer look at the ZyXel OS boot log and found this:

Boot from RAM disk
Mount system disk image ...
yaffs: dev is 32505860 name is "mtdblock4"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.4, "mtdblock4"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
/etc/zyxel/conf exist..
/etc/init.d/rcS: line 406: can't create /sys/block/sda/queue/read_ahead_kb: nonexistent directory
Start rcS2 of ZyXEL style
base address = 40151000
words[0] = phypoke
words[1] = 1
words[2] = 16
words[3] = 3
:GbitPhy[0x00000001:0x00000016] <= 0x00000003
base address = 40151000
words[0] = phypoke
words[1] = 1
words[2] = 10
words[3] = 1017
:GbitPhy[0x00000001:0x00000010] <= 0x00001017
egiga0: link up
base address = , half duplex40151000
words[, speed 10 Mbps0] = phypoke
wo
rds[1] = 1
wordADDRCONF(NETDEV_CHANGE): egiga0: link becomes ready
s[2] = 11
words[3] = 4408
:GbitPhy[0x00000001:0x00000011] <= 0x00004408
Set the phy back to auto-negotiation mode
base address = 40151000
words[0] = phypoke
words[1] = 1
words[2] = 16
words[3] = 0
:GbitPhy[0x00000001:0x00000016] <= 0x00000000
base address = 40151000
words[0] = phypoke
words[1] = 1
words[2] = 4
words[3] = 1e1
:GbitPhy[0x00000001:0x00000004] <= 0x000001e1
base address = 40151000
words[0] = phypoke
words[1] = 1
words[2] = 9
words[3] = 300
:GbitPhy[0x00000001:0x00000009] <= 0x00000300
base address = 40151000
words[0] = phypoke
words[1] = 1
words[2] = 10
words[3] = 3860
:GbitPhy[0x00000001:0egiga0: link down
x00000010] <= 0x00003860
base address = 40151000
words[0] = phypoke
words[1] = 1
words[2] = 0
words[3] = 9140
:GbitPhy[0x00000001:0x00000000] <= 0x00009140
*** Stage 3: Start services on HDD ***
NTFS driver 2.1.29 [Flags: R/O MODULE].
tntfs: module license 'Commercial. For support email ntfs-support@tuxera.com.' taints kernel.
Disabling lock debugging due to kernel taint
Tuxera NTFS driver 3011.12.23 [Flags: R/W MODULE].
PPP generic driver version 2.4.2
PPP MPPE Compression module registered
PPP Deflate Compression module registered
NET: Registered protocol family 24
PPP BSD Compression module registered
modprobe: module fuse not found in modules.dep
egiga0: link up, full duplex, speed 1 Gbps

After this network is working.