Hi bodhi, i really don't wanna mess this thread up, but before flashing to NAND i wanna ensure, that the following two bad blocks are harmless. Can you confirm? root@debian:/# dmesg | grep -i 'bad' [ 11.985410] Scanning device for bad blocks [ 11.994858] Bad eraseblock 100 at 0x000000c80000 [ 12.004771] Bad eraseblock 200 at 0x000001900000 Thanks, Eike EDIT: Everby Eike - uBoot
Try it out and let us know :) But don't forget to write down the original value. I'm sure it's safe to change it in u-boot.by Eike - Debian
You are right. The NSA has somehow two mac addresses. The one you got with ifconfig and which is listed in several other env vars is actually not the one, you have to use for WoL. It actually worked with the one, which is printed on the case bottom (on the first sight, it looked like some serial number, and I didn't paid attention to it.). But I have not found it in the boot log while bootiby Eike - Debian
bodhi, thanks for your fast reply. The reason I came all this way to try out a new u-boot is actually the WoL misfunction. For me it's a very important feature, since the NAS should not run all night without reason. So scheduled shutdown and automated start via WoL is what I actually want. So flashing U-Boot is not top priority right now. I don't have a problem with resetting the whby Eike - uBoot
Ok the test uboot works! It really seems to be a problem with the serial speed. So I tried out to double it: fw_setenv console 'console=ttyS0,230400 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)' but unfortunately the kwboot seems not to work with higher bitrates. I also tried 460800, 921600 baud. ./kwboot -t -B 230400 /dev/ttyACM0 -b uboot.2013.10-tld-1.nsa32by Eike - uBoot
Hi, 1. What installation log do you mean? Actually I have not installed anything to NAND. I just applied the scripts to modify the bootloader to boot from usb (I followed the instruction from http://zyxel.nas-central.org/wiki/Debian_on_325). The script usb_key_func.sh.2 from you is not touching the MAC address. So it should still be stock! It's stored in the ethaddr env var. And also wheby Eike - uBoot
Hi bodhi, since I still struggle with WOL, I'm very interested in trying out a new u-boot. But this is all I got: ./kwboot -t -B 115200 /dev/ttyACM0 -b uboot.2013.10-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target...\ Sending boot image... 0 % [......................................................................] 2 % [...................................by Eike - uBoot
Ok, I'll give it a try after my huge rsync backup job is done :) My NSA don't have an extra sticker with the MAC, but I'm pretty sure that 00:50:43:00:02:02 is the right one since it's in the uboot variable ethaddr, arp -a is detecting it and ifconfig also shows it. And that's the Mac I tried out the whole time. I'm somehow confused why these 'easy' taby Eike - Debian
That's exactly the MAC I used. Where do you see that I used another?by Eike - Debian
bodhi Wrote: ------------------------------------------------------- > I wonder if it could be > something to do with your router. If it's a static > IP the MAC address should be correct all the time. > And do you have bridge somewhere in your network? No bridge. My network: NSA(eth0) --> Fritzbox (GBit Port, but also tried 100M) RPi (eth0) --> Fritzbox (100M) Dby Eike - Debian
Hi bodhi, it's not working with static IP either. This is what I set up: cat /etc/network/interfaces auto lo eth0 iface lo inet loopback #iface eth0 inet dhcp iface eth0 inet static address 192.168.178.35 netmask 255.255.255.0 gateway 192.168.178.1 pre-down ethtool -s eth0 wol g Can you tell me what you tried out exactly? Did you modify the /etc/init.d/halt -> netdownby Eike - Debian