bohdi,

did the changes you've instructed me to as follows:

# Unknown net device (/devices/platform/mv643xx_eth_port.0/net/eth0) (mv643xx_eth_port)

# Unknown net device (/devices/platform/mv643xx_eth_port.0/net/eth0) (mv643xx_eth_port)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# Unknown net device (/devices/platform/mv643xx_eth_port.0/net/eth0) (mv643xx_eth_port)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:f4:ab:df:07:2b", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

IMPORT{cmdline}="net.ifnames"
ENV{net.ifnames}=="1",                  GOTO="persistent_net_generator_end"

# device name whitelist
KERNEL!="Eth*|ath*|Wlan*[0-9]|msh*|ra*|sta*|ctc*|lcs*|hsi*", \
                                        GOTO="persistent_net_generator_end"

here is the bootlog also:
http://pastebin.com/XtAShb1R

Same problem so far.

I had also troubles with the persistant net rules file so I delete it first

pengu Wrote:
-------------------------------------------------------
> I had also troubles with the persistant net rules
> file so I delete it first


moved 70-persistent-net.rules to some other location then did a halt, same problem.

Cheers!

LE: tried to ping the router,

root@debian:~# ping 192.168.1.1
connect: Network is unreachable

Edited 1 time(s). Last edit at 06/30/2015 03:33PM by JohnnyUSA.

Johnny,

You did not mention what did you do here during boot:

From serial boot log:

fsck.ext4: Unable to resolve 'UUID=55c72762-02f1-4d09-b8c1-5e6da7f17dd4'
fsck exited with status code 8
[FAILfailed (code 8).
[....] File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ...[FAIL failed!
[....] A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ...[warn (warning).
Give root password for maintenance
(or type Control-D to continue):

Also, what is the output of

ifconfig -a

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



Edited 1 time(s). Last edit at 06/30/2015 03:41PM by bodhi.

bodhi Wrote:
-------------------------------------------------------
> Johnny,
>
> You did not mention what did you do here during
> boot:
>
> From serial boot log:
>

> fsck.ext4: Unable to resolve
> 'UUID=55c72762-02f1-4d09-b8c1-5e6da7f17dd4'
> fsck exited with status code 8
> [FAILfailed (code 8).
> [....] File system check failed. A log is being
> saved in /var/log/fsck/checkfs if that location is
> writable. Please repair the file system manually.
> ...[FAIL failed!
> [....] A maintenance shell will now be started.
> CONTROL-D will terminate this shell and resume
> system boot. ...[warn (warning).
> Give root password for maintenance
> (or type Control-D to continue):
>

I did in my previous post, it doesn't find the HDD because i keep him unmounted when i work on serial ;)
But even if i plug the HDD back and that error goes away, i still have the same problems with etherned, tested today.

LE: Output of ifconfig -a:

root@debian:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 5c:f4:ab:df:07:2b
          UP BROADCAST MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:87

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:394 errors:0 dropped:0 overruns:0 frame:0
          TX packets:394 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:47015 (45.9 KiB)  TX bytes:47015 (45.9 KiB)

Edited 2 time(s). Last edit at 06/30/2015 03:45PM by JohnnyUSA.

JohnnyUSA Wrote:
-------------------------------------------------------


> LE: Output of ifconfig -a:
>
>

> root@debian:~# ifconfig -a
> eth0      Link encap:Ethernet  HWaddr
> 5c:f4:ab:df:07:2b
>           UP BROADCAST MULTICAST  MTU:1500 
> 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:1000
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>           Interrupt:87
> 
> 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:394 errors:0 dropped:0
> overruns:0 frame:0
>           TX packets:394 errors:0 dropped:0
> overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:47015 (45.9 KiB)  TX
> bytes:47015 (45.9 KiB)
>

Is this with the static IP address in /etc/network/interfaces?

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

@bodhi,

no, it's with dynamic IP

root@debian:~# cat /etc/network/interfaces
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

hwaddress ether 5c:f4:ab:df:07:2b

but that paste is from when eth failed to get link on halt.



Edited 2 time(s). Last edit at 06/30/2015 03:53PM by JohnnyUSA.

can you set a static ip and try to ping it?
does this work?

The fstab thing:
please comment out not available partitions to prevent boot interruptions.

JohnnyUSA Wrote:
-------------------------------------------------------
> @bodhi,
>
> no, it's with dynamic IP
>
>

> root@debian:~# cat /etc/network/interfaces
> auto lo eth0
> iface lo inet loopback
> iface eth0 inet dhcp
> 
> hwaddress ether 5c:f4:ab:df:07:2b
>

>
> but that paste is from when eth failed to get link
> on halt.

Something about these facts:

- You dont need the hwaddress in this interfaces file.
# hwaddress ether 5c:f4:ab:df:07:2b

Remove it to see if it has played any role in this problem.

- the MAC address is zyxel, I think it could possible confuse your router. Not all router behave the same way so I'm not sure if this is relevant: if you look at the MAC address on the case, I think you'll find that the MAC address is differrent. If it is a Marvell MAC address, then I would try to set it in u-boot.

- Should use static IP only to test to narrow the problem scope.

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

@pengu,

i've set a static IP and tried to ping him:

root@debian:~# ping 192.168.1.173
PING 192.168.1.173 (192.168.1.173) 56(84) bytes of data.
64 bytes from 192.168.1.173: icmp_seq=1 ttl=64 time=0.100 ms
64 bytes from 192.168.1.173: icmp_seq=2 ttl=64 time=0.102 ms
64 bytes from 192.168.1.173: icmp_seq=3 ttl=64 time=0.090 ms
^C
--- 192.168.1.173 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.090/0.097/0.102/0.009 ms

Output of /etc/network/interfaces:

root@debian:~# cat /etc/network/interfaces
auto lo eth0
iface lo inet loopback
#iface eth0 inet dhcp

iface eth0 inet static
        address 192.168.1.173
        netmask 255.255.255.0
        gateway 192.168.1.1

Output of ifconfig -a:

root@debian:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 5c:f4:ab:df:07:2b
          inet addr:192.168.1.173  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:87

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:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4230 (4.1 KiB)  TX bytes:4230 (4.1 KiB)

trying to ping the Gateway:

root@debian:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

-- no response

here is the bootlog:
http://pastebin.com/EusXuWTV

@bohdi,

just did what you wanted while you were writing the post :)



Edited 2 time(s). Last edit at 06/30/2015 04:22PM by JohnnyUSA.

Johnny,

Your link has never been up. When it is up, then this message will be shown in dmesg

[   18.265107] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled

So if in serial console, observe that the link still down since powering up, unplug the ethernet cable, and replug it, see if it would trigger the link to be brought up?

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

@bodhi,

Successful Ethernet link booting:

bootlog with successful ethernet link on 1st boot (cables unplugged and plugged back in):
http://pastebin.com/22PmTNzA

ifconfig -a:

root@debian:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 5c:f4:ab:df:07:2b
          inet addr:192.168.1.173  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fde9:6c4e:493e:0:5ef4:abff:fedf:72b/64 Scope:Global
          inet6 addr: 2a02:2f0d:b1f3:3500:5ef4:abff:fedf:72b/64 Scope:Global
          inet6 addr: 2a02:2f0d:bf90:1e00:5ef4:abff:fedf:72b/64 Scope:Global
          inet6 addr: fe80::5ef4:abff:fedf:72b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:662 errors:0 dropped:0 overruns:0 frame:0
          TX packets:573 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:414119 (404.4 KiB)  TX bytes:59922 (58.5 KiB)
          Interrupt:87

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:160 errors:0 dropped:0 overruns:0 frame:0
          TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:21925 (21.4 KiB)  TX bytes:21925 (21.4 KiB)

/etc/network/interfaces cat:

root@debian:~# cat /etc/network/interfaces
auto lo eth0
iface lo inet loopback
#iface eth0 inet dhcp

iface eth0 inet static
        address 192.168.1.173
        netmask 255.255.255.0
        gateway 192.168.1.1

Failed Ethernet link booting (after halt/shutdown -r now):
http://pastebin.com/qMxiaFun

ifconfig -a:

root@debian:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 5c:f4:ab:df:07:2b
          inet addr:192.168.1.173  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:87

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:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4230 (4.1 KiB)  TX bytes:4230 (4.1 KiB)

Now I did what you've asked me. I've booted again and unplugged the Ethernet cable and plugged back in, here's the bootlog:
http://pastebin.com/zgCa6M3P

Johnny,

Quote

Now I did what you've asked me. I've booted again and unplugged the Ethernet cable and plugged back in, here's the bootlog:
http://pastebin.com/zgCa6M3P

In this case, I meant you should:

- login with ssh
- shutdown -h now
- power up, we know it will fail to get the link up.
- login with serial console
- while in Debian, watch dmesg, unplug ethernet cable, plug it back in. See if it the link is up.

If the link was up in the last step, remove ipv6. And repeat the above steps.

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

bodhi,

tried that, nothing happens it's like that ethernet port is dead.

Every 2.0s: dmesg                                       Wed Jul  1 02:25:33 2015

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.1.0-kirkwood-tld-1 (root@tldDebian) (gcc version
4.9.2 (Debian 4.9.2-10) ) #2 PREEMPT Sun Jun 28 01:12:41 PDT 2015
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397
f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: Zyxel NSA320S
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 65536
[    0.000000] free_area_init_node: node 0, pgdat c0871dac, node_mem_map cfdf900
0
[    0.000000]   DMA zone: 512 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 65536 pages, LIFO batch:15
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pag
es: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootd

that's all output of watch dmesg, nothing changes.

Johnny,

The only thing we have not tried is to set the MAC address to be the same as the NIC. You are using the Zyxel MAC address (we all do because of stock FW). This MAC address was set by Zyxel. However, it is NOT the correct one to use when dealing with the NIC (e.g. WOL works only if Marvell MAC addr is used).

- find the Marvell MAC address on the case sticker.
- interrupt u-boot and set ethaddr to that MAC address. saveenv to save it.
- boot into Debian
- Look at ifconfig -a to confirm this MAC address is being used correctly
- And then shutdown -h now. Power up.

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



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

This has to be done on the NSA310, otherwhose the default mac will be used.
It isn't neccesary on (mine) NSA310s, but it doesn't hurt, give it a try JohnnyUSA

On the bottom you see two stickers, the right one contains the MAC



Edited 1 time(s). Last edit at 07/01/2015 02:50PM by pengu.

pengu Wrote:
-------------------------------------------------------
> This has to be done on the NSA310, otherwhose the
> default mac will be used.
> It isn't neccesary on (mine) NSA310s, but it
> doesn't hurt, give it a try JohnnyUSA

I suspect Johnny's router might have something to do with this.

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

Thanks again for replies guys, now, witch one is the mac add?

Here's the pic: http://s24.postimg.org/5wkvmbmc5/IMG_0157.jpg

I'm a little bit confused :)

looks like we have some differences here.
yould you make a better pic of the lan chip?
The board here is similar to the given photos earlier but I'll try to make a better pic
It's quite dark but I have good lights :-)



Edited 1 time(s). Last edit at 07/01/2015 03:18PM by pengu.

pengu Wrote:
-------------------------------------------------------
> looks like we have some differences here.
> yould you make a better pic of the lan chip?


Hope this one is better: http://s1.postimg.org/felxfiq67/IMG_0160.jpg

not really, your flashlight makes it impossible to see the lan chip

I had no idea witch one is so i made several pictures. Sadly i can't improve the quality more, my Iphone camera sucks :(

1. http://s1.postimg.org/iacsrlybj/IMG_0163.jpg
2. http://s28.postimg.org/votdcidl9/IMG_0164.jpg
3. http://s1.postimg.org/yx40bjmyn/IMG_0165.jpg
4. http://s30.postimg.org/3rofz5m81/IMG_0166.jpg

http://abload.de/img/dscf2995v6un2.jpg

and the lan chip:

http://abload.de/img/dscf30022psu7.jpg



Edited 1 time(s). Last edit at 07/01/2015 03:36PM by pengu.

JohnnyUSA Wrote:
-------------------------------------------------------
> Thanks again for replies guys, now, witch one is
> the mac add?
>
> Here's the pic:
> http://s24.postimg.org/5wkvmbmc5/IMG_0157.jpg
>
> I'm a little bit confused :)

It should be outside on the case bottom or rear.

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

pengu Wrote:
-------------------------------------------------------
> http://abload.de/img/dscf2995v6un2.jpg
>
> and the lan chip:
>
> http://abload.de/img/dscf30022psu7.jpg

@pengu Got a perfect one now: http://s13.postimg.org/ujg6vehon/IMG_0171.jpg

@bohdi, got it now, thanks!

it looks like we have the same lan chip

@bohdi,

changed the MAC with the one on the case. Strange thing is, it was the same as the one i've had already on U-Boot. No change, still same problems.

Now i'm trying with rootfs from @pengu, let's see how it goes.

JohnnyUSA Wrote:
-------------------------------------------------------
> @bohdi,
>
> changed the MAC with the one on the case. Strange
> thing is, it was the same as the one i've had
> already on U-Boot. No change, still same
> problems.
>
> Now i'm trying with rootfs from @pengu, let's see
> how it goes.

OK. Then the NIC is not Marvell.

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

@pengu, booted your rootfs, here's the message:

[....] Reconfiguring 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.

oops .. could be my fault ..

aaaah .. please delete or move away /etc/udev/rules.d/70-persistent-net.rules



Edited 2 time(s). Last edit at 10/19/2015 07:29AM by pengu.