cold boot (U-Boot) no LED but 1000 baset-FD connection when booting into ZyxelOS, the amber LED turns on. after power down, the amber LED is off and the green LED turns on this doesn't change when booting into U-Boot (no pinging possible --> 10 baseT-HD connection when booting into debian .. the green LED is still on .. after a while it goes of and the amber LED turns on. now theby pengu - Debian
I know, the same is happening to JohnnyUSA, I have no idea atm Is it driver related? we use the same driver/kernel Is it router/switch related? possible The DIR-825 rev C1 uses an Atheros AR8216/AR8236/AR8316 switchby pengu - Debian
ok let's see .. power off --> 1000 baseT FD at U-Boot --> 1000 baseT-FD I could ping my router and other devices in the network while booting ZyxelOS, the device isn't connectet after a while connectet with 1000 baseT-FD after issuing a halt command and the device is powerd off, --> 10 baseT-HD pinging within U-Boot isn't possible now booting debiaby pengu - Debian
I think I have a possible solution, will post results later. or not ;-( I thought that I have a differend firmware version but it's V4.70(AALH.0) too cold booting ZyxelOS is different here: 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&qby pengu - Debian
I've tried this some time ago since I have this device too but it doesn't come with your and the other mentioned kernel. I couldn't yet find the reason could it be because the initramfs wasn't created after installing the kernel? (so I used the img for initrd creation) but why the other kernel doesn't boot? I've changed some things mentioned here in earlier postsby pengu - Debian
I found this too but it didn't looked important for me because my ethernet connection is working. JohnnyUSA, superelchi: what's your ZyxelOS version? perhaps they changed something so ist's working for meby pengu - Debian
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 ;-(by pengu - Debian
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 arrivingby pengu - Debian
pinging within U-Boot is no problem on NSA310s, let's see what's on NSA320s in a view days I'll seeby pengu - Debian
I'll get a NSA320s in the next fiew days so I can confirm this (or not I hope so)by pengu - Debian
you have a special configuration on your router? my dhcp uses default settingsby pengu - Debian
the only machine that gets an IPv6 adress heare this one from where I type so I think it isn't usedby pengu - Debian
oops .. could be my fault .. aaaah .. please delete or move away /etc/udev/rules.d/70-persistent-net.rulesby pengu - Debian
http://abload.de/img/dscf2995v6un2.jpg and the lan chip: http://abload.de/img/dscf30022psu7.jpgby pengu - Debian
not really, your flashlight makes it impossible to see the lan chipby pengu - Debian
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 :-)by pengu - Debian
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 MACby pengu - Debian
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.by pengu - Debian
I had also troubles with the persistant net rules file so I delete it firstby pengu - Debian
I'm running the latest kernel (4.10) on NSA310s and no problems. please set a correct IP in U-Boot and try to ping your router please try another LAN cable please try to ping your own IP in debian perhaps some component of the board different? perhaps the power supply is faulty? when possible try another power supplyby pengu - Debian
I'm running Gentoo Linux on a BananaPI with cubieboard overlay and OpenWrt Chaos Calmerby pengu - Allwinner A10
@JohnnyUSA could you configure the network manually? https://wiki.debian.org/NetworkConfiguration#Setting_up_an_Ethernet_Interfaceby pengu - Debian
Thanks bodhi, they only publish it in that file and others use wrong specifications, perhaps they think its the same like NSA320 I have reportet this and I hope they will change it.by pengu - Debian
@JohnnyUSA you have to change all tld-1 stuff to tld-2by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > - memory: the NSA320S has 256MB RAM, I thought the > NSA310S also has 256MB? some sites say that the NSA320S has 1,2 GHz and 512 MB RAM correct me if I'm wrong zyxel doesn't say anything about this so I have to use specification published by others.by pengu - Debian
are there any problems earlier in the boot log?by pengu - Debian
No problems with NSA310s and NSA320 here (kernel 3.14, 3,15.3, 3,18.5, 4.0.0)by pengu - Debian
does this look similar to your output? dmesg | grep mv643xx_eth [ 1.825239] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 1.833225] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address .... [ 24.167217] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled is the MAC adress set correctly in your U-Boot eby pengu - Debian