@psychokiller Download this archive, unzip it to a USB stick. Power off NSA320, connect the stick to it, power on, wait (you can watch via TTL serial if you have it connected). https://mega.nz/file/Sz5jDKKJ#gm1NdQBVt9WhkRO4q0Cf6RPJdS7Fp537jkv0a6sRz-0 Got this from deep inside of one of the many official ZyXEL ftp locations, downloaded some years ago, it is a recovery stick. It will resby vcheche - Debian
eine, Quoteeine > Sir, where're initramfs*gz ? > NVM, sir, you could write somewhere that we need > to generate it ourselvs Thoroughly read the first post of this thread, the info is there, you must have skipped it. (Yes, I know it's a very crowded post and a pain to read at this stage, but...just do it. :-p). Also, be aware that after every update/package instby vcheche - Debian
Hello Muchatet, Most of your questions are indeed answered in the thread. ;-) 1. I personally did not find modifications over a basic install other then the ones mentioned in the changelog (first post). I quote: 3.18: - The init system used in this rootfs is sysvinit (same as in the previous wheezy rootfs). To boot with systemd, see note 4 below. - Installed packages: nano,by vcheche - Debian
vcheche Wrote: ------------------------------------------------------- > Thank you for the uboot image, I will download it > and try to flash it tonight and see if the results > change. flashed back tld-3 and now the box wakes up no matter what command I shut it down with. on powerloss (including while box is soft off) wol stops working. the wol behavoiur is consistent compby vcheche - uBoot
I think I tried to fix this myself in june, but as far as I remember for some reason I did not succeed in compiling the dts (I'm kind of a noob in this). And I did not get the time to test/document and report here. The change that had to be done was 'chip-delay = <35>;' change to 'chip-delay = <40>;', right? : nevermind, I just answered my own question,by vcheche - Debian
Oh, wrong LED lights, I must have missed that in the thread. :-) I mentioned it as I thought it was actually correctly indicating the NIC state (100M or 1G). About a year ago I noticed on a friends NSA325 and NSA310 that if the NIC was in 100M mode (lowpower) or the patch cord was a 4 wire (forcing the 100M mode) then WOL did not work. I don't remember specifics of what mods and firmwarby vcheche - uBoot
Bad block errors are gone and I can now read and write to the uboot env from Linux. I will also try an uboot flash with nandwrite, but I think it will work just fine. Thank you very much, Val.by vcheche - Debian
ok, so after testing it looks like it always fails to wol if I issue a 'halt' or if a power loss occurs. If I shutdown the box with 'shutdown -h now' it will sometimes wake up via wol. with the mac address 28:28:5D:16:xx:xx If I shutdown the box with 'shutdown -h now' AND a powerloss occurs it failed to wol in all my tries. The other mac addresses above doby vcheche - uBoot
The MAC on the box sticker is the same as the one in the original environment, and I kept it the same in my current uboot env. ethaddr=28:28:5D:16:xx:xx I don't have the original full bootlog anymore (must have deleted it by accident at some point). However, in the original printenv, I see some more MAC addresses, don't know what's about them. I'll try now to wol the boby vcheche - uBoot
thank you for your reply. I replaced the factory nand some time ago as it was reporting a bad block at very low offset (in the uboot area), so I swapped it out for an identical chip and recovered the box with kwboot. Can't say if the factory nand would report the same errors as the replacement, as I never had anything but stock fw on it. Also, reswapping them is not such an easy job, theby vcheche - Debian
Hello, Until yesterday my NSA320 was running on uboot.2014.07-tld-3.nsa320.bodhi.tar and had no complaint about it (don't need the netconsole, I modded my box with a USB serial TTL port). I upgraded just for the sake of it to uboot.2014.07-tld-4.nsa320.bodhi.tar and now WOL does not work anymore, at all. At least on tld-3 it worked after system halt (did not work after a full powerby vcheche - uBoot
Hello bodhi. First of all thank you very very much for this great work. My NSA320 now runs your Deb8 image with 4.2.0-kirkwood-tld-1, booted with DTB from a USB drive. Uboot is u-boot-2014.07-tld-4 I have a small(ish) issue, counts more towards comfort then a real issue, but it would be great if it can be fixed. The kernel throws alot of bad eraseblock errors at boot, as you can see fromby vcheche - Debian
Hmm, just looked over your env. You want to remove the arcNumber variable and set mainlineLinux=no. The stock fw hangs due to these. And if still not working go from there. Regards, Vali.by vcheche - Debian
Hello enavarrocu, See bellow original env from my NSA320, which atm is 100% untouched. For now... :-) However, I see your U-Boot has a different version and build date, and also teh boot log is differently formatted. Might be another revision. Oh, well, good luck.... (Please do mind the eth addresses. ;-) ) __ __ _ _ | \/ | __ _ _ ____by vcheche - Debian