bodhi, Yeah, i was thinking the same about ZyXEL OS also, somehow they manage to revive the ethernet port on boot. Sadly i have no idea how they do it. Now about your last alternatives, i've tried with 3 different cables in different ports, no luck. You have a point on the router tho and even if we have the same Firmware on it (OpenWRT) the router models differ so, basically i canby JohnnyUSA - Debian
bodhi, first didn't work, second did work, here's the log: http://pastebin.com/7WkNJVJQ but it didn't shutdown the NAS, usb led remained lid and if I've tried to press the power button nothing happens. I needed to unplug the power and plug it back in to make the NAS boot again. still no ethernet at boot.by JohnnyUSA - Debian
bodhi, the problem is still there. here's the shutdown log: http://pastebin.com/24qC4vGe Cheers!by JohnnyUSA - Debian
bodhi, sure thing, take your time, i'm heading to sleep so have a good night also, tomorrow i'll work on troubleshoiting the router and what @pengu instructed me on PM. I'll keep you updated guys, bare with me.by JohnnyUSA - Debian
bodhi Wrote: ------------------------------------------------------- > Johnny, > > Which serial log is your shutdown log? does it > show the network interfaces were deconfigured? bodhi, how do i look for that? I'm tired and my brain is almost on fire :) LE: i think i know what you wanted, here it is: root@debian:~# shutdown -h now Broadcast message fromby JohnnyUSA - Debian
bodhi Wrote: ------------------------------------------------------- > Johnny, > > My guess is your router. I don't think u-boot envs > can affect this. My WAG is the fact that you need > to unplug the power cord, that's causing the NIC > to clear some data. After you did a shutdown -h > now, does the Eternet port still blink green or > yellow? bodhiby JohnnyUSA - Debian
pengu Wrote: ------------------------------------------------------- > you have a special configuration on your router? > my dhcp uses default settings It's default on my side also: 1. http://s27.postimg.org/ibrp0yl0j/image.png 2. http://s7.postimg.org/7l3abdvh7/image.png 3. http://s24.postimg.org/vgmadjmc5/image.pngby JohnnyUSA - Debian
Well, i see the same message as on my rootfs [ 16.494152] NET: Registered protocol family 10 [ 16.674185] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1 Copyright 2004-20by JohnnyUSA - Debian
pengu Wrote: ------------------------------------------------------- > oops .. could be my fauld .. > > aaaah .. please delete or move away > /etc/udev/rules.d/70-persistent-net.rules Did that and rebooted. Same problems as on my rootfs, that makes me wonder... could it be the router only to blame? i keep seeing: Listening on LPF/eth0/5c:f4:ab:df:07:2b Sending onby JohnnyUSA - Debian
@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 meby JohnnyUSA - Debian
@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.by JohnnyUSA - Debian
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!by JohnnyUSA - Debian
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.jpgby JohnnyUSA - Debian
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.jpgby JohnnyUSA - Debian
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 :)by JohnnyUSA - Debian
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.by JohnnyUSA - Debian
@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:feby JohnnyUSA - Debian
@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 tranby JohnnyUSA - Debian
@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.by JohnnyUSA - Debian
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 > File system check failed. A log is being > saved in /varby JohnnyUSA - Debian
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 unreachableby JohnnyUSA - Debian
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}=="0xby JohnnyUSA - Debian
Output of cat /etc/udev/rules.d/70-persistent-net.rules: # This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key. # Unknown net device (/devices/platform/mv643xx_eth_port.0/net/eth0) (mv643by JohnnyUSA - Debian
pengu Wrote: ------------------------------------------------------- > IPv6 is enabled and can be used if needed. Let's try something else please. When you have time, upload somewhere your rootfs and fat16 partitions, i'll try to run your build. This way we will narrow things. Even so.. i don't believe we will succeed, i've tried with fresh install this morning, samby JohnnyUSA - Debian
What do you mean by set up correct IP on U-Boot? I've trie another cable, same result. Also i don't believe the power supply is defective, booting/halting on stock ZyXEL goes without problems. You can't imagine how frustrating it is knowing you have the same NAS and you have no problems because that makes me wonder what's wrong on my side... One thing tho', we boby JohnnyUSA - Debian
@bodhi, tried the "shutdown -h now", also tried with static IP. I've even installed your latest kernel 4.1. No change. same sympthom: If i unplug both ethernet cable and power and plug them back everything works after "halt/shutdown -h now". If i don't unplug both of them i have no ethernet link. @boba, i'm not entirely sure what you want me to do. Can yby JohnnyUSA - Debian
Another day.. :) I've managed to replicate 100% accuracy the way things work on my NAS. So, if i HALT/shutdown -s now when i'm logged into Debian, on PowerON i have no ethernet link, to fix that without booting into ZyXEL OS and then restart, i need to unplug the ethernet cable and power cable from my NAS and then reconnect them. That way, ethernet works again on Debian. Maybe thiby JohnnyUSA - Debian
pengu Wrote: ------------------------------------------------------- > @JohnnyUSA > > could you configure the network manually? > > https://wiki.debian.org/NetworkConfiguration#Setti > ng_up_an_Ethernet_Interface tried that 2hrs ago, no luck, gonna do everything from scratch tomorrow and let you guys know. Have a good night for now. LE: If i unplug the power cordby JohnnyUSA - Debian
You are correct @bodhi, i've regenerated the file, same output, no network. I think i'll give up for today, too tired. But thanks for your assistance guys. http://pastebin.com/0VZKRSbFby JohnnyUSA - Debian
bodhi Wrote: ------------------------------------------------------- > JohnnyUSA Wrote: > -------------------------------------------------- > ----- > > Here is the full bootlog: > > http://pastebin.com/pAyj62Eb > > Johnny, > > You should regenerate the uInitrd. You are running > with older version of the initramfs. Your kernel > is 4.0 Probby JohnnyUSA - Debian